* 14-01:53:29 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 14-01:53:33 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 14-01:53:33 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:56:02 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 14-01:56:02 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 14-01:56:04 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 14-01:56:04 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 14-01:56:04 (2925) [INFO] Checking if your system is up to date:  * 14-01:56:04 (3361) [INFO] Running: /usr/bin/yum clean all * 14-01:56:04 (3362) [INFO]  * 14-01:56:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:56:04 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 14-01:56:04 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-01:56:04 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 14-01:56:04 (3372) [INFO] Cleaning up list of fastest mirrors * 14-01:56:04 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 14-01:56:04 (3382) [INFO]  * 14-01:56:04 (3361) [INFO] Running: /usr/bin/yum check-update * 14-01:56:04 (3362) [INFO]  * 14-01:56:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:56:06 (3372) [INFO] Determining fastest mirrors * 14-01:57:34 (3372) [INFO] * EA4: 208.74.123.62 * 14-01:57:34 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 14-01:57:34 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 14-01:57:34 (3372) [INFO] * base: or-mirror.iwebfusion.net * 14-01:57:34 (3372) [INFO] * epel: ridgewireless.mm.fcix.net * 14-01:57:34 (3372) [INFO] * extras: mirrors.xmission.com * 14-01:57:34 (3372) [INFO] * updates: mirror.fcix.net * 14-02:00:07 (3372) [INFO]  * 14-02:00:07 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 14-02:00:07 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-02:00:07 (3382) [INFO]  * 14-02:00:07 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-02:00:07 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-02:00:07 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 14-02:00:07 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-02:00:07 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-02:00:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-14_02:00:10_modified_for_AlmaLinux_8.json * 14-02:00: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 14-02:08:39 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-01:43:03 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 15-01:43:08 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 15-01:43: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  * 15-01:45:36 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 15-01:45:36 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 15-01:45:37 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 15-01:45:37 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 15-01:45:37 (2925) [INFO] Checking if your system is up to date:  * 15-01:45:37 (3361) [INFO] Running: /usr/bin/yum clean all * 15-01:45:37 (3362) [INFO]  * 15-01:45:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:45:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 15-01:45:38 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-01:45:38 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 15-01:45:38 (3372) [INFO] Cleaning up list of fastest mirrors * 15-01:45:38 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 15-01:45:38 (3382) [INFO]  * 15-01:45:38 (3361) [INFO] Running: /usr/bin/yum check-update * 15-01:45:38 (3362) [INFO]  * 15-01:45:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:45:39 (3372) [INFO] Determining fastest mirrors * 15-01:47:09 (3372) [INFO] * EA4: 184.94.196.94 * 15-01:47:09 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 15-01:47:09 (3372) [INFO] * cpanel-plugins: 184.94.196.94 * 15-01:47:09 (3372) [INFO] * base: repos.forethought.net * 15-01:47:09 (3372) [INFO] * epel: mirrors.xmission.com * 15-01:47:09 (3372) [INFO] * extras: mirror.chpc.utah.edu * 15-01:47:09 (3372) [INFO] * updates: mirrors.vcea.wsu.edu * 15-01:49:12 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/bb4a83fdaeb7918779f18f86c07057c5809314984605bd5cfcfb1e93753a6b52-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 15-01:49:12 (3372) [INFO] Trying other mirror. * 15-01:49:12 (3372) [INFO] To address this issue please refer to the below wiki article  * 15-01:49:12 (3372) [INFO]  * 15-01:49:12 (3372) [INFO] https://wiki.centos.org/yum-errors * 15-01:49:12 (3372) [INFO]  * 15-01:49:12 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 15-01:49:12 (3372) [INFO]  * 15-01:49:56 (3372) [INFO]  * 15-01:49:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 15-01:49:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-01:49:56 (3382) [INFO]  * 15-01:49:56 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-01:49:56 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-01:49:56 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 15-01:49:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-01:49:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-01:49:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-15_01:49:58_modified_for_AlmaLinux_8.json * 15-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 15-01:58:28 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-01:41:58 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 16-01:42:02 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 16-01:42: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-01:44:31 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 16-01:44:31 (3077) [ERROR] https://mirror.fcix.net/epel/7/x86_64/repodata/2f00aa64e42e0380fe9996b08951b95b42ec6087a8d0b3705ef347a1d66cc293-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/.  * 16-01:44:31 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 16-01:44:31 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 16-01:44:31 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 16-01:44:32 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 16-01:44:32 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 16-01:44:32 (2925) [INFO] Checking if your system is up to date:  * 16-01:44:32 (3361) [INFO] Running: /usr/bin/yum clean all * 16-01:44:32 (3362) [INFO]  * 16-01:44:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:44:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 16-01:44:33 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-01:44:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 16-01:44:33 (3372) [INFO] Cleaning up list of fastest mirrors * 16-01:44:33 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 16-01:44:33 (3382) [INFO]  * 16-01:44:33 (3361) [INFO] Running: /usr/bin/yum check-update * 16-01:44:33 (3362) [INFO]  * 16-01:44:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:44:35 (3372) [INFO] Determining fastest mirrors * 16-01:46:04 (3372) [INFO] * EA4: 184.94.196.94 * 16-01:46:04 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 16-01:46:04 (3372) [INFO] * cpanel-plugins: 184.94.196.94 * 16-01:46:04 (3372) [INFO] * base: mirrors.xmission.com * 16-01:46:04 (3372) [INFO] * epel: mirrors.xmission.com * 16-01:46:04 (3372) [INFO] * extras: mirror.sfo12.us.leaseweb.net * 16-01:46:04 (3372) [INFO] * updates: centos-distro.1gservers.com * 16-01:47:38 (3372) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/83c2a9de81aebca9a6437534884b08b71804fd8026d9a74d12370ff62048a8d5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 16-01:47:38 (3372) [INFO] Trying other mirror. * 16-01:47:38 (3372) [INFO] To address this issue please refer to the below wiki article  * 16-01:47:38 (3372) [INFO]  * 16-01:47:38 (3372) [INFO] https://wiki.centos.org/yum-errors * 16-01:47:38 (3372) [INFO]  * 16-01:47:38 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 16-01:47:38 (3372) [INFO]  * 16-01:48:23 (3372) [INFO]  * 16-01:48:23 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 16-01:48:23 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-01:48:23 (3382) [INFO]  * 16-01:48:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-01:48:23 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-01:48:23 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 16-01:48:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-01:48:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-01:48:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-16_01:48:25_modified_for_AlmaLinux_8.json * 16-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 16-01:56:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-01:43:57 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 17-01:44:04 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 17-01:44: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  * 17-01:46:20 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 17-01:46:20 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 17-01:46:21 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 17-01:46:21 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 17-01:46:21 (2925) [INFO] Checking if your system is up to date:  * 17-01:46:21 (3361) [INFO] Running: /usr/bin/yum clean all * 17-01:46:21 (3362) [INFO]  * 17-01:46:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:46:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 17-01:46:21 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-01:46:21 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 17-01:46:22 (3372) [INFO] Cleaning up list of fastest mirrors * 17-01:46:22 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 17-01:46:22 (3382) [INFO]  * 17-01:46:22 (3361) [INFO] Running: /usr/bin/yum check-update * 17-01:46:22 (3362) [INFO]  * 17-01:46:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:46:23 (3372) [INFO] Determining fastest mirrors * 17-01:47:52 (3372) [INFO] * EA4: 184.94.196.92 * 17-01:47:52 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 17-01:47:52 (3372) [INFO] * cpanel-plugins: 184.94.196.92 * 17-01:47:52 (3372) [INFO] * base: mirrors.vcea.wsu.edu * 17-01:47:52 (3372) [INFO] * epel: mirrors.xmission.com * 17-01:47:52 (3372) [INFO] * extras: mirror.arizona.edu * 17-01:47:52 (3372) [INFO] * updates: mirrors.xtom.com * 17-01:49:25 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/e996bf2afa6b5cada4ec32825f69ec5417cc2546b397edf5fa17cee3ccd32afc-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 17-01:49:25 (3372) [INFO] Trying other mirror. * 17-01:49:25 (3372) [INFO] To address this issue please refer to the below wiki article  * 17-01:49:25 (3372) [INFO]  * 17-01:49:25 (3372) [INFO] https://wiki.centos.org/yum-errors * 17-01:49:25 (3372) [INFO]  * 17-01:49:25 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 17-01:49:25 (3372) [INFO]  * 17-01:50:15 (3372) [INFO]  * 17-01:50:15 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 17-01:50:15 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-01:50:15 (3382) [INFO]  * 17-01:50:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-01:50:15 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-01:50:15 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 17-01:50:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-01:50:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-01:50:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-17_01:50:18_modified_for_AlmaLinux_8.json * 17-01:50: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 17-01:58:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-01:41:53 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 18-01:41:59 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 18-01:41: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  * 18-01:43:57 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 18-01:43:57 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 18-01:43:58 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 18-01:43:58 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 18-01:43:58 (2925) [INFO] Checking if your system is up to date:  * 18-01:43:58 (3361) [INFO] Running: /usr/bin/yum clean all * 18-01:43:58 (3362) [INFO]  * 18-01:43:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:43:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 18-01:43:58 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-01:43:58 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 18-01:43:59 (3372) [INFO] Cleaning up list of fastest mirrors * 18-01:43:59 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 18-01:43:59 (3382) [INFO]  * 18-01:43:59 (3361) [INFO] Running: /usr/bin/yum check-update * 18-01:43:59 (3362) [INFO]  * 18-01:43:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:44:00 (3372) [INFO] Determining fastest mirrors * 18-01:45:28 (3372) [INFO] * EA4: 184.94.196.93 * 18-01:45:28 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 18-01:45:28 (3372) [INFO] * cpanel-plugins: 184.94.196.93 * 18-01:45:28 (3372) [INFO] * base: mirrors.xmission.com * 18-01:45:28 (3372) [INFO] * epel: mirrors.xmission.com * 18-01:45:28 (3372) [INFO] * extras: repos.forethought.net * 18-01:45:28 (3372) [INFO] * updates: ridgewireless.mm.fcix.net * 18-01:47:41 (3372) [INFO]  * 18-01:47:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 18-01:47:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-01:47:41 (3382) [INFO]  * 18-01:47:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-01:47:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-01:47:41 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 18-01:47:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-01:47:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-01:47:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-18_01:47:44_modified_for_AlmaLinux_8.json * 18-01:47: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 18-01:56:13 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-01:41:46 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 19-01:41:51 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 19-01:41:51 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 19-01:44:22 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 19-01:44:22 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30362 milliseconds')  * 19-01:44:22 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 19-01:44:22 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 19-01:44:22 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 19-01:44:22 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 19-01:44:22 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 19-01:44:22 (2925) [INFO] Checking if your system is up to date:  * 19-01:44:22 (3361) [INFO] Running: /usr/bin/yum clean all * 19-01:44:22 (3362) [INFO]  * 19-01:44:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:44:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 19-01:44:23 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-01:44:23 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 19-01:44:23 (3372) [INFO] Cleaning up list of fastest mirrors * 19-01:44:23 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 19-01:44:23 (3382) [INFO]  * 19-01:44:23 (3361) [INFO] Running: /usr/bin/yum check-update * 19-01:44:23 (3362) [INFO]  * 19-01:44:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:44:25 (3372) [INFO] Determining fastest mirrors * 19-01:45:54 (3372) [INFO] * EA4: 208.74.123.61 * 19-01:45:54 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 19-01:45:54 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 19-01:45:54 (3372) [INFO] * base: repos.forethought.net * 19-01:45:54 (3372) [INFO] * epel: mirrors.xmission.com * 19-01:45:54 (3372) [INFO] * extras: mirror.arizona.edu * 19-01:45:54 (3372) [INFO] * updates: mirrors.xtom.com * 19-01:48:25 (3372) [INFO]  * 19-01:48:25 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 19-01:48:25 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-01:48:25 (3382) [INFO]  * 19-01:48:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-01:48:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-01:48:26 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 19-01:48:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-01:48:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-01:48:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-19_01:48:28_modified_for_AlmaLinux_8.json * 19-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 19-01:56:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-01:40:39 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 20-01:40:43 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 20-01:40: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  * 20-01:42:41 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 20-01:42:41 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 20-01:42:41 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 20-01:42:41 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 20-01:42:41 (2925) [INFO] Checking if your system is up to date:  * 20-01:42:41 (3361) [INFO] Running: /usr/bin/yum clean all * 20-01:42:41 (3362) [INFO]  * 20-01:42:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:42:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 20-01:42:42 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-01:42:42 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 20-01:42:42 (3372) [INFO] Cleaning up list of fastest mirrors * 20-01:42:42 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 20-01:42:42 (3382) [INFO]  * 20-01:42:42 (3361) [INFO] Running: /usr/bin/yum check-update * 20-01:42:42 (3362) [INFO]  * 20-01:42:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:42:44 (3372) [INFO] Determining fastest mirrors * 20-01:44:12 (3372) [INFO] * EA4: 208.74.123.62 * 20-01:44:12 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 20-01:44:12 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 20-01:44:12 (3372) [INFO] * base: mirror.hostduplex.com * 20-01:44:12 (3372) [INFO] * epel: mirrors.xmission.com * 20-01:44:12 (3372) [INFO] * extras: mirrors.xmission.com * 20-01:44:12 (3372) [INFO] * updates: mirrors.xtom.com * 20-01:46:28 (3372) [INFO]  * 20-01:46:28 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 20-01:46:28 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-01:46:28 (3382) [INFO]  * 20-01:46:28 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-01:46:28 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-01:46:28 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 20-01:46:28 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-01:46:28 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-01:46:31 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-20_01:46:31_modified_for_AlmaLinux_8.json * 20-01:46: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 20-01:55:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-01:57:16 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 21-01:57:22 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 21-01:57: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  * 21-01:59:36 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 21-01:59:36 (3077) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/2453eb0346f89d1089176c1f286d679cb6d0dde6c1d11c873c74cf3a15fc9b42-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/.  * 21-01:59:36 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 21-01:59:36 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 21-01:59:36 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 21-01:59:37 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 21-01:59:37 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 21-01:59:37 (2925) [INFO] Checking if your system is up to date:  * 21-01:59:37 (3361) [INFO] Running: /usr/bin/yum clean all * 21-01:59:37 (3362) [INFO]  * 21-01:59:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:59:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 21-01:59:38 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-01:59:38 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 21-01:59:38 (3372) [INFO] Cleaning up list of fastest mirrors * 21-01:59:38 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 21-01:59:38 (3382) [INFO]  * 21-01:59:38 (3361) [INFO] Running: /usr/bin/yum check-update * 21-01:59:38 (3362) [INFO]  * 21-01:59:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:59:39 (3372) [INFO] Determining fastest mirrors * 21-02:01:11 (3372) [INFO] * EA4: 208.74.123.61 * 21-02:01:11 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 21-02:01:11 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 21-02:01:11 (3372) [INFO] * base: mirror.hostduplex.com * 21-02:01:11 (3372) [INFO] * epel: mirrors.xmission.com * 21-02:01:11 (3372) [INFO] * extras: mirror.chpc.utah.edu * 21-02:01:11 (3372) [INFO] * updates: centos.mirror.ndchost.com * 21-02:03:45 (3372) [INFO]  * 21-02:03:45 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 21-02:03:45 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-02:03:46 (3382) [INFO]  * 21-02:03:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-02:03:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-02:03:46 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 21-02:03:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-02:03:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-02:03:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-21_02:03:49_modified_for_AlmaLinux_8.json * 21-02:03: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 21-02:12:18 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-01:42:42 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 22-01:42:45 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 22-01:42: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-01:44:43 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 22-01:44:43 (3077) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/e1e32936787a431e94629e04cc4761cee7e207905aad0f5808bc8bec6fe8c936-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/.  * 22-01:44:43 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 22-01:44:43 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 22-01:44:43 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 22-01:44:43 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 22-01:44:43 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 22-01:44:43 (2925) [INFO] Checking if your system is up to date:  * 22-01:44:43 (3361) [INFO] Running: /usr/bin/yum clean all * 22-01:44:43 (3362) [INFO]  * 22-01:44:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:44:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 22-01:44:44 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-01:44:44 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 22-01:44:44 (3372) [INFO] Cleaning up list of fastest mirrors * 22-01:44:44 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 22-01:44:45 (3382) [INFO]  * 22-01:44:45 (3361) [INFO] Running: /usr/bin/yum check-update * 22-01:44:45 (3362) [INFO]  * 22-01:44:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:44:46 (3372) [INFO] Determining fastest mirrors * 22-01:46:15 (3372) [INFO] * EA4: 184.94.196.97 * 22-01:46:15 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 22-01:46:15 (3372) [INFO] * cpanel-plugins: 184.94.196.97 * 22-01:46:15 (3372) [INFO] * base: mirrors.raystedman.org * 22-01:46:15 (3372) [INFO] * epel: mirrors.xmission.com * 22-01:46:15 (3372) [INFO] * extras: mirror.web-ster.com * 22-01:46:15 (3372) [INFO] * updates: mirrors.oit.uci.edu * 22-01:47:33 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/a065921b909a0153cb37a7cd6d842013b87ba443016514d1bf05a7ceb96aeaf8-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 22-01:47:33 (3372) [INFO] Trying other mirror. * 22-01:47:33 (3372) [INFO] To address this issue please refer to the below wiki article  * 22-01:47:33 (3372) [INFO]  * 22-01:47:33 (3372) [INFO] https://wiki.centos.org/yum-errors * 22-01:47:33 (3372) [INFO]  * 22-01:47:33 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 22-01:47:33 (3372) [INFO]  * 22-01:48:16 (3372) [INFO]  * 22-01:48:16 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 22-01:48:16 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-01:48:17 (3382) [INFO]  * 22-01:48:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-01:48:17 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-01:48:17 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 22-01:48:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-01:48:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-01:48:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-22_01:48:18_modified_for_AlmaLinux_8.json * 22-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 22-01:56:48 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-01:37:00 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 23-01:37:05 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 23-01:37: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-01:43:26 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 23-01:43:26 (3077) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xmission.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.centos.iad1.serverforge.org/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesishosting.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.tripadvisor.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.tripadvisor.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://mirror.cs.vt.edu/pub/CentOS/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repos.forethought.net/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.advancedhosters.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.advancedhosters.com:80; Operation now in progress" Trying other mirror. http://mirrors.unifiedlayer.com/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.clarkson.edu/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/centos/7.9.2009/updates/x86_64/repodata/17631d532848730eb54f7f57aead85744fe29b779a8fbe1cc32c106e352318a1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror.  * 23-01:43:26 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 23-01:43:26 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 23-01:43:26 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 23-01:43:27 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 23-01:43:27 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 23-01:43:27 (2925) [INFO] Checking if your system is up to date:  * 23-01:43:27 (3361) [INFO] Running: /usr/bin/yum clean all * 23-01:43:27 (3362) [INFO]  * 23-01:43:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:43:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 23-01:43:27 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-01:43:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 23-01:43:28 (3372) [INFO] Cleaning up list of fastest mirrors * 23-01:43:28 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 23-01:43:28 (3382) [INFO]  * 23-01:43:28 (3361) [INFO] Running: /usr/bin/yum check-update * 23-01:43:28 (3362) [INFO]  * 23-01:43:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:43:29 (3372) [INFO] Determining fastest mirrors * 23-01:44:59 (3372) [INFO] * EA4: 184.94.196.93 * 23-01:44:59 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 23-01:44:59 (3372) [INFO] * cpanel-plugins: 184.94.196.93 * 23-01:44:59 (3372) [INFO] * base: mirror.web-ster.com * 23-01:44:59 (3372) [INFO] * epel: mirrors.xmission.com * 23-01:44:59 (3372) [INFO] * extras: la.mirrors.clouvider.net * 23-01:44:59 (3372) [INFO] * updates: mirrors.gigenet.com * 23-01:46:49 (3372) [INFO]  * 23-01:46:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 23-01:46:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-01:46:50 (3382) [INFO]  * 23-01:46:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-01:46:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-01:46:50 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 23-01:46:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-01:46:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-01:46:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-23_01:46:52_modified_for_AlmaLinux_8.json * 23-01:46: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 23-01:55:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-01:43:10 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 24-01:43:14 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 24-01:43: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  * 24-01:45:28 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 24-01:45:28 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 24-01:45:29 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 24-01:45:29 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 24-01:45:29 (2925) [INFO] Checking if your system is up to date:  * 24-01:45:29 (3361) [INFO] Running: /usr/bin/yum clean all * 24-01:45:29 (3362) [INFO]  * 24-01:45:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:45:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 24-01:45:30 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-01:45:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 24-01:45:30 (3372) [INFO] Cleaning up list of fastest mirrors * 24-01:45:30 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 24-01:45:30 (3382) [INFO]  * 24-01:45:30 (3361) [INFO] Running: /usr/bin/yum check-update * 24-01:45:30 (3362) [INFO]  * 24-01:45:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:45:32 (3372) [INFO] Determining fastest mirrors * 24-01:47:02 (3372) [INFO] * EA4: 208.74.123.61 * 24-01:47:02 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 24-01:47:02 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 24-01:47:02 (3372) [INFO] * base: mirror.fcix.net * 24-01:47:02 (3372) [INFO] * epel: mirrors.syringanetworks.net * 24-01:47:02 (3372) [INFO] * extras: centos-distro.1gservers.com * 24-01:47:02 (3372) [INFO] * updates: mirror.arizona.edu * 24-01:49:24 (3372) [INFO]  * 24-01:49:24 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 24-01:49:24 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-01:49:25 (3382) [INFO]  * 24-01:49:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-01:49:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-01:49:25 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 24-01:49:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-01:49:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-01:49:27 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-24_01:49:27_modified_for_AlmaLinux_8.json * 24-01:49:27 (2504) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 24-01:57:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-01:43:26 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 25-01:43:32 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 25-01:43: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  * 25-01:45:30 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 25-01:45:30 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 25-01:45:31 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 25-01:45:31 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 25-01:45:31 (2925) [INFO] Checking if your system is up to date:  * 25-01:45:31 (3361) [INFO] Running: /usr/bin/yum clean all * 25-01:45:31 (3362) [INFO]  * 25-01:45:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:45:31 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 25-01:45:31 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-01:45:31 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 25-01:45:32 (3372) [INFO] Cleaning up list of fastest mirrors * 25-01:45:32 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 25-01:45:32 (3382) [INFO]  * 25-01:45:32 (3361) [INFO] Running: /usr/bin/yum check-update * 25-01:45:32 (3362) [INFO]  * 25-01:45:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:45:33 (3372) [INFO] Determining fastest mirrors * 25-01:47:03 (3372) [INFO] * EA4: 208.74.123.62 * 25-01:47:03 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 25-01:47:03 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 25-01:47:03 (3372) [INFO] * base: mirrors.xmission.com * 25-01:47:03 (3372) [INFO] * epel: mirrors.xmission.com * 25-01:47:03 (3372) [INFO] * extras: ridgewireless.mm.fcix.net * 25-01:47:03 (3372) [INFO] * updates: mirrors.raystedman.org * 25-01:49:20 (3372) [INFO]  * 25-01:49:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 25-01:49:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-01:49:20 (3382) [INFO]  * 25-01:49:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-01:49:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-01:49:20 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 25-01:49:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-01:49:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-01:49:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-25_01:49:22_modified_for_AlmaLinux_8.json * 25-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 25-01:57:52 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:41:48 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:41:53 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:41: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  * 26-01:43:49 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 26-01:43:49 (3077) [ERROR] https://mirror.fcix.net/epel/7/x86_64/repodata/62f0f0605a0fe066f23acce2620d1145d9895e5bf7211fabec7c88724d446f35-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-01:43:49 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 26-01:43:49 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:43:49 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:43:50 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 26-01:43:50 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:43:50 (2925) [INFO] Checking if your system is up to date:  * 26-01:43:50 (3361) [INFO] Running: /usr/bin/yum clean all * 26-01:43:50 (3362) [INFO]  * 26-01:43:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:43:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:43:51 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:43:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:43:51 (3372) [INFO] Cleaning up list of fastest mirrors * 26-01:43:51 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 26-01:43:51 (3382) [INFO]  * 26-01:43:51 (3361) [INFO] Running: /usr/bin/yum check-update * 26-01:43:51 (3362) [INFO]  * 26-01:43:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:43:52 (3372) [INFO] Determining fastest mirrors * 26-01:45:21 (3372) [INFO] * EA4: 208.74.123.61 * 26-01:45:21 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 26-01:45:21 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 26-01:45:21 (3372) [INFO] * base: mirrors.xtom.com * 26-01:45:21 (3372) [INFO] * epel: mirrors.xmission.com * 26-01:45:21 (3372) [INFO] * extras: mirror.keystealth.org * 26-01:45:21 (3372) [INFO] * updates: or-mirror.iwebfusion.net * 26-01:46:54 (3372) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/e403f57a01ee9e2f27a5ba5dea06b989581e5fba211cd6e3d32270487f0342fa-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 26-01:46:54 (3372) [INFO] Trying other mirror. * 26-01:46:54 (3372) [INFO] To address this issue please refer to the below wiki article  * 26-01:46:54 (3372) [INFO]  * 26-01:46:54 (3372) [INFO] https://wiki.centos.org/yum-errors * 26-01:46:54 (3372) [INFO]  * 26-01:46:54 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 26-01:46:54 (3372) [INFO]  * 26-01:47:36 (3372) [INFO]  * 26-01:47:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 26-01:47:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-01:47:37 (3382) [INFO]  * 26-01:47:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:47:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:47:37 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:47:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-01:47:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-01:47:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-26_01:47:39_modified_for_AlmaLinux_8.json * 26-01:47:39 (2504) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 26-01:56:08 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-01:41:59 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 27-01:42:04 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 27-01:42: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  * 27-01:44:18 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 27-01:44:18 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 27-01:44:19 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 27-01:44:19 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 27-01:44:19 (2925) [INFO] Checking if your system is up to date:  * 27-01:44:19 (3361) [INFO] Running: /usr/bin/yum clean all * 27-01:44:19 (3362) [INFO]  * 27-01:44:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:44:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 27-01:44:20 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-01:44:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 27-01:44:20 (3372) [INFO] Cleaning up list of fastest mirrors * 27-01:44:20 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 27-01:44:20 (3382) [INFO]  * 27-01:44:20 (3361) [INFO] Running: /usr/bin/yum check-update * 27-01:44:20 (3362) [INFO]  * 27-01:44:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:44:21 (3372) [INFO] Determining fastest mirrors * 27-01:45:51 (3372) [INFO] * EA4: 208.74.123.62 * 27-01:45:51 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 27-01:45:51 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 27-01:45:51 (3372) [INFO] * base: mirrors.ocf.berkeley.edu * 27-01:45:51 (3372) [INFO] * epel: mirrors.xmission.com * 27-01:45:51 (3372) [INFO] * extras: mirrors.vcea.wsu.edu * 27-01:45:51 (3372) [INFO] * updates: repos.lax.layerhost.com * 27-01:48:22 (3372) [INFO]  * 27-01:48:22 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 27-01:48:22 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-01:48:23 (3382) [INFO]  * 27-01:48:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-01:48:23 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-01:48:23 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 27-01:48:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-01:48:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-01:48:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-27_01:48:25_modified_for_AlmaLinux_8.json * 27-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 27-01:56:54 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-01:41:49 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 28-01:41:54 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 28-01:41: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  * 28-01:44:07 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 28-01:44:07 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 28-01:44:12 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 28-01:44:12 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 28-01:44:12 (2925) [INFO] Checking if your system is up to date:  * 28-01:44:12 (3361) [INFO] Running: /usr/bin/yum clean all * 28-01:44:12 (3362) [INFO]  * 28-01:44:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:44:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 28-01:44:13 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-01:44:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 28-01:44:13 (3372) [INFO] Cleaning up list of fastest mirrors * 28-01:44:13 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 28-01:44:13 (3382) [INFO]  * 28-01:44:13 (3361) [INFO] Running: /usr/bin/yum check-update * 28-01:44:13 (3362) [INFO]  * 28-01:44:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:44:15 (3372) [INFO] Determining fastest mirrors * 28-01:45:43 (3372) [INFO] * EA4: 208.74.123.62 * 28-01:45:43 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 28-01:45:43 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 28-01:45:43 (3372) [INFO] * base: mirror.web-ster.com * 28-01:45:43 (3372) [INFO] * epel: mirrors.xmission.com * 28-01:45:43 (3372) [INFO] * extras: la.mirrors.clouvider.net * 28-01:45:43 (3372) [INFO] * updates: mirrors.xmission.com * 28-01:48:12 (3372) [INFO]  * 28-01:48:12 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 28-01:48:12 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-01:48:12 (3382) [INFO]  * 28-01:48:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-01:48:12 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-01:48:12 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 28-01:48:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-01:48:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-01:48:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-28_01:48:14_modified_for_AlmaLinux_8.json * 28-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 28-01:56:44 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-01:43:07 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 29-01:43:12 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 29-01:43: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  * 29-01:45:24 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 29-01:45:24 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 29-01:45:25 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 29-01:45:25 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 29-01:45:25 (2925) [INFO] Checking if your system is up to date:  * 29-01:45:25 (3361) [INFO] Running: /usr/bin/yum clean all * 29-01:45:25 (3362) [INFO]  * 29-01:45:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:45:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 29-01:45:25 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-01:45:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 29-01:45:26 (3372) [INFO] Cleaning up list of fastest mirrors * 29-01:45:26 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 29-01:45:26 (3382) [INFO]  * 29-01:45:26 (3361) [INFO] Running: /usr/bin/yum check-update * 29-01:45:26 (3362) [INFO]  * 29-01:45:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:45:27 (3372) [INFO] Determining fastest mirrors * 29-01:46:56 (3372) [INFO] * EA4: 63.247.64.58 * 29-01:46:56 (3372) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 29-01:46:56 (3372) [INFO] * cpanel-plugins: 63.247.64.58 * 29-01:46:56 (3372) [INFO] * base: mirror.chpc.utah.edu * 29-01:46:56 (3372) [INFO] * epel: mirrors.xmission.com * 29-01:46:56 (3372) [INFO] * extras: mirror.fcix.net * 29-01:46:56 (3372) [INFO] * updates: mirror.dal.nexril.net * 29-01:48:59 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/700a4ca79120f24dace453b4218dc5753732682539fae30fc3a024398c37f9a7-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 29-01:48:59 (3372) [INFO] Trying other mirror. * 29-01:48:59 (3372) [INFO] To address this issue please refer to the below wiki article  * 29-01:48:59 (3372) [INFO]  * 29-01:48:59 (3372) [INFO] https://wiki.centos.org/yum-errors * 29-01:48:59 (3372) [INFO]  * 29-01:48:59 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 29-01:48:59 (3372) [INFO]  * 29-01:49:41 (3372) [INFO]  * 29-01:49:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 29-01:49:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-01:49:42 (3382) [INFO]  * 29-01:49:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-01:49:42 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-01:49:42 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 29-01:49:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-01:49:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-01:49:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-29_01:49:44_modified_for_AlmaLinux_8.json * 29-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 29-01:58:14 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:54:03 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:54:06 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:54: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-01:56:26 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:56:26 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:56:27 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 30-01:56:27 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:56:27 (2925) [INFO] Checking if your system is up to date:  * 30-01:56:27 (3361) [INFO] Running: /usr/bin/yum clean all * 30-01:56:27 (3362) [INFO]  * 30-01:56:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:56:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:56:27 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:56:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:56:27 (3372) [INFO] Cleaning up list of fastest mirrors * 30-01:56:27 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 30-01:56:27 (3382) [INFO]  * 30-01:56:27 (3361) [INFO] Running: /usr/bin/yum check-update * 30-01:56:27 (3362) [INFO]  * 30-01:56:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:56:28 (3372) [INFO] Determining fastest mirrors * 30-01:57:59 (3372) [INFO] * EA4: 208.74.123.61 * 30-01:57:59 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 30-01:57:59 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 30-01:57:59 (3372) [INFO] * base: mirrors.ocf.berkeley.edu * 30-01:57:59 (3372) [INFO] * epel: mirrors.xmission.com * 30-01:57:59 (3372) [INFO] * extras: abqix.mm.fcix.net * 30-01:57:59 (3372) [INFO] * updates: mirror.fcix.net * 30-02:00:45 (3372) [INFO]  * 30-02:00:45 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 30-02:00:45 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-02:00:45 (3382) [INFO]  * 30-02:00:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-02:00:45 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-02:00:45 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-02:00:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-02:00:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-02:00:48 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-30_02:00:48_modified_for_AlmaLinux_8.json * 30-02:00: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 30-02:09:17 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-01:44:43 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 01-01:44:53 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 01-01:44: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  * 01-01:47:38 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 01-01:47:38 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 01-01:47:40 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 01-01:47:40 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 01-01:47:40 (2925) [INFO] Checking if your system is up to date:  * 01-01:47:40 (3361) [INFO] Running: /usr/bin/yum clean all * 01-01:47:40 (3362) [INFO]  * 01-01:47:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 01-01:47:41 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-01:47:41 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 01-01:47:41 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 01-01:47:42 (3372) [INFO] Cleaning up list of fastest mirrors * 01-01:47:42 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 01-01:47:42 (3382) [INFO]  * 01-01:47:42 (3361) [INFO] Running: /usr/bin/yum check-update * 01-01:47:42 (3362) [INFO]  * 01-01:47:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:43 (3372) [INFO] Determining fastest mirrors * 01-01:49:12 (3372) [INFO] * EA4: 208.74.123.62 * 01-01:49:12 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 01-01:49:12 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 01-01:49:12 (3372) [INFO] * base: mirror.web-ster.com * 01-01:49:12 (3372) [INFO] * epel: mirrors.xmission.com * 01-01:49:12 (3372) [INFO] * extras: mirror.chpc.utah.edu * 01-01:49:12 (3372) [INFO] * updates: mirror.chpc.utah.edu * 01-01:52:37 (3372) [INFO]  * 01-01:52:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 01-01:52:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-01:52:38 (3382) [INFO]  * 01-01:52:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-01:52:38 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-01:52:38 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 01-01:52:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-01:52:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-01:52:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-01_01:52:47_modified_for_AlmaLinux_8.json * 01-01:52: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 01-02:01:16 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-01:44:00 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 02-01:44:06 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 02-01:44: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  * 02-01:46:20 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 02-01:46:20 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 02-01:46:21 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 02-01:46:21 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 02-01:46:21 (2925) [INFO] Checking if your system is up to date:  * 02-01:46:21 (3361) [INFO] Running: /usr/bin/yum clean all * 02-01:46:21 (3362) [INFO]  * 02-01:46:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:46:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 02-01:46:22 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-01:46:22 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 02-01:46:22 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 02-01:46:23 (3372) [INFO] Cleaning up list of fastest mirrors * 02-01:46:23 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 02-01:46:23 (3382) [INFO]  * 02-01:46:23 (3361) [INFO] Running: /usr/bin/yum check-update * 02-01:46:23 (3362) [INFO]  * 02-01:46:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:46:24 (3372) [INFO] Determining fastest mirrors * 02-01:47:52 (3372) [INFO] * EA4: 208.74.123.62 * 02-01:47:52 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 02-01:47:52 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 02-01:47:52 (3372) [INFO] * base: mirror.den01.meanservers.net * 02-01:47:52 (3372) [INFO] * epel: mirrors.xmission.com * 02-01:47:52 (3372) [INFO] * extras: repo1.sea.innoscale.net * 02-01:47:52 (3372) [INFO] * updates: mirror.hostduplex.com * 02-01:49:40 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/d2ed02dcf602496bd76059b2d4170f114eea620c2ad818aa0cd144be4a1cde21-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 02-01:49:40 (3372) [INFO] Trying other mirror. * 02-01:49:40 (3372) [INFO] To address this issue please refer to the below wiki article  * 02-01:49:40 (3372) [INFO]  * 02-01:49:40 (3372) [INFO] https://wiki.centos.org/yum-errors * 02-01:49:40 (3372) [INFO]  * 02-01:49:40 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 02-01:49:40 (3372) [INFO]  * 02-01:50:25 (3372) [INFO]  * 02-01:50:25 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 02-01:50:25 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-01:50:25 (3382) [INFO]  * 02-01:50:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-01:50:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-01:50:25 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 02-01:50:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-01:50:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-01:50:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-02_01:50:28_modified_for_AlmaLinux_8.json * 02-01:50: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 02-01:58:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-01:41:52 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 03-01:41:56 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 03-01:41: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  * 03-01:44:25 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 03-01:44:25 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 03-01:44:25 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 03-01:44:25 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 03-01:44:25 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 03-01:44:25 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 03-01:44:25 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 03-01:44:25 (2925) [INFO] Checking if your system is up to date:  * 03-01:44:25 (3361) [INFO] Running: /usr/bin/yum clean all * 03-01:44:25 (3362) [INFO]  * 03-01:44:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:44:26 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 03-01:44:26 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-01:44:26 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 03-01:44:26 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 03-01:44:27 (3372) [INFO] Cleaning up list of fastest mirrors * 03-01:44:27 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 03-01:44:27 (3382) [INFO]  * 03-01:44:27 (3361) [INFO] Running: /usr/bin/yum check-update * 03-01:44:27 (3362) [INFO]  * 03-01:44:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:44:28 (3372) [INFO] Determining fastest mirrors * 03-01:45:56 (3372) [INFO] * EA4: 184.94.196.94 * 03-01:45:56 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 03-01:45:56 (3372) [INFO] * cpanel-plugins: 184.94.196.94 * 03-01:45:56 (3372) [INFO] * base: mirror.fcix.net * 03-01:45:56 (3372) [INFO] * epel: mirrors.xmission.com * 03-01:45:56 (3372) [INFO] * extras: ridgewireless.mm.fcix.net * 03-01:45:56 (3372) [INFO] * updates: mirror.chpc.utah.edu * 03-01:48:27 (3372) [INFO]  * 03-01:48:27 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 03-01:48:27 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-01:48:27 (3382) [INFO]  * 03-01:48:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-01:48:27 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-01:48:27 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 03-01:48:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-01:48:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-01:48:29 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-03_01:48:29_modified_for_AlmaLinux_8.json * 03-01:48: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 03-01:56:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-01:42:18 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 04-01:42:24 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 04-01:42: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-01:44:51 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 04-01:44:51 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 04-01:44:52 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 04-01:44:52 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 04-01:44:52 (2925) [INFO] Checking if your system is up to date:  * 04-01:44:52 (3361) [INFO] Running: /usr/bin/yum clean all * 04-01:44:52 (3362) [INFO]  * 04-01:44:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:44:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 04-01:44:53 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-01:44:53 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 04-01:44:53 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 04-01:44:53 (3372) [INFO] Cleaning up list of fastest mirrors * 04-01:44:53 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 04-01:44:53 (3382) [INFO]  * 04-01:44:53 (3361) [INFO] Running: /usr/bin/yum check-update * 04-01:44:53 (3362) [INFO]  * 04-01:44:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:44:54 (3372) [INFO] Determining fastest mirrors * 04-01:46:24 (3372) [INFO] * EA4: 208.74.123.62 * 04-01:46:24 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 04-01:46:24 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 04-01:46:24 (3372) [INFO] * base: mirrors.vcea.wsu.edu * 04-01:46:24 (3372) [INFO] * epel: mirrors.xmission.com * 04-01:46:24 (3372) [INFO] * extras: mirrors.radwebhosting.com * 04-01:46:24 (3372) [INFO] * updates: mirror.chpc.utah.edu * 04-01:48:28 (3372) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 04-01:48:28 (3372) [INFO] Trying other mirror. * 04-01:48:28 (3372) [INFO] To address this issue please refer to the below wiki article  * 04-01:48:28 (3372) [INFO]  * 04-01:48:28 (3372) [INFO] https://wiki.centos.org/yum-errors * 04-01:48:28 (3372) [INFO]  * 04-01:48:28 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 04-01:48:28 (3372) [INFO]  * 04-01:49:26 (3372) [INFO]  * 04-01:49:26 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 04-01:49:26 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-01:49:26 (3382) [INFO]  * 04-01:49:26 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-01:49:26 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-01:49:26 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 04-01:49:26 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-01:49:26 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-01:49:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-04_01:49:28_modified_for_AlmaLinux_8.json * 04-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 04-01:57:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-01:38:11 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 05-01:38:15 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 05-01:38: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  * 05-01:57:03 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 05-01:57:03 (3077) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. http://mirror.den01.meanservers.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/57b2d04f3ac467392c484a2e77a49b9ababeb81a03ca831bb9062e5a753aef02-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.gigenet.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.wdc1.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/b52fb718cbd95f928936449dd1157a0ebac01abc1ad5b7ceed20c40c623cda2c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.oit.uci.edu/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.arizona.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.pit.teraswitch.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://or-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.centos.iad1.serverforge.org/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos-distro.1gservers.com/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://bay.uchicago.edu/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo.ialab.dsu.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repos.lax.layerhost.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.dal10.us.leaseweb.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vtti.vt.edu/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cs.vt.edu/pub/CentOS/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesisadaptive.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.umd.edu/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesisadaptive.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.ocf.berkeley.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.liquidweb.com/CentOS/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://coresite.mm.fcix.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesisadaptive.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.steadfastnet.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://fedora.westmancom.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repos.forethought.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.dal.nexril.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.xenyth.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.advancedhosters.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.advancedhosters.com:80; Operation now in progress" Trying other mirror. https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.stjschools.org/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.advancedhosters.com/centos/7.9.2009/updates/x86_64/repodata/eb8f61c1a9c5351b590c3fd65b0801655cf16aace38466db45bfd869c37c12c3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.advancedhosters.com:80; Operation now in progress" Trying other mirror. https://epel.mirror.constant.com/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://linux-mirrors.fnal.gov/linux/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.coastal.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.datto.com/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cs.vt.edu/pub/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.atl.genesisadaptive.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://abqix.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.usi.edu/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://na.edge.kernel.org/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.wcupa.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lshiy.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-cc-rdu01.fedoraproject.org/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.upr.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://mirror.clarkson.edu/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.constant.com/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.constant.com/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://linux-mirrors.fnal.gov/linux/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://linux-mirrors.fnal.gov/linux/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://coresite.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.steadfastnet.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://fedora.westmancom.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.sonic.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.coastal.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.datto.com/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.stjschools.org/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.xenyth.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.atl.genesisadaptive.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://abqix.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.usi.edu/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://na.edge.kernel.org/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lshiy.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.wcupa.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-cc-rdu01.fedoraproject.org/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.upr.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.clarkson.edu/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://coresite.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.steadfastnet.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://fedora.westmancom.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.sonic.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.coastal.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.datto.com/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.stjschools.org/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.xenyth.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.atl.genesisadaptive.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://abqix.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.usi.edu/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.wcupa.edu/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://na.edge.kernel.org/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download-cc-rdu01.fedoraproject.org/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lshiy.com/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.upr.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://coresite.mm.fcix.net/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.steadfastnet.com/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.sonic.net/epel/7/x86_64/repodata/1994beb7b8f846b0f5ec054441354889c2aeaa607fb845f0a7b181baf5dfb532-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.clarkson.edu/fedora/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/e54f3e6cb6e1650406e3a4b7623f4a965b11ea22fa7f7c4812d051ce64a90993-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/dab4efb89e04560cfbe53711f412c32247da39a0d721d9ec2c9f1e88aed424d1-comps-Everything.x86_64.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable 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 MariaDB100: Check uncompressed DB failed  * 05-01:57:03 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 05-01:57:03 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 05-01:57:03 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 05-01:57:10 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 05-01:57:10 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 05-01:57:10 (2925) [INFO] Checking if your system is up to date:  * 05-01:57:10 (3361) [INFO] Running: /usr/bin/yum clean all * 05-01:57:10 (3362) [INFO]  * 05-01:57:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:57:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 05-01:57:11 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-01:57:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 05-01:57:11 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 05-01:57:11 (3372) [INFO] Cleaning up list of fastest mirrors * 05-01:57:11 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 05-01:57:11 (3382) [INFO]  * 05-01:57:11 (3361) [INFO] Running: /usr/bin/yum check-update * 05-01:57:11 (3362) [INFO]  * 05-01:57:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:57:12 (3372) [INFO] Determining fastest mirrors * 05-01:58:42 (3372) [INFO] * EA4: 184.94.196.93 * 05-01:58:42 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 05-01:58:42 (3372) [INFO] * cpanel-plugins: 184.94.196.93 * 05-01:58:42 (3372) [INFO] * base: repos.forethought.net * 05-01:58:42 (3372) [INFO] * epel: mirrors.xmission.com * 05-01:58:42 (3372) [INFO] * extras: repos.lax.layerhost.com * 05-01:58:42 (3372) [INFO] * updates: mirrors.sonic.net * 05-02:01:34 (3372) [INFO]  * 05-02:01:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 05-02:01:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-02:01:35 (3382) [INFO]  * 05-02:01:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-02:01:35 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-02:01:35 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 05-02:01:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-02:01:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-02:01:39 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-05_02:01:39_modified_for_AlmaLinux_8.json * 05-02:01:39 (2504) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 06-01:44:32 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 06-01:44:34 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 06-01:44:34 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 06-01:47:19 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 06-01:47:19 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 06-01:47:20 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 06-01:47:20 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 06-01:47:20 (2925) [INFO] Checking if your system is up to date:  * 06-01:47:20 (3361) [INFO] Running: /usr/bin/yum clean all * 06-01:47:20 (3362) [INFO]  * 06-01:47:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:47:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 06-01:47:21 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-01:47:21 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 06-01:47:21 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 06-01:47:22 (3372) [INFO] Cleaning up list of fastest mirrors * 06-01:47:22 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 06-01:47:22 (3382) [INFO]  * 06-01:47:22 (3361) [INFO] Running: /usr/bin/yum check-update * 06-01:47:22 (3362) [INFO]  * 06-01:47:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:47:24 (3372) [INFO] Determining fastest mirrors * 06-01:48:53 (3372) [INFO] * EA4: 184.94.196.97 * 06-01:48:53 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 06-01:48:53 (3372) [INFO] * cpanel-plugins: 184.94.196.97 * 06-01:48:53 (3372) [INFO] * base: mirror.keystealth.org * 06-01:48:53 (3372) [INFO] * epel: mirrors.xmission.com * 06-01:48:53 (3372) [INFO] * extras: mirror.facebook.net * 06-01:48:53 (3372) [INFO] * updates: abqix.mm.fcix.net * 06-01:51:46 (3372) [INFO]  * 06-01:51:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 06-01:51:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-01:51:46 (3382) [INFO]  * 06-01:51:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-01:51:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-01:51:46 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 06-01:51:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-01:51:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-01:51:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-06_01:51:51_modified_for_AlmaLinux_8.json * 06-01:51: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 06-02:00:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-01:38:32 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 07-01:38:37 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 07-01:38: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  * 07-01:45:29 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 07-01:45:29 (3077) [ERROR] http://centos.mirror.constant.com/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.phx1.us.spryservers.net/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/b52fb718cbd95f928936449dd1157a0ebac01abc1ad5b7ceed20c40c623cda2c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.ussg.iu.edu/linux/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.hivelocity.net/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesishosting.com/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.mirror.shastacoe.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.radwebhosting.com/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vacares.com/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.osuosl.org/pub/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.us-midwest-1.nexcess.net/CentOS/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://la.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.ash.fastserv.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.rackspace.com/CentOS/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.unifiedlayer.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.web-ster.com/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.dal10.us.leaseweb.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://or-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ridgewireless.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/3022bf3c084e6adb8ccc29d9e9ea4d92d817ed07f7c81a876371cb37c9418056-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vacares.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable 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 extras: Check uncompressed DB failed  * 07-01:45:29 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 07-01:45:29 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 07-01:45:29 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 07-01:45:30 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 07-01:45:30 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 07-01:45:30 (2925) [INFO] Checking if your system is up to date:  * 07-01:45:30 (3361) [INFO] Running: /usr/bin/yum clean all * 07-01:45:30 (3362) [INFO]  * 07-01:45:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:45:31 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 07-01:45:31 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-01:45:31 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 07-01:45:31 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 07-01:45:32 (3372) [INFO] Cleaning up list of fastest mirrors * 07-01:45:32 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 07-01:45:32 (3382) [INFO]  * 07-01:45:32 (3361) [INFO] Running: /usr/bin/yum check-update * 07-01:45:32 (3362) [INFO]  * 07-01:45:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:45:33 (3372) [INFO] Determining fastest mirrors * 07-01:47:02 (3372) [INFO] * EA4: 184.94.196.94 * 07-01:47:02 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 07-01:47:02 (3372) [INFO] * cpanel-plugins: 184.94.196.94 * 07-01:47:02 (3372) [INFO] * base: mirrors.unifiedlayer.com * 07-01:47:02 (3372) [INFO] * epel: mirrors.xmission.com * 07-01:47:02 (3372) [INFO] * extras: centos.mirror.shastacoe.net * 07-01:47:02 (3372) [INFO] * updates: ridgewireless.mm.fcix.net * 07-01:49:55 (3372) [INFO]  * 07-01:49:55 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 07-01:49:55 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-01:49:55 (3382) [INFO]  * 07-01:49:55 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-01:49:55 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-01:49:55 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 07-01:49:55 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-01:49:55 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-01:49:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-07_01:49:58_modified_for_AlmaLinux_8.json * 07-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 07-01:58:27 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-01:45:40 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 08-01:45:45 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 08-01:45: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  * 08-01:48:31 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 08-01:48:31 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 08-01:48:32 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 08-01:48:32 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 08-01:48:32 (2925) [INFO] Checking if your system is up to date:  * 08-01:48:32 (3361) [INFO] Running: /usr/bin/yum clean all * 08-01:48:32 (3362) [INFO]  * 08-01:48:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:48:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 08-01:48:32 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-01:48:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 08-01:48:32 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 08-01:48:33 (3372) [INFO] Cleaning up list of fastest mirrors * 08-01:48:33 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 08-01:48:33 (3382) [INFO]  * 08-01:48:33 (3361) [INFO] Running: /usr/bin/yum check-update * 08-01:48:33 (3362) [INFO]  * 08-01:48:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:48:34 (3372) [INFO] Determining fastest mirrors * 08-01:50:07 (3372) [INFO] * EA4: 208.74.123.61 * 08-01:50:07 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 08-01:50:07 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 08-01:50:07 (3372) [INFO] * base: mirrors.ocf.berkeley.edu * 08-01:50:07 (3372) [INFO] * epel: mirrors.xmission.com * 08-01:50:07 (3372) [INFO] * extras: mirror.keystealth.org * 08-01:50:07 (3372) [INFO] * updates: mirror.fcix.net * 08-01:53:23 (3372) [INFO]  * 08-01:53:23 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 08-01:53:23 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-01:53:23 (3382) [INFO]  * 08-01:53:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-01:53:23 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-01:53:23 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 08-01:53:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-01:53:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-01:53:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-08_01:53:32_modified_for_AlmaLinux_8.json * 08-01:53: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 08-02:02:02 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-01:44:45 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 09-01:44:50 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 09-01:44:50 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 09-01:48:02 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 09-01:48:02 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30111 milliseconds')  * 09-01:48:02 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 09-01:48:02 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 09-01:48:02 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 09-01:48:03 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 09-01:48:03 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 09-01:48:03 (2925) [INFO] Checking if your system is up to date:  * 09-01:48:03 (3361) [INFO] Running: /usr/bin/yum clean all * 09-01:48:03 (3362) [INFO]  * 09-01:48:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:48:04 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 09-01:48:04 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-01:48:04 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 09-01:48:04 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 09-01:48:04 (3372) [INFO] Cleaning up list of fastest mirrors * 09-01:48:04 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 09-01:48:04 (3382) [INFO]  * 09-01:48:04 (3361) [INFO] Running: /usr/bin/yum check-update * 09-01:48:04 (3362) [INFO]  * 09-01:48:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:48:05 (3372) [INFO] Determining fastest mirrors * 09-01:49:35 (3372) [INFO] * EA4: 208.74.123.62 * 09-01:49:35 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 09-01:49:35 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 09-01:49:35 (3372) [INFO] * base: mirror.fcix.net * 09-01:49:35 (3372) [INFO] * epel: mirrors.xmission.com * 09-01:49:35 (3372) [INFO] * extras: abqix.mm.fcix.net * 09-01:49:35 (3372) [INFO] * updates: mirror.web-ster.com * 09-01:52:21 (3372) [INFO]  * 09-01:52:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 09-01:52:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-01:52:21 (3382) [INFO]  * 09-01:52:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-01:52:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-01:52:21 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 09-01:52:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-01:52:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-01:52:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-09_01:52:25_modified_for_AlmaLinux_8.json * 09-01:52: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 09-02:00:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-01:37:08 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 10-01:37:13 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 10-01:37: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  * 10-01:42:47 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 10-01:42:47 (3077) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/b52fb718cbd95f928936449dd1157a0ebac01abc1ad5b7ceed20c40c623cda2c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable 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 wp-toolkit-thirdparties: Check uncompressed DB failed  * 10-01:42:47 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 10-01:42:47 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 10-01:42:47 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 10-01:42:52 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 10-01:42:52 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 10-01:42:52 (2925) [INFO] Checking if your system is up to date:  * 10-01:42:52 (3361) [INFO] Running: /usr/bin/yum clean all * 10-01:42:52 (3362) [INFO]  * 10-01:42:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:42:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 10-01:42:53 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-01:42:53 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 10-01:42:53 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 10-01:42:53 (3372) [INFO] Cleaning up list of fastest mirrors * 10-01:42:53 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 10-01:42:53 (3382) [INFO]  * 10-01:42:53 (3361) [INFO] Running: /usr/bin/yum check-update * 10-01:42:53 (3362) [INFO]  * 10-01:42:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:42:55 (3372) [INFO] Determining fastest mirrors * 10-01:44:24 (3372) [INFO] * EA4: 208.74.123.61 * 10-01:44:24 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 10-01:44:24 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 10-01:44:24 (3372) [INFO] * base: mirrors.vcea.wsu.edu * 10-01:44:24 (3372) [INFO] * epel: mirrors.xmission.com * 10-01:44:24 (3372) [INFO] * extras: mirrors.xtom.com * 10-01:44:24 (3372) [INFO] * updates: mirror.arizona.edu * 10-01:46:35 (3372) [INFO]  * 10-01:46:35 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 10-01:46:35 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-01:46:36 (3382) [INFO]  * 10-01:46:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-01:46:36 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-01:46:36 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 10-01:46:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-01:46:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-01:46:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-10_01:46:38_modified_for_AlmaLinux_8.json * 10-01:46: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 10-01:55:07 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-01:47:15 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 11-01:47:19 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 11-01:47:19 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 11-01:50:08 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 11-01:50:08 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 11-01:50:09 (2946) [WARN] JetBackup version 4.1.2-11 currently installed. * 11-01:50:09 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 11-01:50:09 (2925) [INFO] Checking if your system is up to date:  * 11-01:50:09 (3361) [INFO] Running: /usr/bin/yum clean all * 11-01:50:09 (3362) [INFO]  * 11-01:50:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:50:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 11-01:50:10 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-01:50:10 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 11-01:50:10 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 11-01:50:10 (3372) [INFO] Cleaning up list of fastest mirrors * 11-01:50:10 (3372) [INFO] Other repos take up 624 k of disk space (use --verbose for details) * 11-01:50:10 (3382) [INFO]  * 11-01:50:10 (3361) [INFO] Running: /usr/bin/yum check-update * 11-01:50:10 (3362) [INFO]  * 11-01:50:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:50:11 (3372) [INFO] Determining fastest mirrors * 11-01:51:42 (3372) [INFO] * EA4: 208.74.123.62 * 11-01:51:42 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 11-01:51:42 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 11-01:51:42 (3372) [INFO] * base: mirrors.xmission.com * 11-01:51:42 (3372) [INFO] * epel: mirrors.xmission.com * 11-01:51:42 (3372) [INFO] * extras: mirror.keystealth.org * 11-01:51:42 (3372) [INFO] * updates: ridgewireless.mm.fcix.net * 11-01:54:29 (3372) [INFO]  * 11-01:54:29 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 11-01:54:29 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-01:54:30 (3382) [INFO]  * 11-01:54:30 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-01:54:30 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-01:54:30 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 11-01:54:30 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-01:54:30 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-01:54:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-11_01:54:33_modified_for_AlmaLinux_8.json * 11-01:54: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 11-02:03:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-01:43:28 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 12-01:43:31 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 12-01:43: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-01:46:16 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 12-01:46:16 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 12-01:46:19 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 12-01:46:19 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 12-01:46:19 (2925) [INFO] Checking if your system is up to date:  * 12-01:46:19 (3361) [INFO] Running: /usr/bin/yum clean all * 12-01:46:19 (3362) [INFO]  * 12-01:46:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:46:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 12-01:46:20 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-01:46:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 12-01:46:20 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 12-01:46:20 (3372) [INFO] Cleaning up list of fastest mirrors * 12-01:46:20 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 12-01:46:20 (3382) [INFO]  * 12-01:46:20 (3361) [INFO] Running: /usr/bin/yum check-update * 12-01:46:20 (3362) [INFO]  * 12-01:46:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:46:21 (3372) [INFO] Determining fastest mirrors * 12-01:47:53 (3372) [INFO] * EA4: 208.74.123.61 * 12-01:47:53 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 12-01:47:53 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 12-01:47:53 (3372) [INFO] * base: mirror.keystealth.org * 12-01:47:53 (3372) [INFO] * epel: mirrors.xmission.com * 12-01:47:53 (3372) [INFO] * extras: mirror.keystealth.org * 12-01:47:53 (3372) [INFO] * updates: repos.forethought.net * 12-01:50:56 (3372) [INFO]  * 12-01:50:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 12-01:50:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-01:50:57 (3382) [INFO]  * 12-01:50:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-01:50:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-01:50:57 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 12-01:50:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-01:50:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-01:51:01 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-12_01:51:01_modified_for_AlmaLinux_8.json * 12-01:51:01 (2504) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 12-01:59:31 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-01:42:52 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 13-01:43:01 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 13-01:43:01 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 13-01:45:47 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 13-01:45:47 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 13-01:45:47 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 13-01:45:47 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 13-01:45:47 (2925) [INFO] Checking if your system is up to date:  * 13-01:45:47 (3361) [INFO] Running: /usr/bin/yum clean all * 13-01:45:47 (3362) [INFO]  * 13-01:45:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:45:48 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 13-01:45:48 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-01:45:48 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 13-01:45:48 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 13-01:45:49 (3372) [INFO] Cleaning up list of fastest mirrors * 13-01:45:49 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 13-01:45:49 (3382) [INFO]  * 13-01:45:49 (3361) [INFO] Running: /usr/bin/yum check-update * 13-01:45:49 (3362) [INFO]  * 13-01:45:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:45:51 (3372) [INFO] Determining fastest mirrors * 13-01:47:19 (3372) [INFO] * EA4: 208.74.123.62 * 13-01:47:19 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 13-01:47:19 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 13-01:47:19 (3372) [INFO] * base: mirror.sfo12.us.leaseweb.net * 13-01:47:19 (3372) [INFO] * epel: mirrors.xmission.com * 13-01:47:20 (3372) [INFO] * extras: mirrors.xmission.com * 13-01:47:20 (3372) [INFO] * updates: mirror.arizona.edu * 13-01:50:29 (3372) [INFO]  * 13-01:50:29 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 13-01:50:29 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-01:50:30 (3382) [INFO]  * 13-01:50:30 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-01:50:30 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-01:50:30 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 13-01:50:30 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-01:50:30 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-01:50:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-13_01:50:34_modified_for_AlmaLinux_8.json * 13-01:50: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 13-01:59:04 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-01:43:18 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 14-01:43:23 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 14-01:43: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  * 14-01:46:04 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 14-01:46:04 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 14-01:46:05 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 14-01:46:05 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 14-01:46:05 (2925) [INFO] Checking if your system is up to date:  * 14-01:46:05 (3361) [INFO] Running: /usr/bin/yum clean all * 14-01:46:05 (3362) [INFO]  * 14-01:46:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:46:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 14-01:46:06 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-01:46:06 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 14-01:46:06 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 14-01:46:06 (3372) [INFO] Cleaning up list of fastest mirrors * 14-01:46:06 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 14-01:46:06 (3382) [INFO]  * 14-01:46:06 (3361) [INFO] Running: /usr/bin/yum check-update * 14-01:46:06 (3362) [INFO]  * 14-01:46:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:46:08 (3372) [INFO] Determining fastest mirrors * 14-01:47:38 (3372) [INFO] * EA4: 208.74.123.62 * 14-01:47:38 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 14-01:47:38 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 14-01:47:38 (3372) [INFO] * base: centos-distro.cavecreek.net * 14-01:47:38 (3372) [INFO] * epel: mirrors.xmission.com * 14-01:47:38 (3372) [INFO] * extras: mirror.chpc.utah.edu * 14-01:47:38 (3372) [INFO] * updates: mirror.hostduplex.com * 14-01:50:11 (3372) [INFO]  * 14-01:50:11 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 14-01:50:11 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-01:50:11 (3382) [INFO]  * 14-01:50:11 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-01:50:11 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-01:50:11 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 14-01:50:11 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-01:50:11 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-01:50:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-14_01:50:14_modified_for_AlmaLinux_8.json * 14-01:50: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 14-01:58:43 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-01:45:30 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 15-01:45:37 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 15-01:45: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  * 15-01:48:49 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 15-01:48:49 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 15-01:48:50 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 15-01:48:50 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 15-01:48:50 (2925) [INFO] Checking if your system is up to date:  * 15-01:48:50 (3361) [INFO] Running: /usr/bin/yum clean all * 15-01:48:50 (3362) [INFO]  * 15-01:48:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:48:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 15-01:48:51 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-01:48:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 15-01:48:51 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 15-01:48:51 (3372) [INFO] Cleaning up list of fastest mirrors * 15-01:48:51 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 15-01:48:51 (3382) [INFO]  * 15-01:48:51 (3361) [INFO] Running: /usr/bin/yum check-update * 15-01:48:51 (3362) [INFO]  * 15-01:48:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:48:53 (3372) [INFO] Determining fastest mirrors * 15-01:50:23 (3372) [INFO] * EA4: 184.94.196.93 * 15-01:50:23 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 15-01:50:23 (3372) [INFO] * cpanel-plugins: 184.94.196.93 * 15-01:50:23 (3372) [INFO] * base: mirrors.xmission.com * 15-01:50:23 (3372) [INFO] * epel: mirrors.xmission.com * 15-01:50:23 (3372) [INFO] * extras: abqix.mm.fcix.net * 15-01:50:23 (3372) [INFO] * updates: mirrors.sonic.net * 15-01:53:45 (3372) [INFO]  * 15-01:53:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 15-01:53:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-01:53:46 (3382) [INFO]  * 15-01:53:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-01:53:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-01:53:46 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 15-01:53:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-01:53:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-01:53:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-15_01:53:53_modified_for_AlmaLinux_8.json * 15-01:53: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 15-02:02:22 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-01:42:37 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 16-01:42:42 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 16-01:42: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  * 16-01:45:11 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 16-01:45:11 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30330 milliseconds')  * 16-01:45:11 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 16-01:45:11 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 16-01:45:11 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 16-01:45:12 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 16-01:45:12 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 16-01:45:12 (2925) [INFO] Checking if your system is up to date:  * 16-01:45:12 (3361) [INFO] Running: /usr/bin/yum clean all * 16-01:45:12 (3362) [INFO]  * 16-01:45:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:45:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 16-01:45:13 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-01:45:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 16-01:45:13 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 16-01:45:13 (3372) [INFO] Cleaning up list of fastest mirrors * 16-01:45:13 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 16-01:45:13 (3382) [INFO]  * 16-01:45:13 (3361) [INFO] Running: /usr/bin/yum check-update * 16-01:45:13 (3362) [INFO]  * 16-01:45:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:45:14 (3372) [INFO] Determining fastest mirrors * 16-01:46:43 (3372) [INFO] * EA4: 208.74.123.62 * 16-01:46:43 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 16-01:46:43 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 16-01:46:43 (3372) [INFO] * base: mirrors.ocf.berkeley.edu * 16-01:46:43 (3372) [INFO] * epel: mirrors.xmission.com * 16-01:46:43 (3372) [INFO] * extras: mirrors.sonic.net * 16-01:46:43 (3372) [INFO] * updates: mirrors.vcea.wsu.edu * 16-01:49:31 (3372) [INFO]  * 16-01:49:31 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 16-01:49:31 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-01:49:32 (3382) [INFO]  * 16-01:49:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-01:49:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-01:49:32 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 16-01:49:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-01:49:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-01:49:34 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-16_01:49:34_modified_for_AlmaLinux_8.json * 16-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 16-01:58:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-01:42:34 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 17-01:42:38 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 17-01:42:38 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:23 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 17-01:45:23 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 17-01:45:24 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 17-01:45:24 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 17-01:45:24 (2925) [INFO] Checking if your system is up to date:  * 17-01:45:24 (3361) [INFO] Running: /usr/bin/yum clean all * 17-01:45:24 (3362) [INFO]  * 17-01:45:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:45:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 17-01:45:25 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-01:45:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 17-01:45:25 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 17-01:45:25 (3372) [INFO] Cleaning up list of fastest mirrors * 17-01:45:25 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 17-01:45:25 (3382) [INFO]  * 17-01:45:25 (3361) [INFO] Running: /usr/bin/yum check-update * 17-01:45:25 (3362) [INFO]  * 17-01:45:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:45:27 (3372) [INFO] Determining fastest mirrors * 17-01:46:54 (3372) [INFO] * EA4: 208.74.123.62 * 17-01:46:54 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 17-01:46:54 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 17-01:46:54 (3372) [INFO] * base: ridgewireless.mm.fcix.net * 17-01:46:54 (3372) [INFO] * epel: mirrors.xmission.com * 17-01:46:54 (3372) [INFO] * extras: mirrors.xmission.com * 17-01:46:54 (3372) [INFO] * updates: mirror.keystealth.org * 17-01:49:56 (3372) [INFO]  * 17-01:49:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 17-01:49:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-01:49:56 (3382) [INFO]  * 17-01:49:56 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-01:49:56 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-01:49:56 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 17-01:49:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-01:49:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-01:49:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-17_01:49:58_modified_for_AlmaLinux_8.json * 17-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 17-01:58:28 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-01:42:28 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 18-01:42:32 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 18-01:42: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  * 18-01:45:17 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 18-01:45:17 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 18-01:45:18 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 18-01:45:18 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 18-01:45:18 (2925) [INFO] Checking if your system is up to date:  * 18-01:45:18 (3361) [INFO] Running: /usr/bin/yum clean all * 18-01:45:18 (3362) [INFO]  * 18-01:45:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:45:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 18-01:45:18 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-01:45:18 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 18-01:45:18 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 18-01:45:19 (3372) [INFO] Cleaning up list of fastest mirrors * 18-01:45:19 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 18-01:45:19 (3382) [INFO]  * 18-01:45:19 (3361) [INFO] Running: /usr/bin/yum check-update * 18-01:45:19 (3362) [INFO]  * 18-01:45:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:45:19 (3372) [INFO] Determining fastest mirrors * 18-01:46:50 (3372) [INFO] * EA4: 208.74.123.61 * 18-01:46:50 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 18-01:46:50 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 18-01:46:50 (3372) [INFO] * base: ftpmirror.your.org * 18-01:46:50 (3372) [INFO] * epel: mirrors.xmission.com * 18-01:46:50 (3372) [INFO] * extras: mirror.web-ster.com * 18-01:46:50 (3372) [INFO] * updates: ridgewireless.mm.fcix.net * 18-01:49:37 (3372) [INFO]  * 18-01:49:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 18-01:49:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-01:49:38 (3382) [INFO]  * 18-01:49:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-01:49:38 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-01:49:38 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 18-01:49:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-01:49:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-01:49:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-18_01:49:40_modified_for_AlmaLinux_8.json * 18-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 18-01:58:09 (2504) [WARN] *** Elevation Blocker detected: *** This script does not appear to be the newest available release. Please download the latest version from the following URL and try again: wget -O /scripts/elevate-cpanel https://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-01:58:09 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-01:43:28 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 19-01:43:33 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 19-01:43:33 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:49 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 19-01:45:49 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 19-01:45:50 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 19-01:45:50 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 19-01:45:50 (2925) [INFO] Checking if your system is up to date:  * 19-01:45:50 (3361) [INFO] Running: /usr/bin/yum clean all * 19-01:45:50 (3362) [INFO]  * 19-01:45:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:45:50 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 19-01:45:50 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-01:45:50 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 19-01:45:50 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 19-01:45:51 (3372) [INFO] Cleaning up list of fastest mirrors * 19-01:45:51 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 19-01:45:51 (3382) [INFO]  * 19-01:45:51 (3361) [INFO] Running: /usr/bin/yum check-update * 19-01:45:51 (3362) [INFO]  * 19-01:45:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:45:52 (3372) [INFO] Determining fastest mirrors * 19-01:47:23 (3372) [INFO] * EA4: 208.100.0.204 * 19-01:47:23 (3372) [INFO] * cpanel-addons-production-feed: 208.100.0.204 * 19-01:47:23 (3372) [INFO] * cpanel-plugins: 208.100.0.204 * 19-01:47:23 (3372) [INFO] * base: ridgewireless.mm.fcix.net * 19-01:47:23 (3372) [INFO] * epel: mirrors.xmission.com * 19-01:47:23 (3372) [INFO] * extras: abqix.mm.fcix.net * 19-01:47:23 (3372) [INFO] * updates: ridgewireless.mm.fcix.net * 19-01:49:44 (3372) [INFO]  * 19-01:49:44 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 19-01:49:44 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-01:49:45 (3382) [INFO]  * 19-01:49:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-01:49:45 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-01:49:45 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 19-01:49:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-01:49:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-01:49:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-19_01:49:47_modified_for_AlmaLinux_8.json * 19-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 19-01:58:17 (2504) [WARN] *** Elevation Blocker detected: *** This script does not appear to be the newest available release. Please download the latest version from the following URL and try again: wget -O /scripts/elevate-cpanel https://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-01:58:17 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-01:43:57 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 20-01:44:01 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 20-01:44: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-01:46:43 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 20-01:46:43 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 20-01:46:44 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 20-01:46:44 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 20-01:46:44 (2925) [INFO] Checking if your system is up to date:  * 20-01:46:44 (3361) [INFO] Running: /usr/bin/yum clean all * 20-01:46:44 (3362) [INFO]  * 20-01:46:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:46:45 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 20-01:46:45 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-01:46:45 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 20-01:46:45 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 20-01:46:45 (3372) [INFO] Cleaning up list of fastest mirrors * 20-01:46:45 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 20-01:46:45 (3382) [INFO]  * 20-01:46:45 (3361) [INFO] Running: /usr/bin/yum check-update * 20-01:46:45 (3362) [INFO]  * 20-01:46:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:46:46 (3372) [INFO] Determining fastest mirrors * 20-01:48:15 (3372) [INFO] * EA4: 184.94.196.93 * 20-01:48:15 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 20-01:48:15 (3372) [INFO] * cpanel-plugins: 184.94.196.93 * 20-01:48:15 (3372) [INFO] * base: mirror.keystealth.org * 20-01:48:15 (3372) [INFO] * epel: mirrors.xmission.com * 20-01:48:15 (3372) [INFO] * extras: mirror.web-ster.com * 20-01:48:15 (3372) [INFO] * updates: mirror.chpc.utah.edu * 20-01:51:00 (3372) [INFO]  * 20-01:51:00 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 20-01:51:00 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-01:51:00 (3382) [INFO]  * 20-01:51:00 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-01:51:00 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-01:51:00 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 20-01:51:00 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-01:51:00 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-01:51:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-20_01:51:03_modified_for_AlmaLinux_8.json * 20-01:51: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 20-01:59: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.  * 20-01:59:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-01:41:16 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 21-01:41:20 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 21-01:41: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  * 21-01:43:50 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 21-01:43:50 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 21-01:43:50 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 21-01:43:50 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 21-01:43:50 (2925) [INFO] Checking if your system is up to date:  * 21-01:43:50 (3361) [INFO] Running: /usr/bin/yum clean all * 21-01:43:50 (3362) [INFO]  * 21-01:43:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:43:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 21-01:43:51 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-01:43:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 21-01:43:51 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 21-01:43:51 (3372) [INFO] Cleaning up list of fastest mirrors * 21-01:43:51 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 21-01:43:51 (3382) [INFO]  * 21-01:43:51 (3361) [INFO] Running: /usr/bin/yum check-update * 21-01:43:51 (3362) [INFO]  * 21-01:43:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:43:53 (3372) [INFO] Determining fastest mirrors * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] One of the configured repositories failed (Unknown), * 21-01:44:52 (3372) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 21-01:44:52 (3372) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 21-01:44:52 (3372) [INFO] upstream. This is most often useful if you are using a newer * 21-01:44:52 (3372) [INFO] distribution release than is supported by the repository (and the * 21-01:44:52 (3372) [INFO] packages for the previous distribution release still work). * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] 3. Run the command with the repository temporarily disabled * 21-01:44:52 (3372) [INFO] yum --disablerepo= ... * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 21-01:44:52 (3372) [INFO] will then just ignore the repository until you permanently enable it * 21-01:44:52 (3372) [INFO] again or use --enablerepo for temporary usage: * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] yum-config-manager --disable  * 21-01:44:52 (3372) [INFO] or * 21-01:44:52 (3372) [INFO] subscription-manager repos --disable= * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 21-01:44:52 (3372) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 21-01:44:52 (3372) [INFO] so will have to try and fail each time (and thus. yum will be be much * 21-01:44:52 (3372) [INFO] slower). If it is a very temporary problem though, this is often a nice * 21-01:44:52 (3372) [INFO] compromise: * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 21-01:44:52 (3372) [INFO]  * 21-01:44:52 (3372) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 21-01:44:52 (3382) [INFO]  * 21-01:44:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-01:44:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-01:44:52 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 21-01:44:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-01:44:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-01:49:11 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-21_01:49:11_modified_for_AlmaLinux_8.json * 21-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 21-01:57: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.  * 21-01:57:40 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-01:45:02 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 22-01:45:10 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 22-01:45: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  * 22-01:47:54 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 22-01:47:54 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 22-01:47:55 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 22-01:47:55 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 22-01:47:55 (2925) [INFO] Checking if your system is up to date:  * 22-01:47:55 (3361) [INFO] Running: /usr/bin/yum clean all * 22-01:47:55 (3362) [INFO]  * 22-01:47:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:47:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 22-01:47:56 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-01:47:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 22-01:47:56 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 22-01:47:56 (3372) [INFO] Cleaning up list of fastest mirrors * 22-01:47:56 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 22-01:47:56 (3382) [INFO]  * 22-01:47:56 (3361) [INFO] Running: /usr/bin/yum check-update * 22-01:47:56 (3362) [INFO]  * 22-01:47:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:47:58 (3372) [INFO] Determining fastest mirrors * 22-01:49:26 (3372) [INFO] * EA4: 208.74.123.62 * 22-01:49:26 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 22-01:49:26 (3372) [INFO] * cpanel-plugins: 208.74.123.62 * 22-01:49:26 (3372) [INFO] * base: mirror.chpc.utah.edu * 22-01:49:26 (3372) [INFO] * epel: mirrors.xmission.com * 22-01:49:26 (3372) [INFO] * extras: repos.forethought.net * 22-01:49:26 (3372) [INFO] * updates: mirror.fcix.net * 22-01:52:38 (3372) [INFO]  * 22-01:52:38 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 22-01:52:38 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-01:52:38 (3382) [INFO]  * 22-01:52:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-01:52:38 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-01:52:38 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 22-01:52:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-01:52:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-01:52:46 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-22_01:52:46_modified_for_AlmaLinux_8.json * 22-01:52: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 22-02:01:15 (2504) [WARN] *** Elevation Blocker detected: *** This script does not appear to be the newest available release. Please download the latest version from the following URL and try again: wget -O /scripts/elevate-cpanel https://raw.githubusercontent.com/cpanel/elevate/release/elevate-cpanel ; chmod 700 /scripts/elevate-cpanel Pass the --skip-elevate-version-check flag to skip this check.  * 22-02:01:15 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-01:43:01 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 23-01:43:06 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 23-01:43:06 (2504) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues  * 23-01:45:35 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 23-01:45:35 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30362 milliseconds')  * 23-01:45:35 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 23-01:45:35 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 23-01:45:35 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 23-01:45:35 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 23-01:45:35 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 23-01:45:35 (2925) [INFO] Checking if your system is up to date:  * 23-01:45:35 (3361) [INFO] Running: /usr/bin/yum clean all * 23-01:45:35 (3362) [INFO]  * 23-01:45:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:45:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 23-01:45:36 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-01:45:36 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 23-01:45:36 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 23-01:45:36 (3372) [INFO] Cleaning up list of fastest mirrors * 23-01:45:36 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 23-01:45:37 (3382) [INFO]  * 23-01:45:37 (3361) [INFO] Running: /usr/bin/yum check-update * 23-01:45:37 (3362) [INFO]  * 23-01:45:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:45:38 (3372) [INFO] Determining fastest mirrors * 23-01:47:06 (3372) [INFO] * EA4: 208.74.123.61 * 23-01:47:06 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 23-01:47:06 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 23-01:47:06 (3372) [INFO] * base: repos.forethought.net * 23-01:47:06 (3372) [INFO] * epel: mirrors.xmission.com * 23-01:47:06 (3372) [INFO] * extras: centos-distro.1gservers.com * 23-01:47:06 (3372) [INFO] * updates: mirror.hostduplex.com * 23-01:49:38 (3372) [INFO]  * 23-01:49:38 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 23-01:49:38 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-01:49:38 (3382) [INFO]  * 23-01:49:38 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-01:49:38 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-01:49:38 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 23-01:49:38 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-01:49:38 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-01:49:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-23_01:49:41_modified_for_AlmaLinux_8.json * 23-01:49: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 23-01:58: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.  * 23-01:58:10 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-01:43:06 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 24-01:43:11 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 24-01:43: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-01:46:12 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 24-01:46:12 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 24-01:46:13 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 24-01:46:13 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 24-01:46:13 (2925) [INFO] Checking if your system is up to date:  * 24-01:46:13 (3361) [INFO] Running: /usr/bin/yum clean all * 24-01:46:13 (3362) [INFO]  * 24-01:46:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:46:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 24-01:46:13 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-01:46:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 24-01:46:13 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 24-01:46:14 (3372) [INFO] Cleaning up list of fastest mirrors * 24-01:46:14 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 24-01:46:14 (3382) [INFO]  * 24-01:46:14 (3361) [INFO] Running: /usr/bin/yum check-update * 24-01:46:14 (3362) [INFO]  * 24-01:46:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:46:15 (3372) [INFO] Determining fastest mirrors * 24-01:47:46 (3372) [INFO] * EA4: 184.94.196.92 * 24-01:47:46 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 24-01:47:46 (3372) [INFO] * cpanel-plugins: 184.94.196.92 * 24-01:47:46 (3372) [INFO] * base: mirror.keystealth.org * 24-01:47:46 (3372) [INFO] * epel: mirrors.xmission.com * 24-01:47:46 (3372) [INFO] * extras: centos.mirror.shastacoe.net * 24-01:47:46 (3372) [INFO] * updates: mirror.chpc.utah.edu * 24-01:50:47 (3372) [INFO]  * 24-01:50:47 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 24-01:50:47 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-01:50:47 (3382) [INFO]  * 24-01:50:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-01:50:47 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-01:50:47 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 24-01:50:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-01:50:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-01:50:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-24_01:50:50_modified_for_AlmaLinux_8.json * 24-01:50: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 24-01:59: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.  * 24-01:59:20 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-01:44:13 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 25-01:44:18 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 25-01:44: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  * 25-01:47:18 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 25-01:47:18 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 25-01:47:19 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 25-01:47:19 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 25-01:47:19 (2925) [INFO] Checking if your system is up to date:  * 25-01:47:19 (3361) [INFO] Running: /usr/bin/yum clean all * 25-01:47:19 (3362) [INFO]  * 25-01:47:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:47:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 25-01:47:20 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-01:47:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 25-01:47:20 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 25-01:47:20 (3372) [INFO] Cleaning up list of fastest mirrors * 25-01:47:20 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 25-01:47:20 (3382) [INFO]  * 25-01:47:20 (3361) [INFO] Running: /usr/bin/yum check-update * 25-01:47:20 (3362) [INFO]  * 25-01:47:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:47:22 (3372) [INFO] Determining fastest mirrors * 25-01:48:49 (3372) [INFO] * EA4: 208.74.123.61 * 25-01:48:49 (3372) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 25-01:48:49 (3372) [INFO] * cpanel-plugins: 208.74.123.61 * 25-01:48:49 (3372) [INFO] * base: mirrors.xmission.com * 25-01:48:49 (3372) [INFO] * epel: mirrors.xmission.com * 25-01:48:49 (3372) [INFO] * extras: mirror.grid.uchicago.edu * 25-01:48:49 (3372) [INFO] * updates: repos.forethought.net * 25-01:52:11 (3372) [INFO]  * 25-01:52:11 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 25-01:52:11 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-01:52:12 (3382) [INFO]  * 25-01:52:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-01:52:12 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-01:52:12 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 25-01:52:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-01:52:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-01:52:17 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-25_01:52:17_modified_for_AlmaLinux_8.json * 25-01:52:17 (2504) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 25-02:00: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.  * 25-02:00:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:42:40 (2504) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:42:43 (3018) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:42: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  * 26-01:45:54 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 26-01:45:54 (3077) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/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://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/69931c21fa7f874d0698f938dc881181fd4612395ead63fa23dd676d2783443c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/69931c21fa7f874d0698f938dc881181fd4612395ead63fa23dd676d2783443c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. One of the configured repositories failed (MariaDB100), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=MariaDB100 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable MariaDB100 or subscription-manager repos --disable=MariaDB100 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true failure: repodata/69931c21fa7f874d0698f938dc881181fd4612395ead63fa23dd676d2783443c-other.sqlite.bz2 from MariaDB100: [Errno 256] No more mirrors to try. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/69931c21fa7f874d0698f938dc881181fd4612395ead63fa23dd676d2783443c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found  * 26-01:45:54 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 26-01:45:54 (3103) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:45:54 (2504) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:45:54 (2946) [WARN] JetBackup version 4.1.3-3 currently installed. * 26-01:45:54 (2504) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:45:54 (2925) [INFO] Checking if your system is up to date:  * 26-01:45:54 (3361) [INFO] Running: /usr/bin/yum clean all * 26-01:45:54 (3362) [INFO]  * 26-01:45:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:45:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:45:55 (3372) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:45:55 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:45:55 (3372) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 26-01:45:56 (3372) [INFO] Cleaning up list of fastest mirrors * 26-01:45:56 (3372) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 26-01:45:56 (3382) [INFO]  * 26-01:45:56 (3361) [INFO] Running: /usr/bin/yum check-update * 26-01:45:56 (3362) [INFO]  * 26-01:45:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:45:57 (3372) [INFO] Determining fastest mirrors * 26-01:47:25 (3372) [INFO] * EA4: 184.94.196.94 * 26-01:47:25 (3372) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 26-01:47:25 (3372) [INFO] * cpanel-plugins: 184.94.196.94 * 26-01:47:25 (3372) [INFO] * base: mirrors.xmission.com * 26-01:47:25 (3372) [INFO] * epel: mirrors.xmission.com * 26-01:47:25 (3372) [INFO] * extras: mirror.chpc.utah.edu * 26-01:47:25 (3372) [INFO] * updates: mirrors.oit.uci.edu * 26-01:47:41 (3372) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 26-01:47:41 (3372) [INFO] Trying other mirror. * 26-01:47:41 (3372) [INFO] To address this issue please refer to the below wiki article  * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] https://wiki.centos.org/yum-errors * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] One of the configured repositories failed (MariaDB100), * 26-01:47:41 (3372) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 26-01:47:41 (3372) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 26-01:47:41 (3372) [INFO] upstream. This is most often useful if you are using a newer * 26-01:47:41 (3372) [INFO] distribution release than is supported by the repository (and the * 26-01:47:41 (3372) [INFO] packages for the previous distribution release still work). * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] 3. Run the command with the repository temporarily disabled * 26-01:47:41 (3372) [INFO] yum --disablerepo=MariaDB100 ... * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 26-01:47:41 (3372) [INFO] will then just ignore the repository until you permanently enable it * 26-01:47:41 (3372) [INFO] again or use --enablerepo for temporary usage: * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] yum-config-manager --disable MariaDB100 * 26-01:47:41 (3372) [INFO] or * 26-01:47:41 (3372) [INFO] subscription-manager repos --disable=MariaDB100 * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 26-01:47:41 (3372) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 26-01:47:41 (3372) [INFO] so will have to try and fail each time (and thus. yum will be be much * 26-01:47:41 (3372) [INFO] slower). If it is a very temporary problem though, this is often a nice * 26-01:47:41 (3372) [INFO] compromise: * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true * 26-01:47:41 (3372) [INFO]  * 26-01:47:41 (3372) [INFO] failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. * 26-01:47:41 (3372) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 26-01:47:41 (3382) [INFO]  * 26-01:47:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:47:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:47:41 (2504) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:47:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-01:47:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-01:47:59 (2475) [WARN] Unkown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 at /usr/local/cpanel/scripts/elevate-cpanel line 1450.  * 26-01:47:59 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:52:03 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:52:06 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:52:06 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:53:49 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 26-01:53:49 (3473) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/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/. One of the configured repositories failed (MariaDB100), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=MariaDB100 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable MariaDB100 or subscription-manager repos --disable=MariaDB100 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found  * 26-01:53:49 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 26-01:53:49 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:53:49 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:53:49 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 26-01:53:49 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:53:49 (3321) [INFO] Checking if your system is up to date:  * 26-01:53:49 (3766) [INFO] Running: /usr/bin/yum clean all * 26-01:53:49 (3767) [INFO]  * 26-01:53:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:53:50 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:53:50 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:53:50 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:53:50 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 26-01:53:50 (3777) [INFO] Cleaning up list of fastest mirrors * 26-01:53:50 (3777) [INFO] Other repos take up 648 k of disk space (use --verbose for details) * 26-01:53:50 (3787) [INFO]  * 26-01:53:50 (3766) [INFO] Running: /usr/bin/yum check-update * 26-01:53:50 (3767) [INFO]  * 26-01:53:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:53:51 (3777) [INFO] Determining fastest mirrors * 26-01:55:21 (3777) [INFO] * EA4: 208.74.123.62 * 26-01:55:21 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 26-01:55:21 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 26-01:55:21 (3777) [INFO] * base: mirrors.xmission.com * 26-01:55:21 (3777) [INFO] * epel: mirrors.xmission.com * 26-01:55:21 (3777) [INFO] * extras: mirror.chpc.utah.edu * 26-01:55:21 (3777) [INFO] * updates: mirror.keystealth.org * 26-01:55:36 (3777) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 26-01:55:36 (3777) [INFO] Trying other mirror. * 26-01:55:36 (3777) [INFO] To address this issue please refer to the below wiki article  * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] https://wiki.centos.org/yum-errors * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] One of the configured repositories failed (MariaDB100), * 26-01:55:36 (3777) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 26-01:55:36 (3777) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 26-01:55:36 (3777) [INFO] upstream. This is most often useful if you are using a newer * 26-01:55:36 (3777) [INFO] distribution release than is supported by the repository (and the * 26-01:55:36 (3777) [INFO] packages for the previous distribution release still work). * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] 3. Run the command with the repository temporarily disabled * 26-01:55:36 (3777) [INFO] yum --disablerepo=MariaDB100 ... * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 26-01:55:36 (3777) [INFO] will then just ignore the repository until you permanently enable it * 26-01:55:36 (3777) [INFO] again or use --enablerepo for temporary usage: * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] yum-config-manager --disable MariaDB100 * 26-01:55:36 (3777) [INFO] or * 26-01:55:36 (3777) [INFO] subscription-manager repos --disable=MariaDB100 * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 26-01:55:36 (3777) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 26-01:55:36 (3777) [INFO] so will have to try and fail each time (and thus. yum will be be much * 26-01:55:36 (3777) [INFO] slower). If it is a very temporary problem though, this is often a nice * 26-01:55:36 (3777) [INFO] compromise: * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true * 26-01:55:36 (3777) [INFO]  * 26-01:55:36 (3777) [INFO] failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. * 26-01:55:36 (3777) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 26-01:55:37 (3787) [INFO]  * 26-01:55:37 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:55:37 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:55:37 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:55:37 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 26-01:55:37 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X72DpSxi1t/ea_profile.json * 26-01:55:56 (2634) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X72DpSxi1t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1596.  * 26-01:55:56 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 27-01:44:12 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 27-01:44:16 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 27-01:44:16 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:16 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 27-01:47:16 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 27-01:47:17 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 27-01:47:17 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 27-01:47:17 (3321) [INFO] Checking if your system is up to date:  * 27-01:47:17 (3766) [INFO] Running: /usr/bin/yum clean all * 27-01:47:17 (3767) [INFO]  * 27-01:47:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:47:18 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 27-01:47:18 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-01:47:18 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 27-01:47:18 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 27-01:47:18 (3777) [INFO] Cleaning up list of fastest mirrors * 27-01:47:18 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 27-01:47:18 (3787) [INFO]  * 27-01:47:18 (3766) [INFO] Running: /usr/bin/yum check-update * 27-01:47:18 (3767) [INFO]  * 27-01:47:19 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:47:20 (3777) [INFO] Determining fastest mirrors * 27-01:48:49 (3777) [INFO] * EA4: 208.74.123.62 * 27-01:48:49 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 27-01:48:49 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 27-01:48:49 (3777) [INFO] * base: mirrors.xtom.com * 27-01:48:49 (3777) [INFO] * epel: mirrors.xmission.com * 27-01:48:49 (3777) [INFO] * extras: mirror.chpc.utah.edu * 27-01:48:49 (3777) [INFO] * updates: tx-mirror.tier.net * 27-01:51:55 (3777) [INFO]  * 27-01:51:55 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 27-01:51:55 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-01:51:55 (3787) [INFO]  * 27-01:51:55 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-01:51:55 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-01:51:55 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 27-01:51:55 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 27-01:51:55 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/te2dwW5nYq/ea_profile.json * 27-01:51:58 (1619) [INFO] Backed up EA4 profile to /tmp/te2dwW5nYq/ea_profile.json * 27-01:51:58 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 27-01:55:59 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 27-01:55:59 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 28-01:43:52 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 28-01:43:57 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 28-01:43:57 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:56 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 28-01:46:56 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 28-01:46:57 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 28-01:46:57 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 28-01:46:57 (3321) [INFO] Checking if your system is up to date:  * 28-01:46:57 (3766) [INFO] Running: /usr/bin/yum clean all * 28-01:46:57 (3767) [INFO]  * 28-01:46:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:46:57 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 28-01:46:57 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-01:46:57 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 28-01:46:57 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 28-01:46:58 (3777) [INFO] Cleaning up list of fastest mirrors * 28-01:46:58 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 28-01:46:58 (3787) [INFO]  * 28-01:46:58 (3766) [INFO] Running: /usr/bin/yum check-update * 28-01:46:58 (3767) [INFO]  * 28-01:46:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:46:59 (3777) [INFO] Determining fastest mirrors * 28-01:48:30 (3777) [INFO] * EA4: 208.74.123.61 * 28-01:48:30 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 28-01:48:30 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 28-01:48:30 (3777) [INFO] * base: la.mirrors.clouvider.net * 28-01:48:30 (3777) [INFO] * epel: mirrors.xmission.com * 28-01:48:30 (3777) [INFO] * extras: mirrors.xtom.com * 28-01:48:30 (3777) [INFO] * updates: mirrors.sonic.net * 28-01:51:38 (3777) [INFO]  * 28-01:51:38 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 28-01:51:38 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-01:51:39 (3787) [INFO]  * 28-01:51:39 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-01:51:39 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-01:51:39 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 28-01:51:39 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 28-01:51:39 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bZACOGHUCZ/ea_profile.json * 28-01:51:42 (1619) [INFO] Backed up EA4 profile to /tmp/bZACOGHUCZ/ea_profile.json * 28-01:51:42 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 28-01:55:43 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 28-01:55:43 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 29-01:43:19 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 29-01:43:25 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 29-01:43:25 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:57 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 29-01:45:57 (3473) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30315 milliseconds')  * 29-01:45:57 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 29-01:45:57 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 29-01:45:57 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 29-01:45:58 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 29-01:45:58 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 29-01:45:58 (3321) [INFO] Checking if your system is up to date:  * 29-01:45:58 (3766) [INFO] Running: /usr/bin/yum clean all * 29-01:45:58 (3767) [INFO]  * 29-01:45:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:45:59 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 29-01:45:59 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-01:45:59 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 29-01:45:59 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 29-01:45:59 (3777) [INFO] Cleaning up list of fastest mirrors * 29-01:45:59 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 29-01:45:59 (3787) [INFO]  * 29-01:45:59 (3766) [INFO] Running: /usr/bin/yum check-update * 29-01:45:59 (3767) [INFO]  * 29-01:45:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:46:00 (3777) [INFO] Determining fastest mirrors * 29-01:47:30 (3777) [INFO] * EA4: 184.94.196.97 * 29-01:47:30 (3777) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 29-01:47:30 (3777) [INFO] * cpanel-plugins: 184.94.196.97 * 29-01:47:30 (3777) [INFO] * base: repos.forethought.net * 29-01:47:30 (3777) [INFO] * epel: mirrors.xmission.com * 29-01:47:30 (3777) [INFO] * extras: mirror.dal.nexril.net * 29-01:47:30 (3777) [INFO] * updates: la.mirrors.clouvider.net * 29-01:50:13 (3777) [INFO]  * 29-01:50:13 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 29-01:50:13 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-01:50:13 (3787) [INFO]  * 29-01:50:13 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-01:50:13 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-01:50:13 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 29-01:50:13 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 29-01:50:13 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jfTJsaKZc5/ea_profile.json * 29-01:50:16 (1619) [INFO] Backed up EA4 profile to /tmp/jfTJsaKZc5/ea_profile.json * 29-01:50:16 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 29-01:54:17 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 29-01:54:17 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:44:37 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:44:42 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:44:42 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:26 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 30-01:47:26 (3473) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30314 milliseconds')  * 30-01:47:26 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 30-01:47:26 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:47:26 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:47:26 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 30-01:47:26 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:47:26 (3321) [INFO] Checking if your system is up to date:  * 30-01:47:26 (3766) [INFO] Running: /usr/bin/yum clean all * 30-01:47:26 (3767) [INFO]  * 30-01:47:27 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:47:27 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:47:27 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:47:27 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:47:27 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 30-01:47:27 (3777) [INFO] Cleaning up list of fastest mirrors * 30-01:47:27 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 30-01:47:27 (3787) [INFO]  * 30-01:47:27 (3766) [INFO] Running: /usr/bin/yum check-update * 30-01:47:27 (3767) [INFO]  * 30-01:47:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:47:29 (3777) [INFO] Determining fastest mirrors * 30-01:48:58 (3777) [INFO] * EA4: 208.74.123.61 * 30-01:48:58 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 30-01:48:58 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 30-01:48:58 (3777) [INFO] * base: mirrors.xmission.com * 30-01:48:58 (3777) [INFO] * epel: mirrors.xmission.com * 30-01:48:58 (3777) [INFO] * extras: mirror.hostduplex.com * 30-01:48:58 (3777) [INFO] * updates: abqix.mm.fcix.net * 30-01:51:46 (3777) [INFO]  * 30-01:51:46 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 30-01:51:46 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-01:51:47 (3787) [INFO]  * 30-01:51:47 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-01:51:47 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-01:51:47 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-01:51:47 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 30-01:51:47 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GgmzpqJCK2/ea_profile.json * 30-01:51:50 (1619) [INFO] Backed up EA4 profile to /tmp/GgmzpqJCK2/ea_profile.json * 30-01:51:50 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 30-01:55:51 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 30-01:55:51 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 31-01:43:30 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 31-01:43:35 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 31-01:43:35 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:20 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 31-01:46:20 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 31-01:46:21 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 31-01:46:21 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 31-01:46:21 (3321) [INFO] Checking if your system is up to date:  * 31-01:46:21 (3766) [INFO] Running: /usr/bin/yum clean all * 31-01:46:21 (3767) [INFO]  * 31-01:46:21 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:46:21 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 31-01:46:21 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-01:46:21 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 31-01:46:21 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 31-01:46:22 (3777) [INFO] Cleaning up list of fastest mirrors * 31-01:46:22 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 31-01:46:22 (3787) [INFO]  * 31-01:46:22 (3766) [INFO] Running: /usr/bin/yum check-update * 31-01:46:22 (3767) [INFO]  * 31-01:46:23 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:46:24 (3777) [INFO] Determining fastest mirrors * 31-01:47:53 (3777) [INFO] * EA4: 208.74.123.62 * 31-01:47:53 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 31-01:47:53 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 31-01:47:53 (3777) [INFO] * base: ridgewireless.mm.fcix.net * 31-01:47:53 (3777) [INFO] * epel: mirrors.xmission.com * 31-01:47:53 (3777) [INFO] * extras: mirror.web-ster.com * 31-01:47:53 (3777) [INFO] * updates: mirror.keystealth.org * 31-01:50:34 (3777) [INFO]  * 31-01:50:34 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 31-01:50:34 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-01:50:35 (3787) [INFO]  * 31-01:50:35 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-01:50:35 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-01:50:35 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 31-01:50:35 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 31-01:50:35 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xEYI0XlloX/ea_profile.json * 31-01:50:38 (1619) [INFO] Backed up EA4 profile to /tmp/xEYI0XlloX/ea_profile.json * 31-01:50:38 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 31-01:54:38 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 31-01:54:38 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 01-01:43:50 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 01-01:43:53 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 01-01:43:53 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:38 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 01-01:46:38 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 01-01:46:39 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 01-01:46:39 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 01-01:46:39 (3321) [INFO] Checking if your system is up to date:  * 01-01:46:39 (3766) [INFO] Running: /usr/bin/yum clean all * 01-01:46:39 (3767) [INFO]  * 01-01:46:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:46:40 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 01-01:46:40 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-01:46:40 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 01-01:46:40 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 01-01:46:40 (3777) [INFO] Cleaning up list of fastest mirrors * 01-01:46:40 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 01-01:46:40 (3787) [INFO]  * 01-01:46:40 (3766) [INFO] Running: /usr/bin/yum check-update * 01-01:46:40 (3767) [INFO]  * 01-01:46:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:46:41 (3777) [INFO] Determining fastest mirrors * 01-01:48:11 (3777) [INFO] * EA4: 208.74.123.61 * 01-01:48:11 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 01-01:48:11 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 01-01:48:11 (3777) [INFO] * base: mirrors.ocf.berkeley.edu * 01-01:48:11 (3777) [INFO] * epel: mirrors.xmission.com * 01-01:48:11 (3777) [INFO] * extras: mirror.facebook.net * 01-01:48:11 (3777) [INFO] * updates: mirror.chpc.utah.edu * 01-01:50:45 (3777) [INFO]  * 01-01:50:45 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 01-01:50:45 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-01:50:45 (3787) [INFO]  * 01-01:50:45 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-01:50:45 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-01:50:45 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 01-01:50:45 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 01-01:50:45 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LiDvi6LF_T/ea_profile.json * 01-01:50:47 (1619) [INFO] Backed up EA4 profile to /tmp/LiDvi6LF_T/ea_profile.json * 01-01:50:47 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 01-01:54:47 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 01-01:54:47 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 02-01:42:33 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 02-01:42:38 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 02-01:42:38 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:22 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 02-01:45:22 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 02-01:45:23 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 02-01:45:23 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 02-01:45:23 (3321) [INFO] Checking if your system is up to date:  * 02-01:45:23 (3766) [INFO] Running: /usr/bin/yum clean all * 02-01:45:23 (3767) [INFO]  * 02-01:45:24 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:45:24 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 02-01:45:24 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-01:45:24 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 02-01:45:24 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 02-01:45:24 (3777) [INFO] Cleaning up list of fastest mirrors * 02-01:45:24 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 02-01:45:25 (3787) [INFO]  * 02-01:45:25 (3766) [INFO] Running: /usr/bin/yum check-update * 02-01:45:25 (3767) [INFO]  * 02-01:45:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:45:26 (3777) [INFO] Determining fastest mirrors * 02-01:46:56 (3777) [INFO] * EA4: 208.74.123.61 * 02-01:46:56 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 02-01:46:56 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 02-01:46:56 (3777) [INFO] * base: repos.forethought.net * 02-01:46:56 (3777) [INFO] * epel: mirrors.xmission.com * 02-01:46:56 (3777) [INFO] * extras: mirrors.xmission.com * 02-01:46:56 (3777) [INFO] * updates: mirrors.raystedman.org * 02-01:49:44 (3777) [INFO]  * 02-01:49:44 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 02-01:49:44 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-01:49:44 (3787) [INFO]  * 02-01:49:44 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-01:49:44 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-01:49:44 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 02-01:49:44 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 02-01:49:44 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BWFU5GMTQa/ea_profile.json * 02-01:49:47 (1619) [INFO] Backed up EA4 profile to /tmp/BWFU5GMTQa/ea_profile.json * 02-01:49:47 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 02-01:53:47 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 02-01:53:47 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 03-01:45:41 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 03-01:45:44 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 03-01:45:44 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:27 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 03-01:48:27 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 03-01:48:28 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 03-01:48:28 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 03-01:48:28 (3321) [INFO] Checking if your system is up to date:  * 03-01:48:28 (3766) [INFO] Running: /usr/bin/yum clean all * 03-01:48:28 (3767) [INFO]  * 03-01:48:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:48:29 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 03-01:48:29 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-01:48:29 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 03-01:48:29 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 03-01:48:29 (3777) [INFO] Cleaning up list of fastest mirrors * 03-01:48:29 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 03-01:48:29 (3787) [INFO]  * 03-01:48:29 (3766) [INFO] Running: /usr/bin/yum check-update * 03-01:48:29 (3767) [INFO]  * 03-01:48:30 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:48:31 (3777) [INFO] Determining fastest mirrors * 03-01:49:59 (3777) [INFO] * EA4: 208.74.123.61 * 03-01:49:59 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 03-01:49:59 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 03-01:49:59 (3777) [INFO] * base: mirrors.xmission.com * 03-01:49:59 (3777) [INFO] * epel: mirrors.xmission.com * 03-01:49:59 (3777) [INFO] * extras: ridgewireless.mm.fcix.net * 03-01:49:59 (3777) [INFO] * updates: mirrors.xmission.com * 03-01:52:58 (3777) [INFO]  * 03-01:52:58 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 03-01:52:58 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-01:52:58 (3787) [INFO]  * 03-01:52:58 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-01:52:58 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-01:52:58 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 03-01:52:58 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 03-01:52:58 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fc00uBDLTS/ea_profile.json * 03-01:53:05 (1619) [INFO] Backed up EA4 profile to /tmp/fc00uBDLTS/ea_profile.json * 03-01:53:05 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 03-01:57:06 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 03-01:57:06 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 04-01:45:35 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 04-01:45:41 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 04-01:45:41 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:41 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 04-01:48:41 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 04-01:48:42 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 04-01:48:42 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 04-01:48:42 (3321) [INFO] Checking if your system is up to date:  * 04-01:48:42 (3766) [INFO] Running: /usr/bin/yum clean all * 04-01:48:42 (3767) [INFO]  * 04-01:48:42 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:48:43 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 04-01:48:43 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-01:48:43 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 04-01:48:43 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 04-01:48:43 (3777) [INFO] Cleaning up list of fastest mirrors * 04-01:48:43 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 04-01:48:43 (3787) [INFO]  * 04-01:48:43 (3766) [INFO] Running: /usr/bin/yum check-update * 04-01:48:43 (3767) [INFO]  * 04-01:48:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:48:44 (3777) [INFO] Determining fastest mirrors * 04-01:50:12 (3777) [INFO] * EA4: 208.74.123.61 * 04-01:50:12 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 04-01:50:12 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 04-01:50:12 (3777) [INFO] * base: mirrors.xmission.com * 04-01:50:12 (3777) [INFO] * epel: mirrors.xmission.com * 04-01:50:13 (3777) [INFO] * extras: or-mirror.iwebfusion.net * 04-01:50:13 (3777) [INFO] * updates: mirror.keystealth.org * 04-01:53:14 (3777) [INFO]  * 04-01:53:14 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 04-01:53:14 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-01:53:15 (3787) [INFO]  * 04-01:53:15 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-01:53:15 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-01:53:15 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 04-01:53:15 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 04-01:53:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jhAVXy_XQH/ea_profile.json * 04-01:53:18 (1619) [INFO] Backed up EA4 profile to /tmp/jhAVXy_XQH/ea_profile.json * 04-01:53:18 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 04-01:57:19 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 04-01:57:19 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 05-01:44:50 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 05-01:44:55 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 05-01:44:55 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:41 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 05-01:47:41 (3473) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30111 milliseconds')  * 05-01:47:41 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 05-01:47:41 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 05-01:47:41 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 05-01:47:42 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 05-01:47:42 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 05-01:47:42 (3321) [INFO] Checking if your system is up to date:  * 05-01:47:42 (3766) [INFO] Running: /usr/bin/yum clean all * 05-01:47:42 (3767) [INFO]  * 05-01:47:43 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:47:43 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 05-01:47:43 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-01:47:43 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 05-01:47:43 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 05-01:47:44 (3777) [INFO] Cleaning up list of fastest mirrors * 05-01:47:44 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 05-01:47:44 (3787) [INFO]  * 05-01:47:44 (3766) [INFO] Running: /usr/bin/yum check-update * 05-01:47:44 (3767) [INFO]  * 05-01:47:44 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:47:45 (3777) [INFO] Determining fastest mirrors * 05-01:49:14 (3777) [INFO] * EA4: 208.74.123.61 * 05-01:49:14 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 05-01:49:14 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 05-01:49:14 (3777) [INFO] * base: mirrors.sonic.net * 05-01:49:14 (3777) [INFO] * epel: mirrors.xmission.com * 05-01:49:14 (3777) [INFO] * extras: mirror.chpc.utah.edu * 05-01:49:14 (3777) [INFO] * updates: mirror.hostduplex.com * 05-01:52:15 (3777) [INFO]  * 05-01:52:15 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 05-01:52:15 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-01:52:16 (3787) [INFO]  * 05-01:52:16 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-01:52:16 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-01:52:16 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 05-01:52:16 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 05-01:52:16 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2PfbtR_9cp/ea_profile.json * 05-01:52:22 (1619) [INFO] Backed up EA4 profile to /tmp/2PfbtR_9cp/ea_profile.json * 05-01:52:22 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 05-01:56:22 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 05-01:56:22 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 06-01:43:46 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 06-01:43:50 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 06-01:43:50 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:33 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 06-01:46:33 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 06-01:46:34 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 06-01:46:34 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 06-01:46:34 (3321) [INFO] Checking if your system is up to date:  * 06-01:46:34 (3766) [INFO] Running: /usr/bin/yum clean all * 06-01:46:34 (3767) [INFO]  * 06-01:46:34 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:46:34 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 06-01:46:34 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-01:46:34 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 06-01:46:34 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 06-01:46:35 (3777) [INFO] Cleaning up list of fastest mirrors * 06-01:46:35 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 06-01:46:35 (3787) [INFO]  * 06-01:46:35 (3766) [INFO] Running: /usr/bin/yum check-update * 06-01:46:35 (3767) [INFO]  * 06-01:46:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:46:36 (3777) [INFO] Determining fastest mirrors * 06-01:48:05 (3777) [INFO] * EA4: 208.74.123.61 * 06-01:48:05 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 06-01:48:05 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 06-01:48:05 (3777) [INFO] * base: repos.forethought.net * 06-01:48:05 (3777) [INFO] * epel: mirrors.xmission.com * 06-01:48:05 (3777) [INFO] * extras: mirror.fcix.net * 06-01:48:05 (3777) [INFO] * updates: centos-distro.cavecreek.net * 06-01:50:53 (3777) [INFO]  * 06-01:50:53 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 06-01:50:53 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-01:50:54 (3787) [INFO]  * 06-01:50:54 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-01:50:54 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-01:50:54 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 06-01:50:54 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 06-01:50:54 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T9OAKnJJcN/ea_profile.json * 06-01:50:57 (1619) [INFO] Backed up EA4 profile to /tmp/T9OAKnJJcN/ea_profile.json * 06-01:50:57 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 06-01:54:58 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 06-01:54:58 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 07-00:43:55 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 07-00:44:00 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 07-00:44:00 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-00:46:44 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 07-00:46:44 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 07-00:46:45 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 07-00:46:45 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 07-00:46:45 (3321) [INFO] Checking if your system is up to date:  * 07-00:46:45 (3766) [INFO] Running: /usr/bin/yum clean all * 07-00:46:45 (3767) [INFO]  * 07-00:46:45 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-00:46:45 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 07-00:46:45 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-00:46:45 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 07-00:46:45 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 07-00:46:46 (3777) [INFO] Cleaning up list of fastest mirrors * 07-00:46:46 (3777) [INFO] Other repos take up 304 k of disk space (use --verbose for details) * 07-00:46:46 (3787) [INFO]  * 07-00:46:46 (3766) [INFO] Running: /usr/bin/yum check-update * 07-00:46:46 (3767) [INFO]  * 07-00:46:46 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-00:46:47 (3777) [INFO] Determining fastest mirrors * 07-00:48:15 (3777) [INFO] * EA4: 208.74.123.61 * 07-00:48:15 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 07-00:48:15 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 07-00:48:15 (3777) [INFO] * base: mirror.sfo12.us.leaseweb.net * 07-00:48:15 (3777) [INFO] * epel: mirrors.xmission.com * 07-00:48:15 (3777) [INFO] * extras: mirrors.raystedman.org * 07-00:48:15 (3777) [INFO] * updates: mirror.fcix.net * 07-00:51:15 (3777) [INFO]  * 07-00:51:15 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 07-00:51:15 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-00:51:16 (3787) [INFO]  * 07-00:51:16 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-00:51:16 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-00:51:16 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 07-00:51:16 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 07-00:51:16 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FF08ZMc6NF/ea_profile.json * 07-00:51:18 (1619) [INFO] Backed up EA4 profile to /tmp/FF08ZMc6NF/ea_profile.json * 07-00:51:18 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 07-00:55:18 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 07-00:55:18 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 08-01:38:05 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 08-01:38:10 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 08-01:38:10 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:09 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 08-01:45:09 (3473) [ERROR] http://mirrors.oit.uci.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://atl.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/b52fb718cbd95f928936449dd1157a0ebac01abc1ad5b7ceed20c40c623cda2c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.phx1.us.spryservers.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.phx1.us.spryservers.net/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftpmirror.your.org/pub/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rcs.alaska.edu/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.lstn.net/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.ette.biz/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.umd.edu/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos-distro.1gservers.com/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.rackspace.com/CentOS/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.cmich.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.cmich.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://mirror.math.princeton.edu/pub/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux-mirrors.fnal.gov/linux/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesisadaptive.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.ocf.berkeley.edu/centos/7.9.2009/updates/x86_64/repodata/6b59dc6b22393982030ce497cc755292d25f9a9396cb6945197f2db2b6350fb8-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vtti.vt.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repos.forethought.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.clarkson.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror.  * 08-01:45:09 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 08-01:45:09 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 08-01:45:09 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 08-01:45:13 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 08-01:45:13 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 08-01:45:13 (3321) [INFO] Checking if your system is up to date:  * 08-01:45:13 (3766) [INFO] Running: /usr/bin/yum clean all * 08-01:45:13 (3767) [INFO]  * 08-01:45:14 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:45:14 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 08-01:45:14 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-01:45:14 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 08-01:45:14 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 08-01:45:14 (3777) [INFO] Cleaning up list of fastest mirrors * 08-01:45:14 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 08-01:45:14 (3787) [INFO]  * 08-01:45:14 (3766) [INFO] Running: /usr/bin/yum check-update * 08-01:45:14 (3767) [INFO]  * 08-01:45:15 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:45:15 (3777) [INFO] Determining fastest mirrors * 08-01:46:43 (3777) [INFO] * EA4: 208.74.123.61 * 08-01:46:43 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 08-01:46:43 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 08-01:46:43 (3777) [INFO] * base: mirrors.sonic.net * 08-01:46:43 (3777) [INFO] * epel: mirrors.xmission.com * 08-01:46:43 (3777) [INFO] * extras: mirror.hostduplex.com * 08-01:46:43 (3777) [INFO] * updates: mirrors.ocf.berkeley.edu * 08-01:48:57 (3777) [INFO]  * 08-01:48:57 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 08-01:48:57 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-01:48:57 (3787) [INFO]  * 08-01:48:57 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-01:48:57 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-01:48:57 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 08-01:48:57 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 08-01:48:57 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CKohAB9oWP/ea_profile.json * 08-01:48:59 (1619) [INFO] Backed up EA4 profile to /tmp/CKohAB9oWP/ea_profile.json * 08-01:48:59 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 08-01:53:00 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 08-01:53:00 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 09-01:42:41 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 09-01:42:47 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 09-01:42:47 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:31 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 09-01:45:31 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 09-01:45:34 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 09-01:45:34 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 09-01:45:34 (3321) [INFO] Checking if your system is up to date:  * 09-01:45:34 (3766) [INFO] Running: /usr/bin/yum clean all * 09-01:45:34 (3767) [INFO]  * 09-01:45:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:45:35 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 09-01:45:35 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-01:45:35 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 09-01:45:35 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 09-01:45:35 (3777) [INFO] Cleaning up list of fastest mirrors * 09-01:45:35 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 09-01:45:35 (3787) [INFO]  * 09-01:45:35 (3766) [INFO] Running: /usr/bin/yum check-update * 09-01:45:35 (3767) [INFO]  * 09-01:45:35 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:45:36 (3777) [INFO] Determining fastest mirrors * 09-01:47:04 (3777) [INFO] * EA4: 208.74.123.62 * 09-01:47:04 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 09-01:47:04 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 09-01:47:04 (3777) [INFO] * base: mirrors.raystedman.org * 09-01:47:04 (3777) [INFO] * epel: mirrors.xmission.com * 09-01:47:04 (3777) [INFO] * extras: mirrors.xmission.com * 09-01:47:04 (3777) [INFO] * updates: repos.lax.layerhost.com * 09-01:49:53 (3777) [INFO]  * 09-01:49:53 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 09-01:49:53 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-01:49:53 (3787) [INFO]  * 09-01:49:53 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-01:49:53 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-01:49:53 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 09-01:49:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 09-01:49:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AIoDsddQnV/ea_profile.json * 09-01:49:56 (1619) [INFO] Backed up EA4 profile to /tmp/AIoDsddQnV/ea_profile.json * 09-01:49:56 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 09-01:53:57 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 09-01:53:57 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 10-01:42:24 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 10-01:42:29 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 10-01:42:29 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:14 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 10-01:45:14 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 10-01:45:15 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 10-01:45:15 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 10-01:45:15 (3321) [INFO] Checking if your system is up to date:  * 10-01:45:15 (3766) [INFO] Running: /usr/bin/yum clean all * 10-01:45:15 (3767) [INFO]  * 10-01:45:16 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:45:16 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 10-01:45:16 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-01:45:16 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 10-01:45:16 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 10-01:45:16 (3777) [INFO] Cleaning up list of fastest mirrors * 10-01:45:16 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 10-01:45:17 (3787) [INFO]  * 10-01:45:17 (3766) [INFO] Running: /usr/bin/yum check-update * 10-01:45:17 (3767) [INFO]  * 10-01:45:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:45:18 (3777) [INFO] Determining fastest mirrors * 10-01:46:46 (3777) [INFO] * EA4: 208.74.123.62 * 10-01:46:46 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 10-01:46:46 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 10-01:46:46 (3777) [INFO] * base: mirrors.sonic.net * 10-01:46:46 (3777) [INFO] * epel: mirrors.xmission.com * 10-01:46:46 (3777) [INFO] * extras: mirror.chpc.utah.edu * 10-01:46:46 (3777) [INFO] * updates: mirror.keystealth.org * 10-01:49:35 (3777) [INFO]  * 10-01:49:35 (3777) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 10-01:49:35 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-01:49:35 (3787) [INFO]  * 10-01:49:35 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-01:49:35 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-01:49:35 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 10-01:49:35 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 10-01:49:35 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2ia4PZSkU4/ea_profile.json * 10-01:49:39 (1619) [INFO] Backed up EA4 profile to /tmp/2ia4PZSkU4/ea_profile.json * 10-01:49:39 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 10-01:53:40 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 10-01:53:40 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 11-01:47:34 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 11-01:47:39 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 11-01:47:39 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:22 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 11-01:50:22 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 11-01:50:23 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 11-01:50:23 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 11-01:50:23 (3321) [INFO] Checking if your system is up to date:  * 11-01:50:23 (3766) [INFO] Running: /usr/bin/yum clean all * 11-01:50:23 (3767) [INFO]  * 11-01:50:24 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:50:24 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 11-01:50:24 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-01:50:24 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 11-01:50:24 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 11-01:50:24 (3777) [INFO] Cleaning up list of fastest mirrors * 11-01:50:24 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 11-01:50:24 (3787) [INFO]  * 11-01:50:24 (3766) [INFO] Running: /usr/bin/yum check-update * 11-01:50:24 (3767) [INFO]  * 11-01:50:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:50:26 (3777) [INFO] Determining fastest mirrors * 11-01:51:55 (3777) [INFO] * EA4: 208.74.123.61 * 11-01:51:55 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 11-01:51:55 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 11-01:51:55 (3777) [INFO] * base: mirrors.sonic.net * 11-01:51:55 (3777) [INFO] * epel: irltoolkit.mm.fcix.net * 11-01:51:55 (3777) [INFO] * extras: mirror.chpc.utah.edu * 11-01:51:55 (3777) [INFO] * updates: centos.mirrors.hoobly.com * 11-01:54:37 (3777) [INFO]  * 11-01:54:37 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 11-01:54:37 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-01:54:37 (3787) [INFO]  * 11-01:54:37 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-01:54:37 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-01:54:37 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 11-01:54:37 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 11-01:54:37 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IZrJdC9fcO/ea_profile.json * 11-01:54:40 (1619) [INFO] Backed up EA4 profile to /tmp/IZrJdC9fcO/ea_profile.json * 11-01:54:40 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 11-01:58:40 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 11-01:58:40 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 12-01:43:48 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 12-01:43:59 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 12-01:43:59 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:16 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 12-01:46:16 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 12-01:46:16 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 12-01:46:16 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 12-01:46:16 (3321) [INFO] Checking if your system is up to date:  * 12-01:46:16 (3766) [INFO] Running: /usr/bin/yum clean all * 12-01:46:16 (3767) [INFO]  * 12-01:46:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:46:17 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 12-01:46:17 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-01:46:17 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 12-01:46:17 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 12-01:46:17 (3777) [INFO] Cleaning up list of fastest mirrors * 12-01:46:17 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 12-01:46:17 (3787) [INFO]  * 12-01:46:17 (3766) [INFO] Running: /usr/bin/yum check-update * 12-01:46:17 (3767) [INFO]  * 12-01:46:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:46:18 (3777) [INFO] Determining fastest mirrors * 12-01:47:46 (3777) [INFO] * EA4: 208.74.123.61 * 12-01:47:46 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 12-01:47:46 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 12-01:47:46 (3777) [INFO] * base: repos.forethought.net * 12-01:47:46 (3777) [INFO] * epel: irltoolkit.mm.fcix.net * 12-01:47:46 (3777) [INFO] * extras: ridgewireless.mm.fcix.net * 12-01:47:46 (3777) [INFO] * updates: mirrors.sonic.net * 12-01:50:15 (3777) [INFO]  * 12-01:50:15 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 12-01:50:15 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-01:50:15 (3787) [INFO]  * 12-01:50:15 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-01:50:15 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-01:50:15 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 12-01:50:15 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 12-01:50:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Iuea8kw5dv/ea_profile.json * 12-01:50:18 (1619) [INFO] Backed up EA4 profile to /tmp/Iuea8kw5dv/ea_profile.json * 12-01:50:18 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 12-01:54:19 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 12-01:54:19 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 13-01:43:47 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 13-01:43:54 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 13-01:43:54 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:10 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 13-01:46:10 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 13-01:46:10 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 13-01:46:10 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 13-01:46:11 (3321) [INFO] Checking if your system is up to date:  * 13-01:46:11 (3766) [INFO] Running: /usr/bin/yum clean all * 13-01:46:11 (3767) [INFO]  * 13-01:46:11 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:12 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 13-01:46:12 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-01:46:12 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 13-01:46:12 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 13-01:46:12 (3777) [INFO] Cleaning up list of fastest mirrors * 13-01:46:12 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 13-01:46:13 (3787) [INFO]  * 13-01:46:13 (3766) [INFO] Running: /usr/bin/yum check-update * 13-01:46:13 (3767) [INFO]  * 13-01:46:13 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:14 (3777) [INFO] Determining fastest mirrors * 13-01:47:43 (3777) [INFO] * EA4: 184.94.196.92 * 13-01:47:43 (3777) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 13-01:47:43 (3777) [INFO] * cpanel-plugins: 184.94.196.92 * 13-01:47:43 (3777) [INFO] * base: mirror.chpc.utah.edu * 13-01:47:43 (3777) [INFO] * epel: mirrors.xmission.com * 13-01:47:43 (3777) [INFO] * extras: repos.forethought.net * 13-01:47:43 (3777) [INFO] * updates: repos.lax.layerhost.com * 13-01:50:23 (3777) [INFO]  * 13-01:50:23 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 13-01:50:23 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-01:50:23 (3787) [INFO]  * 13-01:50:23 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-01:50:23 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-01:50:23 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 13-01:50:23 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 13-01:50:23 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/x9nmAH0j2Y/ea_profile.json * 13-01:50:26 (1619) [INFO] Backed up EA4 profile to /tmp/x9nmAH0j2Y/ea_profile.json * 13-01:50:26 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 13-01:54:26 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 13-01:54:27 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 14-01:58:33 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 14-01:58:53 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 14-01:58:53 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-02:02:23 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 14-02:02:23 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 14-02:02:36 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 14-02:02:36 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 14-02:02:36 (3321) [INFO] Checking if your system is up to date:  * 14-02:02:36 (3766) [INFO] Running: /usr/bin/yum clean all * 14-02:02:36 (3767) [INFO]  * 14-02:02:38 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-02:02:38 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 14-02:02:38 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-02:02:38 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 14-02:02:38 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 14-02:02:39 (3777) [INFO] Cleaning up list of fastest mirrors * 14-02:02:39 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 14-02:02:39 (3787) [INFO]  * 14-02:02:39 (3766) [INFO] Running: /usr/bin/yum check-update * 14-02:02:39 (3767) [INFO]  * 14-02:02:40 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-02:02:41 (3777) [INFO] Determining fastest mirrors * 14-02:04:11 (3777) [INFO] * EA4: 208.74.123.62 * 14-02:04:11 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 14-02:04:11 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 14-02:04:11 (3777) [INFO] * base: la.mirrors.clouvider.net * 14-02:04:11 (3777) [INFO] * epel: mirrors.xmission.com * 14-02:04:11 (3777) [INFO] * extras: or-mirror.iwebfusion.net * 14-02:04:11 (3777) [INFO] * updates: mirrors.raystedman.org * 14-02:07:15 (3777) [INFO]  * 14-02:07:15 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 14-02:07:15 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-02:07:15 (3787) [INFO]  * 14-02:07:15 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-02:07:15 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-02:07:15 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 14-02:07:15 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 14-02:07:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3KKow15sZf/ea_profile.json * 14-02:07:18 (1619) [INFO] Backed up EA4 profile to /tmp/3KKow15sZf/ea_profile.json * 14-02:07:18 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 14-02:11:18 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 14-02:11:18 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 15-01:58:12 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 15-01:58:32 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 15-01:58:32 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-02:01:35 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 15-02:01:35 (3473) [ERROR] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/7852a650daed88608d7a60664462992fec306df5ba8ca5c1ab03df65b5718a56-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/.  * 15-02:01:35 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 15-02:01:35 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 15-02:01:35 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 15-02:01:36 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 15-02:01:36 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 15-02:01:36 (3321) [INFO] Checking if your system is up to date:  * 15-02:01:36 (3766) [INFO] Running: /usr/bin/yum clean all * 15-02:01:36 (3767) [INFO]  * 15-02:01:36 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-02:01:37 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 15-02:01:37 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-02:01:37 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 15-02:01:37 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 15-02:01:37 (3777) [INFO] Cleaning up list of fastest mirrors * 15-02:01:37 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 15-02:01:37 (3787) [INFO]  * 15-02:01:37 (3766) [INFO] Running: /usr/bin/yum check-update * 15-02:01:37 (3767) [INFO]  * 15-02:01:37 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-02:01:38 (3777) [INFO] Determining fastest mirrors * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] One of the configured repositories failed (Unknown), * 15-02:02:39 (3777) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 15-02:02:39 (3777) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 15-02:02:39 (3777) [INFO] upstream. This is most often useful if you are using a newer * 15-02:02:39 (3777) [INFO] distribution release than is supported by the repository (and the * 15-02:02:39 (3777) [INFO] packages for the previous distribution release still work). * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] 3. Run the command with the repository temporarily disabled * 15-02:02:39 (3777) [INFO] yum --disablerepo= ... * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 15-02:02:39 (3777) [INFO] will then just ignore the repository until you permanently enable it * 15-02:02:39 (3777) [INFO] again or use --enablerepo for temporary usage: * 15-02:02:39 (3777) [INFO]  * 15-02:02:39 (3777) [INFO] yum-config-manager --disable  * 15-02:02:39 (3777) [INFO] or * 15-02:02:39 (3777) [INFO] subscription-manager repos --disable= * 15-02:02:40 (3777) [INFO]  * 15-02:02:40 (3777) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 15-02:02:40 (3777) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 15-02:02:40 (3777) [INFO] so will have to try and fail each time (and thus. yum will be be much * 15-02:02:40 (3777) [INFO] slower). If it is a very temporary problem though, this is often a nice * 15-02:02:40 (3777) [INFO] compromise: * 15-02:02:40 (3777) [INFO]  * 15-02:02:40 (3777) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 15-02:02:40 (3777) [INFO]  * 15-02:02:40 (3777) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 15-02:02:41 (3787) [INFO]  * 15-02:02:41 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-02:02:41 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-02:02:42 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 15-02:02:42 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 15-02:02:42 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HwaDk8biEI/ea_profile.json * 15-02:11:25 (1619) [INFO] Backed up EA4 profile to /tmp/HwaDk8biEI/ea_profile.json * 15-02:11:26 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 15-02:15:29 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 15-02:15:30 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 16-00:42:44 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 16-00:42:59 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 16-00:43:00 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-00:45:46 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 16-00:45:46 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 16-00:45:47 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 16-00:45:47 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 16-00:45:47 (3321) [INFO] Checking if your system is up to date:  * 16-00:45:47 (3766) [INFO] Running: /usr/bin/yum clean all * 16-00:45:47 (3767) [INFO]  * 16-00:45:48 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-00:45:48 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 16-00:45:48 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-00:45:48 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 16-00:45:48 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 16-00:45:48 (3777) [INFO] Cleaning up list of fastest mirrors * 16-00:45:48 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 16-00:45:48 (3787) [INFO]  * 16-00:45:48 (3766) [INFO] Running: /usr/bin/yum check-update * 16-00:45:48 (3767) [INFO]  * 16-00:45:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-00:45:50 (3777) [INFO] Determining fastest mirrors * 16-00:47:17 (3777) [INFO] * EA4: 208.74.123.62 * 16-00:47:17 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 16-00:47:17 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 16-00:47:17 (3777) [INFO] * base: centos.mirrors.hoobly.com * 16-00:47:17 (3777) [INFO] * epel: codingflyboy.mm.fcix.net * 16-00:47:17 (3777) [INFO] * extras: mirror.us.oneandone.net * 16-00:47:17 (3777) [INFO] * updates: ohioix.mm.fcix.net * 16-00:49:52 (3777) [INFO]  * 16-00:49:52 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 16-00:49:52 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-00:49:53 (3787) [INFO]  * 16-00:49:53 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-00:49:53 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-00:49:53 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 16-00:49:53 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 16-00:49:53 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4Jf8h8hI6_/ea_profile.json * 16-00:49:55 (1619) [INFO] Backed up EA4 profile to /tmp/4Jf8h8hI6_/ea_profile.json * 16-00:49:55 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 16-00:53:55 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (1 ). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 16-00:53:55 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 17-00:42:59 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 17-00:43:05 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 17-00:43:05 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-00:45:48 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 17-00:45:48 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 17-00:45:49 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 17-00:45:49 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 17-00:45:49 (3321) [INFO] Checking if your system is up to date:  * 17-00:45:49 (3766) [INFO] Running: /usr/bin/yum clean all * 17-00:45:49 (3767) [INFO]  * 17-00:45:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-00:45:50 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 17-00:45:50 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-00:45:50 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 17-00:45:50 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 17-00:45:50 (3777) [INFO] Cleaning up list of fastest mirrors * 17-00:45:50 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 17-00:45:50 (3787) [INFO]  * 17-00:45:50 (3766) [INFO] Running: /usr/bin/yum check-update * 17-00:45:50 (3767) [INFO]  * 17-00:45:51 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-00:45:52 (3777) [INFO] Determining fastest mirrors * 17-00:47:22 (3777) [INFO] * EA4: 208.74.123.62 * 17-00:47:22 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 17-00:47:22 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 17-00:47:22 (3777) [INFO] * base: ridgewireless.mm.fcix.net * 17-00:47:22 (3777) [INFO] * epel: mirror.fcix.net * 17-00:47:22 (3777) [INFO] * extras: mirrors.vcea.wsu.edu * 17-00:47:22 (3777) [INFO] * updates: mirrors.xmission.com * 17-00:50:08 (3777) [INFO]  * 17-00:50:08 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 17-00:50:08 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-00:50:09 (3787) [INFO]  * 17-00:50:09 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-00:50:09 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-00:50:09 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 17-00:50:09 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 17-00:50:09 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gjRURLA7wA/ea_profile.json * 17-00:50:12 (1619) [INFO] Backed up EA4 profile to /tmp/gjRURLA7wA/ea_profile.json * 17-00:50:12 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 17-00:54:13 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 17-00:54:13 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 18-01:42:57 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 18-01:43:04 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 18-01:43:04 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:48 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 18-01:45:48 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 18-01:45:48 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 18-01:45:48 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 18-01:45:48 (3321) [INFO] Checking if your system is up to date:  * 18-01:45:48 (3766) [INFO] Running: /usr/bin/yum clean all * 18-01:45:48 (3767) [INFO]  * 18-01:45:49 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:45:49 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 18-01:45:49 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-01:45:49 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 18-01:45:49 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 18-01:45:49 (3777) [INFO] Cleaning up list of fastest mirrors * 18-01:45:49 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 18-01:45:49 (3787) [INFO]  * 18-01:45:49 (3766) [INFO] Running: /usr/bin/yum check-update * 18-01:45:49 (3767) [INFO]  * 18-01:45:50 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:45:51 (3777) [INFO] Determining fastest mirrors * 18-01:47:19 (3777) [INFO] * EA4: 208.100.0.204 * 18-01:47:19 (3777) [INFO] * cpanel-addons-production-feed: 208.100.0.204 * 18-01:47:19 (3777) [INFO] * cpanel-plugins: 208.100.0.204 * 18-01:47:19 (3777) [INFO] * base: mirror.fcix.net * 18-01:47:19 (3777) [INFO] * epel: mirror.fcix.net * 18-01:47:19 (3777) [INFO] * extras: repos.eggycrew.com * 18-01:47:19 (3777) [INFO] * updates: mirror.keystealth.org * 18-01:50:05 (3777) [INFO]  * 18-01:50:05 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 18-01:50:05 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-01:50:05 (3787) [INFO]  * 18-01:50:05 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-01:50:05 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-01:50:05 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 18-01:50:05 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 18-01:50:05 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kz2qfXgmtv/ea_profile.json * 18-01:50:09 (1619) [INFO] Backed up EA4 profile to /tmp/kz2qfXgmtv/ea_profile.json * 18-01:50:09 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 18-01:54:09 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 18-01:54:09 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 19-01:45:27 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 19-01:45:37 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 19-01:45:37 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:36 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 19-01:48:36 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 19-01:48:37 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 19-01:48:37 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 19-01:48:37 (3321) [INFO] Checking if your system is up to date:  * 19-01:48:37 (3766) [INFO] Running: /usr/bin/yum clean all * 19-01:48:37 (3767) [INFO]  * 19-01:48:37 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:48:37 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 19-01:48:37 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-01:48:37 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 19-01:48:37 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 19-01:48:38 (3777) [INFO] Cleaning up list of fastest mirrors * 19-01:48:38 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 19-01:48:38 (3787) [INFO]  * 19-01:48:38 (3766) [INFO] Running: /usr/bin/yum check-update * 19-01:48:38 (3767) [INFO]  * 19-01:48:38 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:48:39 (3777) [INFO] Determining fastest mirrors * 19-01:50:08 (3777) [INFO] * EA4: 208.74.123.62 * 19-01:50:08 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 19-01:50:08 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 19-01:50:08 (3777) [INFO] * base: la.mirrors.clouvider.net * 19-01:50:08 (3777) [INFO] * epel: mirrors.xmission.com * 19-01:50:08 (3777) [INFO] * extras: mirrors.xmission.com * 19-01:50:08 (3777) [INFO] * updates: mirrors.ocf.berkeley.edu * 19-01:53:14 (3777) [INFO]  * 19-01:53:14 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 19-01:53:14 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-01:53:14 (3787) [INFO]  * 19-01:53:14 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-01:53:14 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-01:53:14 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 19-01:53:14 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 19-01:53:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4PD8OZ4aFe/ea_profile.json * 19-01:53:17 (1619) [INFO] Backed up EA4 profile to /tmp/4PD8OZ4aFe/ea_profile.json * 19-01:53:17 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 19-01:57:18 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 19-01:57:18 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 20-01:44:00 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 20-01:44:09 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 20-01:44:09 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:56 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 20-01:46:56 (3473) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 20-01:46:56 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 20-01:46:56 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 20-01:46:56 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 20-01:46:57 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 20-01:46:57 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 20-01:46:57 (3321) [INFO] Checking if your system is up to date:  * 20-01:46:57 (3766) [INFO] Running: /usr/bin/yum clean all * 20-01:46:57 (3767) [INFO]  * 20-01:46:57 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:46:57 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 20-01:46:57 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-01:46:57 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 20-01:46:57 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 20-01:46:58 (3777) [INFO] Cleaning up list of fastest mirrors * 20-01:46:58 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 20-01:46:58 (3787) [INFO]  * 20-01:46:58 (3766) [INFO] Running: /usr/bin/yum check-update * 20-01:46:58 (3767) [INFO]  * 20-01:46:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:46:58 (3777) [INFO] Determining fastest mirrors * 20-01:48:28 (3777) [INFO] * EA4: 208.74.123.62 * 20-01:48:28 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 20-01:48:28 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 20-01:48:28 (3777) [INFO] * base: linux.mirrors.es.net * 20-01:48:28 (3777) [INFO] * epel: mirrors.xmission.com * 20-01:48:28 (3777) [INFO] * extras: repos.forethought.net * 20-01:48:28 (3777) [INFO] * updates: abqix.mm.fcix.net * 20-01:51:14 (3777) [INFO]  * 20-01:51:14 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 20-01:51:14 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-01:51:15 (3787) [INFO]  * 20-01:51:15 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-01:51:15 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-01:51:15 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 20-01:51:15 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 20-01:51:15 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KZwF6uyWqn/ea_profile.json * 20-01:51:17 (1619) [INFO] Backed up EA4 profile to /tmp/KZwF6uyWqn/ea_profile.json * 20-01:51:17 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 20-01:55:18 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 20-01:55:18 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 21-01:43:23 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 21-01:43:29 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 21-01:43:29 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:10 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 21-01:46:10 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 21-01:46:11 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 21-01:46:11 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 21-01:46:11 (3321) [INFO] Checking if your system is up to date:  * 21-01:46:11 (3766) [INFO] Running: /usr/bin/yum clean all * 21-01:46:11 (3767) [INFO]  * 21-01:46:12 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:46:12 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 21-01:46:12 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-01:46:12 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 21-01:46:12 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 21-01:46:12 (3777) [INFO] Cleaning up list of fastest mirrors * 21-01:46:12 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 21-01:46:12 (3787) [INFO]  * 21-01:46:12 (3766) [INFO] Running: /usr/bin/yum check-update * 21-01:46:12 (3767) [INFO]  * 21-01:46:12 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:46:13 (3777) [INFO] Determining fastest mirrors * 21-01:47:40 (3777) [INFO] * EA4: 208.74.123.62 * 21-01:47:40 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 21-01:47:40 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 21-01:47:40 (3777) [INFO] * base: mirror.fcix.net * 21-01:47:40 (3777) [INFO] * epel: mirrors.xmission.com * 21-01:47:40 (3777) [INFO] * extras: mirror.web-ster.com * 21-01:47:40 (3777) [INFO] * updates: repos.forethought.net * 21-01:50:24 (3777) [INFO]  * 21-01:50:24 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 21-01:50:24 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-01:50:24 (3787) [INFO]  * 21-01:50:24 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-01:50:24 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-01:50:24 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 21-01:50:24 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 21-01:50:24 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kraaanbs9y/ea_profile.json * 21-01:50:27 (1619) [INFO] Backed up EA4 profile to /tmp/Kraaanbs9y/ea_profile.json * 21-01:50:27 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 21-01:54:27 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 21-01:54:27 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 22-01:44:01 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 22-01:44:07 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 22-01:44:07 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:07 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 22-01:47:07 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 22-01:47:08 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 22-01:47:08 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 22-01:47:08 (3321) [INFO] Checking if your system is up to date:  * 22-01:47:08 (3766) [INFO] Running: /usr/bin/yum clean all * 22-01:47:08 (3767) [INFO]  * 22-01:47:09 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:47:09 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 22-01:47:09 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-01:47:09 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 22-01:47:09 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 22-01:47:09 (3777) [INFO] Cleaning up list of fastest mirrors * 22-01:47:09 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 22-01:47:09 (3787) [INFO]  * 22-01:47:09 (3766) [INFO] Running: /usr/bin/yum check-update * 22-01:47:09 (3767) [INFO]  * 22-01:47:10 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:47:11 (3777) [INFO] Determining fastest mirrors * 22-01:48:42 (3777) [INFO] * EA4: 208.74.123.61 * 22-01:48:42 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 22-01:48:42 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 22-01:48:42 (3777) [INFO] * base: mirror.den01.meanservers.net * 22-01:48:42 (3777) [INFO] * epel: mirrors.xmission.com * 22-01:48:42 (3777) [INFO] * extras: ridgewireless.mm.fcix.net * 22-01:48:42 (3777) [INFO] * updates: mirrors.ocf.berkeley.edu * 22-01:51:44 (3777) [INFO]  * 22-01:51:44 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 22-01:51:44 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-01:51:44 (3787) [INFO]  * 22-01:51:44 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-01:51:44 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-01:51:44 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 22-01:51:44 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 22-01:51:44 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SVMb3AyiDQ/ea_profile.json * 22-01:51:47 (1619) [INFO] Backed up EA4 profile to /tmp/SVMb3AyiDQ/ea_profile.json * 22-01:51:47 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 22-01:55:47 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 22-01:55:47 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 23-01:44:58 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 23-01:45:08 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 23-01:45:08 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:16 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 23-01:48:16 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 23-01:48:17 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 23-01:48:17 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 23-01:48:17 (3321) [INFO] Checking if your system is up to date:  * 23-01:48:17 (3766) [INFO] Running: /usr/bin/yum clean all * 23-01:48:17 (3767) [INFO]  * 23-01:48:17 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:48:17 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 23-01:48:17 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-01:48:17 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 23-01:48:17 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 23-01:48:17 (3777) [INFO] Cleaning up list of fastest mirrors * 23-01:48:17 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 23-01:48:18 (3787) [INFO]  * 23-01:48:18 (3766) [INFO] Running: /usr/bin/yum check-update * 23-01:48:18 (3767) [INFO]  * 23-01:48:18 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:48:18 (3777) [INFO] Determining fastest mirrors * 23-01:49:46 (3777) [INFO] * EA4: 208.74.123.61 * 23-01:49:46 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 23-01:49:46 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 23-01:49:46 (3777) [INFO] * base: mirror.den01.meanservers.net * 23-01:49:46 (3777) [INFO] * epel: mirrors.sonic.net * 23-01:49:46 (3777) [INFO] * extras: mirrors.ocf.berkeley.edu * 23-01:49:46 (3777) [INFO] * updates: mirrors.xtom.com * 23-01:52:59 (3777) [INFO]  * 23-01:52:59 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 23-01:52:59 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-01:52:59 (3787) [INFO]  * 23-01:52:59 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-01:52:59 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-01:52:59 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 23-01:52:59 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 23-01:52:59 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Cdo88fplS7/ea_profile.json * 23-01:53:02 (1619) [INFO] Backed up EA4 profile to /tmp/Cdo88fplS7/ea_profile.json * 23-01:53:02 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 23-01:57:03 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 23-01:57:03 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 24-01:42:03 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 24-01:42:10 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 24-01:42:10 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:44:23 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 24-01:44:23 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 24-01:44:24 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 24-01:44:24 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 24-01:44:24 (3321) [INFO] Checking if your system is up to date:  * 24-01:44:24 (3766) [INFO] Running: /usr/bin/yum clean all * 24-01:44:24 (3767) [INFO]  * 24-01:44:24 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:44:24 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 24-01:44:24 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-01:44:24 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 24-01:44:24 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 24-01:44:24 (3777) [INFO] Cleaning up list of fastest mirrors * 24-01:44:24 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 24-01:44:24 (3787) [INFO]  * 24-01:44:24 (3766) [INFO] Running: /usr/bin/yum check-update * 24-01:44:24 (3767) [INFO]  * 24-01:44:25 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:44:25 (3777) [INFO] Determining fastest mirrors * 24-01:45:53 (3777) [INFO] * EA4: 208.74.123.62 * 24-01:45:53 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 24-01:45:53 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 24-01:45:53 (3777) [INFO] * base: repos.forethought.net * 24-01:45:53 (3777) [INFO] * epel: mirror.fcix.net * 24-01:45:53 (3777) [INFO] * extras: repos.forethought.net * 24-01:45:53 (3777) [INFO] * updates: mirrors.oit.uci.edu * 24-01:48:05 (3777) [INFO]  * 24-01:48:05 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 24-01:48:05 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-01:48:06 (3787) [INFO]  * 24-01:48:06 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-01:48:06 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-01:48:06 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 24-01:48:06 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 24-01:48:06 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EWqTxJ_VjO/ea_profile.json * 24-01:48:10 (1619) [INFO] Backed up EA4 profile to /tmp/EWqTxJ_VjO/ea_profile.json * 24-01:48:10 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 24-01:52:10 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 24-01:52:10 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 25-01:42:01 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 25-01:42:13 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 25-01:42:13 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:44:27 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 25-01:44:27 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 25-01:44:27 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 25-01:44:27 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 25-01:44:27 (3321) [INFO] Checking if your system is up to date:  * 25-01:44:27 (3766) [INFO] Running: /usr/bin/yum clean all * 25-01:44:27 (3767) [INFO]  * 25-01:44:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:44:28 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 25-01:44:28 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-01:44:28 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 25-01:44:28 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 25-01:44:28 (3777) [INFO] Cleaning up list of fastest mirrors * 25-01:44:28 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 25-01:44:28 (3787) [INFO]  * 25-01:44:28 (3766) [INFO] Running: /usr/bin/yum check-update * 25-01:44:28 (3767) [INFO]  * 25-01:44:29 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:44:30 (3777) [INFO] Determining fastest mirrors * 25-01:45:58 (3777) [INFO] * EA4: 208.74.123.62 * 25-01:45:58 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 25-01:45:58 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 25-01:45:58 (3777) [INFO] * base: mirror.arizona.edu * 25-01:45:58 (3777) [INFO] * epel: mirrors.sonic.net * 25-01:45:58 (3777) [INFO] * extras: mirror.hostduplex.com * 25-01:45:58 (3777) [INFO] * updates: mirror.web-ster.com * 25-01:48:59 (3777) [INFO]  * 25-01:48:59 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 25-01:48:59 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-01:48:59 (3787) [INFO]  * 25-01:48:59 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-01:48:59 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-01:48:59 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 25-01:48:59 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 25-01:48:59 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z26ORLsPFW/ea_profile.json * 25-01:49:01 (1619) [INFO] Backed up EA4 profile to /tmp/z26ORLsPFW/ea_profile.json * 25-01:49:01 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 25-01:53:01 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 25-01:53:01 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:44:17 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:44:27 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:44:28 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:57 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:46:57 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:46:58 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 26-01:46:58 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:46:58 (3321) [INFO] Checking if your system is up to date:  * 26-01:46:58 (3766) [INFO] Running: /usr/bin/yum clean all * 26-01:46:58 (3767) [INFO]  * 26-01:46:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:46:59 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:46:59 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:46:59 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:46:59 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 26-01:46:59 (3777) [INFO] Cleaning up list of fastest mirrors * 26-01:46:59 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 26-01:46:59 (3787) [INFO]  * 26-01:46:59 (3766) [INFO] Running: /usr/bin/yum check-update * 26-01:46:59 (3767) [INFO]  * 26-01:47:00 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:47:01 (3777) [INFO] Determining fastest mirrors * 26-01:48:28 (3777) [INFO] * EA4: 184.94.196.94 * 26-01:48:28 (3777) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 26-01:48:28 (3777) [INFO] * cpanel-plugins: 184.94.196.94 * 26-01:48:28 (3777) [INFO] * base: mirror.facebook.net * 26-01:48:28 (3777) [INFO] * epel: ridgewireless.mm.fcix.net * 26-01:48:28 (3777) [INFO] * extras: or-mirror.iwebfusion.net * 26-01:48:28 (3777) [INFO] * updates: ridgewireless.mm.fcix.net * 26-01:51:02 (3777) [INFO]  * 26-01:51:02 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 26-01:51:02 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-01:51:03 (3787) [INFO]  * 26-01:51:03 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:51:03 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:51:03 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:51:03 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 26-01:51:03 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FcHqMgazTU/ea_profile.json * 26-01:51:06 (1619) [INFO] Backed up EA4 profile to /tmp/FcHqMgazTU/ea_profile.json * 26-01:51:06 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 26-01:55:06 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 26-01:55:06 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 27-01:43:19 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 27-01:43:24 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 27-01:43:24 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:38 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 27-01:45:38 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 27-01:45:38 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 27-01:45:38 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 27-01:45:38 (3321) [INFO] Checking if your system is up to date:  * 27-01:45:38 (3766) [INFO] Running: /usr/bin/yum clean all * 27-01:45:38 (3767) [INFO]  * 27-01:45:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:45:39 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 27-01:45:39 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-01:45:39 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 27-01:45:39 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 27-01:45:39 (3777) [INFO] Cleaning up list of fastest mirrors * 27-01:45:39 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 27-01:45:39 (3787) [INFO]  * 27-01:45:39 (3766) [INFO] Running: /usr/bin/yum check-update * 27-01:45:39 (3767) [INFO]  * 27-01:45:39 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:45:40 (3777) [INFO] Determining fastest mirrors * 27-01:47:10 (3777) [INFO] * EA4: 208.74.123.62 * 27-01:47:10 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 27-01:47:10 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 27-01:47:10 (3777) [INFO] * base: mirror.hostduplex.com * 27-01:47:10 (3777) [INFO] * epel: codingflyboy.mm.fcix.net * 27-01:47:10 (3777) [INFO] * extras: mirror.keystealth.org * 27-01:47:10 (3777) [INFO] * updates: mirror.web-ster.com * 27-01:49:40 (3777) [INFO]  * 27-01:49:40 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 27-01:49:40 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-01:49:41 (3787) [INFO]  * 27-01:49:41 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-01:49:41 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-01:49:41 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 27-01:49:41 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 27-01:49:41 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4pAJsUGTl8/ea_profile.json * 27-01:49:45 (1619) [INFO] Backed up EA4 profile to /tmp/4pAJsUGTl8/ea_profile.json * 27-01:49:45 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 27-01:53:46 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 27-01:53:46 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 28-01:42:54 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 28-01:42:59 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 28-01:42:59 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:58 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 28-01:45:58 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 28-01:45:58 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 28-01:45:58 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 28-01:45:58 (3321) [INFO] Checking if your system is up to date:  * 28-01:45:58 (3766) [INFO] Running: /usr/bin/yum clean all * 28-01:45:58 (3767) [INFO]  * 28-01:45:58 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:45:59 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 28-01:45:59 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-01:45:59 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 28-01:45:59 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 28-01:45:59 (3777) [INFO] Cleaning up list of fastest mirrors * 28-01:45:59 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 28-01:45:59 (3787) [INFO]  * 28-01:45:59 (3766) [INFO] Running: /usr/bin/yum check-update * 28-01:45:59 (3767) [INFO]  * 28-01:45:59 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:46:01 (3777) [INFO] Determining fastest mirrors * 28-01:47:29 (3777) [INFO] * EA4: 208.74.123.62 * 28-01:47:29 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 28-01:47:29 (3777) [INFO] * cpanel-plugins: 208.74.123.62 * 28-01:47:29 (3777) [INFO] * base: mirror.keystealth.org * 28-01:47:29 (3777) [INFO] * epel: mirrors.xmission.com * 28-01:47:29 (3777) [INFO] * extras: repos.lax.layerhost.com * 28-01:47:29 (3777) [INFO] * updates: mirrors.sonic.net * 28-01:50:10 (3777) [INFO]  * 28-01:50:10 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 28-01:50:10 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-01:50:10 (3787) [INFO]  * 28-01:50:10 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-01:50:10 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-01:50:10 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 28-01:50:10 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 28-01:50:10 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yravminDyN/ea_profile.json * 28-01:50:12 (1619) [INFO] Backed up EA4 profile to /tmp/yravminDyN/ea_profile.json * 28-01:50:12 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 28-01:54:13 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 28-01:54:13 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 29-01:43:44 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 29-01:43:48 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 29-01:43:48 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:01 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 29-01:46:01 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 29-01:46:02 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 29-01:46:02 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 29-01:46:02 (3321) [INFO] Checking if your system is up to date:  * 29-01:46:02 (3766) [INFO] Running: /usr/bin/yum clean all * 29-01:46:02 (3767) [INFO]  * 29-01:46:03 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:46:03 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 29-01:46:03 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-01:46:03 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 29-01:46:03 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 29-01:46:04 (3777) [INFO] Cleaning up list of fastest mirrors * 29-01:46:04 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 29-01:46:04 (3787) [INFO]  * 29-01:46:04 (3766) [INFO] Running: /usr/bin/yum check-update * 29-01:46:04 (3767) [INFO]  * 29-01:46:04 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:46:05 (3777) [INFO] Determining fastest mirrors * 29-01:47:35 (3777) [INFO] * EA4: 208.74.123.61 * 29-01:47:35 (3777) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 29-01:47:35 (3777) [INFO] * cpanel-plugins: 208.74.123.61 * 29-01:47:35 (3777) [INFO] * base: mirror.hostduplex.com * 29-01:47:35 (3777) [INFO] * epel: mirrors.xmission.com * 29-01:47:35 (3777) [INFO] * extras: ziply.mm.fcix.net * 29-01:47:35 (3777) [INFO] * updates: mirrors.raystedman.org * 29-01:50:09 (3777) [INFO]  * 29-01:50:09 (3777) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 29-01:50:09 (3777) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-01:50:09 (3787) [INFO]  * 29-01:50:09 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-01:50:09 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-01:50:09 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 29-01:50:09 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 29-01:50:09 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vwKTUGshsn/ea_profile.json * 29-01:50:11 (1619) [INFO] Backed up EA4 profile to /tmp/vwKTUGshsn/ea_profile.json * 29-01:50:11 (2667) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 29-01:54:12 (2667) [WARN] *** Elevation Blocker detected: *** This script (version 1) does not appear to be the newest available release (2). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 29-01:54:12 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:44:20 (2667) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:44:26 (3414) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:44:26 (2667) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:27 (3472) [ERROR] yum appears to be unstable. Please address this before upgrading * 30-01:47:27 (3473) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30541 milliseconds')  * 30-01:47:27 (2667) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 30-01:47:27 (3499) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:47:27 (2667) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:47:28 (3342) [WARN] JetBackup version 4.1.3-3 currently installed. * 30-01:47:28 (2667) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:47:28 (3321) [INFO] Checking if your system is up to date:  * 30-01:47:28 (3766) [INFO] Running: /usr/bin/yum clean all * 30-01:47:28 (3767) [INFO]  * 30-01:47:28 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:47:29 (3777) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:47:29 (3777) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:47:29 (3777) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:47:29 (3777) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 30-01:47:29 (3777) [INFO] Cleaning up list of fastest mirrors * 30-01:47:29 (3777) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 30-01:47:29 (3787) [INFO]  * 30-01:47:29 (3766) [INFO] Running: /usr/bin/yum check-update * 30-01:47:29 (3767) [INFO]  * 30-01:47:29 (3777) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:47:30 (3777) [INFO] Determining fastest mirrors * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] One of the configured repositories failed (Unknown), * 30-01:48:29 (3777) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 30-01:48:29 (3777) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 30-01:48:29 (3777) [INFO] upstream. This is most often useful if you are using a newer * 30-01:48:29 (3777) [INFO] distribution release than is supported by the repository (and the * 30-01:48:29 (3777) [INFO] packages for the previous distribution release still work). * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] 3. Run the command with the repository temporarily disabled * 30-01:48:29 (3777) [INFO] yum --disablerepo= ... * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 30-01:48:29 (3777) [INFO] will then just ignore the repository until you permanently enable it * 30-01:48:29 (3777) [INFO] again or use --enablerepo for temporary usage: * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] yum-config-manager --disable  * 30-01:48:29 (3777) [INFO] or * 30-01:48:29 (3777) [INFO] subscription-manager repos --disable= * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 30-01:48:29 (3777) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 30-01:48:29 (3777) [INFO] so will have to try and fail each time (and thus. yum will be be much * 30-01:48:29 (3777) [INFO] slower). If it is a very temporary problem though, this is often a nice * 30-01:48:29 (3777) [INFO] compromise: * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 30-01:48:29 (3777) [INFO]  * 30-01:48:29 (3777) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 30-01:48:29 (3787) [INFO]  * 30-01:48:29 (3324) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-01:48:29 (2667) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-01:48:29 (2667) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-01:48:29 (2986) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 30-01:48:29 (1594) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ILkAstAkzn/ea_profile.json * 30-01:49:51 (2634) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ILkAstAkzn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1596.  * 30-01:49:51 (688) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:53:58 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:54:02 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:54:02 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:59:24 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:59:24 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:59:24 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 30-01:59:24 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:59:24 (3332) [INFO] Checking if your system is up to date:  * 30-01:59:24 (3777) [INFO] Running: /usr/bin/yum clean all * 30-01:59:24 (3778) [INFO]  * 30-01:59:25 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:59:25 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:59:25 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:59:25 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:59:25 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 30-01:59:25 (3788) [INFO] Cleaning up list of fastest mirrors * 30-01:59:25 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 30-01:59:26 (3798) [INFO]  * 30-01:59:26 (3777) [INFO] Running: /usr/bin/yum check-update * 30-01:59:26 (3778) [INFO]  * 30-01:59:26 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:59:27 (3788) [INFO] Determining fastest mirrors * 30-02:00:57 (3788) [INFO] * EA4: 208.74.123.62 * 30-02:00:57 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 30-02:00:57 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 30-02:00:57 (3788) [INFO] * base: repos.forethought.net * 30-02:00:57 (3788) [INFO] * epel: mirrors.xmission.com * 30-02:00:57 (3788) [INFO] * extras: mirrors.xmission.com * 30-02:00:57 (3788) [INFO] * updates: mirrors.sonic.net * 30-02:04:01 (3788) [INFO]  * 30-02:04:01 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 30-02:04:01 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-02:04:03 (3798) [INFO]  * 30-02:04:03 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-02:04:03 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-02:04:03 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-02:04:03 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 30-02:04:03 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S4cn6PtzjB/ea_profile.json * 30-02:04:14 (1623) [INFO] Backed up EA4 profile to /tmp/S4cn6PtzjB/ea_profile.json * 30-02:04:14 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 30-02:08:14 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 01-01:44:12 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 01-01:44:15 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 01-01:44:15 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:01 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 01-01:47:01 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 01-01:47:02 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 01-01:47:02 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 01-01:47:02 (3332) [INFO] Checking if your system is up to date:  * 01-01:47:02 (3777) [INFO] Running: /usr/bin/yum clean all * 01-01:47:02 (3778) [INFO]  * 01-01:47:03 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:03 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 01-01:47:03 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-01:47:03 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 01-01:47:03 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 01-01:47:03 (3788) [INFO] Cleaning up list of fastest mirrors * 01-01:47:03 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 01-01:47:03 (3798) [INFO]  * 01-01:47:03 (3777) [INFO] Running: /usr/bin/yum check-update * 01-01:47:03 (3778) [INFO]  * 01-01:47:04 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:05 (3788) [INFO] Determining fastest mirrors * 01-01:48:35 (3788) [INFO] * EA4: 208.74.123.62 * 01-01:48:35 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 01-01:48:35 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 01-01:48:35 (3788) [INFO] * base: mirror.chpc.utah.edu * 01-01:48:35 (3788) [INFO] * epel: mirrors.xmission.com * 01-01:48:35 (3788) [INFO] * extras: mirrors.xtom.com * 01-01:48:35 (3788) [INFO] * updates: mirrors.oit.uci.edu * 01-01:50:24 (3788) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/82902749b398609965509e674ff635a3f3a675f6284a7fa27e79f077bd11eb6f-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 01-01:50:24 (3788) [INFO] Trying other mirror. * 01-01:50:24 (3788) [INFO] To address this issue please refer to the below wiki article  * 01-01:50:24 (3788) [INFO]  * 01-01:50:24 (3788) [INFO] https://wiki.centos.org/yum-errors * 01-01:50:24 (3788) [INFO]  * 01-01:50:24 (3788) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 01-01:50:24 (3788) [INFO]  * 01-01:51:28 (3788) [INFO]  * 01-01:51:28 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 01-01:51:28 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-01:51:28 (3798) [INFO]  * 01-01:51:28 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-01:51:28 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-01:51:28 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 01-01:51:28 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 01-01:51:28 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ssU8k6Bnhb/ea_profile.json * 01-01:51:31 (1623) [INFO] Backed up EA4 profile to /tmp/ssU8k6Bnhb/ea_profile.json * 01-01:51:31 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 01-01:55:32 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 02-01:49:46 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 02-01:49:54 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 02-01:49:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:52:52 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 02-01:52:52 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 02-01:52:52 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 02-01:52:52 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 02-01:52:52 (3332) [INFO] Checking if your system is up to date:  * 02-01:52:52 (3777) [INFO] Running: /usr/bin/yum clean all * 02-01:52:52 (3778) [INFO]  * 02-01:52:53 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:52:54 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 02-01:52:54 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-01:52:54 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 02-01:52:54 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 02-01:52:54 (3788) [INFO] Cleaning up list of fastest mirrors * 02-01:52:54 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 02-01:52:54 (3798) [INFO]  * 02-01:52:54 (3777) [INFO] Running: /usr/bin/yum check-update * 02-01:52:54 (3778) [INFO]  * 02-01:52:54 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:52:55 (3788) [INFO] Determining fastest mirrors * 02-01:54:25 (3788) [INFO] * EA4: 184.94.196.93 * 02-01:54:25 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 02-01:54:25 (3788) [INFO] * cpanel-plugins: 184.94.196.93 * 02-01:54:25 (3788) [INFO] * base: ziply.mm.fcix.net * 02-01:54:25 (3788) [INFO] * epel: mirrors.xmission.com * 02-01:54:25 (3788) [INFO] * extras: ohioix.mm.fcix.net * 02-01:54:25 (3788) [INFO] * updates: ziply.mm.fcix.net * 02-01:57:28 (3788) [INFO]  * 02-01:57:28 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 02-01:57:28 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-01:57:28 (3798) [INFO]  * 02-01:57:28 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-01:57:28 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-01:57:28 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 02-01:57:28 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 02-01:57:28 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3friSEqAZb/ea_profile.json * 02-01:57:31 (1623) [INFO] Backed up EA4 profile to /tmp/3friSEqAZb/ea_profile.json * 02-01:57:31 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 02-02:01:31 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 03-01:44:17 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 03-01:44:23 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 03-01:44:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:47 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 03-01:47:47 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 03-01:47:48 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 03-01:47:48 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 03-01:47:48 (3332) [INFO] Checking if your system is up to date:  * 03-01:47:48 (3777) [INFO] Running: /usr/bin/yum clean all * 03-01:47:48 (3778) [INFO]  * 03-01:47:48 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:47:49 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 03-01:47:49 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-01:47:49 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 03-01:47:49 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 03-01:47:49 (3788) [INFO] Cleaning up list of fastest mirrors * 03-01:47:49 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 03-01:47:49 (3798) [INFO]  * 03-01:47:49 (3777) [INFO] Running: /usr/bin/yum check-update * 03-01:47:49 (3778) [INFO]  * 03-01:47:49 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:47:50 (3788) [INFO] Determining fastest mirrors * 03-01:49:20 (3788) [INFO] * EA4: 208.74.123.62 * 03-01:49:20 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 03-01:49:20 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 03-01:49:20 (3788) [INFO] * base: mirror.chpc.utah.edu * 03-01:49:20 (3788) [INFO] * epel: irltoolkit.mm.fcix.net * 03-01:49:20 (3788) [INFO] * extras: mirror.keystealth.org * 03-01:49:20 (3788) [INFO] * updates: mirrors.xmission.com * 03-01:52:26 (3788) [INFO]  * 03-01:52:26 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 03-01:52:26 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-01:52:27 (3798) [INFO]  * 03-01:52:27 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-01:52:27 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-01:52:27 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 03-01:52:27 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 03-01:52:27 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NXD4FILUqe/ea_profile.json * 03-01:52:29 (1623) [INFO] Backed up EA4 profile to /tmp/NXD4FILUqe/ea_profile.json * 03-01:52:29 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 03-01:56:29 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 04-01:43:09 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 04-01:43:15 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 04-01:43:15 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:29 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 04-01:45:29 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 04-01:45:30 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 04-01:45:30 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 04-01:45:30 (3332) [INFO] Checking if your system is up to date:  * 04-01:45:30 (3777) [INFO] Running: /usr/bin/yum clean all * 04-01:45:30 (3778) [INFO]  * 04-01:45:31 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:45:31 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 04-01:45:31 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-01:45:31 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 04-01:45:31 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 04-01:45:31 (3788) [INFO] Cleaning up list of fastest mirrors * 04-01:45:31 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 04-01:45:31 (3798) [INFO]  * 04-01:45:31 (3777) [INFO] Running: /usr/bin/yum check-update * 04-01:45:31 (3778) [INFO]  * 04-01:45:32 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:45:32 (3788) [INFO] Determining fastest mirrors * 04-01:47:03 (3788) [INFO] * EA4: 208.74.123.62 * 04-01:47:03 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 04-01:47:03 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 04-01:47:03 (3788) [INFO] * base: ziply.mm.fcix.net * 04-01:47:03 (3788) [INFO] * epel: mirrors.xmission.com * 04-01:47:03 (3788) [INFO] * extras: mirror.us.oneandone.net * 04-01:47:03 (3788) [INFO] * updates: mirrors.oit.uci.edu * 04-01:49:32 (3788) [INFO]  * 04-01:49:32 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 04-01:49:32 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-01:49:33 (3798) [INFO]  * 04-01:49:33 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-01:49:33 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-01:49:33 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 04-01:49:33 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 04-01:49:33 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vyqCj47QVK/ea_profile.json * 04-01:49:35 (1623) [INFO] Backed up EA4 profile to /tmp/vyqCj47QVK/ea_profile.json * 04-01:49:35 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 04-01:53:36 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 05-01:42:21 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 05-01:42:26 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 05-01:42:26 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:44:41 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 05-01:44:41 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 05-01:44:41 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 05-01:44:42 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 05-01:44:42 (3332) [INFO] Checking if your system is up to date:  * 05-01:44:42 (3777) [INFO] Running: /usr/bin/yum clean all * 05-01:44:42 (3778) [INFO]  * 05-01:44:42 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:44:42 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 05-01:44:42 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-01:44:42 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 05-01:44:42 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 05-01:44:42 (3788) [INFO] Cleaning up list of fastest mirrors * 05-01:44:42 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 05-01:44:42 (3798) [INFO]  * 05-01:44:42 (3777) [INFO] Running: /usr/bin/yum check-update * 05-01:44:42 (3778) [INFO]  * 05-01:44:43 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:44:44 (3788) [INFO] Determining fastest mirrors * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] One of the configured repositories failed (Unknown), * 05-01:45:43 (3788) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 05-01:45:43 (3788) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 05-01:45:43 (3788) [INFO] upstream. This is most often useful if you are using a newer * 05-01:45:43 (3788) [INFO] distribution release than is supported by the repository (and the * 05-01:45:43 (3788) [INFO] packages for the previous distribution release still work). * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] 3. Run the command with the repository temporarily disabled * 05-01:45:43 (3788) [INFO] yum --disablerepo= ... * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 05-01:45:43 (3788) [INFO] will then just ignore the repository until you permanently enable it * 05-01:45:43 (3788) [INFO] again or use --enablerepo for temporary usage: * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] yum-config-manager --disable  * 05-01:45:43 (3788) [INFO] or * 05-01:45:43 (3788) [INFO] subscription-manager repos --disable= * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 05-01:45:43 (3788) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 05-01:45:43 (3788) [INFO] so will have to try and fail each time (and thus. yum will be be much * 05-01:45:43 (3788) [INFO] slower). If it is a very temporary problem though, this is often a nice * 05-01:45:43 (3788) [INFO] compromise: * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 05-01:45:43 (3788) [INFO]  * 05-01:45:43 (3788) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 05-01:45:43 (3798) [INFO]  * 05-01:45:43 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-01:45:43 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-01:45:43 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 05-01:45:43 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 05-01:45:43 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RWuHmjH6Cn/ea_profile.json * 05-01:50:00 (1623) [INFO] Backed up EA4 profile to /tmp/RWuHmjH6Cn/ea_profile.json * 05-01:50:00 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 05-01:54:01 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 06-01:43:17 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 06-01:43:28 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 06-01:43:28 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:21 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 06-01:46:21 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 06-01:46:21 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 06-01:46:21 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 06-01:46:21 (3332) [INFO] Checking if your system is up to date:  * 06-01:46:21 (3777) [INFO] Running: /usr/bin/yum clean all * 06-01:46:21 (3778) [INFO]  * 06-01:46:22 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:46:22 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 06-01:46:22 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-01:46:22 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 06-01:46:22 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 06-01:46:22 (3788) [INFO] Cleaning up list of fastest mirrors * 06-01:46:22 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 06-01:46:22 (3798) [INFO]  * 06-01:46:22 (3777) [INFO] Running: /usr/bin/yum check-update * 06-01:46:22 (3778) [INFO]  * 06-01:46:23 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:46:24 (3788) [INFO] Determining fastest mirrors * 06-01:47:53 (3788) [INFO] * EA4: 208.74.123.61 * 06-01:47:53 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 06-01:47:53 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 06-01:47:53 (3788) [INFO] * base: mirrors.xmission.com * 06-01:47:53 (3788) [INFO] * epel: mirrors.xmission.com * 06-01:47:53 (3788) [INFO] * extras: centos.mirror.ndchost.com * 06-01:47:53 (3788) [INFO] * updates: mirror.web-ster.com * 06-01:50:41 (3788) [INFO]  * 06-01:50:41 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 06-01:50:41 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-01:50:41 (3798) [INFO]  * 06-01:50:41 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-01:50:41 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-01:50:41 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 06-01:50:41 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 06-01:50:41 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BK77TjSMrq/ea_profile.json * 06-01:50:45 (1623) [INFO] Backed up EA4 profile to /tmp/BK77TjSMrq/ea_profile.json * 06-01:50:45 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 06-01:54:46 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 07-01:43:57 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 07-01:44:06 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 07-01:44:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:06 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 07-01:47:06 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 07-01:47:07 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 07-01:47:07 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 07-01:47:07 (3332) [INFO] Checking if your system is up to date:  * 07-01:47:07 (3777) [INFO] Running: /usr/bin/yum clean all * 07-01:47:07 (3778) [INFO]  * 07-01:47:08 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:47:08 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 07-01:47:08 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-01:47:08 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 07-01:47:08 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 07-01:47:08 (3788) [INFO] Cleaning up list of fastest mirrors * 07-01:47:08 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 07-01:47:09 (3798) [INFO]  * 07-01:47:09 (3777) [INFO] Running: /usr/bin/yum check-update * 07-01:47:09 (3778) [INFO]  * 07-01:47:09 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:47:10 (3788) [INFO] Determining fastest mirrors * 07-01:48:38 (3788) [INFO] * EA4: 208.74.123.62 * 07-01:48:38 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 07-01:48:38 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 07-01:48:38 (3788) [INFO] * base: mirror.steadfastnet.com * 07-01:48:38 (3788) [INFO] * epel: mirrors.xmission.com * 07-01:48:38 (3788) [INFO] * extras: repos.forethought.net * 07-01:48:38 (3788) [INFO] * updates: linux.mirrors.es.net * 07-01:51:45 (3788) [INFO]  * 07-01:51:45 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 07-01:51:45 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-01:51:45 (3798) [INFO]  * 07-01:51:45 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-01:51:45 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-01:51:45 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 07-01:51:45 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 07-01:51:45 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sUWaXcYdm6/ea_profile.json * 07-01:51:48 (1623) [INFO] Backed up EA4 profile to /tmp/sUWaXcYdm6/ea_profile.json * 07-01:51:48 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 07-01:55:48 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 08-01:45:57 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 08-01:46:00 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 08-01:46:00 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:03 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 08-01:49:03 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 08-01:49:04 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 08-01:49:04 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 08-01:49:05 (3332) [INFO] Checking if your system is up to date:  * 08-01:49:05 (3777) [INFO] Running: /usr/bin/yum clean all * 08-01:49:05 (3778) [INFO]  * 08-01:49:05 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:49:05 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 08-01:49:05 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-01:49:05 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 08-01:49:05 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 08-01:49:05 (3788) [INFO] Cleaning up list of fastest mirrors * 08-01:49:05 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 08-01:49:05 (3798) [INFO]  * 08-01:49:05 (3777) [INFO] Running: /usr/bin/yum check-update * 08-01:49:05 (3778) [INFO]  * 08-01:49:06 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:49:06 (3788) [INFO] Determining fastest mirrors * 08-01:50:35 (3788) [INFO] * EA4: 208.74.123.62 * 08-01:50:35 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 08-01:50:35 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 08-01:50:35 (3788) [INFO] * base: centos-distro.cavecreek.net * 08-01:50:35 (3788) [INFO] * epel: mirrors.xmission.com * 08-01:50:35 (3788) [INFO] * extras: ziply.mm.fcix.net * 08-01:50:35 (3788) [INFO] * updates: mirror.keystealth.org * 08-01:53:22 (3788) [INFO]  * 08-01:53:22 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 08-01:53:22 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-01:53:22 (3798) [INFO]  * 08-01:53:22 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-01:53:22 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-01:53:22 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 08-01:53:22 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 08-01:53:22 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9NJYGcd3DV/ea_profile.json * 08-01:53:26 (1623) [INFO] Backed up EA4 profile to /tmp/9NJYGcd3DV/ea_profile.json * 08-01:53:26 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 08-01:57:27 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 09-01:43:58 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 09-01:44:01 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 09-01:44:01 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:49 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 09-01:46:49 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 09-01:46:49 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 09-01:46:49 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 09-01:46:49 (3332) [INFO] Checking if your system is up to date:  * 09-01:46:49 (3777) [INFO] Running: /usr/bin/yum clean all * 09-01:46:49 (3778) [INFO]  * 09-01:46:50 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:46:50 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 09-01:46:50 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-01:46:50 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 09-01:46:50 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 09-01:46:50 (3788) [INFO] Cleaning up list of fastest mirrors * 09-01:46:50 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 09-01:46:50 (3798) [INFO]  * 09-01:46:50 (3777) [INFO] Running: /usr/bin/yum check-update * 09-01:46:50 (3778) [INFO]  * 09-01:46:51 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:46:52 (3788) [INFO] Determining fastest mirrors * 09-01:48:22 (3788) [INFO] * EA4: 208.74.123.61 * 09-01:48:22 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 09-01:48:22 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 09-01:48:22 (3788) [INFO] * base: mirror.facebook.net * 09-01:48:22 (3788) [INFO] * epel: mirrors.ocf.berkeley.edu * 09-01:48:22 (3788) [INFO] * extras: mirrors.sonic.net * 09-01:48:22 (3788) [INFO] * updates: or-mirror.iwebfusion.net * 09-01:50:39 (3788) [INFO]  * 09-01:50:39 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 09-01:50:39 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-01:50:39 (3798) [INFO]  * 09-01:50:39 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-01:50:39 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-01:50:39 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 09-01:50:39 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 09-01:50:39 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S1NsyyKW4U/ea_profile.json * 09-01:50:42 (1623) [INFO] Backed up EA4 profile to /tmp/S1NsyyKW4U/ea_profile.json * 09-01:50:42 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 09-01:54:42 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 10-01:45:21 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 10-01:45:30 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 10-01:45:30 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:02 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 10-01:48:02 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 10-01:48:03 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 10-01:48:03 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 10-01:48:03 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 10-01:48:03 (3332) [INFO] Checking if your system is up to date:  * 10-01:48:03 (3777) [INFO] Running: /usr/bin/yum clean all * 10-01:48:03 (3778) [INFO]  * 10-01:48:03 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:48:03 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 10-01:48:03 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-01:48:03 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 10-01:48:03 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 10-01:48:04 (3788) [INFO] Cleaning up list of fastest mirrors * 10-01:48:04 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 10-01:48:04 (3798) [INFO]  * 10-01:48:04 (3777) [INFO] Running: /usr/bin/yum check-update * 10-01:48:04 (3778) [INFO]  * 10-01:48:04 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:48:05 (3788) [INFO] Determining fastest mirrors * 10-01:49:35 (3788) [INFO] * EA4: 208.74.123.62 * 10-01:49:35 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 10-01:49:35 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 10-01:49:35 (3788) [INFO] * base: repos.lax.layerhost.com * 10-01:49:35 (3788) [INFO] * epel: mirrors.xmission.com * 10-01:49:35 (3788) [INFO] * extras: mirrors.oit.uci.edu * 10-01:49:35 (3788) [INFO] * updates: la.mirrors.clouvider.net * 10-01:52:25 (3788) [INFO]  * 10-01:52:25 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 10-01:52:25 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-01:52:25 (3798) [INFO]  * 10-01:52:25 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-01:52:25 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-01:52:25 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 10-01:52:25 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 10-01:52:25 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/55lDAsYFhm/ea_profile.json * 10-01:52:29 (1623) [INFO] Backed up EA4 profile to /tmp/55lDAsYFhm/ea_profile.json * 10-01:52:29 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 10-01:56:29 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 11-01:44:00 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 11-01:44:06 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 11-01:44:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:34 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 11-01:46:34 (3484) [ERROR] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/87c152e7411b6ae6cf20164b494e3c6c0061a3575b61ae0a952a622813537af7-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/.  * 11-01:46:34 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 11-01:46:34 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 11-01:46:34 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 11-01:46:35 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 11-01:46:35 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 11-01:46:35 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 11-01:46:35 (3332) [INFO] Checking if your system is up to date:  * 11-01:46:35 (3777) [INFO] Running: /usr/bin/yum clean all * 11-01:46:35 (3778) [INFO]  * 11-01:46:35 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:46:35 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 11-01:46:35 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-01:46:35 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 11-01:46:35 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 11-01:46:36 (3788) [INFO] Cleaning up list of fastest mirrors * 11-01:46:36 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 11-01:46:36 (3798) [INFO]  * 11-01:46:36 (3777) [INFO] Running: /usr/bin/yum check-update * 11-01:46:36 (3778) [INFO]  * 11-01:46:36 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:46:37 (3788) [INFO] Determining fastest mirrors * 11-01:48:11 (3788) [INFO] * EA4: 208.74.123.62 * 11-01:48:11 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 11-01:48:11 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 11-01:48:11 (3788) [INFO] * base: mirrors.xmission.com * 11-01:48:11 (3788) [INFO] * epel: mirrors.xmission.com * 11-01:48:11 (3788) [INFO] * extras: ziply.mm.fcix.net * 11-01:48:11 (3788) [INFO] * updates: mirror.arizona.edu * 11-01:49:45 (3788) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/7135c596148661011cc9248474307cc43a8f8c233eff3e7ebc43980d11f450dd-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 11-01:49:45 (3788) [INFO] Trying other mirror. * 11-01:49:45 (3788) [INFO] To address this issue please refer to the below wiki article  * 11-01:49:45 (3788) [INFO]  * 11-01:49:45 (3788) [INFO] https://wiki.centos.org/yum-errors * 11-01:49:45 (3788) [INFO]  * 11-01:49:45 (3788) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 11-01:49:45 (3788) [INFO]  * 11-01:50:58 (3788) [INFO]  * 11-01:50:58 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 11-01:50:58 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-01:50:59 (3798) [INFO]  * 11-01:50:59 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-01:50:59 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-01:50:59 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 11-01:50:59 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 11-01:50:59 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4nxLMWDqYE/ea_profile.json * 11-01:51:01 (1623) [INFO] Backed up EA4 profile to /tmp/4nxLMWDqYE/ea_profile.json * 11-01:51:01 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 11-01:55:02 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 12-01:42:20 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 12-01:42:26 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 12-01:42:26 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:44:55 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 12-01:44:55 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 12-01:44:56 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 12-01:44:56 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 12-01:44:56 (3332) [INFO] Checking if your system is up to date:  * 12-01:44:56 (3777) [INFO] Running: /usr/bin/yum clean all * 12-01:44:56 (3778) [INFO]  * 12-01:44:56 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:44:57 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 12-01:44:57 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-01:44:57 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 12-01:44:57 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 12-01:44:57 (3788) [INFO] Cleaning up list of fastest mirrors * 12-01:44:57 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 12-01:44:57 (3798) [INFO]  * 12-01:44:57 (3777) [INFO] Running: /usr/bin/yum check-update * 12-01:44:57 (3778) [INFO]  * 12-01:44:58 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:44:59 (3788) [INFO] Determining fastest mirrors * 12-01:46:28 (3788) [INFO] * EA4: 184.94.196.93 * 12-01:46:28 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 12-01:46:28 (3788) [INFO] * cpanel-plugins: 184.94.196.93 * 12-01:46:28 (3788) [INFO] * base: mirrors.xmission.com * 12-01:46:28 (3788) [INFO] * epel: mirrors.xmission.com * 12-01:46:28 (3788) [INFO] * extras: ziply.mm.fcix.net * 12-01:46:28 (3788) [INFO] * updates: mirrors.oit.uci.edu * 12-01:49:13 (3788) [INFO]  * 12-01:49:13 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 12-01:49:13 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-01:49:13 (3798) [INFO]  * 12-01:49:13 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-01:49:13 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-01:49:13 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 12-01:49:13 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 12-01:49:13 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pyXDzv9rNa/ea_profile.json * 12-01:49:15 (1623) [INFO] Backed up EA4 profile to /tmp/pyXDzv9rNa/ea_profile.json * 12-01:49:15 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 12-01:53:16 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 13-01:43:32 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 13-01:43:39 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 13-01:43:39 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:09 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 13-01:46:09 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30002 milliseconds with 0 out of 0 bytes received')  * 13-01:46:09 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 13-01:46:09 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 13-01:46:09 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 13-01:46:10 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 13-01:46:10 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 13-01:46:10 (3332) [INFO] Checking if your system is up to date:  * 13-01:46:10 (3777) [INFO] Running: /usr/bin/yum clean all * 13-01:46:10 (3778) [INFO]  * 13-01:46:10 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:10 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 13-01:46:10 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-01:46:10 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 13-01:46:10 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 13-01:46:11 (3788) [INFO] Cleaning up list of fastest mirrors * 13-01:46:11 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 13-01:46:11 (3798) [INFO]  * 13-01:46:11 (3777) [INFO] Running: /usr/bin/yum check-update * 13-01:46:11 (3778) [INFO]  * 13-01:46:11 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:12 (3788) [INFO] Determining fastest mirrors * 13-01:47:42 (3788) [INFO] * EA4: 208.74.123.62 * 13-01:47:42 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 13-01:47:42 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 13-01:47:42 (3788) [INFO] * base: mirrors.raystedman.org * 13-01:47:43 (3788) [INFO] * epel: ziply.mm.fcix.net * 13-01:47:43 (3788) [INFO] * extras: mirror.fcix.net * 13-01:47:43 (3788) [INFO] * updates: abqix.mm.fcix.net * 13-01:50:37 (3788) [INFO]  * 13-01:50:37 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 13-01:50:37 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-01:50:37 (3798) [INFO]  * 13-01:50:37 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-01:50:37 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-01:50:37 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 13-01:50:37 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 13-01:50:37 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rHBIPu2f2y/ea_profile.json * 13-01:50:40 (1623) [INFO] Backed up EA4 profile to /tmp/rHBIPu2f2y/ea_profile.json * 13-01:50:40 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 13-01:54:40 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 13-01:54:40 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 14-01:43:48 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 14-01:43:51 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 14-01:43:51 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:33 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 14-01:46:33 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 14-01:46:34 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 14-01:46:34 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 14-01:46:34 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 14-01:46:34 (3332) [INFO] Checking if your system is up to date:  * 14-01:46:34 (3777) [INFO] Running: /usr/bin/yum clean all * 14-01:46:34 (3778) [INFO]  * 14-01:46:34 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:46:34 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 14-01:46:34 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-01:46:34 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 14-01:46:34 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 14-01:46:34 (3788) [INFO] Cleaning up list of fastest mirrors * 14-01:46:34 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 14-01:46:34 (3798) [INFO]  * 14-01:46:34 (3777) [INFO] Running: /usr/bin/yum check-update * 14-01:46:34 (3778) [INFO]  * 14-01:46:35 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:46:36 (3788) [INFO] Determining fastest mirrors * 14-01:48:05 (3788) [INFO] * EA4: 208.74.123.61 * 14-01:48:05 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 14-01:48:05 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 14-01:48:05 (3788) [INFO] * base: mirrors.raystedman.org * 14-01:48:05 (3788) [INFO] * epel: mirrors.xmission.com * 14-01:48:05 (3788) [INFO] * extras: repos.lax.layerhost.com * 14-01:48:05 (3788) [INFO] * updates: mirror.keystealth.org * 14-01:50:49 (3788) [INFO]  * 14-01:50:49 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 14-01:50:49 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-01:50:49 (3798) [INFO]  * 14-01:50:49 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-01:50:49 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-01:50:49 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 14-01:50:49 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 14-01:50:49 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/53zLodE8dG/ea_profile.json * 14-01:50:52 (1623) [INFO] Backed up EA4 profile to /tmp/53zLodE8dG/ea_profile.json * 14-01:50:52 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 14-01:54:52 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 14-01:54:52 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 15-01:43:29 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 15-01:43:33 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 15-01:43:33 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:17 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 15-01:46:17 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 15-01:46:18 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 15-01:46:18 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 15-01:46:18 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 15-01:46:18 (3332) [INFO] Checking if your system is up to date:  * 15-01:46:18 (3777) [INFO] Running: /usr/bin/yum clean all * 15-01:46:18 (3778) [INFO]  * 15-01:46:18 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:46:19 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 15-01:46:19 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-01:46:19 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 15-01:46:19 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 15-01:46:19 (3788) [INFO] Cleaning up list of fastest mirrors * 15-01:46:19 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 15-01:46:19 (3798) [INFO]  * 15-01:46:19 (3777) [INFO] Running: /usr/bin/yum check-update * 15-01:46:19 (3778) [INFO]  * 15-01:46:19 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:46:20 (3788) [INFO] Determining fastest mirrors * 15-01:47:49 (3788) [INFO] * EA4: 208.74.123.62 * 15-01:47:49 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 15-01:47:49 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 15-01:47:49 (3788) [INFO] * base: repos.forethought.net * 15-01:47:49 (3788) [INFO] * epel: mirrors.xmission.com * 15-01:47:49 (3788) [INFO] * extras: mirrors.raystedman.org * 15-01:47:49 (3788) [INFO] * updates: repos.forethought.net * 15-01:50:36 (3788) [INFO]  * 15-01:50:36 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 15-01:50:36 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-01:50:36 (3798) [INFO]  * 15-01:50:36 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-01:50:36 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-01:50:36 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 15-01:50:36 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 15-01:50:36 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D7ab18wAfY/ea_profile.json * 15-01:50:39 (1623) [INFO] Backed up EA4 profile to /tmp/D7ab18wAfY/ea_profile.json * 15-01:50:39 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 15-01:54:40 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 15-01:54:40 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 16-01:48:27 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 16-01:48:32 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 16-01:48:32 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:16 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 16-01:51:16 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30004 milliseconds with 0 out of 0 bytes received')  * 16-01:51:16 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 16-01:51:16 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 16-01:51:16 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 16-01:51:17 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 16-01:51:17 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 16-01:51:17 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 16-01:51:17 (3332) [INFO] Checking if your system is up to date:  * 16-01:51:17 (3777) [INFO] Running: /usr/bin/yum clean all * 16-01:51:17 (3778) [INFO]  * 16-01:51:18 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:51:18 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 16-01:51:18 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-01:51:18 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 16-01:51:18 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 16-01:51:18 (3788) [INFO] Cleaning up list of fastest mirrors * 16-01:51:18 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 16-01:51:18 (3798) [INFO]  * 16-01:51:18 (3777) [INFO] Running: /usr/bin/yum check-update * 16-01:51:18 (3778) [INFO]  * 16-01:51:19 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:51:20 (3788) [INFO] Determining fastest mirrors * 16-01:52:49 (3788) [INFO] * EA4: 208.74.123.62 * 16-01:52:49 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 16-01:52:49 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 16-01:52:49 (3788) [INFO] * base: mirrors.xmission.com * 16-01:52:49 (3788) [INFO] * epel: irltoolkit.mm.fcix.net * 16-01:52:49 (3788) [INFO] * extras: ziply.mm.fcix.net * 16-01:52:49 (3788) [INFO] * updates: ftp.osuosl.org * 16-01:55:51 (3788) [INFO]  * 16-01:55:51 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 16-01:55:51 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-01:55:51 (3798) [INFO]  * 16-01:55:51 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-01:55:51 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-01:55:51 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 16-01:55:51 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 16-01:55:51 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dNAuy1MhSW/ea_profile.json * 16-01:55:54 (1623) [INFO] Backed up EA4 profile to /tmp/dNAuy1MhSW/ea_profile.json * 16-01:55:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 16-01:59:55 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 16-01:59:55 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 17-01:46:46 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 17-01:47:03 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 17-01:47:03 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:42 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 17-01:49:42 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30005 milliseconds with 0 out of 0 bytes received')  * 17-01:49:42 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 17-01:49:42 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 17-01:49:42 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 17-01:49:43 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 17-01:49:43 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 17-01:49:43 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 17-01:49:43 (3332) [INFO] Checking if your system is up to date:  * 17-01:49:43 (3777) [INFO] Running: /usr/bin/yum clean all * 17-01:49:43 (3778) [INFO]  * 17-01:49:45 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:49:45 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 17-01:49:45 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-01:49:45 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 17-01:49:45 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 17-01:49:45 (3788) [INFO] Cleaning up list of fastest mirrors * 17-01:49:45 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 17-01:49:45 (3798) [INFO]  * 17-01:49:45 (3777) [INFO] Running: /usr/bin/yum check-update * 17-01:49:45 (3778) [INFO]  * 17-01:49:46 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-01:49:47 (3788) [INFO] Determining fastest mirrors * 17-01:51:18 (3788) [INFO] * EA4: 208.74.123.61 * 17-01:51:18 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 17-01:51:18 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 17-01:51:18 (3788) [INFO] * base: repos.forethought.net * 17-01:51:18 (3788) [INFO] * epel: mirrors.xmission.com * 17-01:51:18 (3788) [INFO] * extras: mirrors.ocf.berkeley.edu * 17-01:51:18 (3788) [INFO] * updates: mirrors.vcea.wsu.edu * 17-01:53:51 (3788) [INFO]  * 17-01:53:51 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 17-01:53:51 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-01:53:52 (3798) [INFO]  * 17-01:53:52 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-01:53:52 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-01:53:52 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 17-01:53:52 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 17-01:53:52 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aRTyZlhq3B/ea_profile.json * 17-01:53:54 (1623) [INFO] Backed up EA4 profile to /tmp/aRTyZlhq3B/ea_profile.json * 17-01:53:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 17-01:57:54 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 17-01:57:55 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 18-01:46:47 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 18-01:46:54 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 18-01:46:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:55 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 18-01:49:55 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 18-01:49:56 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 18-01:49:56 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 18-01:49:56 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 18-01:49:56 (3332) [INFO] Checking if your system is up to date:  * 18-01:49:56 (3777) [INFO] Running: /usr/bin/yum clean all * 18-01:49:56 (3778) [INFO]  * 18-01:49:57 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:49:57 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 18-01:49:57 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-01:49:57 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 18-01:49:57 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 18-01:49:57 (3788) [INFO] Cleaning up list of fastest mirrors * 18-01:49:57 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 18-01:49:57 (3798) [INFO]  * 18-01:49:57 (3777) [INFO] Running: /usr/bin/yum check-update * 18-01:49:57 (3778) [INFO]  * 18-01:49:58 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:49:58 (3788) [INFO] Determining fastest mirrors * 18-01:51:26 (3788) [INFO] * EA4: 184.94.196.97 * 18-01:51:26 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 18-01:51:26 (3788) [INFO] * cpanel-plugins: 184.94.196.97 * 18-01:51:26 (3788) [INFO] * base: mirror.keystealth.org * 18-01:51:26 (3788) [INFO] * epel: mirrors.xmission.com * 18-01:51:26 (3788) [INFO] * extras: mirrors.sonic.net * 18-01:51:26 (3788) [INFO] * updates: mirror.web-ster.com * 18-01:54:26 (3788) [INFO]  * 18-01:54:26 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 18-01:54:26 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-01:54:26 (3798) [INFO]  * 18-01:54:26 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-01:54:26 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-01:54:26 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 18-01:54:26 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 18-01:54:26 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wwJ302hR6M/ea_profile.json * 18-01:54:32 (1623) [INFO] Backed up EA4 profile to /tmp/wwJ302hR6M/ea_profile.json * 18-01:54:32 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 18-01:58:32 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 18-01:58:32 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 19-01:43:14 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 19-01:43:20 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 19-01:43:20 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:17 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 19-01:46:17 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 19-01:46:18 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 19-01:46:18 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 19-01:46:18 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 19-01:46:18 (3332) [INFO] Checking if your system is up to date:  * 19-01:46:18 (3777) [INFO] Running: /usr/bin/yum clean all * 19-01:46:18 (3778) [INFO]  * 19-01:46:18 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:46:18 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 19-01:46:18 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-01:46:18 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 19-01:46:18 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 19-01:46:19 (3788) [INFO] Cleaning up list of fastest mirrors * 19-01:46:19 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 19-01:46:19 (3798) [INFO]  * 19-01:46:19 (3777) [INFO] Running: /usr/bin/yum check-update * 19-01:46:19 (3778) [INFO]  * 19-01:46:19 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:46:20 (3788) [INFO] Determining fastest mirrors * 19-01:47:50 (3788) [INFO] * EA4: 208.74.123.61 * 19-01:47:50 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 19-01:47:50 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 19-01:47:50 (3788) [INFO] * base: mirror.keystealth.org * 19-01:47:50 (3788) [INFO] * epel: mirrors.xmission.com * 19-01:47:50 (3788) [INFO] * extras: mirror.chpc.utah.edu * 19-01:47:50 (3788) [INFO] * updates: mirror.web-ster.com * 19-01:50:52 (3788) [INFO]  * 19-01:50:52 (3788) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 19-01:50:52 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-01:50:53 (3798) [INFO]  * 19-01:50:53 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-01:50:53 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-01:50:53 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 19-01:50:53 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 19-01:50:53 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UkCw5rOivS/ea_profile.json * 19-01:50:55 (1623) [INFO] Backed up EA4 profile to /tmp/UkCw5rOivS/ea_profile.json * 19-01:50:55 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 19-01:54:56 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 19-01:54:56 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 20-01:43:58 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 20-01:44:02 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 20-01:44:02 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:01 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 20-01:47:01 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 20-01:47:01 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 20-01:47:01 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 20-01:47:01 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 20-01:47:01 (3332) [INFO] Checking if your system is up to date:  * 20-01:47:01 (3777) [INFO] Running: /usr/bin/yum clean all * 20-01:47:01 (3778) [INFO]  * 20-01:47:03 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:47:03 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 20-01:47:03 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-01:47:03 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 20-01:47:03 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 20-01:47:03 (3788) [INFO] Cleaning up list of fastest mirrors * 20-01:47:03 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 20-01:47:03 (3798) [INFO]  * 20-01:47:03 (3777) [INFO] Running: /usr/bin/yum check-update * 20-01:47:03 (3778) [INFO]  * 20-01:47:04 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:47:04 (3788) [INFO] Determining fastest mirrors * 20-01:48:35 (3788) [INFO] * EA4: 208.74.123.62 * 20-01:48:35 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 20-01:48:35 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 20-01:48:35 (3788) [INFO] * base: mirror.den01.meanservers.net * 20-01:48:35 (3788) [INFO] * epel: mirrors.xmission.com * 20-01:48:35 (3788) [INFO] * extras: mirrors.xmission.com * 20-01:48:35 (3788) [INFO] * updates: mirror.fcix.net * 20-01:51:35 (3788) [INFO]  * 20-01:51:35 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 20-01:51:35 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-01:51:35 (3798) [INFO]  * 20-01:51:35 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-01:51:35 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-01:51:35 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 20-01:51:35 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 20-01:51:35 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QmbOOO_zpS/ea_profile.json * 20-01:51:38 (1623) [INFO] Backed up EA4 profile to /tmp/QmbOOO_zpS/ea_profile.json * 20-01:51:38 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 20-01:55:38 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (3). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 20-01:55:38 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 21-01:42:39 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 21-01:42:45 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 21-01:42:45 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:27 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 21-01:45:27 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 21-01:45:28 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 21-01:45:28 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 21-01:45:28 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 21-01:45:28 (3332) [INFO] Checking if your system is up to date:  * 21-01:45:28 (3777) [INFO] Running: /usr/bin/yum clean all * 21-01:45:28 (3778) [INFO]  * 21-01:45:28 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:45:29 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 21-01:45:29 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-01:45:29 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 21-01:45:29 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 21-01:45:29 (3788) [INFO] Cleaning up list of fastest mirrors * 21-01:45:29 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 21-01:45:29 (3798) [INFO]  * 21-01:45:29 (3777) [INFO] Running: /usr/bin/yum check-update * 21-01:45:29 (3778) [INFO]  * 21-01:45:29 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:45:30 (3788) [INFO] Determining fastest mirrors * 21-01:46:58 (3788) [INFO] * EA4: 208.74.123.61 * 21-01:46:58 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 21-01:46:58 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 21-01:46:58 (3788) [INFO] * base: mirrors.raystedman.org * 21-01:46:58 (3788) [INFO] * epel: mirrors.xmission.com * 21-01:46:58 (3788) [INFO] * extras: opencolo.mm.fcix.net * 21-01:46:58 (3788) [INFO] * updates: mirror.chpc.utah.edu * 21-01:49:45 (3788) [INFO]  * 21-01:49:45 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 21-01:49:45 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-01:49:45 (3798) [INFO]  * 21-01:49:45 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-01:49:45 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-01:49:45 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 21-01:49:45 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 21-01:49:45 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sBTIFLr67d/ea_profile.json * 21-01:49:48 (1623) [INFO] Backed up EA4 profile to /tmp/sBTIFLr67d/ea_profile.json * 21-01:49:48 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 21-01:53:48 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 21-01:53:49 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 22-01:46:49 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 22-01:46:53 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 22-01:46:53 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:38 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 22-01:49:38 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 22-01:49:39 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 22-01:49:39 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 22-01:49:39 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 22-01:49:39 (3332) [INFO] Checking if your system is up to date:  * 22-01:49:39 (3777) [INFO] Running: /usr/bin/yum clean all * 22-01:49:39 (3778) [INFO]  * 22-01:49:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:49:40 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 22-01:49:40 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-01:49:40 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 22-01:49:40 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 22-01:49:40 (3788) [INFO] Cleaning up list of fastest mirrors * 22-01:49:40 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 22-01:49:40 (3798) [INFO]  * 22-01:49:40 (3777) [INFO] Running: /usr/bin/yum check-update * 22-01:49:40 (3778) [INFO]  * 22-01:49:40 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:49:41 (3788) [INFO] Determining fastest mirrors * 22-01:51:14 (3788) [INFO] * EA4: 208.74.123.62 * 22-01:51:14 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 22-01:51:14 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 22-01:51:14 (3788) [INFO] * base: mirrors.raystedman.org * 22-01:51:14 (3788) [INFO] * epel: mirrors.xmission.com * 22-01:51:14 (3788) [INFO] * extras: la.mirrors.clouvider.net * 22-01:51:14 (3788) [INFO] * updates: mirror.fcix.net * 22-01:53:58 (3788) [INFO]  * 22-01:53:58 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 22-01:53:58 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-01:53:59 (3798) [INFO]  * 22-01:53:59 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-01:53:59 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-01:53:59 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 22-01:53:59 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 22-01:53:59 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V2jOFcU6Ih/ea_profile.json * 22-01:54:04 (1623) [INFO] Backed up EA4 profile to /tmp/V2jOFcU6Ih/ea_profile.json * 22-01:54:04 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 22-01:58:05 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 22-01:58:05 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 23-01:42:13 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 23-01:42:18 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 23-01:42:18 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:01 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 23-01:45:01 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 23-01:45:02 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 23-01:45:02 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 23-01:45:02 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 23-01:45:02 (3332) [INFO] Checking if your system is up to date:  * 23-01:45:02 (3777) [INFO] Running: /usr/bin/yum clean all * 23-01:45:02 (3778) [INFO]  * 23-01:45:03 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:45:04 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 23-01:45:04 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-01:45:04 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 23-01:45:04 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 23-01:45:04 (3788) [INFO] Cleaning up list of fastest mirrors * 23-01:45:04 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 23-01:45:04 (3798) [INFO]  * 23-01:45:04 (3777) [INFO] Running: /usr/bin/yum check-update * 23-01:45:04 (3778) [INFO]  * 23-01:45:04 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:45:05 (3788) [INFO] Determining fastest mirrors * 23-01:46:34 (3788) [INFO] * EA4: 208.74.123.61 * 23-01:46:34 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 23-01:46:34 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 23-01:46:34 (3788) [INFO] * base: mirrors.xtom.com * 23-01:46:34 (3788) [INFO] * epel: mirrors.xmission.com * 23-01:46:34 (3788) [INFO] * extras: ziply.mm.fcix.net * 23-01:46:34 (3788) [INFO] * updates: mirrors.raystedman.org * 23-01:49:05 (3788) [INFO]  * 23-01:49:05 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 23-01:49:05 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-01:49:05 (3798) [INFO]  * 23-01:49:05 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-01:49:05 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-01:49:05 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 23-01:49:05 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 23-01:49:05 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8gQIwWFHTZ/ea_profile.json * 23-01:49:07 (1623) [INFO] Backed up EA4 profile to /tmp/8gQIwWFHTZ/ea_profile.json * 23-01:49:07 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 23-01:53:08 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 23-01:53:08 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 24-01:47:02 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 24-01:47:08 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 24-01:47:08 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:25 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 24-01:49:25 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 24-01:49:26 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 24-01:49:26 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 24-01:49:26 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 24-01:49:26 (3332) [INFO] Checking if your system is up to date:  * 24-01:49:26 (3777) [INFO] Running: /usr/bin/yum clean all * 24-01:49:26 (3778) [INFO]  * 24-01:49:26 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:49:26 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 24-01:49:26 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-01:49:26 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 24-01:49:26 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 24-01:49:27 (3788) [INFO] Cleaning up list of fastest mirrors * 24-01:49:27 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 24-01:49:27 (3798) [INFO]  * 24-01:49:27 (3777) [INFO] Running: /usr/bin/yum check-update * 24-01:49:27 (3778) [INFO]  * 24-01:49:27 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:49:28 (3788) [INFO] Determining fastest mirrors * 24-01:50:56 (3788) [INFO] * EA4: 208.74.123.61 * 24-01:50:56 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 24-01:50:56 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 24-01:50:56 (3788) [INFO] * base: ziply.mm.fcix.net * 24-01:50:56 (3788) [INFO] * epel: mirrors.xmission.com * 24-01:50:56 (3788) [INFO] * extras: ridgewireless.mm.fcix.net * 24-01:50:56 (3788) [INFO] * updates: mirrors.xtom.com * 24-01:53:16 (3788) [INFO]  * 24-01:53:16 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 24-01:53:16 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-01:53:16 (3798) [INFO]  * 24-01:53:16 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-01:53:16 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-01:53:16 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 24-01:53:16 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 24-01:53:16 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VFSqmPx6Pg/ea_profile.json * 24-01:53:20 (1623) [INFO] Backed up EA4 profile to /tmp/VFSqmPx6Pg/ea_profile.json * 24-01:53:20 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 24-01:57:20 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 24-01:57:20 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 25-01:47:25 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 25-01:47:31 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 25-01:47:31 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:14 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 25-01:50:14 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 25-01:50:14 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 25-01:50:14 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 25-01:50:14 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 25-01:50:15 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 25-01:50:15 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 25-01:50:15 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 25-01:50:15 (3332) [INFO] Checking if your system is up to date:  * 25-01:50:15 (3777) [INFO] Running: /usr/bin/yum clean all * 25-01:50:15 (3778) [INFO]  * 25-01:50:15 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:50:16 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 25-01:50:16 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-01:50:16 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 25-01:50:16 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 25-01:50:16 (3788) [INFO] Cleaning up list of fastest mirrors * 25-01:50:16 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 25-01:50:16 (3798) [INFO]  * 25-01:50:16 (3777) [INFO] Running: /usr/bin/yum check-update * 25-01:50:16 (3778) [INFO]  * 25-01:50:16 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:50:17 (3788) [INFO] Determining fastest mirrors * 25-01:51:46 (3788) [INFO] * EA4: 208.74.123.61 * 25-01:51:46 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 25-01:51:46 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 25-01:51:46 (3788) [INFO] * base: la.mirrors.clouvider.net * 25-01:51:46 (3788) [INFO] * epel: mirrors.xmission.com * 25-01:51:46 (3788) [INFO] * extras: repos.forethought.net * 25-01:51:46 (3788) [INFO] * updates: mirrors.xtom.com * 25-01:54:29 (3788) [INFO]  * 25-01:54:29 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 25-01:54:29 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-01:54:30 (3798) [INFO]  * 25-01:54:30 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-01:54:30 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-01:54:30 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 25-01:54:30 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 25-01:54:30 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N1AgAp7mgk/ea_profile.json * 25-01:54:33 (1623) [INFO] Backed up EA4 profile to /tmp/N1AgAp7mgk/ea_profile.json * 25-01:54:33 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 25-01:58:34 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 25-01:58:34 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:46:44 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:46:55 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:46:55 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:54 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:49:54 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:49:57 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 26-01:49:57 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:49:57 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 26-01:49:57 (3332) [INFO] Checking if your system is up to date:  * 26-01:49:57 (3777) [INFO] Running: /usr/bin/yum clean all * 26-01:49:57 (3778) [INFO]  * 26-01:49:58 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:49:59 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:49:59 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:49:59 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:49:59 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 26-01:49:59 (3788) [INFO] Cleaning up list of fastest mirrors * 26-01:49:59 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 26-01:49:59 (3798) [INFO]  * 26-01:49:59 (3777) [INFO] Running: /usr/bin/yum check-update * 26-01:49:59 (3778) [INFO]  * 26-01:50:00 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:50:07 (3788) [INFO] Determining fastest mirrors * 26-01:51:37 (3788) [INFO] * EA4: 208.74.123.61 * 26-01:51:37 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 26-01:51:37 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 26-01:51:37 (3788) [INFO] * base: mirror.sfo12.us.leaseweb.net * 26-01:51:37 (3788) [INFO] * epel: mirrors.xmission.com * 26-01:51:37 (3788) [INFO] * extras: mirror.chpc.utah.edu * 26-01:51:37 (3788) [INFO] * updates: mirrors.raystedman.org * 26-01:54:34 (3788) [INFO]  * 26-01:54:34 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 26-01:54:34 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-01:54:34 (3798) [INFO]  * 26-01:54:34 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:54:34 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:54:34 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:54:34 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 26-01:54:34 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mFC7t2p3f4/ea_profile.json * 26-01:54:38 (1623) [INFO] Backed up EA4 profile to /tmp/mFC7t2p3f4/ea_profile.json * 26-01:54:38 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 26-01:58:39 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 26-01:58:39 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 27-01:46:27 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 27-01:46:33 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 27-01:46:33 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:14 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 27-01:49:14 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 27-01:49:14 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 27-01:49:14 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 27-01:49:14 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 27-01:49:14 (3332) [INFO] Checking if your system is up to date:  * 27-01:49:14 (3777) [INFO] Running: /usr/bin/yum clean all * 27-01:49:14 (3778) [INFO]  * 27-01:49:15 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:49:15 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 27-01:49:15 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-01:49:15 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 27-01:49:15 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 27-01:49:15 (3788) [INFO] Cleaning up list of fastest mirrors * 27-01:49:15 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 27-01:49:16 (3798) [INFO]  * 27-01:49:16 (3777) [INFO] Running: /usr/bin/yum check-update * 27-01:49:16 (3778) [INFO]  * 27-01:49:16 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:49:17 (3788) [INFO] Determining fastest mirrors * 27-01:50:46 (3788) [INFO] * EA4: 208.74.123.61 * 27-01:50:46 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 27-01:50:46 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 27-01:50:46 (3788) [INFO] * base: ridgewireless.mm.fcix.net * 27-01:50:46 (3788) [INFO] * epel: mirrors.xmission.com * 27-01:50:46 (3788) [INFO] * extras: or-mirror.iwebfusion.net * 27-01:50:46 (3788) [INFO] * updates: mirrors.sonic.net * 27-01:53:32 (3788) [INFO]  * 27-01:53:32 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 27-01:53:32 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-01:53:32 (3798) [INFO]  * 27-01:53:32 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-01:53:32 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-01:53:32 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 27-01:53:32 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 27-01:53:32 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ac4VpYBn0D/ea_profile.json * 27-01:53:36 (1623) [INFO] Backed up EA4 profile to /tmp/Ac4VpYBn0D/ea_profile.json * 27-01:53:36 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 27-01:57:37 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 27-01:57:37 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 28-01:47:18 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 28-01:47:24 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 28-01:47:24 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:22 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 28-01:50:22 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 28-01:50:22 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 28-01:50:22 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 28-01:50:22 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 28-01:50:22 (3332) [INFO] Checking if your system is up to date:  * 28-01:50:22 (3777) [INFO] Running: /usr/bin/yum clean all * 28-01:50:22 (3778) [INFO]  * 28-01:50:23 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:50:23 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 28-01:50:23 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-01:50:23 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 28-01:50:23 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 28-01:50:23 (3788) [INFO] Cleaning up list of fastest mirrors * 28-01:50:23 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 28-01:50:23 (3798) [INFO]  * 28-01:50:23 (3777) [INFO] Running: /usr/bin/yum check-update * 28-01:50:23 (3778) [INFO]  * 28-01:50:23 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-01:50:24 (3788) [INFO] Determining fastest mirrors * 28-01:51:56 (3788) [INFO] * EA4: 208.74.123.61 * 28-01:51:56 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 28-01:51:56 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 28-01:51:56 (3788) [INFO] * base: repos.lax.layerhost.com * 28-01:51:56 (3788) [INFO] * epel: mirrors.xmission.com * 28-01:51:56 (3788) [INFO] * extras: mirrors.xmission.com * 28-01:51:56 (3788) [INFO] * updates: mirror.fcix.net * 28-01:54:54 (3788) [INFO]  * 28-01:54:54 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 28-01:54:54 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-01:54:55 (3798) [INFO]  * 28-01:54:55 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-01:54:55 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-01:54:55 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 28-01:54:55 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 28-01:54:55 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LvWMqmlSmC/ea_profile.json * 28-01:54:59 (1623) [INFO] Backed up EA4 profile to /tmp/LvWMqmlSmC/ea_profile.json * 28-01:54:59 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 28-01:58:59 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 28-01:58:59 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 29-01:46:02 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 29-01:46:09 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 29-01:46:09 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:52 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 29-01:48:52 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 29-01:48:52 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 29-01:48:52 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 29-01:48:52 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 29-01:48:52 (3332) [INFO] Checking if your system is up to date:  * 29-01:48:52 (3777) [INFO] Running: /usr/bin/yum clean all * 29-01:48:52 (3778) [INFO]  * 29-01:48:53 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:48:53 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 29-01:48:53 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-01:48:53 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 29-01:48:53 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 29-01:48:53 (3788) [INFO] Cleaning up list of fastest mirrors * 29-01:48:53 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 29-01:48:53 (3798) [INFO]  * 29-01:48:53 (3777) [INFO] Running: /usr/bin/yum check-update * 29-01:48:53 (3778) [INFO]  * 29-01:48:54 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:48:55 (3788) [INFO] Determining fastest mirrors * 29-01:50:24 (3788) [INFO] * EA4: 208.74.123.61 * 29-01:50:24 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 29-01:50:24 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 29-01:50:24 (3788) [INFO] * base: mirrors.raystedman.org * 29-01:50:24 (3788) [INFO] * epel: mirrors.xmission.com * 29-01:50:24 (3788) [INFO] * extras: mirrors.xmission.com * 29-01:50:24 (3788) [INFO] * updates: mirrors.xtom.com * 29-01:53:11 (3788) [INFO]  * 29-01:53:11 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 29-01:53:11 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-01:53:11 (3798) [INFO]  * 29-01:53:11 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-01:53:11 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-01:53:11 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 29-01:53:11 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 29-01:53:11 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mwcXAylDlN/ea_profile.json * 29-01:53:15 (1623) [INFO] Backed up EA4 profile to /tmp/mwcXAylDlN/ea_profile.json * 29-01:53:15 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 29-01:57:16 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 29-01:57:16 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:49:08 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:49:20 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:49:20 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:52:19 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:52:19 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:52:20 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 30-01:52:20 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:52:20 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 30-01:52:20 (3332) [INFO] Checking if your system is up to date:  * 30-01:52:20 (3777) [INFO] Running: /usr/bin/yum clean all * 30-01:52:20 (3778) [INFO]  * 30-01:52:21 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:52:21 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:52:21 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:52:21 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:52:21 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 30-01:52:21 (3788) [INFO] Cleaning up list of fastest mirrors * 30-01:52:21 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 30-01:52:21 (3798) [INFO]  * 30-01:52:21 (3777) [INFO] Running: /usr/bin/yum check-update * 30-01:52:21 (3778) [INFO]  * 30-01:52:22 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:52:23 (3788) [INFO] Determining fastest mirrors * 30-01:53:55 (3788) [INFO] * EA4: 208.74.123.61 * 30-01:53:55 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 30-01:53:55 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 30-01:53:55 (3788) [INFO] * base: centos.mirror.shastacoe.net * 30-01:53:55 (3788) [INFO] * epel: mirrors.xmission.com * 30-01:53:55 (3788) [INFO] * extras: mirrors.sonic.net * 30-01:53:55 (3788) [INFO] * updates: mirrors.xmission.com * 30-01:56:39 (3788) [INFO]  * 30-01:56:39 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 30-01:56:39 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-01:56:39 (3798) [INFO]  * 30-01:56:39 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-01:56:39 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-01:56:39 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-01:56:39 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 30-01:56:39 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GwENhB8sXG/ea_profile.json * 30-01:56:43 (1623) [INFO] Backed up EA4 profile to /tmp/GwENhB8sXG/ea_profile.json * 30-01:56:43 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 30-02:00:44 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 30-02:00:44 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 31-01:45:43 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 31-01:45:50 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 31-01:45:50 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:16 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 31-01:49:16 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30008 milliseconds with 0 out of 0 bytes received')  * 31-01:49:16 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 31-01:49:16 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 31-01:49:16 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 31-01:49:17 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 31-01:49:17 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 31-01:49:17 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 31-01:49:17 (3332) [INFO] Checking if your system is up to date:  * 31-01:49:17 (3777) [INFO] Running: /usr/bin/yum clean all * 31-01:49:17 (3778) [INFO]  * 31-01:49:17 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:49:18 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 31-01:49:18 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-01:49:18 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 31-01:49:18 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 31-01:49:18 (3788) [INFO] Cleaning up list of fastest mirrors * 31-01:49:18 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 31-01:49:18 (3798) [INFO]  * 31-01:49:18 (3777) [INFO] Running: /usr/bin/yum check-update * 31-01:49:18 (3778) [INFO]  * 31-01:49:18 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:49:19 (3788) [INFO] Determining fastest mirrors * 31-01:50:49 (3788) [INFO] * EA4: 208.74.123.62 * 31-01:50:49 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 31-01:50:49 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 31-01:50:49 (3788) [INFO] * base: mirrors.oit.uci.edu * 31-01:50:49 (3788) [INFO] * epel: mirrors.xmission.com * 31-01:50:49 (3788) [INFO] * extras: mirror.dal.nexril.net * 31-01:50:49 (3788) [INFO] * updates: mirror.fcix.net * 31-01:53:36 (3788) [INFO]  * 31-01:53:36 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 31-01:53:36 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-01:53:37 (3798) [INFO]  * 31-01:53:37 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-01:53:37 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-01:53:37 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 31-01:53:37 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 31-01:53:37 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j5JzSQuOyu/ea_profile.json * 31-01:53:40 (1623) [INFO] Backed up EA4 profile to /tmp/j5JzSQuOyu/ea_profile.json * 31-01:53:40 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 31-01:57:41 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 31-01:57:41 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 01-01:48:35 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 01-01:48:40 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 01-01:48:40 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:34 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 01-01:51:34 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 01-01:51:35 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 01-01:51:35 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 01-01:51:35 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 01-01:51:35 (3332) [INFO] Checking if your system is up to date:  * 01-01:51:35 (3777) [INFO] Running: /usr/bin/yum clean all * 01-01:51:35 (3778) [INFO]  * 01-01:51:35 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:51:35 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 01-01:51:35 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-01:51:35 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 01-01:51:35 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 01-01:51:35 (3788) [INFO] Cleaning up list of fastest mirrors * 01-01:51:35 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 01-01:51:35 (3798) [INFO]  * 01-01:51:35 (3777) [INFO] Running: /usr/bin/yum check-update * 01-01:51:35 (3778) [INFO]  * 01-01:51:36 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:51:36 (3788) [INFO] Determining fastest mirrors * 01-01:53:06 (3788) [INFO] * EA4: 208.74.123.62 * 01-01:53:06 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 01-01:53:06 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 01-01:53:06 (3788) [INFO] * base: mirrors.xmission.com * 01-01:53:06 (3788) [INFO] * epel: mirrors.xmission.com * 01-01:53:06 (3788) [INFO] * extras: mirror.chpc.utah.edu * 01-01:53:06 (3788) [INFO] * updates: mirrors.unifiedlayer.com * 01-01:56:07 (3788) [INFO]  * 01-01:56:07 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 01-01:56:07 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-01:56:07 (3798) [INFO]  * 01-01:56:07 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-01:56:07 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-01:56:07 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 01-01:56:07 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 01-01:56:07 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gpUYuD0Bpb/ea_profile.json * 01-01:56:10 (1623) [INFO] Backed up EA4 profile to /tmp/gpUYuD0Bpb/ea_profile.json * 01-01:56:10 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 01-02:00:11 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 01-02:00:11 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 02-01:41:59 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 02-01:42:06 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 02-01:42:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:54 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 02-01:45:54 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')  * 02-01:45:54 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 02-01:45:54 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 02-01:45:54 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 02-01:45:55 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 02-01:45:55 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 02-01:45:55 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 02-01:45:55 (3332) [INFO] Checking if your system is up to date:  * 02-01:45:55 (3777) [INFO] Running: /usr/bin/yum clean all * 02-01:45:55 (3778) [INFO]  * 02-01:45:55 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:45:56 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 02-01:45:56 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-01:45:56 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 02-01:45:56 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 02-01:45:56 (3788) [INFO] Cleaning up list of fastest mirrors * 02-01:45:56 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 02-01:45:56 (3798) [INFO]  * 02-01:45:56 (3777) [INFO] Running: /usr/bin/yum check-update * 02-01:45:56 (3778) [INFO]  * 02-01:45:56 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-01:45:57 (3788) [INFO] Determining fastest mirrors * 02-01:47:27 (3788) [INFO] * EA4: 208.74.123.62 * 02-01:47:27 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 02-01:47:27 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 02-01:47:27 (3788) [INFO] * base: ziply.mm.fcix.net * 02-01:47:27 (3788) [INFO] * epel: mirrors.xmission.com * 02-01:47:27 (3788) [INFO] * extras: repos.lax.layerhost.com * 02-01:47:27 (3788) [INFO] * updates: or-mirror.iwebfusion.net * 02-01:50:23 (3788) [INFO]  * 02-01:50:23 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 02-01:50:23 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-01:50:23 (3798) [INFO]  * 02-01:50:23 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-01:50:23 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-01:50:23 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 02-01:50:23 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 02-01:50:23 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sQysCtqFXW/ea_profile.json * 02-01:50:25 (1623) [INFO] Backed up EA4 profile to /tmp/sQysCtqFXW/ea_profile.json * 02-01:50:25 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 02-01:54:26 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 02-01:54:26 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 03-01:42:51 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 03-01:42:57 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 03-01:42:57 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:32 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 03-01:46:32 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 03-01:46:33 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 03-01:46:33 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 03-01:46:33 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 03-01:46:33 (3332) [INFO] Checking if your system is up to date:  * 03-01:46:33 (3777) [INFO] Running: /usr/bin/yum clean all * 03-01:46:33 (3778) [INFO]  * 03-01:46:33 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:46:34 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 03-01:46:34 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-01:46:34 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 03-01:46:34 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 03-01:46:34 (3788) [INFO] Cleaning up list of fastest mirrors * 03-01:46:34 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 03-01:46:34 (3798) [INFO]  * 03-01:46:34 (3777) [INFO] Running: /usr/bin/yum check-update * 03-01:46:34 (3778) [INFO]  * 03-01:46:35 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:46:36 (3788) [INFO] Determining fastest mirrors * 03-01:48:04 (3788) [INFO] * EA4: 184.94.196.97 * 03-01:48:04 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 03-01:48:04 (3788) [INFO] * cpanel-plugins: 184.94.196.97 * 03-01:48:04 (3788) [INFO] * base: mirror.chpc.utah.edu * 03-01:48:04 (3788) [INFO] * epel: mirrors.xmission.com * 03-01:48:04 (3788) [INFO] * extras: repos.lax.layerhost.com * 03-01:48:04 (3788) [INFO] * updates: mirror.sfo12.us.leaseweb.net * 03-01:50:54 (3788) [INFO]  * 03-01:50:54 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 03-01:50:54 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-01:50:54 (3798) [INFO]  * 03-01:50:54 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-01:50:54 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-01:50:54 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 03-01:50:54 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 03-01:50:54 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nm3kad07Ou/ea_profile.json * 03-01:50:56 (1623) [INFO] Backed up EA4 profile to /tmp/nm3kad07Ou/ea_profile.json * 03-01:50:56 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 03-01:54:57 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 03-01:54:57 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 04-01:44:26 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 04-01:44:29 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 04-01:44:29 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:43 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 04-01:46:43 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 04-01:46:44 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 04-01:46:44 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 04-01:46:44 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 04-01:46:44 (3332) [INFO] Checking if your system is up to date:  * 04-01:46:44 (3777) [INFO] Running: /usr/bin/yum clean all * 04-01:46:44 (3778) [INFO]  * 04-01:46:44 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:46:45 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 04-01:46:45 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-01:46:45 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 04-01:46:45 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 04-01:46:45 (3788) [INFO] Cleaning up list of fastest mirrors * 04-01:46:45 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 04-01:46:45 (3798) [INFO]  * 04-01:46:45 (3777) [INFO] Running: /usr/bin/yum check-update * 04-01:46:45 (3778) [INFO]  * 04-01:46:46 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:46:47 (3788) [INFO] Determining fastest mirrors * 04-01:48:17 (3788) [INFO] * EA4: 184.94.196.94 * 04-01:48:17 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 04-01:48:17 (3788) [INFO] * cpanel-plugins: 184.94.196.94 * 04-01:48:17 (3788) [INFO] * base: mirrors.ocf.berkeley.edu * 04-01:48:17 (3788) [INFO] * epel: mirrors.xmission.com * 04-01:48:17 (3788) [INFO] * extras: ziply.mm.fcix.net * 04-01:48:17 (3788) [INFO] * updates: mirrors.xmission.com * 04-01:51:03 (3788) [INFO]  * 04-01:51:03 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 04-01:51:03 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-01:51:04 (3798) [INFO]  * 04-01:51:04 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-01:51:04 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-01:51:04 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 04-01:51:04 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 04-01:51:04 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fCVqXZ9ew_/ea_profile.json * 04-01:51:06 (1623) [INFO] Backed up EA4 profile to /tmp/fCVqXZ9ew_/ea_profile.json * 04-01:51:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 04-01:55:06 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 04-01:55:07 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 05-01:47:51 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 05-01:47:54 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 05-01:47:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:10 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 05-01:51:10 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 05-01:51:11 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 05-01:51:11 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 05-01:51:11 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 05-01:51:11 (3332) [INFO] Checking if your system is up to date:  * 05-01:51:11 (3777) [INFO] Running: /usr/bin/yum clean all * 05-01:51:11 (3778) [INFO]  * 05-01:51:12 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:51:12 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 05-01:51:12 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-01:51:12 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 05-01:51:12 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 05-01:51:13 (3788) [INFO] Cleaning up list of fastest mirrors * 05-01:51:13 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 05-01:51:13 (3798) [INFO]  * 05-01:51:13 (3777) [INFO] Running: /usr/bin/yum check-update * 05-01:51:13 (3778) [INFO]  * 05-01:51:13 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-01:51:13 (3788) [INFO] Determining fastest mirrors * 05-01:53:15 (3788) [INFO] * EA4: 208.74.123.61 * 05-01:53:15 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 05-01:53:15 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 05-01:53:15 (3788) [INFO] * base: mirrors.ocf.berkeley.edu * 05-01:53:15 (3788) [INFO] * epel: mirrors.xmission.com * 05-01:53:15 (3788) [INFO] * extras: la.mirrors.clouvider.net * 05-01:53:15 (3788) [INFO] * updates: la.mirrors.clouvider.net * 05-01:56:03 (3788) [INFO]  * 05-01:56:03 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 05-01:56:03 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-01:56:03 (3798) [INFO]  * 05-01:56:03 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-01:56:03 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-01:56:03 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 05-01:56:03 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 05-01:56:03 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U5qI_wlNxV/ea_profile.json * 05-01:56:06 (1623) [INFO] Backed up EA4 profile to /tmp/U5qI_wlNxV/ea_profile.json * 05-01:56:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 05-02:00:07 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 05-02:00:07 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 06-01:44:28 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 06-01:44:33 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 06-01:44:33 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:19 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 06-01:47:19 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 06-01:47:20 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 06-01:47:20 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 06-01:47:20 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 06-01:47:20 (3332) [INFO] Checking if your system is up to date:  * 06-01:47:20 (3777) [INFO] Running: /usr/bin/yum clean all * 06-01:47:20 (3778) [INFO]  * 06-01:47:20 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:47:21 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 06-01:47:21 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-01:47:21 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 06-01:47:21 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 06-01:47:21 (3788) [INFO] Cleaning up list of fastest mirrors * 06-01:47:21 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 06-01:47:21 (3798) [INFO]  * 06-01:47:21 (3777) [INFO] Running: /usr/bin/yum check-update * 06-01:47:21 (3778) [INFO]  * 06-01:47:22 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-01:47:22 (3788) [INFO] Determining fastest mirrors * 06-01:48:52 (3788) [INFO] * EA4: 208.74.123.62 * 06-01:48:52 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 06-01:48:52 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 06-01:48:52 (3788) [INFO] * base: mirror.fcix.net * 06-01:48:52 (3788) [INFO] * epel: mirrors.xmission.com * 06-01:48:52 (3788) [INFO] * extras: abqix.mm.fcix.net * 06-01:48:52 (3788) [INFO] * updates: ziply.mm.fcix.net * 06-01:51:39 (3788) [INFO]  * 06-01:51:39 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 06-01:51:39 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-01:51:39 (3798) [INFO]  * 06-01:51:39 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-01:51:39 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-01:51:39 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 06-01:51:39 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 06-01:51:39 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/86889vvdOG/ea_profile.json * 06-01:51:43 (1623) [INFO] Backed up EA4 profile to /tmp/86889vvdOG/ea_profile.json * 06-01:51:43 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 06-01:55:43 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 06-01:55:43 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 07-01:45:47 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 07-01:45:53 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 07-01:45:53 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:48:37 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 07-01:48:37 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 07-01:48:38 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 07-01:48:38 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 07-01:48:38 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 07-01:48:38 (3332) [INFO] Checking if your system is up to date:  * 07-01:48:38 (3777) [INFO] Running: /usr/bin/yum clean all * 07-01:48:38 (3778) [INFO]  * 07-01:48:38 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:48:38 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 07-01:48:38 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-01:48:38 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 07-01:48:38 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 07-01:48:38 (3788) [INFO] Cleaning up list of fastest mirrors * 07-01:48:38 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 07-01:48:38 (3798) [INFO]  * 07-01:48:38 (3777) [INFO] Running: /usr/bin/yum check-update * 07-01:48:38 (3778) [INFO]  * 07-01:48:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-01:48:40 (3788) [INFO] Determining fastest mirrors * 07-01:50:12 (3788) [INFO] * EA4: 208.74.123.62 * 07-01:50:12 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 07-01:50:12 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 07-01:50:12 (3788) [INFO] * base: mirror.chpc.utah.edu * 07-01:50:12 (3788) [INFO] * epel: mirrors.xmission.com * 07-01:50:12 (3788) [INFO] * extras: mirrors.xmission.com * 07-01:50:12 (3788) [INFO] * updates: ziply.mm.fcix.net * 07-01:52:59 (3788) [INFO]  * 07-01:52:59 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 07-01:52:59 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-01:53:00 (3798) [INFO]  * 07-01:53:00 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-01:53:00 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-01:53:00 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 07-01:53:00 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 07-01:53:00 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PimbhGHuI7/ea_profile.json * 07-01:53:04 (1623) [INFO] Backed up EA4 profile to /tmp/PimbhGHuI7/ea_profile.json * 07-01:53:04 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 07-01:57:05 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 07-01:57:05 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 08-01:47:10 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 08-01:47:14 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 08-01:47:14 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:12 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 08-01:50:12 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 08-01:50:12 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 08-01:50:12 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 08-01:50:12 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 08-01:50:13 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 08-01:50:13 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 08-01:50:13 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 08-01:50:13 (3332) [INFO] Checking if your system is up to date:  * 08-01:50:13 (3777) [INFO] Running: /usr/bin/yum clean all * 08-01:50:13 (3778) [INFO]  * 08-01:50:13 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:50:13 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 08-01:50:13 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-01:50:13 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 08-01:50:13 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 08-01:50:14 (3788) [INFO] Cleaning up list of fastest mirrors * 08-01:50:14 (3788) [INFO] Other repos take up 636 k of disk space (use --verbose for details) * 08-01:50:14 (3798) [INFO]  * 08-01:50:14 (3777) [INFO] Running: /usr/bin/yum check-update * 08-01:50:14 (3778) [INFO]  * 08-01:50:14 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-01:50:15 (3788) [INFO] Determining fastest mirrors * 08-01:51:45 (3788) [INFO] * EA4: 208.74.123.62 * 08-01:51:45 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 08-01:51:45 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 08-01:51:45 (3788) [INFO] * base: mirror.web-ster.com * 08-01:51:45 (3788) [INFO] * epel: mirrors.xmission.com * 08-01:51:45 (3788) [INFO] * extras: mirrors.raystedman.org * 08-01:51:45 (3788) [INFO] * updates: repos.forethought.net * 08-01:54:33 (3788) [INFO]  * 08-01:54:33 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 08-01:54:33 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-01:54:33 (3798) [INFO]  * 08-01:54:33 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-01:54:33 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-01:54:33 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 08-01:54:33 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 08-01:54:33 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PDltA2svJN/ea_profile.json * 08-01:54:36 (1623) [INFO] Backed up EA4 profile to /tmp/PDltA2svJN/ea_profile.json * 08-01:54:36 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 08-01:58:37 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 08-01:58:37 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 09-01:46:30 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 09-01:46:36 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 09-01:46:36 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:34 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 09-01:49:34 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 09-01:49:35 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 09-01:49:35 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 09-01:49:35 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 09-01:49:35 (3332) [INFO] Checking if your system is up to date:  * 09-01:49:35 (3777) [INFO] Running: /usr/bin/yum clean all * 09-01:49:35 (3778) [INFO]  * 09-01:49:36 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:49:36 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 09-01:49:36 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-01:49:36 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 09-01:49:36 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 09-01:49:36 (3788) [INFO] Cleaning up list of fastest mirrors * 09-01:49:36 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 09-01:49:36 (3798) [INFO]  * 09-01:49:36 (3777) [INFO] Running: /usr/bin/yum check-update * 09-01:49:36 (3778) [INFO]  * 09-01:49:37 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-01:49:37 (3788) [INFO] Determining fastest mirrors * 09-01:51:13 (3788) [INFO] * EA4: 208.74.123.62 * 09-01:51:13 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 09-01:51:13 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 09-01:51:13 (3788) [INFO] * base: mirrors.xmission.com * 09-01:51:13 (3788) [INFO] * epel: mirrors.sonic.net * 09-01:51:13 (3788) [INFO] * extras: opencolo.mm.fcix.net * 09-01:51:13 (3788) [INFO] * updates: mirrors.xtom.com * 09-01:54:13 (3788) [INFO]  * 09-01:54:13 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 09-01:54:13 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-01:54:14 (3798) [INFO]  * 09-01:54:14 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-01:54:14 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-01:54:14 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 09-01:54:14 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 09-01:54:14 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_EbHdUit_p/ea_profile.json * 09-01:54:17 (1623) [INFO] Backed up EA4 profile to /tmp/_EbHdUit_p/ea_profile.json * 09-01:54:17 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 09-01:58:18 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 09-01:58:18 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 10-01:43:18 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 10-01:43:23 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 10-01:43:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:56 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 10-01:46:56 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 10-01:46:58 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 10-01:46:58 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 10-01:46:58 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 10-01:46:58 (3332) [INFO] Checking if your system is up to date:  * 10-01:46:58 (3777) [INFO] Running: /usr/bin/yum clean all * 10-01:46:58 (3778) [INFO]  * 10-01:46:58 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:46:59 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 10-01:46:59 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-01:46:59 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 10-01:46:59 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 10-01:46:59 (3788) [INFO] Cleaning up list of fastest mirrors * 10-01:46:59 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 10-01:46:59 (3798) [INFO]  * 10-01:46:59 (3777) [INFO] Running: /usr/bin/yum check-update * 10-01:46:59 (3778) [INFO]  * 10-01:47:00 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-01:47:00 (3788) [INFO] Determining fastest mirrors * 10-01:48:29 (3788) [INFO] * EA4: 208.74.123.61 * 10-01:48:29 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 10-01:48:29 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 10-01:48:29 (3788) [INFO] * base: ridgewireless.mm.fcix.net * 10-01:48:29 (3788) [INFO] * epel: mirrors.xmission.com * 10-01:48:29 (3788) [INFO] * extras: centos-distro.cavecreek.net * 10-01:48:29 (3788) [INFO] * updates: abqix.mm.fcix.net * 10-01:51:17 (3788) [INFO]  * 10-01:51:17 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 10-01:51:17 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-01:51:17 (3798) [INFO]  * 10-01:51:17 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-01:51:17 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-01:51:17 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 10-01:51:17 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 10-01:51:17 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xl14bcBRV6/ea_profile.json * 10-01:51:21 (1623) [INFO] Backed up EA4 profile to /tmp/xl14bcBRV6/ea_profile.json * 10-01:51:21 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 10-01:55:21 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 10-01:55:21 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 11-01:44:32 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 11-01:44:38 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 11-01:44:38 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:22 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 11-01:47:22 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30020 milliseconds with 0 out of 0 bytes received')  * 11-01:47:22 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 11-01:47:22 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 11-01:47:22 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 11-01:47:23 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 11-01:47:23 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 11-01:47:23 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 11-01:47:23 (3332) [INFO] Checking if your system is up to date:  * 11-01:47:23 (3777) [INFO] Running: /usr/bin/yum clean all * 11-01:47:23 (3778) [INFO]  * 11-01:47:23 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:47:23 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 11-01:47:23 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-01:47:23 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 11-01:47:23 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 11-01:47:24 (3788) [INFO] Cleaning up list of fastest mirrors * 11-01:47:24 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 11-01:47:24 (3798) [INFO]  * 11-01:47:24 (3777) [INFO] Running: /usr/bin/yum check-update * 11-01:47:24 (3778) [INFO]  * 11-01:47:24 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-01:47:25 (3788) [INFO] Determining fastest mirrors * 11-01:48:56 (3788) [INFO] * EA4: 184.94.196.93 * 11-01:48:56 (3788) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 11-01:48:56 (3788) [INFO] * cpanel-plugins: 184.94.196.93 * 11-01:48:56 (3788) [INFO] * base: repos.lax.layerhost.com * 11-01:48:56 (3788) [INFO] * epel: mirrors.xmission.com * 11-01:48:56 (3788) [INFO] * extras: repos.forethought.net * 11-01:48:56 (3788) [INFO] * updates: mirrors.xmission.com * 11-01:51:54 (3788) [INFO]  * 11-01:51:54 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 11-01:51:54 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-01:51:55 (3798) [INFO]  * 11-01:51:55 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-01:51:55 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-01:51:55 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 11-01:51:55 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 11-01:51:55 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rBpcZACAbO/ea_profile.json * 11-01:51:58 (1623) [INFO] Backed up EA4 profile to /tmp/rBpcZACAbO/ea_profile.json * 11-01:51:58 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 11-01:55:59 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 11-01:55:59 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 12-01:52:14 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 12-01:52:16 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 12-01:52:16 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:55:15 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 12-01:55:15 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30053 milliseconds with 0 out of 0 bytes received')  * 12-01:55:15 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 12-01:55:15 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 12-01:55:15 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 12-01:55:16 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 12-01:55:16 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 12-01:55:16 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 12-01:55:16 (3332) [INFO] Checking if your system is up to date:  * 12-01:55:16 (3777) [INFO] Running: /usr/bin/yum clean all * 12-01:55:16 (3778) [INFO]  * 12-01:55:16 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:55:17 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 12-01:55:17 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-01:55:17 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 12-01:55:17 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 12-01:55:17 (3788) [INFO] Cleaning up list of fastest mirrors * 12-01:55:17 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 12-01:55:17 (3798) [INFO]  * 12-01:55:17 (3777) [INFO] Running: /usr/bin/yum check-update * 12-01:55:17 (3778) [INFO]  * 12-01:55:17 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-01:55:18 (3788) [INFO] Determining fastest mirrors * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] One of the configured repositories failed (Unknown), * 12-01:56:17 (3788) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 12-01:56:17 (3788) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 12-01:56:17 (3788) [INFO] upstream. This is most often useful if you are using a newer * 12-01:56:17 (3788) [INFO] distribution release than is supported by the repository (and the * 12-01:56:17 (3788) [INFO] packages for the previous distribution release still work). * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] 3. Run the command with the repository temporarily disabled * 12-01:56:17 (3788) [INFO] yum --disablerepo= ... * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 12-01:56:17 (3788) [INFO] will then just ignore the repository until you permanently enable it * 12-01:56:17 (3788) [INFO] again or use --enablerepo for temporary usage: * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] yum-config-manager --disable  * 12-01:56:17 (3788) [INFO] or * 12-01:56:17 (3788) [INFO] subscription-manager repos --disable= * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 12-01:56:17 (3788) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 12-01:56:17 (3788) [INFO] so will have to try and fail each time (and thus. yum will be be much * 12-01:56:17 (3788) [INFO] slower). If it is a very temporary problem though, this is often a nice * 12-01:56:17 (3788) [INFO] compromise: * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 12-01:56:17 (3788) [INFO]  * 12-01:56:17 (3788) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 12-01:56:17 (3798) [INFO]  * 12-01:56:17 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-01:56:17 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-01:56:17 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 12-01:56:17 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 12-01:56:17 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pHyZRTKMkI/ea_profile.json * 12-02:01:06 (1623) [INFO] Backed up EA4 profile to /tmp/pHyZRTKMkI/ea_profile.json * 12-02:01:06 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 12-02:05:07 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 12-02:05:07 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 13-01:43:48 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 13-01:43:55 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 13-01:43:55 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:46:10 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 13-01:46:10 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 13-01:46:10 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 13-01:46:10 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 13-01:46:10 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 13-01:46:10 (3332) [INFO] Checking if your system is up to date:  * 13-01:46:10 (3777) [INFO] Running: /usr/bin/yum clean all * 13-01:46:10 (3778) [INFO]  * 13-01:46:11 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:11 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 13-01:46:11 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-01:46:11 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 13-01:46:11 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 13-01:46:11 (3788) [INFO] Cleaning up list of fastest mirrors * 13-01:46:11 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 13-01:46:11 (3798) [INFO]  * 13-01:46:11 (3777) [INFO] Running: /usr/bin/yum check-update * 13-01:46:11 (3778) [INFO]  * 13-01:46:12 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-01:46:12 (3788) [INFO] Determining fastest mirrors * 13-01:47:42 (3788) [INFO] * EA4: 208.74.123.61 * 13-01:47:42 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 13-01:47:42 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 13-01:47:42 (3788) [INFO] * base: or-mirror.iwebfusion.net * 13-01:47:42 (3788) [INFO] * epel: mirrors.xmission.com * 13-01:47:42 (3788) [INFO] * extras: mirror.chpc.utah.edu * 13-01:47:42 (3788) [INFO] * updates: centos-distro.1gservers.com * 13-01:50:16 (3788) [INFO]  * 13-01:50:16 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 13-01:50:16 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-01:50:16 (3798) [INFO]  * 13-01:50:16 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-01:50:16 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-01:50:16 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 13-01:50:16 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 13-01:50:16 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qgbJvHgfKi/ea_profile.json * 13-01:50:18 (1623) [INFO] Backed up EA4 profile to /tmp/qgbJvHgfKi/ea_profile.json * 13-01:50:18 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 13-01:50:19 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 13-01:50:19 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 14-01:47:42 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 14-01:47:54 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 14-01:47:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:42 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 14-01:50:42 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 14-01:50:43 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 14-01:50:43 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 14-01:50:43 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 14-01:50:43 (3332) [INFO] Checking if your system is up to date:  * 14-01:50:43 (3777) [INFO] Running: /usr/bin/yum clean all * 14-01:50:43 (3778) [INFO]  * 14-01:50:43 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:50:43 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 14-01:50:43 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-01:50:43 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 14-01:50:43 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 14-01:50:44 (3788) [INFO] Cleaning up list of fastest mirrors * 14-01:50:44 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 14-01:50:44 (3798) [INFO]  * 14-01:50:44 (3777) [INFO] Running: /usr/bin/yum check-update * 14-01:50:44 (3778) [INFO]  * 14-01:50:44 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-01:50:45 (3788) [INFO] Determining fastest mirrors * 14-01:52:18 (3788) [INFO] * EA4: 208.74.123.61 * 14-01:52:18 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 14-01:52:18 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 14-01:52:18 (3788) [INFO] * base: mirrors.vcea.wsu.edu * 14-01:52:18 (3788) [INFO] * epel: mirrors.xmission.com * 14-01:52:18 (3788) [INFO] * extras: mirrors.xmission.com * 14-01:52:18 (3788) [INFO] * updates: mirrors.vcea.wsu.edu * 14-01:55:20 (3788) [INFO]  * 14-01:55:20 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 14-01:55:20 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-01:55:20 (3798) [INFO]  * 14-01:55:20 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-01:55:20 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-01:55:20 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 14-01:55:20 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 14-01:55:20 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DplPCAWwZE/ea_profile.json * 14-01:55:23 (1623) [INFO] Backed up EA4 profile to /tmp/DplPCAWwZE/ea_profile.json * 14-01:55:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 14-01:59:23 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 14-01:59:23 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 15-01:50:01 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 15-01:50:21 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 15-01:50:21 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:53:26 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 15-01:53:26 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30003 milliseconds with 0 out of 0 bytes received')  * 15-01:53:26 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 15-01:53:26 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 15-01:53:26 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 15-01:53:27 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 15-01:53:27 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 15-01:53:27 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 15-01:53:27 (3332) [INFO] Checking if your system is up to date:  * 15-01:53:27 (3777) [INFO] Running: /usr/bin/yum clean all * 15-01:53:27 (3778) [INFO]  * 15-01:53:27 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:53:27 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 15-01:53:27 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-01:53:27 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 15-01:53:27 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 15-01:53:27 (3788) [INFO] Cleaning up list of fastest mirrors * 15-01:53:27 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 15-01:53:27 (3798) [INFO]  * 15-01:53:27 (3777) [INFO] Running: /usr/bin/yum check-update * 15-01:53:27 (3778) [INFO]  * 15-01:53:28 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-01:53:29 (3788) [INFO] Determining fastest mirrors * 15-01:54:58 (3788) [INFO] * EA4: 208.74.123.61 * 15-01:54:58 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 15-01:54:58 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 15-01:54:58 (3788) [INFO] * base: mirrors.raystedman.org * 15-01:54:58 (3788) [INFO] * epel: mirrors.xmission.com * 15-01:54:58 (3788) [INFO] * extras: mirror.chpc.utah.edu * 15-01:54:58 (3788) [INFO] * updates: la.mirrors.clouvider.net * 15-01:57:57 (3788) [INFO]  * 15-01:57:57 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 15-01:57:57 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-01:57:58 (3798) [INFO]  * 15-01:57:58 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-01:57:58 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-01:57:58 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 15-01:57:58 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 15-01:57:58 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TvQrsqIjmA/ea_profile.json * 15-01:58:00 (1623) [INFO] Backed up EA4 profile to /tmp/TvQrsqIjmA/ea_profile.json * 15-01:58:00 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 15-02:02:01 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 15-02:02:01 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 16-01:50:08 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 16-01:50:30 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 16-01:50:30 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:53:25 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 16-01:53:25 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake')  * 16-01:53:25 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 16-01:53:25 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 16-01:53:25 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 16-01:53:29 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 16-01:53:29 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 16-01:53:29 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 16-01:53:29 (3332) [INFO] Checking if your system is up to date:  * 16-01:53:29 (3777) [INFO] Running: /usr/bin/yum clean all * 16-01:53:29 (3778) [INFO]  * 16-01:53:30 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:53:30 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 16-01:53:30 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-01:53:30 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 16-01:53:30 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 16-01:53:31 (3788) [INFO] Cleaning up list of fastest mirrors * 16-01:53:31 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 16-01:53:31 (3798) [INFO]  * 16-01:53:31 (3777) [INFO] Running: /usr/bin/yum check-update * 16-01:53:31 (3778) [INFO]  * 16-01:53:31 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-01:53:33 (3788) [INFO] Determining fastest mirrors * 16-01:55:02 (3788) [INFO] * EA4: 208.74.123.61 * 16-01:55:02 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 16-01:55:02 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 16-01:55:02 (3788) [INFO] * base: mirror.web-ster.com * 16-01:55:02 (3788) [INFO] * epel: mirrors.xmission.com * 16-01:55:03 (3788) [INFO] * extras: mirror.web-ster.com * 16-01:55:03 (3788) [INFO] * updates: mirrors.ocf.berkeley.edu * 16-01:57:53 (3788) [INFO]  * 16-01:57:53 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 16-01:57:53 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-01:57:53 (3798) [INFO]  * 16-01:57:53 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-01:57:53 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-01:57:53 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 16-01:57:53 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 16-01:57:53 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4bwqLmPEqg/ea_profile.json * 16-01:58:04 (1623) [INFO] Backed up EA4 profile to /tmp/4bwqLmPEqg/ea_profile.json * 16-01:58:04 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 16-02:02:05 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 16-02:02:05 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 17-00:44:32 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 17-00:44:40 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 17-00:44:40 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-00:47:36 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 17-00:47:36 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 17-00:47:37 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 17-00:47:37 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 17-00:47:37 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 17-00:47:37 (3332) [INFO] Checking if your system is up to date:  * 17-00:47:37 (3777) [INFO] Running: /usr/bin/yum clean all * 17-00:47:37 (3778) [INFO]  * 17-00:47:37 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-00:47:38 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 17-00:47:38 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-00:47:38 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 17-00:47:38 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 17-00:47:38 (3788) [INFO] Cleaning up list of fastest mirrors * 17-00:47:38 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 17-00:47:38 (3798) [INFO]  * 17-00:47:38 (3777) [INFO] Running: /usr/bin/yum check-update * 17-00:47:38 (3778) [INFO]  * 17-00:47:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-00:47:40 (3788) [INFO] Determining fastest mirrors * 17-00:49:10 (3788) [INFO] * EA4: 208.74.123.61 * 17-00:49:10 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 17-00:49:10 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 17-00:49:10 (3788) [INFO] * base: opencolo.mm.fcix.net * 17-00:49:10 (3788) [INFO] * epel: mirrors.xmission.com * 17-00:49:10 (3788) [INFO] * extras: repos.forethought.net * 17-00:49:10 (3788) [INFO] * updates: mirrors.xmission.com * 17-00:52:07 (3788) [INFO]  * 17-00:52:07 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 17-00:52:07 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-00:52:08 (3798) [INFO]  * 17-00:52:08 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-00:52:08 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-00:52:08 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 17-00:52:08 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 17-00:52:08 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DwNDbSU4HR/ea_profile.json * 17-00:52:09 (1623) [INFO] Backed up EA4 profile to /tmp/DwNDbSU4HR/ea_profile.json * 17-00:52:10 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 17-00:56:10 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 17-00:56:10 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 18-01:44:48 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 18-01:44:57 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 18-01:44:57 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:43 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 18-01:47:43 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 18-01:47:45 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 18-01:47:45 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 18-01:47:45 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 18-01:47:45 (3332) [INFO] Checking if your system is up to date:  * 18-01:47:45 (3777) [INFO] Running: /usr/bin/yum clean all * 18-01:47:45 (3778) [INFO]  * 18-01:47:45 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:47:46 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 18-01:47:46 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-01:47:46 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 18-01:47:46 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 18-01:47:46 (3788) [INFO] Cleaning up list of fastest mirrors * 18-01:47:46 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 18-01:47:46 (3798) [INFO]  * 18-01:47:46 (3777) [INFO] Running: /usr/bin/yum check-update * 18-01:47:46 (3778) [INFO]  * 18-01:47:46 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-01:47:47 (3788) [INFO] Determining fastest mirrors * 18-01:49:17 (3788) [INFO] * EA4: 208.100.0.204 * 18-01:49:17 (3788) [INFO] * cpanel-addons-production-feed: 208.100.0.204 * 18-01:49:17 (3788) [INFO] * cpanel-plugins: 208.100.0.204 * 18-01:49:17 (3788) [INFO] * base: mirrors.ocf.berkeley.edu * 18-01:49:17 (3788) [INFO] * epel: mirrors.xmission.com * 18-01:49:17 (3788) [INFO] * extras: mirrors.xmission.com * 18-01:49:17 (3788) [INFO] * updates: mirrors.oit.uci.edu * 18-01:52:01 (3788) [INFO]  * 18-01:52:01 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 18-01:52:01 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-01:52:01 (3798) [INFO]  * 18-01:52:01 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-01:52:01 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-01:52:01 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 18-01:52:01 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 18-01:52:01 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SE8g8S_0Jw/ea_profile.json * 18-01:52:04 (1623) [INFO] Backed up EA4 profile to /tmp/SE8g8S_0Jw/ea_profile.json * 18-01:52:04 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 18-01:56:05 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 18-01:56:05 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 19-01:48:51 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 19-01:48:54 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 19-01:48:54 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:53 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 19-01:51:53 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 19-01:51:54 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 19-01:51:54 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 19-01:51:54 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 19-01:51:54 (3332) [INFO] Checking if your system is up to date:  * 19-01:51:54 (3777) [INFO] Running: /usr/bin/yum clean all * 19-01:51:54 (3778) [INFO]  * 19-01:51:55 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:51:55 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 19-01:51:55 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-01:51:55 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 19-01:51:55 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 19-01:51:55 (3788) [INFO] Cleaning up list of fastest mirrors * 19-01:51:55 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 19-01:51:55 (3798) [INFO]  * 19-01:51:55 (3777) [INFO] Running: /usr/bin/yum check-update * 19-01:51:55 (3778) [INFO]  * 19-01:51:56 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-01:51:57 (3788) [INFO] Determining fastest mirrors * 19-01:53:26 (3788) [INFO] * EA4: 185.125.185.32 * 19-01:53:26 (3788) [INFO] * cpanel-addons-production-feed: 185.125.185.32 * 19-01:53:26 (3788) [INFO] * cpanel-plugins: 185.125.185.32 * 19-01:53:26 (3788) [INFO] * base: mirror.dal.nexril.net * 19-01:53:26 (3788) [INFO] * epel: mirrors.xmission.com * 19-01:53:26 (3788) [INFO] * extras: abqix.mm.fcix.net * 19-01:53:26 (3788) [INFO] * updates: repos.forethought.net * 19-01:56:10 (3788) [INFO]  * 19-01:56:10 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 19-01:56:10 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-01:56:11 (3798) [INFO]  * 19-01:56:11 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-01:56:11 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-01:56:11 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 19-01:56:11 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 19-01:56:11 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sZN96Vti5j/ea_profile.json * 19-01:56:13 (1623) [INFO] Backed up EA4 profile to /tmp/sZN96Vti5j/ea_profile.json * 19-01:56:13 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 19-02:00:13 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 19-02:00:13 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 20-01:41:52 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 20-01:41:55 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 20-01:41:55 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:45:46 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 20-01:45:46 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30003 milliseconds with 0 out of 0 bytes received')  * 20-01:45:46 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 20-01:45:46 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 20-01:45:46 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 20-01:45:50 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 20-01:45:50 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 20-01:45:50 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 20-01:45:50 (3332) [INFO] Checking if your system is up to date:  * 20-01:45:50 (3777) [INFO] Running: /usr/bin/yum clean all * 20-01:45:50 (3778) [INFO]  * 20-01:45:51 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:45:52 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 20-01:45:52 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-01:45:52 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 20-01:45:52 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 20-01:45:52 (3788) [INFO] Cleaning up list of fastest mirrors * 20-01:45:52 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 20-01:45:52 (3798) [INFO]  * 20-01:45:52 (3777) [INFO] Running: /usr/bin/yum check-update * 20-01:45:52 (3778) [INFO]  * 20-01:45:53 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-01:45:54 (3788) [INFO] Determining fastest mirrors * 20-01:47:22 (3788) [INFO] * EA4: 208.74.123.62 * 20-01:47:22 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 20-01:47:22 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 20-01:47:22 (3788) [INFO] * base: mirrors.xmission.com * 20-01:47:22 (3788) [INFO] * epel: mirrors.xmission.com * 20-01:47:22 (3788) [INFO] * extras: opencolo.mm.fcix.net * 20-01:47:22 (3788) [INFO] * updates: ridgewireless.mm.fcix.net * 20-01:50:23 (3788) [INFO]  * 20-01:50:23 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 20-01:50:23 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-01:50:24 (3798) [INFO]  * 20-01:50:24 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-01:50:24 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-01:50:24 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 20-01:50:24 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 20-01:50:24 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MwctzDvdm3/ea_profile.json * 20-01:50:25 (1623) [INFO] Backed up EA4 profile to /tmp/MwctzDvdm3/ea_profile.json * 20-01:50:25 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 20-01:54:26 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 20-01:54:26 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 21-01:50:30 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 21-01:50:38 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 21-01:50:38 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:53:22 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 21-01:53:22 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 21-01:53:23 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 21-01:53:23 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 21-01:53:23 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 21-01:53:23 (3332) [INFO] Checking if your system is up to date:  * 21-01:53:23 (3777) [INFO] Running: /usr/bin/yum clean all * 21-01:53:23 (3778) [INFO]  * 21-01:53:23 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:53:24 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 21-01:53:24 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-01:53:24 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 21-01:53:24 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 21-01:53:24 (3788) [INFO] Cleaning up list of fastest mirrors * 21-01:53:24 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 21-01:53:24 (3798) [INFO]  * 21-01:53:24 (3777) [INFO] Running: /usr/bin/yum check-update * 21-01:53:24 (3778) [INFO]  * 21-01:53:24 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-01:53:25 (3788) [INFO] Determining fastest mirrors * 21-01:54:55 (3788) [INFO] * EA4: 208.74.123.62 * 21-01:54:55 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 21-01:54:55 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 21-01:54:55 (3788) [INFO] * base: opencolo.mm.fcix.net * 21-01:54:55 (3788) [INFO] * epel: mirrors.xmission.com * 21-01:54:55 (3788) [INFO] * extras: mirrors.raystedman.org * 21-01:54:55 (3788) [INFO] * updates: mirror.web-ster.com * 21-01:57:38 (3788) [INFO]  * 21-01:57:38 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 21-01:57:38 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-01:57:38 (3798) [INFO]  * 21-01:57:38 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-01:57:38 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-01:57:38 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 21-01:57:38 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 21-01:57:38 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Y8ICq9GHpN/ea_profile.json * 21-01:57:40 (1623) [INFO] Backed up EA4 profile to /tmp/Y8ICq9GHpN/ea_profile.json * 21-01:57:40 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 21-02:01:40 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 21-02:01:40 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 22-01:50:14 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 22-01:50:23 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 22-01:50:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:52:37 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 22-01:52:37 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 22-01:52:38 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 22-01:52:38 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 22-01:52:38 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 22-01:52:38 (3332) [INFO] Checking if your system is up to date:  * 22-01:52:38 (3777) [INFO] Running: /usr/bin/yum clean all * 22-01:52:38 (3778) [INFO]  * 22-01:52:38 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:52:38 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 22-01:52:38 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-01:52:38 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 22-01:52:38 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 22-01:52:39 (3788) [INFO] Cleaning up list of fastest mirrors * 22-01:52:39 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 22-01:52:39 (3798) [INFO]  * 22-01:52:39 (3777) [INFO] Running: /usr/bin/yum check-update * 22-01:52:39 (3778) [INFO]  * 22-01:52:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-01:52:40 (3788) [INFO] Determining fastest mirrors * 22-01:54:11 (3788) [INFO] * EA4: 208.74.123.62 * 22-01:54:11 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 22-01:54:11 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 22-01:54:11 (3788) [INFO] * base: mirrors.xmission.com * 22-01:54:11 (3788) [INFO] * epel: opencolo.mm.fcix.net * 22-01:54:11 (3788) [INFO] * extras: mirrors.oit.uci.edu * 22-01:54:11 (3788) [INFO] * updates: mirror.sfo12.us.leaseweb.net * 22-01:56:23 (3788) [INFO]  * 22-01:56:23 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 22-01:56:23 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-01:56:23 (3798) [INFO]  * 22-01:56:23 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-01:56:23 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-01:56:23 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 22-01:56:23 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 22-01:56:23 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nHrz7WmjRo/ea_profile.json * 22-01:56:25 (1623) [INFO] Backed up EA4 profile to /tmp/nHrz7WmjRo/ea_profile.json * 22-01:56:25 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 22-02:00:25 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 22-02:00:25 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 23-01:49:50 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 23-01:50:00 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 23-01:50:00 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:52:43 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 23-01:52:43 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 23-01:52:44 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 23-01:52:44 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 23-01:52:44 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 23-01:52:44 (3332) [INFO] Checking if your system is up to date:  * 23-01:52:44 (3777) [INFO] Running: /usr/bin/yum clean all * 23-01:52:44 (3778) [INFO]  * 23-01:52:44 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:52:45 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 23-01:52:45 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-01:52:45 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 23-01:52:45 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 23-01:52:45 (3788) [INFO] Cleaning up list of fastest mirrors * 23-01:52:45 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 23-01:52:45 (3798) [INFO]  * 23-01:52:45 (3777) [INFO] Running: /usr/bin/yum check-update * 23-01:52:45 (3778) [INFO]  * 23-01:52:45 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-01:52:46 (3788) [INFO] Determining fastest mirrors * 23-01:54:15 (3788) [INFO] * EA4: 208.74.123.62 * 23-01:54:15 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 23-01:54:15 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 23-01:54:15 (3788) [INFO] * base: ridgewireless.mm.fcix.net * 23-01:54:15 (3788) [INFO] * epel: mirrors.xmission.com * 23-01:54:15 (3788) [INFO] * extras: ftp.ussg.iu.edu * 23-01:54:15 (3788) [INFO] * updates: mirrors.raystedman.org * 23-01:56:56 (3788) [INFO]  * 23-01:56:56 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 23-01:56:56 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-01:56:56 (3798) [INFO]  * 23-01:56:56 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-01:56:56 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-01:56:56 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 23-01:56:57 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 23-01:56:57 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cx2qy88d9y/ea_profile.json * 23-01:56:59 (1623) [INFO] Backed up EA4 profile to /tmp/cx2qy88d9y/ea_profile.json * 23-01:56:59 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 23-02:00:59 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 23-02:00:59 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 24-01:49:31 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 24-01:49:35 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 24-01:49:35 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:52:20 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 24-01:52:20 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30141 milliseconds with 0 out of 0 bytes received')  * 24-01:52:20 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 24-01:52:20 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 24-01:52:20 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 24-01:52:21 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 24-01:52:21 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 24-01:52:21 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 24-01:52:21 (3332) [INFO] Checking if your system is up to date:  * 24-01:52:21 (3777) [INFO] Running: /usr/bin/yum clean all * 24-01:52:21 (3778) [INFO]  * 24-01:52:21 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:52:22 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 24-01:52:22 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-01:52:22 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 24-01:52:22 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 24-01:52:22 (3788) [INFO] Cleaning up list of fastest mirrors * 24-01:52:22 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 24-01:52:22 (3798) [INFO]  * 24-01:52:22 (3777) [INFO] Running: /usr/bin/yum check-update * 24-01:52:22 (3778) [INFO]  * 24-01:52:22 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-01:52:23 (3788) [INFO] Determining fastest mirrors * 24-01:53:53 (3788) [INFO] * EA4: 208.74.123.61 * 24-01:53:53 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 24-01:53:53 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 24-01:53:53 (3788) [INFO] * base: repos.lax.layerhost.com * 24-01:53:53 (3788) [INFO] * epel: mirrors.xmission.com * 24-01:53:53 (3788) [INFO] * extras: linux.mirrors.es.net * 24-01:53:53 (3788) [INFO] * updates: centos.mirror.shastacoe.net * 24-01:56:19 (3788) [INFO]  * 24-01:56:19 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 24-01:56:19 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-01:56:19 (3798) [INFO]  * 24-01:56:19 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-01:56:19 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-01:56:19 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 24-01:56:19 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 24-01:56:19 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/M6X9U969dj/ea_profile.json * 24-01:56:20 (1623) [INFO] Backed up EA4 profile to /tmp/M6X9U969dj/ea_profile.json * 24-01:56:20 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 24-02:00:21 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 24-02:00:21 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 25-01:53:11 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 25-01:53:20 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 25-01:53:20 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:56:06 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 25-01:56:06 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 25-01:56:06 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 25-01:56:06 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 25-01:56:06 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 25-01:56:07 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 25-01:56:07 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 25-01:56:08 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 25-01:56:08 (3332) [INFO] Checking if your system is up to date:  * 25-01:56:08 (3777) [INFO] Running: /usr/bin/yum clean all * 25-01:56:08 (3778) [INFO]  * 25-01:56:08 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:56:08 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 25-01:56:08 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-01:56:08 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 25-01:56:08 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 25-01:56:09 (3788) [INFO] Cleaning up list of fastest mirrors * 25-01:56:09 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 25-01:56:09 (3798) [INFO]  * 25-01:56:09 (3777) [INFO] Running: /usr/bin/yum check-update * 25-01:56:09 (3778) [INFO]  * 25-01:56:09 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-01:56:10 (3788) [INFO] Determining fastest mirrors * 25-01:57:40 (3788) [INFO] * EA4: 208.74.123.62 * 25-01:57:40 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 25-01:57:40 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 25-01:57:40 (3788) [INFO] * base: mirrors.ocf.berkeley.edu * 25-01:57:40 (3788) [INFO] * epel: ziply.mm.fcix.net * 25-01:57:40 (3788) [INFO] * extras: mirrors.xtom.com * 25-01:57:40 (3788) [INFO] * updates: mirror.chpc.utah.edu * 25-02:00:23 (3788) [INFO]  * 25-02:00:23 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 25-02:00:23 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-02:00:23 (3798) [INFO]  * 25-02:00:23 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-02:00:23 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-02:00:23 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 25-02:00:23 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 25-02:00:23 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/12hEYJsH1w/ea_profile.json * 25-02:00:26 (1623) [INFO] Backed up EA4 profile to /tmp/12hEYJsH1w/ea_profile.json * 25-02:00:27 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 25-02:04:27 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 25-02:04:27 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 26-01:47:59 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 26-01:48:04 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 26-01:48:04 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:32 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 26-01:50:32 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 26-01:50:34 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 26-01:50:34 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 26-01:50:34 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 26-01:50:34 (3332) [INFO] Checking if your system is up to date:  * 26-01:50:34 (3777) [INFO] Running: /usr/bin/yum clean all * 26-01:50:34 (3778) [INFO]  * 26-01:50:34 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:50:34 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 26-01:50:34 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-01:50:34 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 26-01:50:34 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 26-01:50:35 (3788) [INFO] Cleaning up list of fastest mirrors * 26-01:50:35 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 26-01:50:35 (3798) [INFO]  * 26-01:50:35 (3777) [INFO] Running: /usr/bin/yum check-update * 26-01:50:35 (3778) [INFO]  * 26-01:50:35 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-01:50:35 (3788) [INFO] Determining fastest mirrors * 26-01:52:05 (3788) [INFO] * EA4: 208.74.123.61 * 26-01:52:05 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 26-01:52:05 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 26-01:52:05 (3788) [INFO] * base: mirrors.oit.uci.edu * 26-01:52:05 (3788) [INFO] * epel: mirrors.xmission.com * 26-01:52:05 (3788) [INFO] * extras: mirrors.oit.uci.edu * 26-01:52:05 (3788) [INFO] * updates: mirrors.oit.uci.edu * 26-01:54:21 (3788) [INFO]  * 26-01:54:21 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 26-01:54:21 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-01:54:22 (3798) [INFO]  * 26-01:54:22 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-01:54:22 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-01:54:22 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 26-01:54:22 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 26-01:54:22 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aWLIUlR6k6/ea_profile.json * 26-01:54:23 (1623) [INFO] Backed up EA4 profile to /tmp/aWLIUlR6k6/ea_profile.json * 26-01:54:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 26-01:58:24 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 26-01:58:24 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 27-01:46:43 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 27-01:46:52 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 27-01:46:52 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:49:38 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 27-01:49:38 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 27-01:49:38 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 27-01:49:38 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 27-01:49:38 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 27-01:49:38 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 27-01:49:38 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 27-01:49:38 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 27-01:49:38 (3332) [INFO] Checking if your system is up to date:  * 27-01:49:38 (3777) [INFO] Running: /usr/bin/yum clean all * 27-01:49:38 (3778) [INFO]  * 27-01:49:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:49:39 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 27-01:49:39 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-01:49:39 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 27-01:49:39 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 27-01:49:39 (3788) [INFO] Cleaning up list of fastest mirrors * 27-01:49:39 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 27-01:49:39 (3798) [INFO]  * 27-01:49:39 (3777) [INFO] Running: /usr/bin/yum check-update * 27-01:49:39 (3778) [INFO]  * 27-01:49:39 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-01:49:40 (3788) [INFO] Determining fastest mirrors * 27-01:51:10 (3788) [INFO] * EA4: 208.74.123.61 * 27-01:51:10 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 27-01:51:10 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 27-01:51:10 (3788) [INFO] * base: mirrors.xtom.com * 27-01:51:10 (3788) [INFO] * epel: mirrors.xmission.com * 27-01:51:10 (3788) [INFO] * extras: ridgewireless.mm.fcix.net * 27-01:51:10 (3788) [INFO] * updates: mirror.lstn.net * 27-01:54:05 (3788) [INFO]  * 27-01:54:05 (3788) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 27-01:54:05 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-01:54:05 (3798) [INFO]  * 27-01:54:05 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-01:54:05 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-01:54:05 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 27-01:54:05 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 27-01:54:05 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Thzk8Wv53O/ea_profile.json * 27-01:54:08 (1623) [INFO] Backed up EA4 profile to /tmp/Thzk8Wv53O/ea_profile.json * 27-01:54:08 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 27-01:58:08 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 27-01:58:08 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 28-02:02:54 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 28-02:03:00 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 28-02:03:00 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-02:05:35 (3483) [ERROR] yum appears to be unstable. Please address this before upgrading * 28-02:05:35 (3484) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')  * 28-02:05:35 (2671) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 28-02:05:35 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 28-02:05:35 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 28-02:05:36 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 28-02:05:36 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 28-02:05:36 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 28-02:05:36 (3332) [INFO] Checking if your system is up to date:  * 28-02:05:36 (3777) [INFO] Running: /usr/bin/yum clean all * 28-02:05:36 (3778) [INFO]  * 28-02:05:36 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-02:05:36 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 28-02:05:36 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-02:05:36 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 28-02:05:36 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 28-02:05:37 (3788) [INFO] Cleaning up list of fastest mirrors * 28-02:05:37 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 28-02:05:37 (3798) [INFO]  * 28-02:05:37 (3777) [INFO] Running: /usr/bin/yum check-update * 28-02:05:37 (3778) [INFO]  * 28-02:05:37 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-02:05:38 (3788) [INFO] Determining fastest mirrors * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] One of the configured repositories failed (Unknown), * 28-02:06:39 (3788) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 28-02:06:39 (3788) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 28-02:06:39 (3788) [INFO] upstream. This is most often useful if you are using a newer * 28-02:06:39 (3788) [INFO] distribution release than is supported by the repository (and the * 28-02:06:39 (3788) [INFO] packages for the previous distribution release still work). * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] 3. Run the command with the repository temporarily disabled * 28-02:06:39 (3788) [INFO] yum --disablerepo= ... * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 28-02:06:39 (3788) [INFO] will then just ignore the repository until you permanently enable it * 28-02:06:39 (3788) [INFO] again or use --enablerepo for temporary usage: * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] yum-config-manager --disable  * 28-02:06:39 (3788) [INFO] or * 28-02:06:39 (3788) [INFO] subscription-manager repos --disable= * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 28-02:06:39 (3788) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 28-02:06:39 (3788) [INFO] so will have to try and fail each time (and thus. yum will be be much * 28-02:06:39 (3788) [INFO] slower). If it is a very temporary problem though, this is often a nice * 28-02:06:39 (3788) [INFO] compromise: * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 28-02:06:39 (3788) [INFO]  * 28-02:06:39 (3788) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 28-02:06:39 (3798) [INFO]  * 28-02:06:39 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-02:06:39 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-02:06:39 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 28-02:06:39 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 28-02:06:39 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2L05PxADLj/ea_profile.json * 28-02:12:22 (1623) [INFO] Backed up EA4 profile to /tmp/2L05PxADLj/ea_profile.json * 28-02:12:22 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 28-02:16:23 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 28-02:16:23 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 29-01:47:38 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 29-01:47:46 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 29-01:47:46 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:50:29 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 29-01:50:29 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 29-01:50:29 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 29-01:50:29 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 29-01:50:29 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 29-01:50:29 (3332) [INFO] Checking if your system is up to date:  * 29-01:50:29 (3777) [INFO] Running: /usr/bin/yum clean all * 29-01:50:29 (3778) [INFO]  * 29-01:50:30 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:50:30 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 29-01:50:30 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-01:50:30 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 29-01:50:30 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 29-01:50:30 (3788) [INFO] Cleaning up list of fastest mirrors * 29-01:50:30 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 29-01:50:30 (3798) [INFO]  * 29-01:50:30 (3777) [INFO] Running: /usr/bin/yum check-update * 29-01:50:30 (3778) [INFO]  * 29-01:50:31 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-01:50:31 (3788) [INFO] Determining fastest mirrors * 29-01:52:03 (3788) [INFO] * EA4: 208.74.123.61 * 29-01:52:03 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 29-01:52:03 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 29-01:52:03 (3788) [INFO] * base: ridgewireless.mm.fcix.net * 29-01:52:03 (3788) [INFO] * epel: mirrors.xmission.com * 29-01:52:03 (3788) [INFO] * extras: mirrors.xmission.com * 29-01:52:03 (3788) [INFO] * updates: mirrors.xmission.com * 29-01:54:46 (3788) [INFO]  * 29-01:54:46 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 29-01:54:46 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-01:54:47 (3798) [INFO]  * 29-01:54:47 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-01:54:47 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-01:54:47 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 29-01:54:47 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 29-01:54:47 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iTHu5fkucT/ea_profile.json * 29-01:54:53 (1623) [INFO] Backed up EA4 profile to /tmp/iTHu5fkucT/ea_profile.json * 29-01:54:53 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 29-01:58:53 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 29-01:58:53 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 30-01:48:19 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 30-01:48:26 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 30-01:48:26 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:12 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 30-01:51:12 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 30-01:51:13 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 30-01:51:13 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 30-01:51:13 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 30-01:51:13 (3332) [INFO] Checking if your system is up to date:  * 30-01:51:13 (3777) [INFO] Running: /usr/bin/yum clean all * 30-01:51:13 (3778) [INFO]  * 30-01:51:14 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:51:14 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 30-01:51:14 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-01:51:14 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 30-01:51:14 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 30-01:51:14 (3788) [INFO] Cleaning up list of fastest mirrors * 30-01:51:14 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 30-01:51:14 (3798) [INFO]  * 30-01:51:14 (3777) [INFO] Running: /usr/bin/yum check-update * 30-01:51:14 (3778) [INFO]  * 30-01:51:15 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-01:51:15 (3788) [INFO] Determining fastest mirrors * 30-01:52:45 (3788) [INFO] * EA4: 208.74.123.62 * 30-01:52:45 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 30-01:52:45 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 30-01:52:45 (3788) [INFO] * base: opencolo.mm.fcix.net * 30-01:52:45 (3788) [INFO] * epel: mirrors.xmission.com * 30-01:52:45 (3788) [INFO] * extras: opencolo.mm.fcix.net * 30-01:52:45 (3788) [INFO] * updates: mirror.dal.nexril.net * 30-01:55:29 (3788) [INFO]  * 30-01:55:29 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 30-01:55:29 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-01:55:30 (3798) [INFO]  * 30-01:55:30 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-01:55:30 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-01:55:30 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 30-01:55:30 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 30-01:55:30 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xtcEiYoO5R/ea_profile.json * 30-01:55:32 (1623) [INFO] Backed up EA4 profile to /tmp/xtcEiYoO5R/ea_profile.json * 30-01:55:32 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 30-01:59:33 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 30-01:59:33 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 31-01:50:57 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 31-01:51:05 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 31-01:51:05 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:54:05 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 31-01:54:05 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 31-01:54:06 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 31-01:54:06 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 31-01:54:06 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 31-01:54:06 (3332) [INFO] Checking if your system is up to date:  * 31-01:54:06 (3777) [INFO] Running: /usr/bin/yum clean all * 31-01:54:06 (3778) [INFO]  * 31-01:54:07 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:54:07 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 31-01:54:07 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-01:54:07 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 31-01:54:07 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 31-01:54:08 (3788) [INFO] Cleaning up list of fastest mirrors * 31-01:54:08 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 31-01:54:08 (3798) [INFO]  * 31-01:54:08 (3777) [INFO] Running: /usr/bin/yum check-update * 31-01:54:08 (3778) [INFO]  * 31-01:54:08 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-01:54:08 (3788) [INFO] Determining fastest mirrors * 31-01:55:39 (3788) [INFO] * EA4: 208.74.123.62 * 31-01:55:39 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 31-01:55:39 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 31-01:55:39 (3788) [INFO] * base: repos.lax.layerhost.com * 31-01:55:39 (3788) [INFO] * epel: mirrors.xmission.com * 31-01:55:39 (3788) [INFO] * extras: mirrors.xtom.com * 31-01:55:39 (3788) [INFO] * updates: mirrors.sonic.net * 31-01:58:38 (3788) [INFO]  * 31-01:58:38 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 31-01:58:38 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-01:58:38 (3798) [INFO]  * 31-01:58:38 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-01:58:38 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-01:58:38 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 31-01:58:38 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 31-01:58:38 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7PD8WM5MTe/ea_profile.json * 31-01:58:42 (1623) [INFO] Backed up EA4 profile to /tmp/7PD8WM5MTe/ea_profile.json * 31-01:58:42 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 31-02:02:42 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 31-02:02:42 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 01-01:45:19 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 01-01:45:25 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 01-01:45:25 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:47:23 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 01-01:47:23 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 01-01:47:25 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 01-01:47:25 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 01-01:47:25 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 01-01:47:25 (3332) [INFO] Checking if your system is up to date:  * 01-01:47:25 (3777) [INFO] Running: /usr/bin/yum clean all * 01-01:47:25 (3778) [INFO]  * 01-01:47:25 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:25 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 01-01:47:25 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-01:47:25 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 01-01:47:25 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 01-01:47:26 (3788) [INFO] Cleaning up list of fastest mirrors * 01-01:47:26 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 01-01:47:26 (3798) [INFO]  * 01-01:47:26 (3777) [INFO] Running: /usr/bin/yum check-update * 01-01:47:26 (3778) [INFO]  * 01-01:47:26 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-01:47:27 (3788) [INFO] Determining fastest mirrors * 01-01:48:57 (3788) [INFO] * EA4: 208.74.123.61 * 01-01:48:57 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 01-01:48:57 (3788) [INFO] * cpanel-plugins: 208.74.123.61 * 01-01:48:57 (3788) [INFO] * base: opencolo.mm.fcix.net * 01-01:48:57 (3788) [INFO] * epel: ziply.mm.fcix.net * 01-01:48:57 (3788) [INFO] * extras: mirror.usi.edu * 01-01:48:57 (3788) [INFO] * updates: mirror.web-ster.com * 01-01:51:14 (3788) [INFO]  * 01-01:51:14 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 01-01:51:14 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-01:51:14 (3798) [INFO]  * 01-01:51:14 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-01:51:14 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-01:51:14 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 01-01:51:14 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 01-01:51:14 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5lWVJN43A9/ea_profile.json * 01-01:51:18 (1623) [INFO] Backed up EA4 profile to /tmp/5lWVJN43A9/ea_profile.json * 01-01:51:18 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 01-01:55:18 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 01-01:55:18 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 02-01:57:46 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 02-01:57:50 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 02-01:57:50 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-02:00:32 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 02-02:00:32 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 02-02:00:33 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 02-02:00:33 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 02-02:00:33 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 02-02:00:33 (3332) [INFO] Checking if your system is up to date:  * 02-02:00:33 (3777) [INFO] Running: /usr/bin/yum clean all * 02-02:00:33 (3778) [INFO]  * 02-02:00:33 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-02:00:34 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 02-02:00:34 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-02:00:34 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 02-02:00:34 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 02-02:00:34 (3788) [INFO] Cleaning up list of fastest mirrors * 02-02:00:34 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 02-02:00:34 (3798) [INFO]  * 02-02:00:34 (3777) [INFO] Running: /usr/bin/yum check-update * 02-02:00:34 (3778) [INFO]  * 02-02:00:34 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-02:00:35 (3788) [INFO] Determining fastest mirrors * 02-02:02:03 (3788) [INFO] * EA4: 208.74.123.62 * 02-02:02:03 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 02-02:02:03 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 02-02:02:03 (3788) [INFO] * base: repos.forethought.net * 02-02:02:03 (3788) [INFO] * epel: mirrors.xmission.com * 02-02:02:03 (3788) [INFO] * extras: repos.forethought.net * 02-02:02:03 (3788) [INFO] * updates: mirror.lstn.net * 02-02:04:46 (3788) [INFO]  * 02-02:04:46 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 02-02:04:46 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-02:04:47 (3798) [INFO]  * 02-02:04:47 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-02:04:47 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-02:04:47 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 02-02:04:47 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 02-02:04:47 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LhxVXRaC2H/ea_profile.json * 02-02:04:50 (1623) [INFO] Backed up EA4 profile to /tmp/LhxVXRaC2H/ea_profile.json * 02-02:04:50 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 02-02:08:51 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 02-02:08:51 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 03-01:48:20 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 03-01:48:23 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 03-01:48:23 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:51:07 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 03-01:51:07 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 03-01:51:07 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 03-01:51:07 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 03-01:51:07 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 03-01:51:07 (3332) [INFO] Checking if your system is up to date:  * 03-01:51:07 (3777) [INFO] Running: /usr/bin/yum clean all * 03-01:51:07 (3778) [INFO]  * 03-01:51:08 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:51:08 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 03-01:51:08 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-01:51:08 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 03-01:51:08 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 03-01:51:09 (3788) [INFO] Cleaning up list of fastest mirrors * 03-01:51:09 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 03-01:51:09 (3798) [INFO]  * 03-01:51:09 (3777) [INFO] Running: /usr/bin/yum check-update * 03-01:51:09 (3778) [INFO]  * 03-01:51:09 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-01:51:10 (3788) [INFO] Determining fastest mirrors * 03-01:52:40 (3788) [INFO] * EA4: 208.74.123.62 * 03-01:52:40 (3788) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 03-01:52:40 (3788) [INFO] * cpanel-plugins: 208.74.123.62 * 03-01:52:40 (3788) [INFO] * base: mirrors.raystedman.org * 03-01:52:40 (3788) [INFO] * epel: mirrors.xmission.com * 03-01:52:40 (3788) [INFO] * extras: mirror.chpc.utah.edu * 03-01:52:40 (3788) [INFO] * updates: opencolo.mm.fcix.net * 03-01:55:21 (3788) [INFO]  * 03-01:55:21 (3788) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 03-01:55:21 (3788) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-01:55:22 (3798) [INFO]  * 03-01:55:22 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-01:55:22 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-01:55:22 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 03-01:55:22 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 03-01:55:22 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xHdfuS0KXC/ea_profile.json * 03-01:55:24 (1623) [INFO] Backed up EA4 profile to /tmp/xHdfuS0KXC/ea_profile.json * 03-01:55:24 (2671) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime  * 03-01:59:24 (2671) [WARN] *** Elevation Blocker detected: *** This script (version 2) does not appear to be the newest available release (4). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check.  * 03-01:59:24 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 04-01:50:04 (2671) [WARN] *** Elevation Blocker detected: *** We do not know how to upgrade to AlmaLinux 8 with MySQL version 10.0. Please open a support ticket.  * 04-01:50:14 (3425) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 04-01:50:14 (2671) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should 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-01:53:17 (3510) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading.  * 04-01:53:17 (2671) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration  * 04-01:53:17 (3353) [WARN] JetBackup version 4.1.3-3 currently installed. * 04-01:53:17 (2671) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate.  * 04-01:53:17 (2671) [WARN] *** Elevation Blocker detected: *** disk space issue  * 04-01:53:17 (3332) [INFO] Checking if your system is up to date:  * 04-01:53:17 (3777) [INFO] Running: /usr/bin/yum clean all * 04-01:53:17 (3778) [INFO]  * 04-01:53:18 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:53:18 (3788) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 04-01:53:18 (3788) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-01:53:18 (3788) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 04-01:53:18 (3788) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 04-01:53:18 (3788) [INFO] Cleaning up list of fastest mirrors * 04-01:53:18 (3788) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 04-01:53:19 (3798) [INFO]  * 04-01:53:19 (3777) [INFO] Running: /usr/bin/yum check-update * 04-01:53:19 (3778) [INFO]  * 04-01:53:19 (3788) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-01:53:20 (3788) [INFO] Determining fastest mirrors * 04-01:53:50 (3788) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was * 04-01:53:50 (3788) [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') * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] One of the configured repositories failed (Unknown), * 04-01:53:50 (3788) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 04-01:53:50 (3788) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 04-01:53:50 (3788) [INFO] upstream. This is most often useful if you are using a newer * 04-01:53:50 (3788) [INFO] distribution release than is supported by the repository (and the * 04-01:53:50 (3788) [INFO] packages for the previous distribution release still work). * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] 3. Run the command with the repository temporarily disabled * 04-01:53:50 (3788) [INFO] yum --disablerepo= ... * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 04-01:53:50 (3788) [INFO] will then just ignore the repository until you permanently enable it * 04-01:53:50 (3788) [INFO] again or use --enablerepo for temporary usage: * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] yum-config-manager --disable  * 04-01:53:50 (3788) [INFO] or * 04-01:53:50 (3788) [INFO] subscription-manager repos --disable= * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 04-01:53:50 (3788) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 04-01:53:50 (3788) [INFO] so will have to try and fail each time (and thus. yum will be be much * 04-01:53:50 (3788) [INFO] slower). If it is a very temporary problem though, this is often a nice * 04-01:53:50 (3788) [INFO] compromise: * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 04-01:53:50 (3788) [INFO]  * 04-01:53:50 (3788) [INFO] Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64 * 04-01:53:50 (3798) [INFO]  * 04-01:53:50 (3335) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-01:53:50 (2671) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-01:53:50 (2671) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update.  * 04-01:53:50 (2994) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 04-01:53:50 (1598) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3mOtqoCVNb/ea_profile.json * 04-01:54:22 (2638) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3mOtqoCVNb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1600.  * 04-01:54:22 (692) [WARN] Please fix the detected issues before performing the elevation process.  * 2023-02-04 01:58:25 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-04 01:58:28 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-04 01:58:28 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-04 02:05:08 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-04 02:05:08 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-04 02:05:12 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-04 02:05:12 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-04 02:05:12 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-04 02:05:12 (3385) [INFO] Checking if your system is up to date: * 2023-02-04 02:05:12 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-04 02:05:12 (3898) [INFO] * 2023-02-04 02:05:13 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-04 02:05:13 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-04 02:05:13 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-04 02:05:13 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-04 02:05:13 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-04 02:05:14 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-04 02:05:14 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-04 02:05:14 (3929) [INFO] * 2023-02-04 02:05:14 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-04 02:05:14 (3898) [INFO] * 2023-02-04 02:09:12 (3912) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" * 2023-02-04 02:09:12 (3912) [INFO] Trying other mirror. * 2023-02-04 02:09:28 (3912) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-02-04 02:09:28 (3912) [INFO] Trying other mirror. * 2023-02-04 02:10:04 (3912) [INFO] * 2023-02-04 02:10:04 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-04 02:10:04 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-04 02:10:04 (3929) [INFO] * 2023-02-04 02:10:04 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-04 02:10:04 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-04 02:10:04 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-04 02:10:04 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-04 02:10:04 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mGDNQrMMcB/ea_profile.json * 2023-02-04 02:10:08 (1667) [INFO] Backed up EA4 profile to /tmp/mGDNQrMMcB/ea_profile.json * 2023-02-04 02:10:08 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-04 02:14:09 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-05 01:45:52 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-05 01:45:58 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-05 01:45:58 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-05 01:46:32 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-05 01:46:32 (3553) [ERROR] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Resolving timed out after 30572 milliseconds') 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 find a valid baseurl for repo: base/7/x86_64 * 2023-02-05 01:46:32 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-05 01:46:32 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-05 01:46:32 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-05 01:46:33 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-05 01:46:33 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-05 01:46:33 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-05 01:46:33 (3385) [INFO] Checking if your system is up to date: * 2023-02-05 01:46:33 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-05 01:46:33 (3898) [INFO] * 2023-02-05 01:46:33 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-05 01:46:33 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-05 01:46:33 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-05 01:46:33 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-05 01:46:33 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-05 01:46:33 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-05 01:46:33 (3912) [INFO] Other repos take up 652 k of disk space (use --verbose for details) * 2023-02-05 01:46:33 (3929) [INFO] * 2023-02-05 01:46:33 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-05 01:46:33 (3898) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was * 2023-02-05 01:46:35 (3912) [INFO] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-05 01:46:35 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-05 01:46:35 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-05 01:46:35 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-05 01:46:35 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-05 01:46:35 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-05 01:46:35 (3912) [INFO] yum --disablerepo= ... * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-05 01:46:35 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-05 01:46:35 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] yum-config-manager --disable * 2023-02-05 01:46:35 (3912) [INFO] or * 2023-02-05 01:46:35 (3912) [INFO] subscription-manager repos --disable= * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-05 01:46:35 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-05 01:46:35 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-05 01:46:35 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-05 01:46:35 (3912) [INFO] compromise: * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-05 01:46:35 (3912) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] Cannot find a valid baseurl for repo: base/7/x86_64 * 2023-02-05 01:46:35 (3929) [INFO] * 2023-02-05 01:46:35 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-05 01:46:35 (3408) [INFO] Checking /scripts/sysup * 2023-02-05 01:46:35 (3897) [INFO] Running: /scripts/sysup * 2023-02-05 01:46:35 (3898) [INFO] * 2023-02-05 01:46:35 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-05 01:46:38 (3912) [INFO] All Needed Packages are already installed. * 2023-02-05 01:46:38 (3929) [INFO] * 2023-02-05 01:46:38 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-05 01:46:38 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-05 01:46:38 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j8sHExDi8Z/ea_profile.json * 2023-02-05 01:46:57 (2694) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j8sHExDi8Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644. * 2023-02-05 01:46:57 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-05 01:50:59 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-05 01:51:02 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-05 01:51:02 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-05 01:51:36 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-05 01:51:36 (3553) [ERROR] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Resolving timed out after 30590 milliseconds') 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 find a valid baseurl for repo: base/7/x86_64 * 2023-02-05 01:51:36 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-05 01:51:36 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-05 01:51:36 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-05 01:51:36 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-05 01:51:36 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-05 01:51:36 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-05 01:51:36 (3385) [INFO] Checking if your system is up to date: * 2023-02-05 01:51:36 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-05 01:51:36 (3898) [INFO] * 2023-02-05 01:51:37 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-05 01:51:37 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-05 01:51:37 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-05 01:51:37 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-05 01:51:37 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-05 01:51:37 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-05 01:51:37 (3912) [INFO] Other repos take up 652 k of disk space (use --verbose for details) * 2023-02-05 01:51:37 (3929) [INFO] * 2023-02-05 01:51:37 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-05 01:51:37 (3898) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was * 2023-02-05 01:51:39 (3912) [INFO] 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Name or service not known" * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-05 01:51:39 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-05 01:51:39 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-05 01:51:39 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-05 01:51:39 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-05 01:51:39 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-05 01:51:39 (3912) [INFO] yum --disablerepo= ... * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-05 01:51:39 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-05 01:51:39 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] yum-config-manager --disable * 2023-02-05 01:51:39 (3912) [INFO] or * 2023-02-05 01:51:39 (3912) [INFO] subscription-manager repos --disable= * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-05 01:51:39 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-05 01:51:39 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-05 01:51:39 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-05 01:51:39 (3912) [INFO] compromise: * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-05 01:51:39 (3912) [INFO] * 2023-02-05 01:51:39 (3912) [INFO] Cannot find a valid baseurl for repo: base/7/x86_64 * 2023-02-05 01:51:39 (3929) [INFO] * 2023-02-05 01:51:39 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-05 01:51:39 (3408) [INFO] Checking /scripts/sysup * 2023-02-05 01:51:39 (3897) [INFO] Running: /scripts/sysup * 2023-02-05 01:51:39 (3898) [INFO] * 2023-02-05 01:51:40 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-05 01:51:42 (3912) [INFO] All Needed Packages are already installed. * 2023-02-05 01:51:42 (3929) [INFO] * 2023-02-05 01:51:42 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-05 01:51:42 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-05 01:51:42 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ObFfhDZRRt/ea_profile.json * 2023-02-05 01:52:01 (2694) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ObFfhDZRRt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1644. * 2023-02-05 01:52:01 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-06 01:48:15 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-06 01:48:23 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-06 01:48:23 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-06 01:51:05 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-06 01:51:05 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-06 01:51:06 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-06 01:51:06 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-06 01:51:06 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-06 01:51:06 (3385) [INFO] Checking if your system is up to date: * 2023-02-06 01:51:06 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-06 01:51:06 (3898) [INFO] * 2023-02-06 01:51:06 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-06 01:51:06 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-06 01:51:06 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-06 01:51:06 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-06 01:51:06 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-06 01:51:07 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-06 01:51:07 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-06 01:51:07 (3929) [INFO] * 2023-02-06 01:51:07 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-06 01:51:07 (3898) [INFO] * 2023-02-06 01:55:23 (3912) [INFO] * 2023-02-06 01:55:23 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-06 01:55:23 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-06 01:55:23 (3929) [INFO] * 2023-02-06 01:55:23 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-06 01:55:23 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-06 01:55:23 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-06 01:55:23 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-06 01:55:23 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ssCmC3Tq3T/ea_profile.json * 2023-02-06 01:55:25 (1667) [INFO] Backed up EA4 profile to /tmp/ssCmC3Tq3T/ea_profile.json * 2023-02-06 01:55:25 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-06 01:59:26 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-07 01:48:23 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-07 01:48:34 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-07 01:48:34 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-07 01:51:31 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-07 01:51:31 (3553) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-02-07 01:51:31 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-07 01:51:31 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-07 01:51:31 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-07 01:51:32 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-07 01:51:32 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-07 01:51:32 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-07 01:51:32 (3385) [INFO] Checking if your system is up to date: * 2023-02-07 01:51:32 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-07 01:51:32 (3898) [INFO] * 2023-02-07 01:51:33 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-07 01:51:33 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-07 01:51:33 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-07 01:51:33 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-07 01:51:33 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-07 01:51:33 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-07 01:51:33 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-07 01:51:33 (3929) [INFO] * 2023-02-07 01:51:33 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-07 01:51:33 (3898) [INFO] * 2023-02-07 01:56:09 (3912) [INFO] * 2023-02-07 01:56:09 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-07 01:56:09 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-07 01:56:09 (3929) [INFO] * 2023-02-07 01:56:09 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-07 01:56:09 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-07 01:56:09 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-07 01:56:09 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-07 01:56:09 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3cWwkvKBxQ/ea_profile.json * 2023-02-07 01:56:18 (1667) [INFO] Backed up EA4 profile to /tmp/3cWwkvKBxQ/ea_profile.json * 2023-02-07 01:56:18 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-07 02:00:21 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-08 01:49:54 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-08 01:50:00 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-08 01:50:00 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-08 01:53:01 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-08 01:53:01 (3553) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30539 milliseconds') * 2023-02-08 01:53:01 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-08 01:53:01 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-08 01:53:01 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-08 01:53:03 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-08 01:53:03 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-08 01:53:03 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-08 01:53:03 (3385) [INFO] Checking if your system is up to date: * 2023-02-08 01:53:03 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-08 01:53:03 (3898) [INFO] * 2023-02-08 01:53:03 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-08 01:53:03 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-08 01:53:03 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-08 01:53:03 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-08 01:53:03 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-08 01:53:04 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-08 01:53:04 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-08 01:53:04 (3929) [INFO] * 2023-02-08 01:53:04 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-08 01:53:04 (3898) [INFO] * 2023-02-08 01:57:34 (3912) [INFO] * 2023-02-08 01:57:34 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-08 01:57:34 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-08 01:57:34 (3929) [INFO] * 2023-02-08 01:57:34 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-08 01:57:34 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-08 01:57:34 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-08 01:57:34 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-08 01:57:34 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oCEiS2sSJo/ea_profile.json * 2023-02-08 01:57:37 (1667) [INFO] Backed up EA4 profile to /tmp/oCEiS2sSJo/ea_profile.json * 2023-02-08 01:57:37 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-08 02:01:38 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-09 01:45:50 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-09 01:45:58 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-09 01:45:58 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-09 01:48:29 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-09 01:48:29 (3553) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-02-09 01:48:29 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-09 01:48:29 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-09 01:48:29 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-09 01:48:30 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-09 01:48:30 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-09 01:48:30 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-09 01:48:30 (3385) [INFO] Checking if your system is up to date: * 2023-02-09 01:48:30 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-09 01:48:30 (3898) [INFO] * 2023-02-09 01:48:30 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-09 01:48:30 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-09 01:48:30 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-09 01:48:30 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-09 01:48:30 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-09 01:48:31 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-09 01:48:31 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-09 01:48:31 (3929) [INFO] * 2023-02-09 01:48:31 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-09 01:48:31 (3898) [INFO] * 2023-02-09 01:52:32 (3912) [INFO] * 2023-02-09 01:52:32 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-09 01:52:32 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-09 01:52:32 (3929) [INFO] * 2023-02-09 01:52:32 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-09 01:52:32 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-09 01:52:32 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-09 01:52:32 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-09 01:52:32 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1x6O7E77Ic/ea_profile.json * 2023-02-09 01:52:35 (1667) [INFO] Backed up EA4 profile to /tmp/1x6O7E77Ic/ea_profile.json * 2023-02-09 01:52:35 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-09 01:56:36 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-10 01:50:36 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-10 01:50:40 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-10 01:50:40 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-10 01:56:32 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-10 01:56:32 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-10 01:56:35 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-10 01:56:35 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-10 01:56:35 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-10 01:56:35 (3385) [INFO] Checking if your system is up to date: * 2023-02-10 01:56:35 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-10 01:56:35 (3898) [INFO] * 2023-02-10 01:56:36 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-10 01:56:36 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-10 01:56:36 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-10 01:56:36 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-10 01:56:36 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-10 01:56:37 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-10 01:56:37 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-10 01:56:37 (3929) [INFO] * 2023-02-10 01:56:37 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-10 01:56:37 (3898) [INFO] * 2023-02-10 02:01:09 (3912) [INFO] * 2023-02-10 02:01:09 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-10 02:01:09 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-10 02:01:10 (3929) [INFO] * 2023-02-10 02:01:10 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-10 02:01:10 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-10 02:01:10 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-10 02:01:10 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-10 02:01:10 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EluigdNZL_/ea_profile.json * 2023-02-10 02:01:15 (1667) [INFO] Backed up EA4 profile to /tmp/EluigdNZL_/ea_profile.json * 2023-02-10 02:01:15 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-10 02:05:17 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-11 01:49:18 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-11 01:49:27 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-11 01:49:27 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-11 01:51:57 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-11 01:51:57 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-11 01:51:58 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-11 01:51:58 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-11 01:51:58 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-11 01:51:58 (3385) [INFO] Checking if your system is up to date: * 2023-02-11 01:51:58 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-11 01:51:58 (3898) [INFO] * 2023-02-11 01:51:59 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-11 01:51:59 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-11 01:51:59 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-11 01:51:59 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-11 01:51:59 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-11 01:51:59 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-11 01:51:59 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-11 01:51:59 (3929) [INFO] * 2023-02-11 01:51:59 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-11 01:51:59 (3898) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-11 01:53:00 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-11 01:53:00 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-11 01:53:00 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-11 01:53:00 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-11 01:53:00 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-11 01:53:00 (3912) [INFO] yum --disablerepo= ... * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-11 01:53:00 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-11 01:53:00 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] yum-config-manager --disable * 2023-02-11 01:53:00 (3912) [INFO] or * 2023-02-11 01:53:00 (3912) [INFO] subscription-manager repos --disable= * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-11 01:53:00 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-11 01:53:00 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-11 01:53:00 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-11 01:53:00 (3912) [INFO] compromise: * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-11 01:53:00 (3912) [INFO] * 2023-02-11 01:53:00 (3912) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-11 01:53:00 (3929) [INFO] * 2023-02-11 01:53:00 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-11 01:53:00 (3408) [INFO] Checking /scripts/sysup * 2023-02-11 01:53:00 (3897) [INFO] Running: /scripts/sysup * 2023-02-11 01:53:00 (3898) [INFO] * 2023-02-11 01:53:01 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-11 01:53:05 (3912) [INFO] All Needed Packages are already installed. * 2023-02-11 01:53:05 (3929) [INFO] * 2023-02-11 01:53:05 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-11 01:53:05 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-11 01:53:05 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r1hEVpzgf2/ea_profile.json * 2023-02-11 01:57:38 (1667) [INFO] Backed up EA4 profile to /tmp/r1hEVpzgf2/ea_profile.json * 2023-02-11 01:57:38 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-11 02:01:40 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-12 01:49:47 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-12 01:49:52 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-12 01:49:52 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-12 01:52:37 (3552) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-12 01:52:37 (3553) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-02-12 01:52:37 (2727) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-12 01:52:37 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-12 01:52:37 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-12 01:52:38 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-12 01:52:38 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-12 01:52:38 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-12 01:52:38 (3385) [INFO] Checking if your system is up to date: * 2023-02-12 01:52:38 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-12 01:52:38 (3898) [INFO] * 2023-02-12 01:52:38 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-12 01:52:39 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-12 01:52:39 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-12 01:52:39 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-12 01:52:39 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-12 01:52:39 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-12 01:52:39 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-12 01:52:39 (3929) [INFO] * 2023-02-12 01:52:39 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-12 01:52:39 (3898) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-12 01:53:40 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-12 01:53:40 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-12 01:53:40 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-12 01:53:40 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-12 01:53:40 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-12 01:53:40 (3912) [INFO] yum --disablerepo= ... * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-12 01:53:40 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-12 01:53:40 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] yum-config-manager --disable * 2023-02-12 01:53:40 (3912) [INFO] or * 2023-02-12 01:53:40 (3912) [INFO] subscription-manager repos --disable= * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-12 01:53:40 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-12 01:53:40 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-12 01:53:40 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-12 01:53:40 (3912) [INFO] compromise: * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-12 01:53:40 (3912) [INFO] * 2023-02-12 01:53:40 (3912) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-12 01:53:40 (3929) [INFO] * 2023-02-12 01:53:40 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-12 01:53:40 (3408) [INFO] Checking /scripts/sysup * 2023-02-12 01:53:40 (3897) [INFO] Running: /scripts/sysup * 2023-02-12 01:53:40 (3898) [INFO] * 2023-02-12 01:53:41 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-12 01:53:44 (3912) [INFO] All Needed Packages are already installed. * 2023-02-12 01:53:44 (3929) [INFO] * 2023-02-12 01:53:44 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-12 01:53:44 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-12 01:53:44 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KwrSgukxV_/ea_profile.json * 2023-02-12 01:58:13 (1667) [INFO] Backed up EA4 profile to /tmp/KwrSgukxV_/ea_profile.json * 2023-02-12 01:58:13 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-12 02:02:17 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-13 01:47:46 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-13 01:47:53 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-13 01:47:53 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-13 01:50:37 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-13 01:50:37 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-13 01:50:38 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-13 01:50:38 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-13 01:50:38 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-13 01:50:38 (3385) [INFO] Checking if your system is up to date: * 2023-02-13 01:50:38 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-13 01:50:38 (3898) [INFO] * 2023-02-13 01:50:38 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-13 01:50:39 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-13 01:50:39 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-13 01:50:39 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-13 01:50:39 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-13 01:50:39 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-13 01:50:39 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-13 01:50:39 (3929) [INFO] * 2023-02-13 01:50:39 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-13 01:50:39 (3898) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-13 01:51:39 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-13 01:51:39 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-13 01:51:39 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-13 01:51:39 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-13 01:51:39 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-13 01:51:39 (3912) [INFO] yum --disablerepo= ... * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-13 01:51:39 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-13 01:51:39 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] yum-config-manager --disable * 2023-02-13 01:51:39 (3912) [INFO] or * 2023-02-13 01:51:39 (3912) [INFO] subscription-manager repos --disable= * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-13 01:51:39 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-13 01:51:39 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-13 01:51:39 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-13 01:51:39 (3912) [INFO] compromise: * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-13 01:51:39 (3912) [INFO] * 2023-02-13 01:51:39 (3912) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-13 01:51:39 (3929) [INFO] * 2023-02-13 01:51:39 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-13 01:51:39 (3408) [INFO] Checking /scripts/sysup * 2023-02-13 01:51:39 (3897) [INFO] Running: /scripts/sysup * 2023-02-13 01:51:39 (3898) [INFO] * 2023-02-13 01:51:40 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-13 01:51:44 (3912) [INFO] All Needed Packages are already installed. * 2023-02-13 01:51:44 (3929) [INFO] * 2023-02-13 01:51:44 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-13 01:51:44 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-13 01:51:44 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/akMd0usl8_/ea_profile.json * 2023-02-13 01:56:32 (1667) [INFO] Backed up EA4 profile to /tmp/akMd0usl8_/ea_profile.json * 2023-02-13 01:56:32 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-13 02:00:33 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-14 01:46:20 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-14 01:46:24 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-14 01:46:24 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-14 01:49:02 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-14 01:49:02 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-14 01:49:03 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-14 01:49:03 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-14 01:49:03 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-14 01:49:03 (3385) [INFO] Checking if your system is up to date: * 2023-02-14 01:49:03 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-14 01:49:03 (3898) [INFO] * 2023-02-14 01:49:03 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-14 01:49:04 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-14 01:49:04 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-14 01:49:04 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-14 01:49:04 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-14 01:49:04 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-14 01:49:04 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-14 01:49:04 (3929) [INFO] * 2023-02-14 01:49:04 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-14 01:49:04 (3898) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] One of the configured repositories failed (Unknown), * 2023-02-14 01:50:04 (3912) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-14 01:50:04 (3912) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-14 01:50:04 (3912) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-14 01:50:04 (3912) [INFO] distribution release than is supported by the repository (and the * 2023-02-14 01:50:04 (3912) [INFO] packages for the previous distribution release still work). * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-14 01:50:04 (3912) [INFO] yum --disablerepo= ... * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-14 01:50:04 (3912) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-14 01:50:04 (3912) [INFO] again or use --enablerepo for temporary usage: * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] yum-config-manager --disable * 2023-02-14 01:50:04 (3912) [INFO] or * 2023-02-14 01:50:04 (3912) [INFO] subscription-manager repos --disable= * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-14 01:50:04 (3912) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-14 01:50:04 (3912) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-14 01:50:04 (3912) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-14 01:50:04 (3912) [INFO] compromise: * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-14 01:50:04 (3912) [INFO] * 2023-02-14 01:50:04 (3912) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-14 01:50:04 (3929) [INFO] * 2023-02-14 01:50:04 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-14 01:50:04 (3408) [INFO] Checking /scripts/sysup * 2023-02-14 01:50:04 (3897) [INFO] Running: /scripts/sysup * 2023-02-14 01:50:04 (3898) [INFO] * 2023-02-14 01:50:05 (3912) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-14 01:50:10 (3912) [INFO] All Needed Packages are already installed. * 2023-02-14 01:50:10 (3929) [INFO] * 2023-02-14 01:50:10 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-14 01:50:10 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-14 01:50:10 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SjCT84bjyp/ea_profile.json * 2023-02-14 01:54:38 (1667) [INFO] Backed up EA4 profile to /tmp/SjCT84bjyp/ea_profile.json * 2023-02-14 01:54:38 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-14 01:58:40 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-15 01:49:19 (2727) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-15 01:49:26 (3494) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-15 01:49:26 (2727) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-15 01:52:24 (3579) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-15 01:52:24 (2727) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-15 01:52:25 (3422) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-15 01:52:25 (2727) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-15 01:52:25 (2727) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-15 01:52:25 (3385) [INFO] Checking if your system is up to date: * 2023-02-15 01:52:25 (3897) [INFO] Running: /usr/bin/yum clean all * 2023-02-15 01:52:25 (3898) [INFO] * 2023-02-15 01:52:25 (3912) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-15 01:52:26 (3912) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-15 01:52:26 (3912) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-15 01:52:26 (3912) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-15 01:52:26 (3912) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-15 01:52:26 (3912) [INFO] Cleaning up list of fastest mirrors * 2023-02-15 01:52:26 (3912) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-15 01:52:26 (3929) [INFO] * 2023-02-15 01:52:26 (3897) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-15 01:52:26 (3898) [INFO] * 2023-02-15 01:57:00 (3912) [INFO] * 2023-02-15 01:57:00 (3912) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-15 01:57:00 (3912) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-15 01:57:01 (3929) [INFO] * 2023-02-15 01:57:01 (3393) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-15 01:57:01 (2727) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-15 01:57:01 (2727) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-15 01:57:01 (3047) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-15 01:57:01 (1642) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mSY19eMNRk/ea_profile.json * 2023-02-15 01:57:04 (1667) [INFO] Backed up EA4 profile to /tmp/mSY19eMNRk/ea_profile.json * 2023-02-15 01:57:04 (2727) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-15 02:01:04 (2727) [WARN] *** Elevation Blocker detected: *** This script (version 4) does not appear to be the newest available release (5). Run this script with the --update option: /scripts/elevate-cpanel --update Pass the --skip-elevate-version-check flag to skip this check. * 2023-02-15 02:01:05 (709) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-16 02:05:40 (366) [INFO] Self-update of script version 4 requested. * 2023-02-16 02:09:40 (371) [INFO] Newer version of script found. Downloading. * 2023-02-16 02:13:41 (380) [INFO] Script update to version 5 successful. * 2023-02-16 02:13:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-02-16 02:13:46 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-16 02:13:51 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-16 02:13:51 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-16 02:16:16 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-16 02:16:16 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30598 milliseconds') * 2023-02-16 02:16:16 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-16 02:16:16 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-16 02:16:16 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-16 02:16:17 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-16 02:16:17 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-16 02:16:17 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-16 02:16:17 (3566) [INFO] Checking if your system is up to date: * 2023-02-16 02:16:17 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-16 02:16:17 (4079) [INFO] * 2023-02-16 02:16:17 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-16 02:16:17 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-16 02:16:17 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-16 02:16:17 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-16 02:16:17 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-16 02:16:18 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-16 02:16:18 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-16 02:16:18 (4110) [INFO] * 2023-02-16 02:16:18 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-16 02:16:18 (4079) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-02-16 02:17:18 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-16 02:17:18 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-16 02:17:18 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-16 02:17:18 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-02-16 02:17:18 (4093) [INFO] packages for the previous distribution release still work). * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-16 02:17:18 (4093) [INFO] yum --disablerepo= ... * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-16 02:17:18 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-16 02:17:18 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] yum-config-manager --disable * 2023-02-16 02:17:18 (4093) [INFO] or * 2023-02-16 02:17:18 (4093) [INFO] subscription-manager repos --disable= * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-16 02:17:18 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-16 02:17:18 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-16 02:17:18 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-16 02:17:18 (4093) [INFO] compromise: * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-16 02:17:18 (4093) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-16 02:17:18 (4110) [INFO] * 2023-02-16 02:17:18 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-16 02:17:18 (3589) [INFO] Checking /scripts/sysup * 2023-02-16 02:17:18 (4078) [INFO] Running: /scripts/sysup * 2023-02-16 02:17:18 (4079) [INFO] * 2023-02-16 02:17:18 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-16 02:17:22 (4093) [INFO] All Needed Packages are already installed. * 2023-02-16 02:17:22 (4110) [INFO] * 2023-02-16 02:17:22 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-16 02:17:22 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-16 02:17:22 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VvVq74yemB/ea_profile.json * 2023-02-16 02:20:55 (1694) [INFO] Backed up EA4 profile to /tmp/VvVq74yemB/ea_profile.json * 2023-02-16 02:20:55 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-16 02:24:58 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-17 01:53:40 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-17 01:53:44 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-17 01:53:44 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-17 01:56:30 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-17 01:56:30 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-17 01:56:31 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-17 01:56:31 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-17 01:56:31 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-17 01:56:31 (3566) [INFO] Checking if your system is up to date: * 2023-02-17 01:56:31 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-17 01:56:31 (4079) [INFO] * 2023-02-17 01:56:31 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-17 01:56:32 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-17 01:56:32 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-17 01:56:32 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-17 01:56:32 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-17 01:56:32 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-17 01:56:32 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-17 01:56:32 (4110) [INFO] * 2023-02-17 01:56:32 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-17 01:56:32 (4079) [INFO] * 2023-02-17 02:00:48 (4093) [INFO] * 2023-02-17 02:00:48 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-17 02:00:48 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-17 02:00:49 (4110) [INFO] * 2023-02-17 02:00:49 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-17 02:00:49 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-17 02:00:49 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-17 02:00:49 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-17 02:00:49 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UGhJls06hV/ea_profile.json * 2023-02-17 02:00:52 (1694) [INFO] Backed up EA4 profile to /tmp/UGhJls06hV/ea_profile.json * 2023-02-17 02:00:52 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-17 02:04:55 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-18 01:47:59 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-18 01:48:04 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-18 01:48:04 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-18 01:51:56 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-18 01:51:56 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30535 milliseconds') * 2023-02-18 01:51:56 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-18 01:51:56 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-18 01:51:56 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-18 01:51:59 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-18 01:51:59 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-18 01:51:59 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-18 01:51:59 (3566) [INFO] Checking if your system is up to date: * 2023-02-18 01:51:59 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-18 01:51:59 (4079) [INFO] * 2023-02-18 01:52:00 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-18 01:52:00 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-18 01:52:00 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-18 01:52:00 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-18 01:52:00 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-18 01:52:01 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-18 01:52:01 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-18 01:52:01 (4110) [INFO] * 2023-02-18 01:52:01 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-18 01:52:01 (4079) [INFO] * 2023-02-18 01:56:38 (4093) [INFO] * 2023-02-18 01:56:38 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-18 01:56:38 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-18 01:56:39 (4110) [INFO] * 2023-02-18 01:56:39 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-18 01:56:39 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-18 01:56:39 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-18 01:56:39 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-18 01:56:39 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Of6EfQ3eod/ea_profile.json * 2023-02-18 01:56:41 (1694) [INFO] Backed up EA4 profile to /tmp/Of6EfQ3eod/ea_profile.json * 2023-02-18 01:56:41 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-18 02:00:45 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-19 01:54:02 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-19 01:54:09 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-19 01:54:09 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-19 01:56:54 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-19 01:56:54 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-19 01:56:55 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-19 01:56:55 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-19 01:56:55 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-19 01:56:55 (3566) [INFO] Checking if your system is up to date: * 2023-02-19 01:56:55 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-19 01:56:55 (4079) [INFO] * 2023-02-19 01:56:55 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-19 01:56:55 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-19 01:56:55 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-19 01:56:55 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-19 01:56:55 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-19 01:56:55 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-19 01:56:55 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-19 01:56:55 (4110) [INFO] * 2023-02-19 01:56:55 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-19 01:56:55 (4079) [INFO] * 2023-02-19 02:01:17 (4093) [INFO] * 2023-02-19 02:01:17 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-19 02:01:17 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-19 02:01:18 (4110) [INFO] * 2023-02-19 02:01:18 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-19 02:01:18 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-19 02:01:18 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-19 02:01:18 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-19 02:01:18 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zEJbrSNemP/ea_profile.json * 2023-02-19 02:01:22 (1694) [INFO] Backed up EA4 profile to /tmp/zEJbrSNemP/ea_profile.json * 2023-02-19 02:01:22 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-19 02:05:26 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-20 01:53:37 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-20 01:53:42 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-20 01:53:42 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-20 01:56:42 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-20 01:56:42 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-02-20 01:56:42 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-20 01:56:42 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-20 01:56:42 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-20 01:56:43 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-20 01:56:43 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-20 01:56:43 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-20 01:56:43 (3566) [INFO] Checking if your system is up to date: * 2023-02-20 01:56:43 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-20 01:56:43 (4079) [INFO] * 2023-02-20 01:56:43 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-20 01:56:44 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-20 01:56:44 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-20 01:56:44 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-20 01:56:44 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-20 01:56:44 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-20 01:56:44 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-20 01:56:44 (4110) [INFO] * 2023-02-20 01:56:44 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-20 01:56:44 (4079) [INFO] * 2023-02-20 02:01:01 (4093) [INFO] * 2023-02-20 02:01:01 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-20 02:01:01 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-20 02:01:01 (4110) [INFO] * 2023-02-20 02:01:01 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-20 02:01:01 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-20 02:01:01 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-20 02:01:01 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-20 02:01:01 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mmawvu6_N6/ea_profile.json * 2023-02-20 02:01:05 (1694) [INFO] Backed up EA4 profile to /tmp/mmawvu6_N6/ea_profile.json * 2023-02-20 02:01:05 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-20 02:05:07 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-21 01:52:32 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-21 01:52:37 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-21 01:52:37 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-21 01:55:24 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-21 01:55:24 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-21 01:55:25 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-21 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-21 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-21 01:55:25 (3566) [INFO] Checking if your system is up to date: * 2023-02-21 01:55:25 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-21 01:55:25 (4079) [INFO] * 2023-02-21 01:55:25 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-21 01:55:25 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-21 01:55:25 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-21 01:55:25 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-21 01:55:25 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-21 01:55:25 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-21 01:55:25 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-21 01:55:25 (4110) [INFO] * 2023-02-21 01:55:25 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-21 01:55:25 (4079) [INFO] * 2023-02-21 01:59:39 (4093) [INFO] * 2023-02-21 01:59:39 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-21 01:59:39 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-21 01:59:40 (4110) [INFO] * 2023-02-21 01:59:40 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-21 01:59:40 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-21 01:59:40 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-21 01:59:40 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-21 01:59:40 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nGZ1TLDukg/ea_profile.json * 2023-02-21 01:59:43 (1694) [INFO] Backed up EA4 profile to /tmp/nGZ1TLDukg/ea_profile.json * 2023-02-21 01:59:43 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-21 02:03:47 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-22 01:52:22 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-22 01:52:28 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-22 01:52:28 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-22 01:55:53 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-22 01:55:53 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2023-02-22 01:55:53 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-22 01:55:53 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-22 01:55:53 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-22 01:55:54 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-22 01:55:54 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-22 01:55:54 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-22 01:55:54 (3566) [INFO] Checking if your system is up to date: * 2023-02-22 01:55:54 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-22 01:55:54 (4079) [INFO] * 2023-02-22 01:55:54 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-22 01:55:55 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-22 01:55:55 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-22 01:55:55 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-22 01:55:55 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-22 01:55:55 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-22 01:55:55 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-22 01:55:55 (4110) [INFO] * 2023-02-22 01:55:55 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-22 01:55:55 (4079) [INFO] * 2023-02-22 01:59:47 (4093) [INFO] * 2023-02-22 01:59:47 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-22 01:59:47 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-22 01:59:47 (4110) [INFO] * 2023-02-22 01:59:47 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-22 01:59:47 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-22 01:59:47 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-22 01:59:47 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-22 01:59:47 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E4b1iATOtL/ea_profile.json * 2023-02-22 01:59:49 (1694) [INFO] Backed up EA4 profile to /tmp/E4b1iATOtL/ea_profile.json * 2023-02-22 01:59:49 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-22 02:03:53 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-23 01:52:50 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-23 01:52:55 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-23 01:52:55 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-23 01:55:24 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-23 01:55:24 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-23 01:55:25 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-23 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-23 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-23 01:55:25 (3566) [INFO] Checking if your system is up to date: * 2023-02-23 01:55:25 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-23 01:55:25 (4079) [INFO] * 2023-02-23 01:55:25 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-23 01:55:25 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-23 01:55:25 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-23 01:55:25 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-23 01:55:25 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-23 01:55:26 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-23 01:55:26 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-23 01:55:26 (4110) [INFO] * 2023-02-23 01:55:26 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-23 01:55:26 (4079) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-02-23 01:56:24 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-23 01:56:24 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-23 01:56:24 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-23 01:56:24 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-02-23 01:56:24 (4093) [INFO] packages for the previous distribution release still work). * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-23 01:56:24 (4093) [INFO] yum --disablerepo= ... * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-23 01:56:24 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-23 01:56:24 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] yum-config-manager --disable * 2023-02-23 01:56:24 (4093) [INFO] or * 2023-02-23 01:56:24 (4093) [INFO] subscription-manager repos --disable= * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-23 01:56:24 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-23 01:56:24 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-23 01:56:24 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-23 01:56:24 (4093) [INFO] compromise: * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-23 01:56:24 (4093) [INFO] * 2023-02-23 01:56:24 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-23 01:56:24 (4110) [INFO] * 2023-02-23 01:56:24 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-23 01:56:24 (3589) [INFO] Checking /scripts/sysup * 2023-02-23 01:56:24 (4078) [INFO] Running: /scripts/sysup * 2023-02-23 01:56:24 (4079) [INFO] * 2023-02-23 01:56:25 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-23 01:56:28 (4093) [INFO] All Needed Packages are already installed. * 2023-02-23 01:56:28 (4110) [INFO] * 2023-02-23 01:56:28 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-23 01:56:28 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-23 01:56:28 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R03kpiUW9g/ea_profile.json * 2023-02-23 02:00:40 (1694) [INFO] Backed up EA4 profile to /tmp/R03kpiUW9g/ea_profile.json * 2023-02-23 02:00: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-23 02:04:45 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-24 01:57:51 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-24 01:57:55 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-24 01:57:55 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-24 02:00:25 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-24 02:00:25 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-24 02:00:27 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-24 02:00:27 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-24 02:00:27 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-24 02:00:27 (3566) [INFO] Checking if your system is up to date: * 2023-02-24 02:00:27 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-24 02:00:27 (4079) [INFO] * 2023-02-24 02:00:27 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-24 02:00:28 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-24 02:00:28 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-24 02:00:28 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-24 02:00:28 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-24 02:00:28 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-24 02:00:28 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-24 02:00:28 (4110) [INFO] * 2023-02-24 02:00:28 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-24 02:00:28 (4079) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-02-24 02:01:26 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-02-24 02:01:26 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-02-24 02:01:26 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-02-24 02:01:26 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-02-24 02:01:26 (4093) [INFO] packages for the previous distribution release still work). * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-02-24 02:01:26 (4093) [INFO] yum --disablerepo= ... * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-02-24 02:01:26 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-02-24 02:01:26 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] yum-config-manager --disable * 2023-02-24 02:01:26 (4093) [INFO] or * 2023-02-24 02:01:26 (4093) [INFO] subscription-manager repos --disable= * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-02-24 02:01:26 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-02-24 02:01:26 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-02-24 02:01:26 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-02-24 02:01:26 (4093) [INFO] compromise: * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-02-24 02:01:26 (4093) [INFO] * 2023-02-24 02:01:26 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-02-24 02:01:26 (4110) [INFO] * 2023-02-24 02:01:26 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-24 02:01:26 (3589) [INFO] Checking /scripts/sysup * 2023-02-24 02:01:26 (4078) [INFO] Running: /scripts/sysup * 2023-02-24 02:01:26 (4079) [INFO] * 2023-02-24 02:01:27 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-02-24 02:01:31 (4093) [INFO] All Needed Packages are already installed. * 2023-02-24 02:01:31 (4110) [INFO] * 2023-02-24 02:01:31 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-24 02:01:31 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-24 02:01:31 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BI_UQwuMJB/ea_profile.json * 2023-02-24 02:05:55 (1694) [INFO] Backed up EA4 profile to /tmp/BI_UQwuMJB/ea_profile.json * 2023-02-24 02:05:55 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-24 02:09:57 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-25 01:55:32 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-25 01:55:38 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-25 01:55:38 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-25 01:58:39 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-02-25 01:58:39 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-02-25 01:58:39 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-02-25 01:58:39 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-25 01:58:39 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-25 01:58:40 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-25 01:58:40 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-25 01:58:40 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-25 01:58:40 (3566) [INFO] Checking if your system is up to date: * 2023-02-25 01:58:40 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-25 01:58:40 (4079) [INFO] * 2023-02-25 01:58:41 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-25 01:58:41 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-25 01:58:41 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-25 01:58:41 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-25 01:58:41 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-25 01:58:41 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-25 01:58:41 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-25 01:58:41 (4110) [INFO] * 2023-02-25 01:58:41 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-25 01:58:41 (4079) [INFO] * 2023-02-25 02:03:07 (4093) [INFO] * 2023-02-25 02:03:07 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-25 02:03:07 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-25 02:03:08 (4110) [INFO] * 2023-02-25 02:03:08 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-25 02:03:08 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-25 02:03:08 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-25 02:03:08 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-25 02:03:08 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z2LLqtKRYP/ea_profile.json * 2023-02-25 02:03:13 (1694) [INFO] Backed up EA4 profile to /tmp/Z2LLqtKRYP/ea_profile.json * 2023-02-25 02:03:13 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-25 02:07:16 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-26 01:54:27 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-26 01:54:32 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-26 01:54:32 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-26 01:57:16 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-26 01:57:16 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-26 01:57:17 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-26 01:57:17 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-26 01:57:17 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-26 01:57:17 (3566) [INFO] Checking if your system is up to date: * 2023-02-26 01:57:17 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-26 01:57:17 (4079) [INFO] * 2023-02-26 01:57:18 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-26 01:57:18 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-26 01:57:18 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-26 01:57:18 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-26 01:57:18 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-26 01:57:18 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-26 01:57:18 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-26 01:57:18 (4110) [INFO] * 2023-02-26 01:57:18 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-26 01:57:18 (4079) [INFO] * 2023-02-26 02:01:29 (4093) [INFO] * 2023-02-26 02:01:29 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-26 02:01:29 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-26 02:01:29 (4110) [INFO] * 2023-02-26 02:01:29 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-26 02:01:29 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-26 02:01:29 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-26 02:01:29 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-26 02:01:29 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rBTTgqxG9i/ea_profile.json * 2023-02-26 02:01:33 (1694) [INFO] Backed up EA4 profile to /tmp/rBTTgqxG9i/ea_profile.json * 2023-02-26 02:01: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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-26 02:05:36 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-27 01:48:33 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-27 01:48:38 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-27 01:48:38 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-27 01:51:54 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-27 01:51:54 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-27 01:51:57 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-27 01:51:57 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-27 01:51:57 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-27 01:51:57 (3566) [INFO] Checking if your system is up to date: * 2023-02-27 01:51:57 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-27 01:51:57 (4079) [INFO] * 2023-02-27 01:51:57 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-27 01:51:57 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-27 01:51:57 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-27 01:51:57 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-27 01:51:57 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-27 01:51:58 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-27 01:51:58 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-27 01:51:58 (4110) [INFO] * 2023-02-27 01:51:58 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-27 01:51:58 (4079) [INFO] * 2023-02-27 01:56:19 (4093) [INFO] * 2023-02-27 01:56:19 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-27 01:56:19 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-27 01:56:19 (4110) [INFO] * 2023-02-27 01:56:19 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-27 01:56:19 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-27 01:56:19 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-27 01:56:19 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-27 01:56:19 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HJZvexrfUs/ea_profile.json * 2023-02-27 01:56:24 (1694) [INFO] Backed up EA4 profile to /tmp/HJZvexrfUs/ea_profile.json * 2023-02-27 01:56:24 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-27 02:00:28 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-02-28 01:51:33 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-02-28 01:51:37 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-02-28 01:51:37 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-02-28 01:57:19 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-02-28 01:57:19 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-02-28 01:57:22 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-02-28 01:57:22 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-02-28 01:57:22 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-02-28 01:57:22 (3566) [INFO] Checking if your system is up to date: * 2023-02-28 01:57:22 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-02-28 01:57:22 (4079) [INFO] * 2023-02-28 01:57:22 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-02-28 01:57:23 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-02-28 01:57:23 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-02-28 01:57:23 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-02-28 01:57:23 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-02-28 01:57:23 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-02-28 01:57:23 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-02-28 01:57:23 (4110) [INFO] * 2023-02-28 01:57:23 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-02-28 01:57:23 (4079) [INFO] * 2023-02-28 02:01:11 (4093) [INFO] * 2023-02-28 02:01:11 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-02-28 02:01:11 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-02-28 02:01:11 (4110) [INFO] * 2023-02-28 02:01:11 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-02-28 02:01:11 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-02-28 02:01:11 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-02-28 02:01:11 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-02-28 02:01:11 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CtEmLaS7jR/ea_profile.json * 2023-02-28 02:01:13 (1694) [INFO] Backed up EA4 profile to /tmp/CtEmLaS7jR/ea_profile.json * 2023-02-28 02:01:13 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-02-28 02:05:16 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-01 02:01:25 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-01 02:01:31 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-01 02:01:31 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-01 02:04:19 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-01 02:04:19 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-01 02:04:20 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-01 02:04:20 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-01 02:04:20 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-01 02:04:20 (3566) [INFO] Checking if your system is up to date: * 2023-03-01 02:04:20 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-01 02:04:20 (4079) [INFO] * 2023-03-01 02:04:21 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-01 02:04:21 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-01 02:04:21 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-01 02:04:21 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-01 02:04:21 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-01 02:04:21 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-01 02:04:21 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-01 02:04:21 (4110) [INFO] * 2023-03-01 02:04:21 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-01 02:04:21 (4079) [INFO] * 2023-03-01 02:08:26 (4093) [INFO] * 2023-03-01 02:08:26 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-03-01 02:08:26 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-01 02:08:26 (4110) [INFO] * 2023-03-01 02:08:27 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-01 02:08:27 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-01 02:08:27 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-01 02:08:27 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-01 02:08:27 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b5Mqoj3Jai/ea_profile.json * 2023-03-01 02:08:30 (1694) [INFO] Backed up EA4 profile to /tmp/b5Mqoj3Jai/ea_profile.json * 2023-03-01 02:08:30 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-01 02:12:33 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-02 01:50:01 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-02 01:50:07 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-02 01:50:07 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-02 01:53:23 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-02 01:53:23 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-02 01:53:24 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-02 01:53:24 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-02 01:53:24 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-02 01:53:24 (3566) [INFO] Checking if your system is up to date: * 2023-03-02 01:53:24 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-02 01:53:24 (4079) [INFO] * 2023-03-02 01:53:25 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-02 01:53:25 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-02 01:53:25 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-02 01:53:25 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-02 01:53:25 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-02 01:53:25 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-02 01:53:25 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-02 01:53:25 (4110) [INFO] * 2023-03-02 01:53:25 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-02 01:53:25 (4079) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-03-02 01:54:21 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-02 01:54:21 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-02 01:54:21 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-02 01:54:21 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-03-02 01:54:21 (4093) [INFO] packages for the previous distribution release still work). * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-02 01:54:21 (4093) [INFO] yum --disablerepo= ... * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-02 01:54:21 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-02 01:54:21 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] yum-config-manager --disable * 2023-03-02 01:54:21 (4093) [INFO] or * 2023-03-02 01:54:21 (4093) [INFO] subscription-manager repos --disable= * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-02 01:54:21 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-02 01:54:21 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-02 01:54:21 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-02 01:54:21 (4093) [INFO] compromise: * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-02 01:54:21 (4093) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-02 01:54:21 (4110) [INFO] * 2023-03-02 01:54:21 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-02 01:54:21 (3589) [INFO] Checking /scripts/sysup * 2023-03-02 01:54:21 (4078) [INFO] Running: /scripts/sysup * 2023-03-02 01:54:21 (4079) [INFO] * 2023-03-02 01:54:21 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-02 01:54:25 (4093) [INFO] All Needed Packages are already installed. * 2023-03-02 01:54:25 (4110) [INFO] * 2023-03-02 01:54:25 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-02 01:54:25 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-02 01:54:25 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5vMrIBJMCP/ea_profile.json * 2023-03-02 01:55:55 (2716) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5vMrIBJMCP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1671. * 2023-03-02 01:55:55 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-03 01:51:12 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-03 01:51:16 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-03 01:51:16 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-03 01:54:00 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-03 01:54:00 (3734) [ERROR] http://centos.mirror.shastacoe.net/centos/7.9.2009/updates/x86_64/repodata/98876002d3a172ed7c6e3e2e4a81199ee54e93ad062450e0916abaad7954d49d-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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-03-03 01:54:00 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-03 01:54:00 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-03 01:54:00 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-03 01:54:01 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-03 01:54:01 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-03 01:54:01 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-03 01:54:01 (3566) [INFO] Checking if your system is up to date: * 2023-03-03 01:54:01 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-03 01:54:01 (4079) [INFO] * 2023-03-03 01:54:02 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-03 01:54:02 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-03 01:54:02 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-03 01:54:02 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-03 01:54:02 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-03 01:54:03 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-03 01:54:03 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-03 01:54:03 (4110) [INFO] * 2023-03-03 01:54:03 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-03 01:54:03 (4079) [INFO] * 2023-03-03 01:58:08 (4093) [INFO] * 2023-03-03 01:58:08 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-03-03 01:58:08 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-03 01:58:08 (4110) [INFO] * 2023-03-03 01:58:08 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-03 01:58:08 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-03 01:58:08 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-03 01:58:08 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-03 01:58:08 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4o4VyVqKo0/ea_profile.json * 2023-03-03 01:58:12 (1694) [INFO] Backed up EA4 profile to /tmp/4o4VyVqKo0/ea_profile.json * 2023-03-03 01:58:12 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-03 02:02:17 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-04 01:56:54 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-04 01:57:03 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-04 01:57:03 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-04 01:59:34 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-04 01:59:34 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-04 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-04 01:59:34 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-04 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-04 01:59:34 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-04 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-04 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-04 01:59:34 (3566) [INFO] Checking if your system is up to date: * 2023-03-04 01:59:34 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-04 01:59:34 (4079) [INFO] * 2023-03-04 01:59:35 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-04 01:59:35 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-04 01:59:35 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-04 01:59:35 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-04 01:59:35 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-04 01:59:35 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-04 01:59:35 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-04 01:59:35 (4110) [INFO] * 2023-03-04 01:59:35 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-04 01:59:35 (4079) [INFO] * 2023-03-04 02:03:41 (4093) [INFO] * 2023-03-04 02:03:41 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-03-04 02:03:41 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-04 02:03:41 (4110) [INFO] * 2023-03-04 02:03:41 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-04 02:03:41 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-04 02:03:41 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-04 02:03:41 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-04 02:03:41 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tt6aojKdPt/ea_profile.json * 2023-03-04 02:03:48 (1694) [INFO] Backed up EA4 profile to /tmp/tt6aojKdPt/ea_profile.json * 2023-03-04 02:03:48 (2749) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-04 02:07:51 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-05 01:53:31 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-05 01:53:37 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-05 01:53:37 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-05 01:56:05 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-05 01:56:05 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-05 01:56:06 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-05 01:56:06 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-05 01:56:06 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-05 01:56:06 (3566) [INFO] Checking if your system is up to date: * 2023-03-05 01:56:06 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-05 01:56:06 (4079) [INFO] * 2023-03-05 01:56:07 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-05 01:56:07 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-05 01:56:07 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-05 01:56:07 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-05 01:56:07 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-05 01:56:07 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-05 01:56:07 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-05 01:56:08 (4110) [INFO] * 2023-03-05 01:56:08 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-05 01:56:08 (4079) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-03-05 01:57:03 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-05 01:57:03 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-05 01:57:03 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-05 01:57:03 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-03-05 01:57:03 (4093) [INFO] packages for the previous distribution release still work). * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-05 01:57:03 (4093) [INFO] yum --disablerepo= ... * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-05 01:57:03 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-05 01:57:03 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] yum-config-manager --disable * 2023-03-05 01:57:03 (4093) [INFO] or * 2023-03-05 01:57:03 (4093) [INFO] subscription-manager repos --disable= * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-05 01:57:03 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-05 01:57:03 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-05 01:57:03 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-05 01:57:03 (4093) [INFO] compromise: * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-05 01:57:03 (4093) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-05 01:57:03 (4110) [INFO] * 2023-03-05 01:57:03 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-05 01:57:03 (3589) [INFO] Checking /scripts/sysup * 2023-03-05 01:57:03 (4078) [INFO] Running: /scripts/sysup * 2023-03-05 01:57:03 (4079) [INFO] * 2023-03-05 01:57:03 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-05 01:57:07 (4093) [INFO] All Needed Packages are already installed. * 2023-03-05 01:57:07 (4110) [INFO] * 2023-03-05 01:57:07 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-05 01:57:07 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-05 01:57:07 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OCgTj0ZHQW/ea_profile.json * 2023-03-05 02:01:24 (1694) [INFO] Backed up EA4 profile to /tmp/OCgTj0ZHQW/ea_profile.json * 2023-03-05 02:01:24 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-05 02:05:28 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-06 01:53:01 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-06 01:53:06 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-06 01:53:06 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-06 01:55:50 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-06 01:55:50 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-06 01:55:52 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-06 01:55:52 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-06 01:55:52 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-06 01:55:52 (3566) [INFO] Checking if your system is up to date: * 2023-03-06 01:55:52 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-06 01:55:52 (4079) [INFO] * 2023-03-06 01:55:52 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-06 01:55:53 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-06 01:55:53 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-06 01:55:53 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-06 01:55:53 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-06 01:55:53 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-06 01:55:53 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-06 01:55:53 (4110) [INFO] * 2023-03-06 01:55:53 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-06 01:55:53 (4079) [INFO] * 2023-03-06 01:59:55 (4093) [INFO] * 2023-03-06 01:59:55 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-03-06 01:59:55 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-06 01:59:55 (4110) [INFO] * 2023-03-06 01:59:55 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-06 01:59:55 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-06 01:59:55 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-06 01:59:55 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-06 01:59:55 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/G1NYlb2OJm/ea_profile.json * 2023-03-06 01:59:59 (1694) [INFO] Backed up EA4 profile to /tmp/G1NYlb2OJm/ea_profile.json * 2023-03-06 01:59:59 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-06 02:04:02 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-07 01:56:30 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-07 01:56:35 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-07 01:56:35 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-07 01:59:19 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-07 01:59:19 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-07 01:59:21 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-07 01:59:21 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-07 01:59:21 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-07 01:59:21 (3566) [INFO] Checking if your system is up to date: * 2023-03-07 01:59:21 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-07 01:59:21 (4079) [INFO] * 2023-03-07 01:59:21 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-07 01:59:22 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-07 01:59:22 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-07 01:59:22 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-07 01:59:22 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-07 01:59:22 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-07 01:59:22 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-07 01:59:22 (4110) [INFO] * 2023-03-07 01:59:22 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-07 01:59:22 (4079) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-03-07 02:00:18 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-07 02:00:18 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-07 02:00:18 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-07 02:00:18 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-03-07 02:00:18 (4093) [INFO] packages for the previous distribution release still work). * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-07 02:00:18 (4093) [INFO] yum --disablerepo= ... * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-07 02:00:18 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-07 02:00:18 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] yum-config-manager --disable * 2023-03-07 02:00:18 (4093) [INFO] or * 2023-03-07 02:00:18 (4093) [INFO] subscription-manager repos --disable= * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-07 02:00:18 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-07 02:00:18 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-07 02:00:18 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-07 02:00:18 (4093) [INFO] compromise: * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-07 02:00:18 (4093) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-07 02:00:18 (4110) [INFO] * 2023-03-07 02:00:18 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-07 02:00:18 (3589) [INFO] Checking /scripts/sysup * 2023-03-07 02:00:18 (4078) [INFO] Running: /scripts/sysup * 2023-03-07 02:00:18 (4079) [INFO] * 2023-03-07 02:00:18 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-07 02:00:23 (4093) [INFO] All Needed Packages are already installed. * 2023-03-07 02:00:23 (4110) [INFO] * 2023-03-07 02:00:23 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-07 02:00:23 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-07 02:00:23 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aLKA4cz7Ii/ea_profile.json * 2023-03-07 02:05:29 (1694) [INFO] Backed up EA4 profile to /tmp/aLKA4cz7Ii/ea_profile.json * 2023-03-07 02:05:29 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-07 02:09:31 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-08 01:50:59 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-08 01:51:05 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-08 01:51:05 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-08 01:53:51 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-08 01:53:51 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30543 milliseconds') * 2023-03-08 01:53:51 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-08 01:53:51 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-08 01:53:51 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-08 01:53:52 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-08 01:53:52 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-08 01:53:52 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-08 01:53:52 (3566) [INFO] Checking if your system is up to date: * 2023-03-08 01:53:52 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-08 01:53:52 (4079) [INFO] * 2023-03-08 01:53:52 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-08 01:53:53 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-08 01:53:53 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-08 01:53:53 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-08 01:53:53 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-08 01:53:53 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-08 01:53:53 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-08 01:53:53 (4110) [INFO] * 2023-03-08 01:53:53 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-08 01:53:53 (4079) [INFO] * 2023-03-08 01:57:40 (4093) [INFO] * 2023-03-08 01:57:40 (4093) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 2023-03-08 01:57:40 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-08 01:57:40 (4110) [INFO] * 2023-03-08 01:57:40 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-08 01:57:40 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-08 01:57:40 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-08 01:57:40 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-08 01:57:40 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dGFdFM0R3i/ea_profile.json * 2023-03-08 01:57:45 (1694) [INFO] Backed up EA4 profile to /tmp/dGFdFM0R3i/ea_profile.json * 2023-03-08 01:57:45 (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-openssl-devel - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-08 02:01:47 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-09 01:48:35 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-09 01:48:38 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-09 01:48:38 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-09 01:53:38 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-09 01:53:38 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-09 01:53:41 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-09 01:53:41 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-09 01:53:41 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-09 01:53:41 (3566) [INFO] Checking if your system is up to date: * 2023-03-09 01:53:41 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-09 01:53:41 (4079) [INFO] * 2023-03-09 01:53:42 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-09 01:53:43 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-09 01:53:43 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-09 01:53:43 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-09 01:53:43 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-09 01:53:43 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-09 01:53:43 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-09 01:53:43 (4110) [INFO] * 2023-03-09 01:53:43 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-09 01:53:43 (4079) [INFO] * 2023-03-09 01:57:34 (4093) [INFO] * 2023-03-09 01:57:34 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-09 01:57:34 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-09 01:57:34 (4110) [INFO] * 2023-03-09 01:57:34 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-09 01:57:34 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-09 01:57:34 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-09 01:57:34 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-09 01:57:34 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dLUGDW3ezn/ea_profile.json * 2023-03-09 01:57:37 (1694) [INFO] Backed up EA4 profile to /tmp/dLUGDW3ezn/ea_profile.json * 2023-03-09 01:57:37 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-09 02:01:41 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-10 01:54:42 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-10 01:54:47 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-10 01:54:47 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-10 01:57:16 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-10 01:57:16 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-10 01:57:16 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-10 01:57:16 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-10 01:57:16 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-10 01:57:17 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-10 01:57:17 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-10 01:57:17 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-10 01:57:17 (3566) [INFO] Checking if your system is up to date: * 2023-03-10 01:57:17 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-10 01:57:17 (4079) [INFO] * 2023-03-10 01:57:18 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-10 01:57:18 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-10 01:57:18 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-10 01:57:18 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-10 01:57:18 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-10 01:57:18 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-10 01:57:18 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-10 01:57:18 (4110) [INFO] * 2023-03-10 01:57:18 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-10 01:57:18 (4079) [INFO] * 2023-03-10 02:01:16 (4093) [INFO] * 2023-03-10 02:01:16 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-10 02:01:16 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-10 02:01:16 (4110) [INFO] * 2023-03-10 02:01:16 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-10 02:01:16 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-10 02:01:16 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-10 02:01:16 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-10 02:01:16 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OAaKQvuBgN/ea_profile.json * 2023-03-10 02:01:30 (1694) [INFO] Backed up EA4 profile to /tmp/OAaKQvuBgN/ea_profile.json * 2023-03-10 02:01:30 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-10 02:05:38 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-11 01:53:36 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-11 01:53:40 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-11 01:53:40 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-11 01:56:10 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-11 01:56:10 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30298 milliseconds') * 2023-03-11 01:56:10 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-11 01:56:10 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-11 01:56:10 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-11 01:56:11 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-11 01:56:11 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-11 01:56:11 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-11 01:56:11 (3566) [INFO] Checking if your system is up to date: * 2023-03-11 01:56:11 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-11 01:56:11 (4079) [INFO] * 2023-03-11 01:56:12 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-11 01:56:12 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-11 01:56:12 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-11 01:56:12 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-11 01:56:12 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-11 01:56:13 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-11 01:56:13 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-11 01:56:13 (4110) [INFO] * 2023-03-11 01:56:13 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-11 01:56:13 (4079) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] One of the configured repositories failed (Unknown), * 2023-03-11 01:57:08 (4093) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-11 01:57:08 (4093) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-11 01:57:08 (4093) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-11 01:57:08 (4093) [INFO] distribution release than is supported by the repository (and the * 2023-03-11 01:57:08 (4093) [INFO] packages for the previous distribution release still work). * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-11 01:57:08 (4093) [INFO] yum --disablerepo= ... * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-11 01:57:08 (4093) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-11 01:57:08 (4093) [INFO] again or use --enablerepo for temporary usage: * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] yum-config-manager --disable * 2023-03-11 01:57:08 (4093) [INFO] or * 2023-03-11 01:57:08 (4093) [INFO] subscription-manager repos --disable= * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-11 01:57:08 (4093) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-11 01:57:08 (4093) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-11 01:57:08 (4093) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-11 01:57:08 (4093) [INFO] compromise: * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-11 01:57:08 (4093) [INFO] * 2023-03-11 01:57:08 (4093) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-11 01:57:08 (4110) [INFO] * 2023-03-11 01:57:08 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-11 01:57:08 (3589) [INFO] Checking /scripts/sysup * 2023-03-11 01:57:08 (4078) [INFO] Running: /scripts/sysup * 2023-03-11 01:57:08 (4079) [INFO] * 2023-03-11 01:57:09 (4093) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-11 01:57:13 (4093) [INFO] All Needed Packages are already installed. * 2023-03-11 01:57:13 (4110) [INFO] * 2023-03-11 01:57:13 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-11 01:57:13 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-11 01:57:13 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WhqOvXbU7f/ea_profile.json * 2023-03-11 02:01:38 (1694) [INFO] Backed up EA4 profile to /tmp/WhqOvXbU7f/ea_profile.json * 2023-03-11 02:01:38 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-11 02:05:43 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-12 01:52:35 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-12 01:52:40 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-12 01:52:40 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-12 01:55:25 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-12 01:55:25 (3734) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-12 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-12 01:55:25 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-12 01:55:25 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-12 01:55:26 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-12 01:55:26 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-12 01:55:26 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-12 01:55:26 (3566) [INFO] Checking if your system is up to date: * 2023-03-12 01:55:26 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-12 01:55:26 (4079) [INFO] * 2023-03-12 01:55:27 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-12 01:55:27 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-12 01:55:27 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-12 01:55:27 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-12 01:55:27 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-12 01:55:27 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-12 01:55:27 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-12 01:55:27 (4110) [INFO] * 2023-03-12 01:55:27 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-12 01:55:27 (4079) [INFO] * 2023-03-12 01:59:34 (4093) [INFO] * 2023-03-12 01:59:34 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-12 01:59:34 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-12 01:59:34 (4110) [INFO] * 2023-03-12 01:59:34 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-12 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-12 01:59:34 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-12 01:59:34 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-12 01:59:34 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DquCYG5ZAb/ea_profile.json * 2023-03-12 01:59:36 (1694) [INFO] Backed up EA4 profile to /tmp/DquCYG5ZAb/ea_profile.json * 2023-03-12 01:59:36 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-12 03:03:44 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-13 01:50:36 (2749) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-13 01:50:40 (3675) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-13 01:50:40 (2749) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-13 01:53:12 (3760) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-13 01:53:12 (2749) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-13 01:53:13 (3603) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-13 01:53:13 (2749) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-13 01:53:13 (2749) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-13 01:53:13 (3566) [INFO] Checking if your system is up to date: * 2023-03-13 01:53:13 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-13 01:53:13 (4079) [INFO] * 2023-03-13 01:53:14 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-13 01:53:14 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-13 01:53:14 (4093) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-13 01:53:14 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-13 01:53:14 (4093) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-13 01:53:14 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-13 01:53:14 (4093) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-13 01:53:14 (4110) [INFO] * 2023-03-13 01:53:14 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-13 01:53:14 (4079) [INFO] * 2023-03-13 01:57:26 (4093) [INFO] * 2023-03-13 01:57:26 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-13 01:57:26 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-13 01:57:27 (4110) [INFO] * 2023-03-13 01:57:27 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-13 01:57:27 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-13 01:57:27 (2749) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-13 01:57:27 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-13 01:57:27 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1Jx1ZdQHk4/ea_profile.json * 2023-03-13 01:57:29 (1694) [INFO] Backed up EA4 profile to /tmp/1Jx1ZdQHk4/ea_profile.json * 2023-03-13 01:57:29 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-13 02:01:32 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-14 01:52:21 (368) [INFO] Self-update of script version 5 requested. * 2023-03-14 01:56:22 (373) [INFO] Newer version of script found. Downloading. * 2023-03-14 02:00:23 (382) [INFO] Script update to version 6 successful. * 2023-03-14 02:00:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-03-14 02:00:27 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-14 02:00:31 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-14 02:00:31 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-14 02:03:03 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-14 02:03:03 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30234 milliseconds with 0 out of 0 bytes received') * 2023-03-14 02:03:03 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-14 02:03:03 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-14 02:03:03 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-14 02:03:05 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-14 02:03:05 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-14 02:03:05 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-14 02:03:05 (3638) [INFO] Checking if your system is up to date: * 2023-03-14 02:03:05 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-14 02:03:05 (4151) [INFO] * 2023-03-14 02:03:06 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-14 02:03:06 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-14 02:03:06 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-14 02:03:06 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-14 02:03:06 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-14 02:03:06 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-14 02:03:06 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-14 02:03:06 (4182) [INFO] * 2023-03-14 02:03:06 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-14 02:03:06 (4151) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-14 02:04:00 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-14 02:04:00 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-14 02:04:00 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-14 02:04:00 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-14 02:04:00 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-14 02:04:00 (4165) [INFO] yum --disablerepo= ... * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-14 02:04:00 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-14 02:04:00 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] yum-config-manager --disable * 2023-03-14 02:04:00 (4165) [INFO] or * 2023-03-14 02:04:00 (4165) [INFO] subscription-manager repos --disable= * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-14 02:04:00 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-14 02:04:00 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-14 02:04:00 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-14 02:04:00 (4165) [INFO] compromise: * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-14 02:04:00 (4165) [INFO] * 2023-03-14 02:04:00 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-14 02:04:00 (4182) [INFO] * 2023-03-14 02:04:00 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-14 02:04:00 (3661) [INFO] Checking /scripts/sysup * 2023-03-14 02:04:00 (4150) [INFO] Running: /scripts/sysup * 2023-03-14 02:04:00 (4151) [INFO] * 2023-03-14 02:04:01 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-14 02:04:06 (4165) [INFO] All Needed Packages are already installed. * 2023-03-14 02:04:07 (4182) [INFO] * 2023-03-14 02:04:07 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-14 02:04:07 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-14 02:04:07 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oGR4R5kVAZ/ea_profile.json * 2023-03-14 02:08:14 (1765) [INFO] Backed up EA4 profile to /tmp/oGR4R5kVAZ/ea_profile.json * 2023-03-14 02:08:14 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-14 02:12:17 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-15 00:52:36 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-15 00:52:41 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-15 00:52:41 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-15 00:55:36 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-15 00:55:36 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-15 00:55:37 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-15 00:55:37 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-15 00:55:37 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-15 00:55:37 (3638) [INFO] Checking if your system is up to date: * 2023-03-15 00:55:37 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-15 00:55:37 (4151) [INFO] * 2023-03-15 00:55:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-15 00:55:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-15 00:55:37 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-15 00:55:37 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-15 00:55:37 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-15 00:55:38 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-15 00:55:38 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-15 00:55:38 (4182) [INFO] * 2023-03-15 00:55:38 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-15 00:55:38 (4151) [INFO] * 2023-03-15 00:59:27 (4165) [INFO] * 2023-03-15 00:59:27 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-15 00:59:27 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-15 00:59:27 (4182) [INFO] * 2023-03-15 00:59:27 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-15 00:59:27 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-15 00:59:27 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-15 00:59:27 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-15 00:59:27 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/irxDjQdzRb/ea_profile.json * 2023-03-15 00:59:29 (1765) [INFO] Backed up EA4 profile to /tmp/irxDjQdzRb/ea_profile.json * 2023-03-15 00:59: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-15 01:03:33 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-16 01:50:46 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-16 01:50:49 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-16 01:50:49 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-16 01:53:02 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-16 01:53:02 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-16 01:53:02 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-16 01:53:02 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-16 01:53:02 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-16 01:53:03 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-16 01:53:03 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-16 01:53:03 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-16 01:53:03 (3638) [INFO] Checking if your system is up to date: * 2023-03-16 01:53:03 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-16 01:53:03 (4151) [INFO] * 2023-03-16 01:53:03 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-16 01:53:03 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-16 01:53:03 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-16 01:53:03 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-16 01:53:03 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-16 01:53:04 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-16 01:53:04 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-16 01:53:04 (4182) [INFO] * 2023-03-16 01:53:04 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-16 01:53:04 (4151) [INFO] * 2023-03-16 01:56:39 (4165) [INFO] * 2023-03-16 01:56:39 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-16 01:56:39 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-16 01:56:39 (4182) [INFO] * 2023-03-16 01:56:39 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-16 01:56:39 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-16 01:56:39 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-16 01:56:39 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-16 01:56:39 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0dQc1_EaCV/ea_profile.json * 2023-03-16 01:56:43 (1765) [INFO] Backed up EA4 profile to /tmp/0dQc1_EaCV/ea_profile.json * 2023-03-16 01:56:43 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-16 02:00:45 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-17 01:52:32 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-17 01:52:36 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-17 01:52:36 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-17 01:55:36 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-17 01:55:36 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-17 01:55:36 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-17 01:55:36 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-17 01:55:36 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-17 01:55:36 (3638) [INFO] Checking if your system is up to date: * 2023-03-17 01:55:36 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-17 01:55:36 (4151) [INFO] * 2023-03-17 01:55:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-17 01:55:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-17 01:55:37 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-17 01:55:37 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-17 01:55:37 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-17 01:55:37 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-17 01:55:37 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-17 01:55:37 (4182) [INFO] * 2023-03-17 01:55:37 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-17 01:55:37 (4151) [INFO] * 2023-03-17 01:59:56 (4165) [INFO] * 2023-03-17 01:59:56 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-17 01:59:56 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-17 01:59:56 (4182) [INFO] * 2023-03-17 01:59:56 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-17 01:59:56 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-17 01:59:56 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-17 01:59:56 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-17 01:59:56 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dzoV8oi9ab/ea_profile.json * 2023-03-17 01:59:59 (1765) [INFO] Backed up EA4 profile to /tmp/dzoV8oi9ab/ea_profile.json * 2023-03-17 01:59:59 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-17 02:04:04 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-18 01:47:31 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-18 01:47:37 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-18 01:47:37 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-18 01:53:17 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-18 01:53:17 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-18 01:53:24 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-18 01:53:24 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-18 01:53:24 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-18 01:53:24 (3638) [INFO] Checking if your system is up to date: * 2023-03-18 01:53:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-18 01:53:24 (4151) [INFO] * 2023-03-18 01:53:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-18 01:53:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-18 01:53:25 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-18 01:53:25 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-18 01:53:25 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-18 01:53:25 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-18 01:53:25 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-18 01:53:26 (4182) [INFO] * 2023-03-18 01:53:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-18 01:53:26 (4151) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-18 01:54:21 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-18 01:54:21 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-18 01:54:21 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-18 01:54:21 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-18 01:54:21 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-18 01:54:21 (4165) [INFO] yum --disablerepo= ... * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-18 01:54:21 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-18 01:54:21 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] yum-config-manager --disable * 2023-03-18 01:54:21 (4165) [INFO] or * 2023-03-18 01:54:21 (4165) [INFO] subscription-manager repos --disable= * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-18 01:54:21 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-18 01:54:21 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-18 01:54:21 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-18 01:54:21 (4165) [INFO] compromise: * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-18 01:54:21 (4165) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-18 01:54:21 (4182) [INFO] * 2023-03-18 01:54:21 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-18 01:54:21 (3661) [INFO] Checking /scripts/sysup * 2023-03-18 01:54:21 (4150) [INFO] Running: /scripts/sysup * 2023-03-18 01:54:21 (4151) [INFO] * 2023-03-18 01:54:21 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-18 01:54:25 (4165) [INFO] All Needed Packages are already installed. * 2023-03-18 01:54:25 (4182) [INFO] * 2023-03-18 01:54:25 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-18 01:54:25 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-18 01:54:25 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mTkH6v9v0O/ea_profile.json * 2023-03-18 01:58:42 (1765) [INFO] Backed up EA4 profile to /tmp/mTkH6v9v0O/ea_profile.json * 2023-03-18 01:58: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-18 02:02:49 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-19 01:53:49 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-19 01:53:54 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-19 01:53:54 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-19 01:56:35 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-19 01:56:35 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-19 01:56:36 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-19 01:56:36 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-19 01:56:36 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-19 01:56:36 (3638) [INFO] Checking if your system is up to date: * 2023-03-19 01:56:36 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-19 01:56:36 (4151) [INFO] * 2023-03-19 01:56:36 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-19 01:56:36 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-19 01:56:36 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-19 01:56:36 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-19 01:56:36 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-19 01:56:37 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-19 01:56:37 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-19 01:56:37 (4182) [INFO] * 2023-03-19 01:56:37 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-19 01:56:37 (4151) [INFO] * 2023-03-19 02:00:37 (4165) [INFO] * 2023-03-19 02:00:37 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-19 02:00:37 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-19 02:00:37 (4182) [INFO] * 2023-03-19 02:00:37 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-19 02:00:37 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-19 02:00:37 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-19 02:00:37 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-19 02:00:37 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j1uxwqlX2_/ea_profile.json * 2023-03-19 02:00:40 (1765) [INFO] Backed up EA4 profile to /tmp/j1uxwqlX2_/ea_profile.json * 2023-03-19 02:00: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-19 02:04:43 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-20 01:48:37 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-20 01:48:42 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-20 01:48:42 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-20 01:51:35 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-20 01:51:35 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-20 01:51:37 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-20 01:51:37 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-20 01:51:37 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-20 01:51:37 (3638) [INFO] Checking if your system is up to date: * 2023-03-20 01:51:37 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-20 01:51:37 (4151) [INFO] * 2023-03-20 01:51:38 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-20 01:51:38 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-20 01:51:38 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-20 01:51:38 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-20 01:51:38 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-20 01:51:38 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-20 01:51:38 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-20 01:51:38 (4182) [INFO] * 2023-03-20 01:51:38 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-20 01:51:38 (4151) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-20 01:52:36 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-20 01:52:36 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-20 01:52:36 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-20 01:52:36 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-20 01:52:36 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-20 01:52:36 (4165) [INFO] yum --disablerepo= ... * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-20 01:52:36 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-20 01:52:36 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] yum-config-manager --disable * 2023-03-20 01:52:36 (4165) [INFO] or * 2023-03-20 01:52:36 (4165) [INFO] subscription-manager repos --disable= * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-20 01:52:36 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-20 01:52:36 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-20 01:52:36 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-20 01:52:36 (4165) [INFO] compromise: * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-20 01:52:36 (4165) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-20 01:52:36 (4182) [INFO] * 2023-03-20 01:52:36 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-20 01:52:36 (3661) [INFO] Checking /scripts/sysup * 2023-03-20 01:52:36 (4150) [INFO] Running: /scripts/sysup * 2023-03-20 01:52:36 (4151) [INFO] * 2023-03-20 01:52:36 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-20 01:52:40 (4165) [INFO] All Needed Packages are already installed. * 2023-03-20 01:52:40 (4182) [INFO] * 2023-03-20 01:52:40 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-20 01:52:40 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-20 01:52:40 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XYZ8MIxb4J/ea_profile.json * 2023-03-20 01:56:25 (1765) [INFO] Backed up EA4 profile to /tmp/XYZ8MIxb4J/ea_profile.json * 2023-03-20 01:56:25 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-20 02:00:29 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-21 01:51:50 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-21 01:51:53 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-21 01:51:53 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-21 01:54:08 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-21 01:54:08 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-21 01:54:09 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-21 01:54:09 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-21 01:54:09 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-21 01:54:09 (3638) [INFO] Checking if your system is up to date: * 2023-03-21 01:54:09 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-21 01:54:09 (4151) [INFO] * 2023-03-21 01:54:09 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-21 01:54:09 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-21 01:54:09 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-21 01:54:09 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-21 01:54:09 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-21 01:54:10 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-21 01:54:10 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-21 01:54:10 (4182) [INFO] * 2023-03-21 01:54:10 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-21 01:54:10 (4151) [INFO] * 2023-03-21 01:58:08 (4165) [INFO] * 2023-03-21 01:58:08 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-21 01:58:08 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-21 01:58:08 (4182) [INFO] * 2023-03-21 01:58:08 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-21 01:58:08 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-21 01:58:08 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-21 01:58:08 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-21 01:58:08 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wXOmIX6Ys5/ea_profile.json * 2023-03-21 01:58:11 (1765) [INFO] Backed up EA4 profile to /tmp/wXOmIX6Ys5/ea_profile.json * 2023-03-21 01:58:11 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-21 02:02:15 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-22 01:53:40 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-22 01:53:43 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-22 01:53:43 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-22 01:56:41 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-22 01:56:41 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2023-03-22 01:56:41 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-22 01:56:41 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-22 01:56:41 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-22 01:56:42 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-22 01:56:42 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-22 01:56:42 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-22 01:56:42 (3638) [INFO] Checking if your system is up to date: * 2023-03-22 01:56:42 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-22 01:56:42 (4151) [INFO] * 2023-03-22 01:56:42 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-22 01:56:42 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-22 01:56:42 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-22 01:56:42 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-22 01:56:42 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-22 01:56:43 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-22 01:56:43 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-22 01:56:43 (4182) [INFO] * 2023-03-22 01:56:43 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-22 01:56:43 (4151) [INFO] * 2023-03-22 02:01:04 (4165) [INFO] * 2023-03-22 02:01:04 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-22 02:01:04 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-22 02:01:04 (4182) [INFO] * 2023-03-22 02:01:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-22 02:01:04 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-22 02:01:04 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-22 02:01:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-22 02:01:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hMNdwMGVOw/ea_profile.json * 2023-03-22 02:01:11 (1765) [INFO] Backed up EA4 profile to /tmp/hMNdwMGVOw/ea_profile.json * 2023-03-22 02:01:11 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-22 02:05:18 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-23 01:52:25 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-23 01:52:30 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-23 01:52:30 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-23 01:54:59 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-23 01:54:59 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30619 milliseconds') * 2023-03-23 01:54:59 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-23 01:54:59 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-23 01:54:59 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-23 01:55:00 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-23 01:55:00 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-23 01:55:00 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-23 01:55:00 (3638) [INFO] Checking if your system is up to date: * 2023-03-23 01:55:00 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-23 01:55:00 (4151) [INFO] * 2023-03-23 01:55:01 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-23 01:55:01 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-23 01:55:01 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-23 01:55:01 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-23 01:55:01 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-23 01:55:02 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-23 01:55:02 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-23 01:55:02 (4182) [INFO] * 2023-03-23 01:55:02 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-23 01:55:02 (4151) [INFO] * 2023-03-23 01:58:34 (4165) [INFO] * 2023-03-23 01:58:34 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-23 01:58:34 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-23 01:58:35 (4182) [INFO] * 2023-03-23 01:58:35 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-23 01:58:35 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-23 01:58:35 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-23 01:58:35 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-23 01:58:35 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LKIq5pVSgU/ea_profile.json * 2023-03-23 01:58:38 (1765) [INFO] Backed up EA4 profile to /tmp/LKIq5pVSgU/ea_profile.json * 2023-03-23 01:58: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-23 02:02:42 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-24 01:51:26 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-24 01:51:29 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-24 01:51:29 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-24 01:53:45 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-24 01:53:45 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-24 01:53:46 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-24 01:53:46 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-24 01:53:46 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-24 01:53:46 (3638) [INFO] Checking if your system is up to date: * 2023-03-24 01:53:46 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-24 01:53:46 (4151) [INFO] * 2023-03-24 01:53:46 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-24 01:53:46 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-24 01:53:46 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-24 01:53:46 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-24 01:53:46 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-24 01:53:47 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-24 01:53:47 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-24 01:53:47 (4182) [INFO] * 2023-03-24 01:53:47 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-24 01:53:47 (4151) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-24 01:54:41 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-24 01:54:41 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-24 01:54:41 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-24 01:54:41 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-24 01:54:41 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-24 01:54:41 (4165) [INFO] yum --disablerepo= ... * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-24 01:54:41 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-24 01:54:41 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] yum-config-manager --disable * 2023-03-24 01:54:41 (4165) [INFO] or * 2023-03-24 01:54:41 (4165) [INFO] subscription-manager repos --disable= * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-24 01:54:41 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-24 01:54:41 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-24 01:54:41 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-24 01:54:41 (4165) [INFO] compromise: * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-24 01:54:41 (4165) [INFO] * 2023-03-24 01:54:41 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-24 01:54:41 (4182) [INFO] * 2023-03-24 01:54:41 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-24 01:54:41 (3661) [INFO] Checking /scripts/sysup * 2023-03-24 01:54:41 (4150) [INFO] Running: /scripts/sysup * 2023-03-24 01:54:41 (4151) [INFO] * 2023-03-24 01:54:42 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-24 01:54:45 (4165) [INFO] All Needed Packages are already installed. * 2023-03-24 01:54:45 (4182) [INFO] * 2023-03-24 01:54:45 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-24 01:54:45 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-24 01:54:45 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UcIFff7sEj/ea_profile.json * 2023-03-24 01:56:12 (2787) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UcIFff7sEj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1742. * 2023-03-24 01:56:12 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-25 01:57:03 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-25 01:57:08 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-25 01:57:08 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-25 01:59:38 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-25 01:59:38 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-25 01:59:39 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-25 01:59:39 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-25 01:59:39 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-25 01:59:39 (3638) [INFO] Checking if your system is up to date: * 2023-03-25 01:59:39 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-25 01:59:39 (4151) [INFO] * 2023-03-25 01:59:39 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-25 01:59:39 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-25 01:59:39 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-25 01:59:39 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-25 01:59:39 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-25 01:59:40 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-25 01:59:40 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-25 01:59:40 (4182) [INFO] * 2023-03-25 01:59:40 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-25 01:59:40 (4151) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-25 02:00:37 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-25 02:00:37 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-25 02:00:37 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-25 02:00:37 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-25 02:00:37 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-25 02:00:37 (4165) [INFO] yum --disablerepo= ... * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-25 02:00:37 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-25 02:00:37 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] yum-config-manager --disable * 2023-03-25 02:00:37 (4165) [INFO] or * 2023-03-25 02:00:37 (4165) [INFO] subscription-manager repos --disable= * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-25 02:00:37 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-25 02:00:37 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-25 02:00:37 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-25 02:00:37 (4165) [INFO] compromise: * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-25 02:00:37 (4165) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-25 02:00:37 (4182) [INFO] * 2023-03-25 02:00:37 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-25 02:00:37 (3661) [INFO] Checking /scripts/sysup * 2023-03-25 02:00:37 (4150) [INFO] Running: /scripts/sysup * 2023-03-25 02:00:37 (4151) [INFO] * 2023-03-25 02:00:37 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-25 02:00:42 (4165) [INFO] All Needed Packages are already installed. * 2023-03-25 02:00:42 (4182) [INFO] * 2023-03-25 02:00:42 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-25 02:00:42 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-25 02:00:42 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CJhx7Yb_dD/ea_profile.json * 2023-03-25 02:05:24 (1765) [INFO] Backed up EA4 profile to /tmp/CJhx7Yb_dD/ea_profile.json * 2023-03-25 02:05: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-25 02:09:27 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-26 01:54:22 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-26 01:54:28 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-26 01:54:28 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-26 01:56:59 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-26 01:56:59 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-26 01:56:59 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-26 01:56:59 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-26 01:56:59 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-26 01:57:00 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-26 01:57:00 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-26 01:57:00 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-26 01:57:00 (3638) [INFO] Checking if your system is up to date: * 2023-03-26 01:57:00 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-26 01:57:00 (4151) [INFO] * 2023-03-26 01:57:01 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-26 01:57:01 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-26 01:57:01 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-26 01:57:01 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-26 01:57:01 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-26 01:57:01 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-26 01:57:01 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-26 01:57:01 (4182) [INFO] * 2023-03-26 01:57:01 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-26 01:57:01 (4151) [INFO] * 2023-03-26 02:00:35 (4165) [INFO] * 2023-03-26 02:00:35 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-26 02:00:35 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-26 02:00:35 (4182) [INFO] * 2023-03-26 02:00:35 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-26 02:00:35 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-26 02:00:35 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-26 02:00:35 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-26 02:00:35 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ywWLY0_VfM/ea_profile.json * 2023-03-26 02:00:40 (1765) [INFO] Backed up EA4 profile to /tmp/ywWLY0_VfM/ea_profile.json * 2023-03-26 02:00: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-26 02:04:43 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-27 01:51:39 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-27 01:51:44 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-27 01:51:44 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-27 01:54:32 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-27 01:54:32 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-27 01:54:33 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-27 01:54:33 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-27 01:54:33 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-27 01:54:33 (3638) [INFO] Checking if your system is up to date: * 2023-03-27 01:54:33 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-27 01:54:33 (4151) [INFO] * 2023-03-27 01:54:34 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-27 01:54:34 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-27 01:54:34 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-27 01:54:34 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-27 01:54:34 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-27 01:54:35 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-27 01:54:35 (4165) [INFO] Other repos take up 644 k of disk space (use --verbose for details) * 2023-03-27 01:54:35 (4182) [INFO] * 2023-03-27 01:54:35 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-27 01:54:35 (4151) [INFO] * 2023-03-27 01:58:27 (4165) [INFO] * 2023-03-27 01:58:27 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-27 01:58:27 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-27 01:58:28 (4182) [INFO] * 2023-03-27 01:58:28 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-27 01:58:28 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-27 01:58:28 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-27 01:58:28 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-27 01:58:28 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HDh2H9ujyu/ea_profile.json * 2023-03-27 01:58:32 (1765) [INFO] Backed up EA4 profile to /tmp/HDh2H9ujyu/ea_profile.json * 2023-03-27 01:58:32 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-27 02:02:38 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-28 00:57:14 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-28 00:57:20 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-28 00:57:20 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-28 00:59:33 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-28 00:59:33 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-28 00:59:33 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-28 00:59:33 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-28 00:59:33 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-28 00:59:36 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-28 00:59:36 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-28 00:59:36 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-28 00:59:36 (3638) [INFO] Checking if your system is up to date: * 2023-03-28 00:59:36 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-28 00:59:36 (4151) [INFO] * 2023-03-28 00:59:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-28 00:59:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-28 00:59:37 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-28 00:59:37 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-28 00:59:37 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-28 00:59:37 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-28 00:59:37 (4165) [INFO] Other repos take up 640 k of disk space (use --verbose for details) * 2023-03-28 00:59:38 (4182) [INFO] * 2023-03-28 00:59:38 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-28 00:59:38 (4151) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-28 01:00:36 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-28 01:00:36 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-28 01:00:36 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-28 01:00:36 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-28 01:00:36 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-28 01:00:36 (4165) [INFO] yum --disablerepo= ... * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-28 01:00:36 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-28 01:00:36 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] yum-config-manager --disable * 2023-03-28 01:00:36 (4165) [INFO] or * 2023-03-28 01:00:36 (4165) [INFO] subscription-manager repos --disable= * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-28 01:00:36 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-28 01:00:36 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-28 01:00:36 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-28 01:00:36 (4165) [INFO] compromise: * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-28 01:00:36 (4165) [INFO] * 2023-03-28 01:00:36 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-28 01:00:36 (4182) [INFO] * 2023-03-28 01:00:36 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-28 01:00:36 (3661) [INFO] Checking /scripts/sysup * 2023-03-28 01:00:36 (4150) [INFO] Running: /scripts/sysup * 2023-03-28 01:00:36 (4151) [INFO] * 2023-03-28 01:00:37 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-28 01:00:44 (4165) [INFO] All Needed Packages are already installed. * 2023-03-28 01:00:44 (4182) [INFO] * 2023-03-28 01:00:44 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-28 01:00:44 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-28 01:00:44 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TjryoJ8G0o/ea_profile.json * 2023-03-28 01:04:56 (1765) [INFO] Backed up EA4 profile to /tmp/TjryoJ8G0o/ea_profile.json * 2023-03-28 01:04: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-28 01:09:02 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-29 01:51:38 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-29 01:51:44 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-29 01:51:44 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-29 01:54:12 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-29 01:54:12 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-29 01:54:13 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-29 01:54:13 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-29 01:54:13 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-29 01:54:13 (3638) [INFO] Checking if your system is up to date: * 2023-03-29 01:54:13 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-29 01:54:13 (4151) [INFO] * 2023-03-29 01:54:14 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-29 01:54:14 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-29 01:54:14 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-29 01:54:14 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-29 01:54:14 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-29 01:54:15 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-29 01:54:15 (4165) [INFO] Other repos take up 640 k of disk space (use --verbose for details) * 2023-03-29 01:54:15 (4182) [INFO] * 2023-03-29 01:54:15 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-29 01:54:15 (4151) [INFO] * 2023-03-29 01:58:17 (4165) [INFO] * 2023-03-29 01:58:17 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-29 01:58:17 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-29 01:58:18 (4182) [INFO] * 2023-03-29 01:58:18 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-29 01:58:18 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-29 01:58:18 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-29 01:58:18 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-29 01:58:18 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SUw6n13J0_/ea_profile.json * 2023-03-29 01:58:21 (1765) [INFO] Backed up EA4 profile to /tmp/SUw6n13J0_/ea_profile.json * 2023-03-29 01:58:21 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-29 02:02:23 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-30 01:52:32 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-30 01:52:35 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-30 01:52:35 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-30 01:54:54 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-30 01:54:54 (3806) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/e2fe3cab91c91f50c78093dd14cc2b424bfc651f56fc9989e83544d33258be2f-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/. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/fecb038b8e3435b26a59afe38cc1fc965a74442f24affa8060ed2219d0565552-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. Error: Error writing to file /var/cache/yum/x86_64/7/updates/gen/filelists_db.sqlite: [Errno 28] No space left on device * 2023-03-30 01:54:54 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-30 01:54:54 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-30 01:54:54 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-30 01:54:55 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-30 01:54:55 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-30 01:54:55 (2820) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-03-30 01:54:55 (3638) [INFO] Checking if your system is up to date: * 2023-03-30 01:54:55 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-30 01:54:55 (4151) [INFO] * 2023-03-30 01:54:56 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-30 01:54:56 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-30 01:54:56 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-30 01:54:56 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-30 01:54:56 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-30 01:54:56 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-30 01:54:56 (4165) [INFO] Other repos take up 640 k of disk space (use --verbose for details) * 2023-03-30 01:54:57 (4182) [INFO] * 2023-03-30 01:54:57 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-30 01:54:57 (4151) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-03-30 01:55:51 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-03-30 01:55:51 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-03-30 01:55:51 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-03-30 01:55:51 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-03-30 01:55:51 (4165) [INFO] packages for the previous distribution release still work). * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-03-30 01:55:51 (4165) [INFO] yum --disablerepo= ... * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-03-30 01:55:51 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-03-30 01:55:51 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] yum-config-manager --disable * 2023-03-30 01:55:51 (4165) [INFO] or * 2023-03-30 01:55:51 (4165) [INFO] subscription-manager repos --disable= * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-03-30 01:55:51 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-03-30 01:55:51 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-03-30 01:55:51 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-03-30 01:55:51 (4165) [INFO] compromise: * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-03-30 01:55:51 (4165) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-03-30 01:55:51 (4182) [INFO] * 2023-03-30 01:55:51 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-30 01:55:51 (3661) [INFO] Checking /scripts/sysup * 2023-03-30 01:55:51 (4150) [INFO] Running: /scripts/sysup * 2023-03-30 01:55:51 (4151) [INFO] * 2023-03-30 01:55:51 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-03-30 01:55:55 (4165) [INFO] All Needed Packages are already installed. * 2023-03-30 01:55:55 (4182) [INFO] * 2023-03-30 01:55:55 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-30 01:55:55 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-30 01:55:55 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/umq5SYDH1H/ea_profile.json * 2023-03-30 01:57:06 (2787) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/umq5SYDH1H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 1742. * 2023-03-30 01:57:06 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-31 00:59:02 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-31 00:59:05 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-03-31 00:59:05 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-03-31 01:01:50 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-03-31 01:01:50 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-03-31 01:01:50 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-03-31 01:01:50 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-03-31 01:01:50 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-03-31 01:01:51 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-03-31 01:01:51 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-03-31 01:01:51 (3638) [INFO] Checking if your system is up to date: * 2023-03-31 01:01:51 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-31 01:01:51 (4151) [INFO] * 2023-03-31 01:01:51 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-31 01:01:52 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-03-31 01:01:52 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-31 01:01:52 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-03-31 01:01:52 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-03-31 01:01:52 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-31 01:01:52 (4165) [INFO] Other repos take up 640 k of disk space (use --verbose for details) * 2023-03-31 01:01:52 (4182) [INFO] * 2023-03-31 01:01:52 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-31 01:01:52 (4151) [INFO] * 2023-03-31 01:06:03 (4165) [INFO] * 2023-03-31 01:06:03 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-31 01:06:03 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-31 01:06:03 (4182) [INFO] * 2023-03-31 01:06:03 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-31 01:06:03 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-31 01:06:03 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-03-31 01:06:03 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-31 01:06:03 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/csDH9nfQ2_/ea_profile.json * 2023-03-31 01:06:06 (1765) [INFO] Backed up EA4 profile to /tmp/csDH9nfQ2_/ea_profile.json * 2023-03-31 01:06: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-03-31 01:10:08 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-01 01:53:28 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-01 01:53:34 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-01 01:53:34 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-01 01:55:49 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-01 01:55:49 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-04-01 01:55:49 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-01 01:55:49 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-01 01:55:49 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-01 01:55:50 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-01 01:55:50 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-01 01:55:50 (3638) [INFO] Checking if your system is up to date: * 2023-04-01 01:55:50 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-01 01:55:50 (4151) [INFO] * 2023-04-01 01:55:50 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-01 01:55:51 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-01 01:55:51 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-01 01:55:51 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-01 01:55:51 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-01 01:55:51 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-01 01:55:51 (4165) [INFO] Other repos take up 640 k of disk space (use --verbose for details) * 2023-04-01 01:55:51 (4182) [INFO] * 2023-04-01 01:55:51 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-01 01:55:51 (4151) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-04-01 01:56:46 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-01 01:56:46 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-01 01:56:46 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-01 01:56:46 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-04-01 01:56:46 (4165) [INFO] packages for the previous distribution release still work). * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-01 01:56:46 (4165) [INFO] yum --disablerepo= ... * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-01 01:56:46 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-01 01:56:46 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] yum-config-manager --disable * 2023-04-01 01:56:46 (4165) [INFO] or * 2023-04-01 01:56:46 (4165) [INFO] subscription-manager repos --disable= * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-01 01:56:46 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-01 01:56:46 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-01 01:56:46 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-01 01:56:46 (4165) [INFO] compromise: * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-01 01:56:46 (4165) [INFO] * 2023-04-01 01:56:46 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-01 01:56:46 (4182) [INFO] * 2023-04-01 01:56:46 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-01 01:56:46 (3661) [INFO] Checking /scripts/sysup * 2023-04-01 01:56:46 (4150) [INFO] Running: /scripts/sysup * 2023-04-01 01:56:46 (4151) [INFO] * 2023-04-01 01:56:47 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-01 01:56:50 (4165) [INFO] All Needed Packages are already installed. * 2023-04-01 01:56:50 (4182) [INFO] * 2023-04-01 01:56:50 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-01 01:56:50 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-01 01:56:50 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/C0GcfW8_zL/ea_profile.json * 2023-04-01 02:00:55 (1765) [INFO] Backed up EA4 profile to /tmp/C0GcfW8_zL/ea_profile.json * 2023-04-01 02:00:55 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-01 02:04:58 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-02 01:53:18 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-02 01:53:23 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-02 01:53:23 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-02 01:56:30 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-02 01:56:30 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30542 milliseconds') * 2023-04-02 01:56:30 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-02 01:56:30 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-02 01:56:30 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-02 01:56:31 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-02 01:56:31 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-02 01:56:31 (3638) [INFO] Checking if your system is up to date: * 2023-04-02 01:56:31 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-02 01:56:31 (4151) [INFO] * 2023-04-02 01:56:31 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-02 01:56:32 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-02 01:56:32 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-02 01:56:32 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-02 01:56:32 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-02 01:56:32 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-02 01:56:32 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-02 01:56:32 (4182) [INFO] * 2023-04-02 01:56:32 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-02 01:56:32 (4151) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-04-02 01:57:27 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-02 01:57:27 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-02 01:57:27 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-02 01:57:27 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-04-02 01:57:27 (4165) [INFO] packages for the previous distribution release still work). * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-02 01:57:27 (4165) [INFO] yum --disablerepo= ... * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-02 01:57:27 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-02 01:57:27 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] yum-config-manager --disable * 2023-04-02 01:57:27 (4165) [INFO] or * 2023-04-02 01:57:27 (4165) [INFO] subscription-manager repos --disable= * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-02 01:57:27 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-02 01:57:27 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-02 01:57:27 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-02 01:57:27 (4165) [INFO] compromise: * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-02 01:57:27 (4165) [INFO] * 2023-04-02 01:57:27 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-02 01:57:27 (4182) [INFO] * 2023-04-02 01:57:27 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-02 01:57:27 (3661) [INFO] Checking /scripts/sysup * 2023-04-02 01:57:27 (4150) [INFO] Running: /scripts/sysup * 2023-04-02 01:57:27 (4151) [INFO] * 2023-04-02 01:57:28 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-02 01:57:31 (4165) [INFO] All Needed Packages are already installed. * 2023-04-02 01:57:31 (4182) [INFO] * 2023-04-02 01:57:31 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-02 01:57:31 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-02 01:57:31 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d6yDX1SKLB/ea_profile.json * 2023-04-02 02:01:32 (1765) [INFO] Backed up EA4 profile to /tmp/d6yDX1SKLB/ea_profile.json * 2023-04-02 02:01:32 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-02 02:05:35 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-03 01:49:49 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-03 01:49:54 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-03 01:49:54 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-03 01:52:40 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-03 01:52:40 (3806) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') * 2023-04-03 01:52:40 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-03 01:52:40 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-03 01:52:40 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-03 01:52:41 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-03 01:52:41 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-03 01:52:41 (3638) [INFO] Checking if your system is up to date: * 2023-04-03 01:52:41 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-03 01:52:41 (4151) [INFO] * 2023-04-03 01:52:41 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-03 01:52:41 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-03 01:52:41 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-03 01:52:41 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-03 01:52:41 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-03 01:52:42 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-03 01:52:42 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-03 01:52:42 (4182) [INFO] * 2023-04-03 01:52:42 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-03 01:52:42 (4151) [INFO] * 2023-04-03 01:56:33 (4165) [INFO] * 2023-04-03 01:56:33 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-03 01:56:33 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-03 01:56:34 (4182) [INFO] * 2023-04-03 01:56:34 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-03 01:56:34 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-03 01:56:34 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-03 01:56:34 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-03 01:56:34 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2FmF4kiMIt/ea_profile.json * 2023-04-03 01:56:35 (1765) [INFO] Backed up EA4 profile to /tmp/2FmF4kiMIt/ea_profile.json * 2023-04-03 01:56:35 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-03 02:00:38 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-04 00:53:30 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-04 00:53:33 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-04 00:53:33 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-04 00:56:03 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-04 00:56:03 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-04 00:56:04 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-04 00:56:04 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-04 00:56:04 (3638) [INFO] Checking if your system is up to date: * 2023-04-04 00:56:04 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-04 00:56:04 (4151) [INFO] * 2023-04-04 00:56:05 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-04 00:56:05 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-04 00:56:05 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-04 00:56:05 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-04 00:56:05 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-04 00:56:05 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-04 00:56:05 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-04 00:56:05 (4182) [INFO] * 2023-04-04 00:56:05 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-04 00:56:05 (4151) [INFO] * 2023-04-04 01:00:12 (4165) [INFO] * 2023-04-04 01:00:12 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-04 01:00:12 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-04 01:00:13 (4182) [INFO] * 2023-04-04 01:00:13 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-04 01:00:13 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-04 01:00:13 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-04 01:00:13 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-04 01:00:13 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H78kaDYhLT/ea_profile.json * 2023-04-04 01:00:15 (1765) [INFO] Backed up EA4 profile to /tmp/H78kaDYhLT/ea_profile.json * 2023-04-04 01:00:15 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-04 01:04:18 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-05 01:51:32 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-05 01:51:35 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-05 01:51:35 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-05 01:54:05 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-05 01:54:05 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-05 01:54:05 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-05 01:54:06 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-05 01:54:06 (3638) [INFO] Checking if your system is up to date: * 2023-04-05 01:54:06 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-05 01:54:06 (4151) [INFO] * 2023-04-05 01:54:06 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-05 01:54:06 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-05 01:54:06 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-05 01:54:06 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-05 01:54:06 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-05 01:54:07 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-05 01:54:07 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-05 01:54:07 (4182) [INFO] * 2023-04-05 01:54:07 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-05 01:54:07 (4151) [INFO] * 2023-04-05 01:58:12 (4165) [INFO] * 2023-04-05 01:58:12 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-05 01:58:12 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-05 01:58:12 (4182) [INFO] * 2023-04-05 01:58:12 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-05 01:58:12 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-05 01:58:12 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-05 01:58:12 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-05 01:58:12 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aE_7P_iyDA/ea_profile.json * 2023-04-05 01:58:14 (1765) [INFO] Backed up EA4 profile to /tmp/aE_7P_iyDA/ea_profile.json * 2023-04-05 01:58:14 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-05 02:02:17 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-06 01:52:41 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-06 01:52:44 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-06 01:52:44 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-06 01:55:47 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-06 01:55:47 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-06 01:55:48 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-06 01:55:48 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-06 01:55:48 (3638) [INFO] Checking if your system is up to date: * 2023-04-06 01:55:48 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-06 01:55:48 (4151) [INFO] * 2023-04-06 01:55:48 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-06 01:55:48 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-06 01:55:48 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-06 01:55:48 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-06 01:55:48 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-06 01:55:49 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-06 01:55:49 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-06 01:55:49 (4182) [INFO] * 2023-04-06 01:55:49 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-06 01:55:49 (4151) [INFO] * 2023-04-06 01:59:56 (4165) [INFO] * 2023-04-06 01:59:56 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-06 01:59:56 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-06 01:59:57 (4182) [INFO] * 2023-04-06 01:59:57 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-06 01:59:57 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-06 01:59:57 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-06 01:59:57 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-06 01:59:57 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bO4RBrnnzB/ea_profile.json * 2023-04-06 01:59:59 (1765) [INFO] Backed up EA4 profile to /tmp/bO4RBrnnzB/ea_profile.json * 2023-04-06 01:59:59 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-06 02:04:02 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-07 01:52:34 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-07 01:52:37 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-07 01:52:37 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-07 01:55:51 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-07 01:55:51 (3806) [ERROR] https://epel.mirror.constant.com/7/x86_64/repodata/d8fb6455ebc29cd99f4feff3ad78bd89b2f5d8e190dedc9afe98899e59ec1255-updateinfo.xml.bz2: [Errno 14] curl#7 - "Failed connect to epel.mirror.constant.com:443; Operation now in progress" Trying other mirror. * 2023-04-07 01:55:51 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-07 01:55:51 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-07 01:55:51 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-07 01:55:52 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-07 01:55:52 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-07 01:55:52 (3638) [INFO] Checking if your system is up to date: * 2023-04-07 01:55:52 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-07 01:55:52 (4151) [INFO] * 2023-04-07 01:55:53 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-07 01:55:53 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-07 01:55:53 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-07 01:55:53 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-07 01:55:53 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-07 01:55:53 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-07 01:55:53 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-07 01:55:53 (4182) [INFO] * 2023-04-07 01:55:53 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-07 01:55:53 (4151) [INFO] * 2023-04-07 02:00:06 (4165) [INFO] * 2023-04-07 02:00:06 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-07 02:00:06 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-07 02:00:06 (4182) [INFO] * 2023-04-07 02:00:06 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-07 02:00:06 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-07 02:00:06 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-07 02:00:06 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-07 02:00:07 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/71amYsxd71/ea_profile.json * 2023-04-07 02:00:09 (1765) [INFO] Backed up EA4 profile to /tmp/71amYsxd71/ea_profile.json * 2023-04-07 02:00:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-07 02:04:12 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-08 01:54:23 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-08 01:54:26 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-08 01:54:26 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-08 01:57:08 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-08 01:57:08 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-08 01:57:09 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-08 01:57:09 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-08 01:57:09 (3638) [INFO] Checking if your system is up to date: * 2023-04-08 01:57:09 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-08 01:57:09 (4151) [INFO] * 2023-04-08 01:57:09 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-08 01:57:10 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-08 01:57:10 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-08 01:57:10 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-08 01:57:10 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-08 01:57:10 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-08 01:57:10 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-08 01:57:10 (4182) [INFO] * 2023-04-08 01:57:10 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-08 01:57:10 (4151) [INFO] * 2023-04-08 02:01:17 (4165) [INFO] * 2023-04-08 02:01:17 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-08 02:01:17 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-08 02:01:18 (4182) [INFO] * 2023-04-08 02:01:18 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-08 02:01:18 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-08 02:01:18 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-08 02:01:18 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-08 02:01:18 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_wsIsDx_i8/ea_profile.json * 2023-04-08 02:01:20 (1765) [INFO] Backed up EA4 profile to /tmp/_wsIsDx_i8/ea_profile.json * 2023-04-08 02:01:20 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-08 02:05:23 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-09 01:52:07 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-09 01:52:11 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-09 01:52:11 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-09 01:54:23 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-09 01:54:23 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-09 01:54:24 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-09 01:54:24 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-09 01:54:24 (3638) [INFO] Checking if your system is up to date: * 2023-04-09 01:54:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-09 01:54:24 (4151) [INFO] * 2023-04-09 01:54:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-09 01:54:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-09 01:54:25 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-09 01:54:25 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-09 01:54:25 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-09 01:54:25 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-09 01:54:25 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-09 01:54:26 (4182) [INFO] * 2023-04-09 01:54:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-09 01:54:26 (4151) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] One of the configured repositories failed (Unknown), * 2023-04-09 01:55:21 (4165) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-09 01:55:21 (4165) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-09 01:55:21 (4165) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-09 01:55:21 (4165) [INFO] distribution release than is supported by the repository (and the * 2023-04-09 01:55:21 (4165) [INFO] packages for the previous distribution release still work). * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-09 01:55:21 (4165) [INFO] yum --disablerepo= ... * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-09 01:55:21 (4165) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-09 01:55:21 (4165) [INFO] again or use --enablerepo for temporary usage: * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] yum-config-manager --disable * 2023-04-09 01:55:21 (4165) [INFO] or * 2023-04-09 01:55:21 (4165) [INFO] subscription-manager repos --disable= * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-09 01:55:21 (4165) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-09 01:55:21 (4165) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-09 01:55:21 (4165) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-09 01:55:21 (4165) [INFO] compromise: * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-09 01:55:21 (4165) [INFO] * 2023-04-09 01:55:21 (4165) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-09 01:55:22 (4182) [INFO] * 2023-04-09 01:55:22 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-09 01:55:22 (3661) [INFO] Checking /scripts/sysup * 2023-04-09 01:55:22 (4150) [INFO] Running: /scripts/sysup * 2023-04-09 01:55:22 (4151) [INFO] * 2023-04-09 01:55:22 (4165) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-09 01:55:23 (4165) [INFO] All Needed Packages are already installed. * 2023-04-09 01:55:24 (4182) [INFO] * 2023-04-09 01:55:24 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-09 01:55:24 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-09 01:55:24 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oR5L65bQwa/ea_profile.json * 2023-04-09 01:59:24 (1765) [INFO] Backed up EA4 profile to /tmp/oR5L65bQwa/ea_profile.json * 2023-04-09 01:59: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-09 02:03:27 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-10 01:51:01 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-10 01:51:04 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-10 01:51:04 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-10 01:53:36 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-10 01:53:36 (3806) [ERROR] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.1.3/wp-toolkit/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: wp-toolkit.plesk.com; Unknown error" Trying other mirror. * 2023-04-10 01:53:36 (2820) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-10 01:53:36 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-10 01:53:36 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-10 01:53:37 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-10 01:53:37 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-10 01:53:37 (3638) [INFO] Checking if your system is up to date: * 2023-04-10 01:53:37 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-10 01:53:37 (4151) [INFO] * 2023-04-10 01:53:38 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-10 01:53:38 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-10 01:53:38 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-10 01:53:38 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-10 01:53:38 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-10 01:53:38 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-10 01:53:38 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-10 01:53:38 (4182) [INFO] * 2023-04-10 01:53:38 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-10 01:53:38 (4151) [INFO] * 2023-04-10 01:57:15 (4165) [INFO] * 2023-04-10 01:57:15 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-10 01:57:15 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-10 01:57:15 (4182) [INFO] * 2023-04-10 01:57:15 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-10 01:57:15 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-10 01:57:15 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-10 01:57:15 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-10 01:57:15 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SolEd2k92i/ea_profile.json * 2023-04-10 01:57:18 (1765) [INFO] Backed up EA4 profile to /tmp/SolEd2k92i/ea_profile.json * 2023-04-10 01:57:18 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-10 02:01:21 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-11 01:51:54 (2820) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-11 01:51:57 (3747) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-11 01:51:57 (2820) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-11 01:54:11 (3832) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-11 01:54:11 (2820) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-11 01:54:12 (3675) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-11 01:54:12 (2820) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-11 01:54:12 (3638) [INFO] Checking if your system is up to date: * 2023-04-11 01:54:12 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-11 01:54:12 (4151) [INFO] * 2023-04-11 01:54:12 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-11 01:54:13 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-11 01:54:13 (4165) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-11 01:54:13 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-11 01:54:13 (4165) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-11 01:54:13 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-11 01:54:13 (4165) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-11 01:54:13 (4182) [INFO] * 2023-04-11 01:54:13 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-11 01:54:13 (4151) [INFO] * 2023-04-11 01:58:05 (4165) [INFO] * 2023-04-11 01:58:05 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-11 01:58:05 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-11 01:58:05 (4182) [INFO] * 2023-04-11 01:58:05 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-11 01:58:05 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-11 01:58:05 (2820) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-11 01:58:05 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-11 01:58:05 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6NxbLePh9/ea_profile.json * 2023-04-11 01:58:08 (1765) [INFO] Backed up EA4 profile to /tmp/o6NxbLePh9/ea_profile.json * 2023-04-11 01:58:08 (2820) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-11 02:02:11 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-12 01:51:59 (372) [INFO] Self-update of script version 6 requested. * 2023-04-12 01:55:59 (377) [INFO] Newer version of script found. Downloading. * 2023-04-12 02:00:01 (386) [INFO] Script update to version 7 successful. * 2023-04-12 02:00:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-04-12 02:00:04 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-12 02:00:07 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-12 02:00:07 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-12 02:02:51 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-12 02:02:51 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-12 02:02:52 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-12 02:02:52 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-12 02:02:52 (3686) [INFO] Checking if your system is up to date: * 2023-04-12 02:02:52 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-12 02:02:52 (4199) [INFO] * 2023-04-12 02:02:52 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-12 02:02:52 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-12 02:02:52 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-12 02:02:52 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-12 02:02:52 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-12 02:02:53 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-12 02:02:53 (4213) [INFO] Other repos take up 716 k of disk space (use --verbose for details) * 2023-04-12 02:02:53 (4230) [INFO] * 2023-04-12 02:02:53 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-12 02:02:53 (4199) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] One of the configured repositories failed (Unknown), * 2023-04-12 02:03:48 (4213) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-12 02:03:48 (4213) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-12 02:03:48 (4213) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-12 02:03:48 (4213) [INFO] distribution release than is supported by the repository (and the * 2023-04-12 02:03:48 (4213) [INFO] packages for the previous distribution release still work). * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-12 02:03:48 (4213) [INFO] yum --disablerepo= ... * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-12 02:03:48 (4213) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-12 02:03:48 (4213) [INFO] again or use --enablerepo for temporary usage: * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] yum-config-manager --disable * 2023-04-12 02:03:48 (4213) [INFO] or * 2023-04-12 02:03:48 (4213) [INFO] subscription-manager repos --disable= * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-12 02:03:48 (4213) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-12 02:03:48 (4213) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-12 02:03:48 (4213) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-12 02:03:48 (4213) [INFO] compromise: * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-12 02:03:48 (4213) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-12 02:03:48 (4230) [INFO] * 2023-04-12 02:03:48 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-12 02:03:48 (3709) [INFO] Checking /scripts/sysup * 2023-04-12 02:03:48 (4198) [INFO] Running: /scripts/sysup * 2023-04-12 02:03:48 (4199) [INFO] * 2023-04-12 02:03:48 (4213) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-12 02:03:51 (4213) [INFO] All Needed Packages are already installed. * 2023-04-12 02:03:51 (4230) [INFO] * 2023-04-12 02:03:51 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-12 02:03:51 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-12 02:03:51 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9wrdztAHSm/ea_profile.json * 2023-04-12 02:07:52 (1805) [INFO] Backed up EA4 profile to /tmp/9wrdztAHSm/ea_profile.json * 2023-04-12 02:07:52 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-12 02:11:55 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-13 01:51:55 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-13 01:51:58 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-13 01:51:58 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-13 01:54:10 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-13 01:54:10 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-13 01:54:11 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-13 01:54:11 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-13 01:54:11 (3686) [INFO] Checking if your system is up to date: * 2023-04-13 01:54:11 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-13 01:54:11 (4199) [INFO] * 2023-04-13 01:54:11 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-13 01:54:12 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-13 01:54:12 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-13 01:54:12 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-13 01:54:12 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-13 01:54:12 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-13 01:54:12 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-13 01:54:12 (4230) [INFO] * 2023-04-13 01:54:12 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-13 01:54:12 (4199) [INFO] * 2023-04-13 01:57:33 (4213) [INFO] * 2023-04-13 01:57:33 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-13 01:57:33 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-13 01:57:33 (4230) [INFO] * 2023-04-13 01:57:33 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-13 01:57:33 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-13 01:57:33 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-13 01:57:33 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-13 01:57:33 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/95sJYGHvUM/ea_profile.json * 2023-04-13 01:57:35 (1805) [INFO] Backed up EA4 profile to /tmp/95sJYGHvUM/ea_profile.json * 2023-04-13 01:57:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-13 02:01:37 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-14 01:50:21 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-14 01:50:23 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-14 01:50:23 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-14 01:52:53 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-14 01:52:53 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-04-14 01:52:53 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-14 01:52:53 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-14 01:52:53 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-14 01:52:54 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-14 01:52:54 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-14 01:52:54 (3686) [INFO] Checking if your system is up to date: * 2023-04-14 01:52:54 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-14 01:52:54 (4199) [INFO] * 2023-04-14 01:52:54 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-14 01:52:54 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-14 01:52:54 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-14 01:52:54 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-14 01:52:54 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-14 01:52:55 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-14 01:52:55 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-14 01:52:55 (4230) [INFO] * 2023-04-14 01:52:55 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-14 01:52:55 (4199) [INFO] * 2023-04-14 01:56:33 (4213) [INFO] * 2023-04-14 01:56:33 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-14 01:56:33 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-14 01:56:33 (4230) [INFO] * 2023-04-14 01:56:33 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-14 01:56:33 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-14 01:56:33 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-14 01:56:33 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-14 01:56:33 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ydtarfE82N/ea_profile.json * 2023-04-14 01:56:35 (1805) [INFO] Backed up EA4 profile to /tmp/ydtarfE82N/ea_profile.json * 2023-04-14 01:56:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-14 02:00:38 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-15 01:53:34 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-15 01:53:37 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-15 01:53:37 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-15 01:56:08 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-15 01:56:08 (3854) [ERROR] https://mirror.fcix.net/epel/7/x86_64/repodata/2e82fbefb4e6cc18174b922f1bf247440e60992333ce74ba11498429454b7094-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/. * 2023-04-15 01:56:08 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-15 01:56:08 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-15 01:56:08 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-15 01:56:09 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-15 01:56:09 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-15 01:56:09 (3686) [INFO] Checking if your system is up to date: * 2023-04-15 01:56:09 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-15 01:56:09 (4199) [INFO] * 2023-04-15 01:56:09 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-15 01:56:09 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-15 01:56:09 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-15 01:56:09 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-15 01:56:09 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-15 01:56:10 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-15 01:56:10 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-15 01:56:10 (4230) [INFO] * 2023-04-15 01:56:10 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-15 01:56:10 (4199) [INFO] * 2023-04-15 01:59:16 (4213) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/f550da263491b9300189f4e75103d34ab3862fdec7b29fb655da32be626c12cc-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-04-15 01:59:16 (4213) [INFO] Trying other mirror. * 2023-04-15 01:59:16 (4213) [INFO] To address this issue please refer to the below wiki article * 2023-04-15 01:59:16 (4213) [INFO] * 2023-04-15 01:59:16 (4213) [INFO] https://wiki.centos.org/yum-errors * 2023-04-15 01:59:16 (4213) [INFO] * 2023-04-15 01:59:16 (4213) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-04-15 01:59:16 (4213) [INFO] * 2023-04-15 02:00:14 (4213) [INFO] * 2023-04-15 02:00:14 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-15 02:00:14 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-15 02:00:15 (4230) [INFO] * 2023-04-15 02:00:15 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-15 02:00:15 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-15 02:00:15 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-15 02:00:15 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-15 02:00:15 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sxU_z75mwX/ea_profile.json * 2023-04-15 02:00:17 (1805) [INFO] Backed up EA4 profile to /tmp/sxU_z75mwX/ea_profile.json * 2023-04-15 02:00:17 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-15 02:04:20 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-16 01:51:22 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-16 01:51:25 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-16 01:51:25 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-16 01:53:38 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-16 01:53:38 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30539 milliseconds') * 2023-04-16 01:53:38 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-16 01:53:38 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-16 01:53:38 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-16 01:53:39 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-16 01:53:39 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-16 01:53:39 (3686) [INFO] Checking if your system is up to date: * 2023-04-16 01:53:39 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-16 01:53:39 (4199) [INFO] * 2023-04-16 01:53:40 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-16 01:53:40 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-16 01:53:40 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-16 01:53:40 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-16 01:53:40 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-16 01:53:41 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-16 01:53:41 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-16 01:53:41 (4230) [INFO] * 2023-04-16 01:53:41 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-16 01:53:41 (4199) [INFO] * 2023-04-16 01:57:30 (4213) [INFO] * 2023-04-16 01:57:30 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-16 01:57:30 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-16 01:57:30 (4230) [INFO] * 2023-04-16 01:57:30 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-16 01:57:30 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-16 01:57:30 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-16 01:57:30 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-16 01:57:30 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PBvRvWN8rC/ea_profile.json * 2023-04-16 01:57:32 (1805) [INFO] Backed up EA4 profile to /tmp/PBvRvWN8rC/ea_profile.json * 2023-04-16 01:57:32 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-16 02:01:35 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-17 01:46:05 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.3 or later. You can update to version 10.3 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.3 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-17 01:46:08 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-17 01:46:08 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-17 01:49:45 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-17 01:49:45 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30127 milliseconds with 0 out of 0 bytes received') * 2023-04-17 01:49:45 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-17 01:49:45 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-17 01:49:45 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-17 01:49:46 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-17 01:49:46 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-17 01:49:46 (3686) [INFO] Checking if your system is up to date: * 2023-04-17 01:49:46 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-17 01:49:46 (4199) [INFO] * 2023-04-17 01:49:47 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-17 01:49:47 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-17 01:49:47 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-17 01:49:47 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-17 01:49:47 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-17 01:49:48 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-17 01:49:48 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-17 01:49:48 (4230) [INFO] * 2023-04-17 01:49:48 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-17 01:49:48 (4199) [INFO] * 2023-04-17 01:53:50 (4213) [INFO] * 2023-04-17 01:53:50 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-17 01:53:50 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-17 01:53:51 (4230) [INFO] * 2023-04-17 01:53:51 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-17 01:53:51 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-17 01:53:51 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-17 01:53:51 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-17 01:53:51 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3R6fQPwQG3/ea_profile.json * 2023-04-17 01:53:53 (1805) [INFO] Backed up EA4 profile to /tmp/3R6fQPwQG3/ea_profile.json * 2023-04-17 01:53:53 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-17 01:57:56 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-18 01:58:23 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-18 01:58:26 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-18 01:58:26 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-18 02:01:12 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-18 02:01:12 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-18 02:01:13 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-18 02:01:13 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-18 02:01:13 (3686) [INFO] Checking if your system is up to date: * 2023-04-18 02:01:13 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-18 02:01:13 (4199) [INFO] * 2023-04-18 02:01:13 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-18 02:01:13 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-18 02:01:13 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-18 02:01:13 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-18 02:01:13 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-18 02:01:14 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-18 02:01:14 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-18 02:01:14 (4230) [INFO] * 2023-04-18 02:01:14 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-18 02:01:14 (4199) [INFO] * 2023-04-18 02:05:09 (4213) [INFO] * 2023-04-18 02:05:09 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-18 02:05:09 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-18 02:05:09 (4230) [INFO] * 2023-04-18 02:05:09 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-18 02:05:09 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-18 02:05:09 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-18 02:05:09 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-18 02:05:10 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/C4SV0QU3IJ/ea_profile.json * 2023-04-18 02:05:12 (1805) [INFO] Backed up EA4 profile to /tmp/C4SV0QU3IJ/ea_profile.json * 2023-04-18 02:05:12 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-18 02:09:15 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-19 01:49:21 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-19 01:49:25 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-19 01:49:25 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-19 01:51:39 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-19 01:51:39 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-19 01:51:40 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-19 01:51:40 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-19 01:51:40 (3686) [INFO] Checking if your system is up to date: * 2023-04-19 01:51:40 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-19 01:51:40 (4199) [INFO] * 2023-04-19 01:51:40 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-19 01:51:41 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-19 01:51:41 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-19 01:51:41 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-19 01:51:41 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-19 01:51:41 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-19 01:51:41 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-19 01:51:41 (4230) [INFO] * 2023-04-19 01:51:41 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-19 01:51:41 (4199) [INFO] * 2023-04-19 01:55:30 (4213) [INFO] * 2023-04-19 01:55:30 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-19 01:55:30 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-19 01:55:31 (4230) [INFO] * 2023-04-19 01:55:31 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-19 01:55:31 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-19 01:55:31 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-19 01:55:31 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-19 01:55:31 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z03EbO5ULP/ea_profile.json * 2023-04-19 01:55:32 (1805) [INFO] Backed up EA4 profile to /tmp/Z03EbO5ULP/ea_profile.json * 2023-04-19 01:55:32 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-19 01:59:35 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-20 01:51:14 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-20 01:51:17 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-20 01:51:17 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-20 01:54:02 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-20 01:54:02 (3854) [ERROR] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/fea917c85657723e745f619a3570e6031293c25391fc84185fa20bc96c42d32c-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/. * 2023-04-20 01:54:02 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-20 01:54:02 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-20 01:54:02 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-20 01:54:03 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-20 01:54:03 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-20 01:54:03 (3686) [INFO] Checking if your system is up to date: * 2023-04-20 01:54:03 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-20 01:54:03 (4199) [INFO] * 2023-04-20 01:54:04 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-20 01:54:04 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-20 01:54:04 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-20 01:54:04 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-20 01:54:04 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-20 01:54:04 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-20 01:54:04 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-20 01:54:04 (4230) [INFO] * 2023-04-20 01:54:04 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-20 01:54:04 (4199) [INFO] * 2023-04-20 01:56:58 (4213) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/31f1686bf6a308b14d9bf5105928d650112555c5c7706cb640dbd5d20bcc9fe5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-04-20 01:56:58 (4213) [INFO] Trying other mirror. * 2023-04-20 01:56:58 (4213) [INFO] To address this issue please refer to the below wiki article * 2023-04-20 01:56:58 (4213) [INFO] * 2023-04-20 01:56:58 (4213) [INFO] https://wiki.centos.org/yum-errors * 2023-04-20 01:56:58 (4213) [INFO] * 2023-04-20 01:56:58 (4213) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-04-20 01:56:58 (4213) [INFO] * 2023-04-20 01:56:58 (4213) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/da8a7cfec29cdcd4e01df846ede972b9e9e01d181cb784db3292df022bee17eb-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-04-20 01:56:58 (4213) [INFO] Trying other mirror. * 2023-04-20 01:58:08 (4213) [INFO] * 2023-04-20 01:58:08 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-20 01:58:08 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-20 01:58:08 (4230) [INFO] * 2023-04-20 01:58:08 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-20 01:58:08 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-20 01:58:08 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-20 01:58:08 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-20 01:58:08 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tBNc7TfTFN/ea_profile.json * 2023-04-20 01:58:10 (1805) [INFO] Backed up EA4 profile to /tmp/tBNc7TfTFN/ea_profile.json * 2023-04-20 01:58:10 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-20 02:02:13 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-21 01:50:19 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-21 01:50:22 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-21 01:50:22 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-21 01:53:36 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-21 01:53:36 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-21 01:53:37 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-21 01:53:37 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-21 01:53:37 (3686) [INFO] Checking if your system is up to date: * 2023-04-21 01:53:37 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-21 01:53:37 (4199) [INFO] * 2023-04-21 01:53:37 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-21 01:53:38 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-21 01:53:38 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-21 01:53:38 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-21 01:53:38 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-21 01:53:38 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-21 01:53:38 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-21 01:53:38 (4230) [INFO] * 2023-04-21 01:53:38 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-21 01:53:38 (4199) [INFO] * 2023-04-21 01:58:01 (4213) [INFO] * 2023-04-21 01:58:01 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-21 01:58:01 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-21 01:58:01 (4230) [INFO] * 2023-04-21 01:58:01 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-21 01:58:01 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-21 01:58:01 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-21 01:58:01 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-21 01:58:01 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OOK0jbw3uA/ea_profile.json * 2023-04-21 01:58:03 (1805) [INFO] Backed up EA4 profile to /tmp/OOK0jbw3uA/ea_profile.json * 2023-04-21 01:58:03 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-21 02:02:06 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-22 01:48:45 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-22 01:48:48 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-22 01:48:48 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-22 01:51:02 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-22 01:51:02 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-22 01:51:03 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-22 01:51:03 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-22 01:51:03 (3686) [INFO] Checking if your system is up to date: * 2023-04-22 01:51:03 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-22 01:51:03 (4199) [INFO] * 2023-04-22 01:51:03 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-22 01:51:04 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-22 01:51:04 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-22 01:51:04 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-22 01:51:04 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-22 01:51:04 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-22 01:51:04 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-22 01:51:04 (4230) [INFO] * 2023-04-22 01:51:04 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-22 01:51:04 (4199) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] One of the configured repositories failed (Unknown), * 2023-04-22 01:51:59 (4213) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-22 01:51:59 (4213) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-22 01:51:59 (4213) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-22 01:51:59 (4213) [INFO] distribution release than is supported by the repository (and the * 2023-04-22 01:51:59 (4213) [INFO] packages for the previous distribution release still work). * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-22 01:51:59 (4213) [INFO] yum --disablerepo= ... * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-22 01:51:59 (4213) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-22 01:51:59 (4213) [INFO] again or use --enablerepo for temporary usage: * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] yum-config-manager --disable * 2023-04-22 01:51:59 (4213) [INFO] or * 2023-04-22 01:51:59 (4213) [INFO] subscription-manager repos --disable= * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-22 01:51:59 (4213) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-22 01:51:59 (4213) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-22 01:51:59 (4213) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-22 01:51:59 (4213) [INFO] compromise: * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-22 01:51:59 (4213) [INFO] * 2023-04-22 01:51:59 (4213) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-22 01:51:59 (4230) [INFO] * 2023-04-22 01:51:59 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-22 01:51:59 (3709) [INFO] Checking /scripts/sysup * 2023-04-22 01:51:59 (4198) [INFO] Running: /scripts/sysup * 2023-04-22 01:51:59 (4199) [INFO] * 2023-04-22 01:52:00 (4213) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-22 01:52:02 (4213) [INFO] All Needed Packages are already installed. * 2023-04-22 01:52:02 (4230) [INFO] * 2023-04-22 01:52:02 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-22 01:52:02 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-22 01:52:02 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xmeZDONuwj/ea_profile.json * 2023-04-22 01:56:04 (1805) [INFO] Backed up EA4 profile to /tmp/xmeZDONuwj/ea_profile.json * 2023-04-22 01:56:04 (2856) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-22 02:00:07 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-23 01:50:30 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-23 01:50:33 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-23 01:50:33 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-23 01:53:00 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-23 01:53:00 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-04-23 01:53:00 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-23 01:53:00 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-23 01:53:00 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-23 01:53:01 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-23 01:53:01 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-23 01:53:01 (3686) [INFO] Checking if your system is up to date: * 2023-04-23 01:53:01 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-23 01:53:01 (4199) [INFO] * 2023-04-23 01:53:02 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-23 01:53:02 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-23 01:53:02 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-23 01:53:02 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-23 01:53:02 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-23 01:53:02 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-23 01:53:02 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-23 01:53:02 (4230) [INFO] * 2023-04-23 01:53:02 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-23 01:53:02 (4199) [INFO] * 2023-04-23 01:56:36 (4213) [INFO] * 2023-04-23 01:56:36 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-23 01:56:36 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-23 01:56:36 (4230) [INFO] * 2023-04-23 01:56:36 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-23 01:56:36 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-23 01:56:36 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-23 01:56:36 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-23 01:56:36 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9YdhJg8wEA/ea_profile.json * 2023-04-23 01:56:38 (1805) [INFO] Backed up EA4 profile to /tmp/9YdhJg8wEA/ea_profile.json * 2023-04-23 01:56:38 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-23 02:00:41 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-24 01:49:21 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-24 01:49:24 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-24 01:49:24 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-24 01:52:09 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-24 01:52:09 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-04-24 01:52:09 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-24 01:52:09 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-24 01:52:09 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-24 01:52:10 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-24 01:52:10 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-24 01:52:10 (3686) [INFO] Checking if your system is up to date: * 2023-04-24 01:52:10 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-24 01:52:10 (4199) [INFO] * 2023-04-24 01:52:10 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-24 01:52:10 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-24 01:52:10 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-24 01:52:10 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-24 01:52:10 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-24 01:52:11 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-24 01:52:11 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-24 01:52:11 (4230) [INFO] * 2023-04-24 01:52:11 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-24 01:52:11 (4199) [INFO] * 2023-04-24 01:56:16 (4213) [INFO] * 2023-04-24 01:56:16 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-24 01:56:16 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-24 01:56:17 (4230) [INFO] * 2023-04-24 01:56:17 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-24 01:56:17 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-24 01:56:17 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-24 01:56:17 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-24 01:56:17 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kBmeQbq14h/ea_profile.json * 2023-04-24 01:56:19 (1805) [INFO] Backed up EA4 profile to /tmp/kBmeQbq14h/ea_profile.json * 2023-04-24 01:56:19 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-24 02:00:22 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-25 01:49:17 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-25 01:49:20 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-25 01:49:20 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-25 01:52:02 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-25 01:52:02 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-25 01:52:03 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-25 01:52:03 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-25 01:52:03 (3686) [INFO] Checking if your system is up to date: * 2023-04-25 01:52:03 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-25 01:52:03 (4199) [INFO] * 2023-04-25 01:52:03 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-25 01:52:03 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-25 01:52:03 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-25 01:52:03 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-25 01:52:03 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-25 01:52:04 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-25 01:52:04 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-25 01:52:04 (4230) [INFO] * 2023-04-25 01:52:04 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-25 01:52:04 (4199) [INFO] * 2023-04-25 01:56:06 (4213) [INFO] * 2023-04-25 01:56:06 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-25 01:56:06 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-25 01:56:07 (4230) [INFO] * 2023-04-25 01:56:07 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-25 01:56:07 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-25 01:56:07 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-25 01:56:07 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-25 01:56:07 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LQmmLtCKO1/ea_profile.json * 2023-04-25 01:56:09 (1805) [INFO] Backed up EA4 profile to /tmp/LQmmLtCKO1/ea_profile.json * 2023-04-25 01:56:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-25 02:00:12 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-26 01:50:12 (2856) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-26 01:50:14 (3796) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-26 01:50:14 (2856) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. Consider reporting this limitation to https://github.com/cpanel/elevate/issues * 2023-04-26 01:52:57 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-04-26 01:52:57 (3854) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-04-26 01:52:57 (2856) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-04-26 01:52:57 (3880) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-04-26 01:52:57 (2856) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-04-26 01:52:58 (3723) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-04-26 01:52:58 (2856) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-04-26 01:52:58 (3686) [INFO] Checking if your system is up to date: * 2023-04-26 01:52:58 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-26 01:52:58 (4199) [INFO] * 2023-04-26 01:52:59 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-26 01:52:59 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-26 01:52:59 (4213) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-26 01:52:59 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-26 01:52:59 (4213) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-26 01:53:00 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-26 01:53:00 (4213) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-26 01:53:00 (4230) [INFO] * 2023-04-26 01:53:00 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-26 01:53:00 (4199) [INFO] * 2023-04-26 01:57:32 (4213) [INFO] * 2023-04-26 01:57:32 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-26 01:57:32 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-26 01:57:32 (4230) [INFO] * 2023-04-26 01:57:32 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-26 01:57:32 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-26 01:57:32 (2856) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-04-26 01:57:32 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-26 01:57:32 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LEe2LtKrVF/ea_profile.json * 2023-04-26 01:57:34 (1805) [INFO] Backed up EA4 profile to /tmp/LEe2LtKrVF/ea_profile.json * 2023-04-26 01:57:34 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems - ea-ruby24-runtime * 2023-04-26 02:01:37 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-27 01:46:15 (410) [INFO] Self-update of script version 7 requested. * 2023-04-27 01:50:15 (415) [INFO] Newer version of script found. Downloading. * 2023-04-27 01:54:17 (424) [INFO] Script update to version 8 successful. * 2023-04-27 01:58:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-04-27 01:58:21 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-27 01:58:21 (1573) [INFO] Checking if your system is up to date: * 2023-04-27 01:58:21 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-27 01:58:21 (3854) [INFO] * 2023-04-27 01:58:21 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-27 01:58:22 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-27 01:58:22 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-27 01:58:22 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-27 01:58:22 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-27 01:58:22 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-27 01:58:22 (3884) [INFO] * 2023-04-27 01:58:22 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-27 01:58:22 (3854) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] One of the configured repositories failed (Unknown), * 2023-04-27 01:59:17 (3867) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-04-27 01:59:17 (3867) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-04-27 01:59:17 (3867) [INFO] upstream. This is most often useful if you are using a newer * 2023-04-27 01:59:17 (3867) [INFO] distribution release than is supported by the repository (and the * 2023-04-27 01:59:17 (3867) [INFO] packages for the previous distribution release still work). * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] 3. Run the command with the repository temporarily disabled * 2023-04-27 01:59:17 (3867) [INFO] yum --disablerepo= ... * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-04-27 01:59:17 (3867) [INFO] will then just ignore the repository until you permanently enable it * 2023-04-27 01:59:17 (3867) [INFO] again or use --enablerepo for temporary usage: * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] yum-config-manager --disable * 2023-04-27 01:59:17 (3867) [INFO] or * 2023-04-27 01:59:17 (3867) [INFO] subscription-manager repos --disable= * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-04-27 01:59:17 (3867) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-04-27 01:59:17 (3867) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-04-27 01:59:17 (3867) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-04-27 01:59:17 (3867) [INFO] compromise: * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-04-27 01:59:17 (3867) [INFO] * 2023-04-27 01:59:17 (3867) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-04-27 01:59:17 (3884) [INFO] * 2023-04-27 01:59:17 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-27 01:59:17 (1594) [INFO] Checking /scripts/sysup * 2023-04-27 01:59:17 (3853) [INFO] Running: /scripts/sysup * 2023-04-27 01:59:17 (3854) [INFO] * 2023-04-27 01:59:18 (3867) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-04-27 01:59:20 (3867) [INFO] All Needed Packages are already installed. * 2023-04-27 01:59:20 (3884) [INFO] * 2023-04-27 01:59:22 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-27 01:59:22 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-04-27 01:59:22 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-28 01:58:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-04-28 01:58:41 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-28 01:58:41 (1573) [INFO] Checking if your system is up to date: * 2023-04-28 01:58:41 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-28 01:58:41 (3854) [INFO] * 2023-04-28 01:58:41 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-28 01:58:41 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-28 01:58:41 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-28 01:58:41 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-28 01:58:41 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-28 01:58:42 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-28 01:58:42 (3884) [INFO] * 2023-04-28 01:58:42 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-28 01:58:42 (3854) [INFO] * 2023-04-28 02:03:10 (3867) [INFO] * 2023-04-28 02:03:10 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-28 02:03:10 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-28 02:03:10 (3884) [INFO] * 2023-04-28 02:03:10 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-28 02:03:10 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-28 02:03:15 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-28 02:03:15 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-04-28 02:03:15 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-29 01:59:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-04-29 01:59:42 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-29 01:59:42 (1573) [INFO] Checking if your system is up to date: * 2023-04-29 01:59:42 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-29 01:59:42 (3854) [INFO] * 2023-04-29 01:59:42 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-29 01:59:43 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-29 01:59:43 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-29 01:59:43 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-29 01:59:43 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-29 01:59:43 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-29 01:59:43 (3884) [INFO] * 2023-04-29 01:59:43 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-29 01:59:43 (3854) [INFO] * 2023-04-29 02:03:57 (3867) [INFO] * 2023-04-29 02:03:57 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-29 02:03:57 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-29 02:03:58 (3884) [INFO] * 2023-04-29 02:03:58 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-29 02:03:58 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-29 02:04:01 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-29 02:04:01 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-04-29 02:04:01 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-30 01:59:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-04-30 01:59:34 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-30 01:59:34 (1573) [INFO] Checking if your system is up to date: * 2023-04-30 01:59:34 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-30 01:59:34 (3854) [INFO] * 2023-04-30 01:59:34 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-30 01:59:34 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-04-30 01:59:34 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-30 01:59:34 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-04-30 01:59:34 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-04-30 01:59:34 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-04-30 01:59:35 (3884) [INFO] * 2023-04-30 01:59:35 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-30 01:59:35 (3854) [INFO] * 2023-04-30 02:03:26 (3867) [INFO] * 2023-04-30 02:03:26 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-30 02:03:26 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-30 02:03:26 (3884) [INFO] * 2023-04-30 02:03:26 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-30 02:03:26 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-30 02:03:30 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-04-30 02:03:30 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-04-30 02:03:30 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-01 01:58:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-01 01:58:05 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-01 01:58:05 (1573) [INFO] Checking if your system is up to date: * 2023-05-01 01:58:05 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-01 01:58:05 (3854) [INFO] * 2023-05-01 01:58:05 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-01 01:58:05 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-01 01:58:05 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-01 01:58:05 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-05-01 01:58:05 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-01 01:58:06 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-01 01:58:06 (3884) [INFO] * 2023-05-01 01:58:06 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-01 01:58:06 (3854) [INFO] * 2023-05-01 02:02:24 (3867) [INFO] * 2023-05-01 02:02:24 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-01 02:02:24 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-01 02:02:24 (3884) [INFO] * 2023-05-01 02:02:24 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-01 02:02:24 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-01 02:02:27 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-01 02:02:28 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-05-01 02:02:28 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-02 02:01:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-02 02:01:47 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-02 02:01:47 (1573) [INFO] Checking if your system is up to date: * 2023-05-02 02:01:47 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-02 02:01:47 (3854) [INFO] * 2023-05-02 02:01:48 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-02 02:01:48 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-02 02:01:48 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-02 02:01:48 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-05-02 02:01:48 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-02 02:01:49 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-02 02:01:49 (3884) [INFO] * 2023-05-02 02:01:49 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-02 02:01:49 (3854) [INFO] * 2023-05-02 02:06:04 (3867) [INFO] * 2023-05-02 02:06:04 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-02 02:06:04 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-02 02:06:04 (3884) [INFO] * 2023-05-02 02:06:04 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-02 02:06:04 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-02 02:06:07 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-02 02:06:07 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-05-02 02:06:07 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-03 01:55:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-03 01:55:11 (144) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-03 01:55:11 (1573) [INFO] Checking if your system is up to date: * 2023-05-03 01:55:11 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-03 01:55:11 (3854) [INFO] * 2023-05-03 01:55:11 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-03 01:55:11 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-03 01:55:11 (3867) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-03 01:55:11 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 updates * 2023-05-03 01:55:11 (3867) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-03 01:55:12 (3867) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-03 01:55:12 (3884) [INFO] * 2023-05-03 01:55:12 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-03 01:55:12 (3854) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] One of the configured repositories failed (Unknown), * 2023-05-03 01:56:11 (3867) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-03 01:56:11 (3867) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-03 01:56:11 (3867) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-03 01:56:11 (3867) [INFO] distribution release than is supported by the repository (and the * 2023-05-03 01:56:11 (3867) [INFO] packages for the previous distribution release still work). * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-03 01:56:11 (3867) [INFO] yum --disablerepo= ... * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-03 01:56:11 (3867) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-03 01:56:11 (3867) [INFO] again or use --enablerepo for temporary usage: * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] yum-config-manager --disable * 2023-05-03 01:56:11 (3867) [INFO] or * 2023-05-03 01:56:11 (3867) [INFO] subscription-manager repos --disable= * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-03 01:56:11 (3867) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-03 01:56:11 (3867) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-03 01:56:11 (3867) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-03 01:56:11 (3867) [INFO] compromise: * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-03 01:56:11 (3867) [INFO] * 2023-05-03 01:56:11 (3867) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-03 01:56:11 (3884) [INFO] * 2023-05-03 01:56:11 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-03 01:56:11 (1594) [INFO] Checking /scripts/sysup * 2023-05-03 01:56:11 (3853) [INFO] Running: /scripts/sysup * 2023-05-03 01:56:11 (3854) [INFO] * 2023-05-03 01:56:12 (3867) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-03 01:56:14 (3867) [INFO] All Needed Packages are already installed. * 2023-05-03 01:56:14 (3884) [INFO] * 2023-05-03 01:56:17 (1498) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-03 01:56:17 (278) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 101. * 2023-05-03 01:56:17 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-04 02:00:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-04 02:00:57 (145) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-04 02:00:57 (1625) [INFO] Checking if your system is up to date: * 2023-05-04 02:00:57 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-04 02:00:57 (3906) [INFO] * 2023-05-04 02:00:58 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-04 02:00:58 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-04 02:00:58 (3919) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-04 02:00:58 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-04 02:00:58 (3919) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-04 02:00:58 (3919) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-04 02:00:58 (3919) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-04 02:00:59 (3936) [INFO] * 2023-05-04 02:00:59 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-04 02:00:59 (3906) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] One of the configured repositories failed (Unknown), * 2023-05-04 02:01:54 (3919) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-04 02:01:54 (3919) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-04 02:01:54 (3919) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-04 02:01:54 (3919) [INFO] distribution release than is supported by the repository (and the * 2023-05-04 02:01:54 (3919) [INFO] packages for the previous distribution release still work). * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-04 02:01:54 (3919) [INFO] yum --disablerepo= ... * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-04 02:01:54 (3919) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-04 02:01:54 (3919) [INFO] again or use --enablerepo for temporary usage: * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] yum-config-manager --disable * 2023-05-04 02:01:54 (3919) [INFO] or * 2023-05-04 02:01:54 (3919) [INFO] subscription-manager repos --disable= * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-04 02:01:54 (3919) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-04 02:01:54 (3919) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-04 02:01:54 (3919) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-04 02:01:54 (3919) [INFO] compromise: * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-04 02:01:54 (3919) [INFO] * 2023-05-04 02:01:54 (3919) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-04 02:01:54 (3936) [INFO] * 2023-05-04 02:01:54 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-04 02:01:54 (1646) [INFO] Checking /scripts/sysup * 2023-05-04 02:01:54 (3905) [INFO] Running: /scripts/sysup * 2023-05-04 02:01:54 (3906) [INFO] * 2023-05-04 02:01:55 (3919) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-04 02:01:57 (3919) [INFO] All Needed Packages are already installed. * 2023-05-04 02:01:57 (3936) [INFO] * 2023-05-04 02:02:00 (1550) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-04 02:02:00 (1561) [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-04 02:02:00 (1561) [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-04 02:02:00 (1561) [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-04 02:02:00 (1561) [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-04 02:02:00 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102. * 2023-05-04 02:02:00 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-05 01:57:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-05 01:58:01 (145) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-05 01:58:01 (1625) [INFO] Checking if your system is up to date: * 2023-05-05 01:58:01 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-05 01:58:01 (3906) [INFO] * 2023-05-05 01:58:01 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-05 01:58:02 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-05 01:58:02 (3919) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-05 01:58:02 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-05 01:58:02 (3919) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-05 01:58:02 (3919) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-05 01:58:02 (3919) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-05 01:58:02 (3936) [INFO] * 2023-05-05 01:58:02 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-05 01:58:02 (3906) [INFO] * 2023-05-05 02:02:26 (3919) [INFO] * 2023-05-05 02:02:26 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-05 02:02:26 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-05 02:02:26 (3936) [INFO] * 2023-05-05 02:02:26 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-05 02:02:26 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-05 02:02:29 (1550) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-05 02:02:29 (1561) [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-05 02:02:29 (1561) [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-05 02:02:29 (1561) [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-05 02:02:29 (1561) [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-05 02:02:29 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102. * 2023-05-05 02:02:29 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-06 01:59:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-06 01:59:52 (145) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-06 01:59:52 (1625) [INFO] Checking if your system is up to date: * 2023-05-06 01:59:52 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-06 01:59:52 (3906) [INFO] * 2023-05-06 01:59:53 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-06 01:59:53 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-06 01:59:53 (3919) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-06 01:59:53 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-06 01:59:53 (3919) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-06 01:59:53 (3919) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-06 01:59:53 (3919) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-06 01:59:53 (3936) [INFO] * 2023-05-06 01:59:53 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-06 01:59:53 (3906) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] One of the configured repositories failed (Unknown), * 2023-05-06 02:00:48 (3919) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-06 02:00:48 (3919) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-06 02:00:48 (3919) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-06 02:00:48 (3919) [INFO] distribution release than is supported by the repository (and the * 2023-05-06 02:00:48 (3919) [INFO] packages for the previous distribution release still work). * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-06 02:00:48 (3919) [INFO] yum --disablerepo= ... * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-06 02:00:48 (3919) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-06 02:00:48 (3919) [INFO] again or use --enablerepo for temporary usage: * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] yum-config-manager --disable * 2023-05-06 02:00:48 (3919) [INFO] or * 2023-05-06 02:00:48 (3919) [INFO] subscription-manager repos --disable= * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-06 02:00:48 (3919) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-06 02:00:48 (3919) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-06 02:00:48 (3919) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-06 02:00:48 (3919) [INFO] compromise: * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-06 02:00:48 (3919) [INFO] * 2023-05-06 02:00:48 (3919) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-06 02:00:49 (3936) [INFO] * 2023-05-06 02:00:49 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-06 02:00:49 (1646) [INFO] Checking /scripts/sysup * 2023-05-06 02:00:49 (3905) [INFO] Running: /scripts/sysup * 2023-05-06 02:00:49 (3906) [INFO] * 2023-05-06 02:00:49 (3919) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-06 02:00:51 (3919) [INFO] All Needed Packages are already installed. * 2023-05-06 02:00:51 (3936) [INFO] * 2023-05-06 02:00:55 (1550) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-06 02:00:55 (1561) [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-06 02:00:55 (1561) [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-06 02:00:55 (1561) [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-06 02:00:55 (1561) [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-06 02:00:55 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102. * 2023-05-06 02:00:55 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-07 01:58:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-07 01:58:59 (145) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-07 01:58:59 (1625) [INFO] Checking if your system is up to date: * 2023-05-07 01:58:59 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-07 01:58:59 (3906) [INFO] * 2023-05-07 01:58:59 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-07 01:58:59 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-07 01:58:59 (3919) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-07 01:58:59 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-07 01:58:59 (3919) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-07 01:58:59 (3919) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-07 01:59:00 (3919) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-07 01:59:00 (3936) [INFO] * 2023-05-07 01:59:00 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-07 01:59:00 (3906) [INFO] * 2023-05-07 02:03:10 (3919) [INFO] * 2023-05-07 02:03:10 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-07 02:03:10 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-07 02:03:10 (3936) [INFO] * 2023-05-07 02:03:10 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-07 02:03:10 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-07 02:03:13 (1550) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-07 02:03:13 (1561) [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-07 02:03:13 (1561) [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-07 02:03:13 (1561) [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-07 02:03:13 (1561) [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-07 02:03:13 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102. * 2023-05-07 02:03:13 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-08 01:55:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-08 01:55:08 (145) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-08 01:55:08 (1625) [INFO] Checking if your system is up to date: * 2023-05-08 01:55:08 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-08 01:55:08 (3906) [INFO] * 2023-05-08 01:55:08 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-08 01:55:09 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-08 01:55:09 (3919) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-08 01:55:09 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-08 01:55:09 (3919) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-08 01:55:09 (3919) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-08 01:55:09 (3919) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-08 01:55:09 (3936) [INFO] * 2023-05-08 01:55:09 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-08 01:55:09 (3906) [INFO] * 2023-05-08 01:59:31 (3919) [INFO] * 2023-05-08 01:59:31 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-08 01:59:31 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-08 01:59:31 (3936) [INFO] * 2023-05-08 01:59:31 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-08 01:59:31 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-08 01:59:34 (1550) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-08 01:59:34 (1561) [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-08 01:59:34 (1561) [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-08 01:59:34 (1561) [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-08 01:59:34 (1561) [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-08 01:59:34 (280) [WARN] Unknown error while checking blockers: Missing blockers at /usr/local/cpanel/scripts/elevate-cpanel line 102. * 2023-05-08 01:59:34 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-09 01:58:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-09 01:58:12 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-09 01:58:12 (1659) [INFO] Checking if your system is up to date: * 2023-05-09 01:58:12 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-09 01:58:12 (3975) [INFO] * 2023-05-09 01:58:13 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-09 01:58:13 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-09 01:58:13 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-09 01:58:13 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-09 01:58:13 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-09 01:58:13 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-09 01:58:13 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-09 01:58:14 (4005) [INFO] * 2023-05-09 01:58:14 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-09 01:58:14 (3975) [INFO] * 2023-05-09 02:01:24 (3988) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/76992398ac29e791064104a09414d80ee4c969ab50d2396b311c373a4d3fd920-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-05-09 02:01:24 (3988) [INFO] Trying other mirror. * 2023-05-09 02:01:24 (3988) [INFO] To address this issue please refer to the below wiki article * 2023-05-09 02:01:24 (3988) [INFO] * 2023-05-09 02:01:24 (3988) [INFO] https://wiki.centos.org/yum-errors * 2023-05-09 02:01:24 (3988) [INFO] * 2023-05-09 02:01:24 (3988) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-05-09 02:01:24 (3988) [INFO] * 2023-05-09 02:02:21 (3988) [INFO] * 2023-05-09 02:02:21 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-09 02:02:21 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-09 02:02:22 (4005) [INFO] * 2023-05-09 02:02:22 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-09 02:02:22 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-09 02:02:25 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-09 02:02: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-09 02:02: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-09 02:02: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-09 02:02: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-09 02:02:25 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-09 02:05:43 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-09 02:05:43 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-09 02:05:44 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-09 02:05:44 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-09 02:05:44 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-09 02:05:44 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-09 02:05:44 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2mY8TQhYj2/ea_profile.json * 2023-05-09 02:05:46 (2159) [INFO] Backed up EA4 profile to /tmp/2mY8TQhYj2/ea_profile.json * 2023-05-09 02:05:50 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-10 01:57:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-10 01:57:46 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-10 01:57:46 (1659) [INFO] Checking if your system is up to date: * 2023-05-10 01:57:46 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-10 01:57:46 (3975) [INFO] * 2023-05-10 01:57:47 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-10 01:57:47 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-10 01:57:47 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-10 01:57:47 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-10 01:57:47 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-10 01:57:47 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-10 01:57:47 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-10 01:57:47 (4005) [INFO] * 2023-05-10 01:57:47 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-10 01:57:47 (3975) [INFO] * 2023-05-10 02:02:11 (3988) [INFO] * 2023-05-10 02:02:11 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-10 02:02:11 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-10 02:02:12 (4005) [INFO] * 2023-05-10 02:02:12 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-10 02:02:12 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-10 02:02:15 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-10 02:02:15 (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 02:02:15 (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 02:02:15 (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 02:02:15 (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 02:02:15 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-10 02:05:54 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-10 02:05:54 (1526) [ERROR] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/3c4a4cb658c5a71bc15aa135246b9c1348ec17652361a9ed7d42ef75c4b6049f-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/a5302cd78ef1454dd991a02399a426896b7cf9b4aeb17368efeec7afb5dde5fd-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/e793cde01b9f701dee6821342a497d7b2e280649d9bcae3fd206abe66d1b118f-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/5f430871331f226e452d9f27373a06c601f48e99694fddc3f7612348339097ce-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/e793cde01b9f701dee6821342a497d7b2e280649d9bcae3fd206abe66d1b118f-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/a5302cd78ef1454dd991a02399a426896b7cf9b4aeb17368efeec7afb5dde5fd-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2023-05-10 02:05:54 (148) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-10 02:05:54 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-10 02:05:54 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-10 02:05:55 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-10 02:05:55 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-10 02:05:55 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-10 02:05:55 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-10 02:05:55 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JBtP16Wh3g/ea_profile.json * 2023-05-10 02:05:57 (2159) [INFO] Backed up EA4 profile to /tmp/JBtP16Wh3g/ea_profile.json * 2023-05-10 02:06:00 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-11 02:02:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-11 02:02:51 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-11 02:02:51 (1659) [INFO] Checking if your system is up to date: * 2023-05-11 02:02:51 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-11 02:02:51 (3975) [INFO] * 2023-05-11 02:02:52 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-11 02:02:52 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-11 02:02:52 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-11 02:02:52 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-11 02:02:52 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-11 02:02:52 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-11 02:02:52 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-11 02:02:52 (4005) [INFO] * 2023-05-11 02:02:52 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-11 02:02:52 (3975) [INFO] * 2023-05-11 02:07:02 (3988) [INFO] * 2023-05-11 02:07:02 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-11 02:07:02 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-11 02:07:02 (4005) [INFO] * 2023-05-11 02:07:02 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-11 02:07:02 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-11 02:07:06 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-11 02:07:06 (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 02:07:06 (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 02:07:06 (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 02:07:06 (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 02:07:06 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-11 02:11:23 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-11 02:11:23 (1526) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5e92ca0e619b4990e16b94bfec59815137e1a6b7d9cd469f01cdd217c6ad3f60-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5e92ca0e619b4990e16b94bfec59815137e1a6b7d9cd469f01cdd217c6ad3f60-filelists.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/34885748d9746d7db58cd5b164cb7bb75f4c3b247544e0f33262a980951d6a9b-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/34885748d9746d7db58cd5b164cb7bb75f4c3b247544e0f33262a980951d6a9b-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds') Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5e92ca0e619b4990e16b94bfec59815137e1a6b7d9cd469f01cdd217c6ad3f60-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5e92ca0e619b4990e16b94bfec59815137e1a6b7d9cd469f01cdd217c6ad3f60-filelists.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') Trying other mirror. * 2023-05-11 02:11:23 (148) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-11 02:11:23 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-11 02:11:23 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-11 02:11:24 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-11 02:11:24 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-11 02:11:24 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-11 02:11:24 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-11 02:11:24 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XKhNXSjmxf/ea_profile.json * 2023-05-11 02:11:27 (2159) [INFO] Backed up EA4 profile to /tmp/XKhNXSjmxf/ea_profile.json * 2023-05-11 02:11:29 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-12 02:07:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-12 02:07:56 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-12 02:07:56 (1659) [INFO] Checking if your system is up to date: * 2023-05-12 02:07:56 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-12 02:07:56 (3975) [INFO] * 2023-05-12 02:07:57 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-12 02:07:57 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-12 02:07:57 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-12 02:07:57 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-12 02:07:57 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-12 02:07:57 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-12 02:07:58 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-12 02:07:58 (4005) [INFO] * 2023-05-12 02:07:58 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-12 02:07:58 (3975) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] One of the configured repositories failed (Unknown), * 2023-05-12 02:09:03 (3988) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-12 02:09:03 (3988) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-12 02:09:03 (3988) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-12 02:09:03 (3988) [INFO] distribution release than is supported by the repository (and the * 2023-05-12 02:09:03 (3988) [INFO] packages for the previous distribution release still work). * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-12 02:09:03 (3988) [INFO] yum --disablerepo= ... * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-12 02:09:03 (3988) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-12 02:09:03 (3988) [INFO] again or use --enablerepo for temporary usage: * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] yum-config-manager --disable * 2023-05-12 02:09:03 (3988) [INFO] or * 2023-05-12 02:09:03 (3988) [INFO] subscription-manager repos --disable= * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-12 02:09:03 (3988) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-12 02:09:03 (3988) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-12 02:09:03 (3988) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-12 02:09:03 (3988) [INFO] compromise: * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-12 02:09:03 (3988) [INFO] * 2023-05-12 02:09:03 (3988) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-12 02:09:03 (4005) [INFO] * 2023-05-12 02:09:03 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-12 02:09:03 (1680) [INFO] Checking /scripts/sysup * 2023-05-12 02:09:03 (3974) [INFO] Running: /scripts/sysup * 2023-05-12 02:09:03 (3975) [INFO] * 2023-05-12 02:09:04 (3988) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-12 02:09:06 (3988) [INFO] All Needed Packages are already installed. * 2023-05-12 02:09:06 (4005) [INFO] * 2023-05-12 02:09:09 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-12 02:09:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-12 02:09:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-12 02:09:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-12 02:09:09 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-12 02:09:09 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-12 02:10:04 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-12 02:10:04 (1526) [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-05-12 02:10:04 (148) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-12 02:10:04 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-12 02:10:04 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-12 02:10:05 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-12 02:10:05 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-12 02:10:05 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-12 02:10:05 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-12 02:10:05 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QEGLoPdqN9/ea_profile.json * 2023-05-12 02:13:16 (2159) [INFO] Backed up EA4 profile to /tmp/QEGLoPdqN9/ea_profile.json * 2023-05-12 02:13:20 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-13 01:57:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-13 01:57:47 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-13 01:57:47 (1659) [INFO] Checking if your system is up to date: * 2023-05-13 01:57:47 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-13 01:57:47 (3975) [INFO] * 2023-05-13 01:57:48 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-13 01:57:48 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-13 01:57:48 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-13 01:57:48 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-13 01:57:48 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-13 01:57:48 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-13 01:57:49 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-13 01:57:49 (4005) [INFO] * 2023-05-13 01:57:49 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-13 01:57:49 (3975) [INFO] * 2023-05-13 01:59:59 (3988) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30000 milliseconds') * 2023-05-13 01:59:59 (3988) [INFO] Trying other mirror. * 2023-05-13 02:00:49 (3988) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/02e1056c0ac6f6e713205d08e03aebf5790c123ced96d68ad7c1b6e398485afb-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-13 02:00:49 (3988) [INFO] Trying other mirror. * 2023-05-13 02:00:49 (3988) [INFO] To address this issue please refer to the below wiki article * 2023-05-13 02:00:49 (3988) [INFO] * 2023-05-13 02:00:49 (3988) [INFO] https://wiki.centos.org/yum-errors * 2023-05-13 02:00:49 (3988) [INFO] * 2023-05-13 02:00:49 (3988) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-05-13 02:00:49 (3988) [INFO] * 2023-05-13 02:01:43 (3988) [INFO] * 2023-05-13 02:01:43 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-13 02:01:43 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-13 02:01:44 (4005) [INFO] * 2023-05-13 02:01:44 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-13 02:01:44 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-13 02:01:47 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-13 02:01:47 (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 02:01:47 (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 02:01:47 (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 02:01:47 (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 02:01:47 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-13 02:04:47 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-13 02:04:47 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-13 02:04:48 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-13 02:04:48 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-13 02:04:48 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-13 02:04:48 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-13 02:04:48 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7hhJ5wds32/ea_profile.json * 2023-05-13 02:04:50 (2159) [INFO] Backed up EA4 profile to /tmp/7hhJ5wds32/ea_profile.json * 2023-05-13 02:04:54 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-14 01:55:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-14 01:55:59 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-14 01:55:59 (1659) [INFO] Checking if your system is up to date: * 2023-05-14 01:55:59 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-14 01:55:59 (3975) [INFO] * 2023-05-14 01:55:59 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-14 01:56:00 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-14 01:56:00 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-14 01:56:00 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-14 01:56:00 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-14 01:56:00 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-14 01:56:00 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-14 01:56:00 (4005) [INFO] * 2023-05-14 01:56:00 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-14 01:56:00 (3975) [INFO] * 2023-05-14 01:59:24 (3988) [INFO] * 2023-05-14 01:59:24 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-14 01:59:24 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-14 01:59:24 (4005) [INFO] * 2023-05-14 01:59:24 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-14 01:59:24 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-14 01:59:27 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-14 01:59: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-14 01:59: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-14 01:59: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-14 01:59: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-14 01:59:27 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-14 02:02:17 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-14 02:02:17 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-14 02:02:18 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-14 02:02:18 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-14 02:02:18 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-14 02:02:18 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-14 02:02:18 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H5CClKKxo3/ea_profile.json * 2023-05-14 02:02:20 (2159) [INFO] Backed up EA4 profile to /tmp/H5CClKKxo3/ea_profile.json * 2023-05-14 02:02:24 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-15 01:51:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-15 01:51:41 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-15 01:51:41 (1659) [INFO] Checking if your system is up to date: * 2023-05-15 01:51:41 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-15 01:51:41 (3975) [INFO] * 2023-05-15 01:51:41 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-15 01:51:41 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-15 01:51:41 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-15 01:51:41 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-15 01:51:41 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-15 01:51:41 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-15 01:51:41 (3988) [INFO] Other repos take up 712 k of disk space (use --verbose for details) * 2023-05-15 01:51:41 (4005) [INFO] * 2023-05-15 01:51:41 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-15 01:51:41 (3975) [INFO] * 2023-05-15 01:55:36 (3988) [INFO] * 2023-05-15 01:55:36 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-15 01:55:36 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-15 01:55:36 (4005) [INFO] * 2023-05-15 01:55:36 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-15 01:55:36 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-15 01:55:40 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-15 01:55:40 (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 01:55:40 (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 01:55:40 (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 01:55:40 (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 01:55:40 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-15 01:58:36 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-15 01:58:36 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-15 01:58:37 (1083) [WARN] JetBackup version 4.1.3-3 currently installed. * 2023-05-15 01:58:37 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-15 01:58:37 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-15 01:58:37 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-15 01:58:37 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qTuTbLvcWq/ea_profile.json * 2023-05-15 01:58:40 (2159) [INFO] Backed up EA4 profile to /tmp/qTuTbLvcWq/ea_profile.json * 2023-05-15 01:58:43 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-16 01:51:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-16 01:51:42 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-16 01:51:42 (1659) [INFO] Checking if your system is up to date: * 2023-05-16 01:51:42 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-16 01:51:42 (3975) [INFO] * 2023-05-16 01:51:43 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-16 01:51:43 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-16 01:51:43 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-16 01:51:43 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-16 01:51:43 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-16 01:51:43 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-16 01:51:43 (3988) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-16 01:51:43 (4005) [INFO] * 2023-05-16 01:51:43 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-16 01:51:43 (3975) [INFO] * 2023-05-16 01:55:57 (3988) [INFO] * 2023-05-16 01:55:57 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-16 01:55:57 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-16 01:55:58 (4005) [INFO] * 2023-05-16 01:55:58 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-16 01:55:58 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-16 01:56:01 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-16 01:56:01 (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 01:56:01 (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 01:56:01 (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 01:56:01 (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 01:56:01 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-16 01:59:22 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-16 01:59:22 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-16 01:59:23 (1083) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-16 01:59:23 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-16 01:59:23 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-16 01:59:23 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-16 01:59:23 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QlHQYjnqij/ea_profile.json * 2023-05-16 01:59:25 (2159) [INFO] Backed up EA4 profile to /tmp/QlHQYjnqij/ea_profile.json * 2023-05-16 01:59:28 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-17 01:56:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-17 01:56:59 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-17 01:56:59 (1659) [INFO] Checking if your system is up to date: * 2023-05-17 01:56:59 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-17 01:56:59 (3975) [INFO] * 2023-05-17 01:57:00 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-17 01:57:00 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-17 01:57:00 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-17 01:57:00 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-17 01:57:00 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-17 01:57:00 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-17 01:57:00 (3988) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-17 01:57:00 (4005) [INFO] * 2023-05-17 01:57:00 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-17 01:57:00 (3975) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] One of the configured repositories failed (Unknown), * 2023-05-17 01:57:55 (3988) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-17 01:57:55 (3988) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-17 01:57:55 (3988) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-17 01:57:55 (3988) [INFO] distribution release than is supported by the repository (and the * 2023-05-17 01:57:55 (3988) [INFO] packages for the previous distribution release still work). * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-17 01:57:55 (3988) [INFO] yum --disablerepo= ... * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-17 01:57:55 (3988) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-17 01:57:55 (3988) [INFO] again or use --enablerepo for temporary usage: * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] yum-config-manager --disable * 2023-05-17 01:57:55 (3988) [INFO] or * 2023-05-17 01:57:55 (3988) [INFO] subscription-manager repos --disable= * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-17 01:57:55 (3988) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-17 01:57:55 (3988) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-17 01:57:55 (3988) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-17 01:57:55 (3988) [INFO] compromise: * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-17 01:57:55 (3988) [INFO] * 2023-05-17 01:57:55 (3988) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-17 01:57:55 (4005) [INFO] * 2023-05-17 01:57:55 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-17 01:57:55 (1680) [INFO] Checking /scripts/sysup * 2023-05-17 01:57:55 (3974) [INFO] Running: /scripts/sysup * 2023-05-17 01:57:55 (3975) [INFO] * 2023-05-17 01:57:56 (3988) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-17 01:57:58 (3988) [INFO] All Needed Packages are already installed. * 2023-05-17 01:57:58 (4005) [INFO] * 2023-05-17 01:58:01 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-17 01:58:01 (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 01:58:01 (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 01:58:01 (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 01:58:01 (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 01:58:01 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-17 02:05:30 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-17 02:05:30 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-17 02:05:31 (1083) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-17 02:05:31 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-17 02:05:31 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-17 02:05:31 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-17 02:05:31 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mchjoBe8zo/ea_profile.json * 2023-05-17 02:05:33 (2159) [INFO] Backed up EA4 profile to /tmp/mchjoBe8zo/ea_profile.json * 2023-05-17 02:05:36 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-18 00:58:25 (148) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-18 00:58:25 (1659) [INFO] Checking if your system is up to date: * 2023-05-18 00:58:25 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-18 00:58:25 (3975) [INFO] * 2023-05-18 00:58:26 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-18 00:58:26 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-18 00:58:26 (3988) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-18 00:58:26 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-18 00:58:26 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-18 00:58:26 (3988) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-18 00:58:27 (3988) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-18 00:58:27 (4005) [INFO] * 2023-05-18 00:58:27 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-18 00:58:27 (3975) [INFO] * 2023-05-18 01:02:34 (3988) [INFO] * 2023-05-18 01:02:34 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-18 01:02:34 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-18 01:02:35 (4005) [INFO] * 2023-05-18 01:02:35 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-18 01:02:35 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-18 01:02:37 (1584) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-18 01:02:37 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-18 01:02:37 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-18 01:02:37 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-18 01:02:37 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation * 2023-05-18 01:02:37 (148) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-18 01:05:58 (1727) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-18 01:05:58 (148) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-18 01:05:59 (1083) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-18 01:05:59 (148) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-18 01:05:59 (148) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-18 01:05:59 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-18 01:05:59 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ghGvQiOXHg/ea_profile.json * 2023-05-18 01:06:01 (2159) [INFO] Backed up EA4 profile to /tmp/ghGvQiOXHg/ea_profile.json * 2023-05-18 01:06:04 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-19 01:59:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-19 01:59:37 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-19 01:59:37 (1699) [INFO] Checking if your system is up to date: * 2023-05-19 01:59:37 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-19 01:59:37 (4086) [INFO] * 2023-05-19 01:59:37 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-19 01:59:38 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-19 01:59:38 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-19 01:59:38 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-19 01:59:38 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-19 01:59:38 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-19 01:59:38 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-19 01:59:38 (4116) [INFO] * 2023-05-19 01:59:38 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-19 01:59:38 (4086) [INFO] * 2023-05-19 02:04:09 (4099) [INFO] * 2023-05-19 02:04:09 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-19 02:04:09 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-19 02:04:09 (4116) [INFO] * 2023-05-19 02:04:09 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-19 02:04:09 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-19 02:04:13 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-19 02:04:13 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-19 02:07:32 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-19 02:07:32 (1566) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-05-19 02:07:32 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-19 02:07:32 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-19 02:07:32 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-19 02:07:33 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-19 02:07:33 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-19 02:07:33 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-19 02:07:33 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-19 02:07:33 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ESfC2fUk34/ea_profile.json * 2023-05-19 02:07:36 (2258) [INFO] Backed up EA4 profile to /tmp/ESfC2fUk34/ea_profile.json * 2023-05-19 02:07:39 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-20 02:00:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-20 02:00:55 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-20 02:00:55 (1699) [INFO] Checking if your system is up to date: * 2023-05-20 02:00:55 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-20 02:00:55 (4086) [INFO] * 2023-05-20 02:00:55 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-20 02:00:55 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-20 02:00:55 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-20 02:00:55 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-20 02:00:55 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-20 02:00:55 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-20 02:00:56 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-20 02:00:56 (4116) [INFO] * 2023-05-20 02:00:56 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-20 02:00:56 (4086) [INFO] * 2023-05-20 02:05:22 (4099) [INFO] * 2023-05-20 02:05:22 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-20 02:05:22 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-20 02:05:23 (4116) [INFO] * 2023-05-20 02:05:23 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-20 02:05:23 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-20 02:05:26 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-20 02:05:26 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-20 02:09:02 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-20 02:09:02 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-20 02:09:03 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-20 02:09:03 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-20 02:09:03 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-20 02:09:03 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-20 02:09:03 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q6ZXiJTuo7/ea_profile.json * 2023-05-20 02:09:05 (2258) [INFO] Backed up EA4 profile to /tmp/q6ZXiJTuo7/ea_profile.json * 2023-05-20 02:09:09 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-21 01:58:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-21 01:58:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-21 01:58:20 (1699) [INFO] Checking if your system is up to date: * 2023-05-21 01:58:20 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-21 01:58:20 (4086) [INFO] * 2023-05-21 01:58:20 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-21 01:58:21 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-21 01:58:21 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-21 01:58:21 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-21 01:58:21 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-21 01:58:21 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-21 01:58:21 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-21 01:58:21 (4116) [INFO] * 2023-05-21 01:58:21 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-21 01:58:21 (4086) [INFO] * 2023-05-21 02:02:29 (4099) [INFO] * 2023-05-21 02:02:29 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-21 02:02:29 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-21 02:02:29 (4116) [INFO] * 2023-05-21 02:02:29 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-21 02:02:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-21 02:02:32 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-21 02:02:32 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-21 02:05:46 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-21 02:05:46 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-21 02:05:47 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-21 02:05:47 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-21 02:05:47 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-21 02:05:47 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-21 02:05:47 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vPl9DkCmH5/ea_profile.json * 2023-05-21 02:05:49 (2258) [INFO] Backed up EA4 profile to /tmp/vPl9DkCmH5/ea_profile.json * 2023-05-21 02:05:53 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-22 01:57:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-22 01:57:18 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-22 01:57:18 (1699) [INFO] Checking if your system is up to date: * 2023-05-22 01:57:18 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-22 01:57:18 (4086) [INFO] * 2023-05-22 01:57:19 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-22 01:57:19 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-22 01:57:19 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-22 01:57:19 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-22 01:57:19 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-22 01:57:19 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-22 01:57:20 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-22 01:57:20 (4116) [INFO] * 2023-05-22 01:57:20 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-22 01:57:20 (4086) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-22 01:58:15 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-22 01:58:15 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-22 01:58:15 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-22 01:58:15 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-22 01:58:15 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-22 01:58:15 (4099) [INFO] yum --disablerepo= ... * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-22 01:58:15 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-22 01:58:15 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] yum-config-manager --disable * 2023-05-22 01:58:15 (4099) [INFO] or * 2023-05-22 01:58:15 (4099) [INFO] subscription-manager repos --disable= * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-22 01:58:15 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-22 01:58:15 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-22 01:58:15 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-22 01:58:15 (4099) [INFO] compromise: * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-22 01:58:15 (4099) [INFO] * 2023-05-22 01:58:15 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-22 01:58:15 (4116) [INFO] * 2023-05-22 01:58:15 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-22 01:58:15 (1720) [INFO] Checking /scripts/sysup * 2023-05-22 01:58:15 (4085) [INFO] Running: /scripts/sysup * 2023-05-22 01:58:15 (4086) [INFO] * 2023-05-22 01:58:16 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-22 01:58:17 (4099) [INFO] All Needed Packages are already installed. * 2023-05-22 01:58:17 (4116) [INFO] * 2023-05-22 01:58:21 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-22 01:58:21 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-22 01:59:17 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-22 01:59:17 (1566) [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-05-22 01:59:17 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-22 01:59:17 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-22 01:59:17 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-22 01:59:18 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-22 01:59:18 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-22 01:59:18 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-22 01:59:18 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-22 01:59:18 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yoZvjSFCEi/ea_profile.json * 2023-05-22 02:03:34 (2258) [INFO] Backed up EA4 profile to /tmp/yoZvjSFCEi/ea_profile.json * 2023-05-22 02:03:38 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-23 02:01:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-23 02:01:32 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-23 02:01:32 (1699) [INFO] Checking if your system is up to date: * 2023-05-23 02:01:32 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-23 02:01:32 (4086) [INFO] * 2023-05-23 02:01:33 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-23 02:01:33 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-23 02:01:33 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-23 02:01:33 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-23 02:01:33 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-23 02:01:33 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-23 02:01:34 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-23 02:01:34 (4116) [INFO] * 2023-05-23 02:01:34 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-23 02:01:34 (4086) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-23 02:02:28 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-23 02:02:28 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-23 02:02:28 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-23 02:02:28 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-23 02:02:28 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-23 02:02:28 (4099) [INFO] yum --disablerepo= ... * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-23 02:02:28 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-23 02:02:28 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] yum-config-manager --disable * 2023-05-23 02:02:28 (4099) [INFO] or * 2023-05-23 02:02:28 (4099) [INFO] subscription-manager repos --disable= * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-23 02:02:28 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-23 02:02:28 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-23 02:02:28 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-23 02:02:28 (4099) [INFO] compromise: * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-23 02:02:28 (4099) [INFO] * 2023-05-23 02:02:28 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-23 02:02:28 (4116) [INFO] * 2023-05-23 02:02:28 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-23 02:02:28 (1720) [INFO] Checking /scripts/sysup * 2023-05-23 02:02:28 (4085) [INFO] Running: /scripts/sysup * 2023-05-23 02:02:28 (4086) [INFO] * 2023-05-23 02:02:29 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-23 02:02:31 (4099) [INFO] All Needed Packages are already installed. * 2023-05-23 02:02:31 (4116) [INFO] * 2023-05-23 02:02:34 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-23 02:02:34 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-23 02:09:21 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-23 02:09:21 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-23 02:09:22 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-23 02:09:22 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-23 02:09:22 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-23 02:09:22 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-23 02:09:22 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/voxK9dXlEM/ea_profile.json * 2023-05-23 02:09:24 (2258) [INFO] Backed up EA4 profile to /tmp/voxK9dXlEM/ea_profile.json * 2023-05-23 02:09:27 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-24 01:51:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-24 01:51:42 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-24 01:51:42 (1699) [INFO] Checking if your system is up to date: * 2023-05-24 01:51:42 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-24 01:51:42 (4086) [INFO] * 2023-05-24 01:51:43 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-24 01:51:43 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-24 01:51:43 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-24 01:51:43 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-24 01:51:43 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-24 01:51:43 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-24 01:51:43 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-24 01:51:43 (4116) [INFO] * 2023-05-24 01:51:43 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-24 01:51:43 (4086) [INFO] * 2023-05-24 01:55:50 (4099) [INFO] * 2023-05-24 01:55:50 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-24 01:55:50 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-24 01:55:50 (4116) [INFO] * 2023-05-24 01:55:50 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-24 01:55:50 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-24 01:55:52 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-24 01:55:53 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-24 01:59:13 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-24 01:59:13 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-24 01:59:13 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-24 01:59:13 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-24 01:59:13 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-24 01:59:13 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-24 01:59:13 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XlpaKMY0jx/ea_profile.json * 2023-05-24 01:59:16 (2258) [INFO] Backed up EA4 profile to /tmp/XlpaKMY0jx/ea_profile.json * 2023-05-24 01:59:19 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-25 01:55:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-25 01:55:16 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-25 01:55:16 (1699) [INFO] Checking if your system is up to date: * 2023-05-25 01:55:16 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-25 01:55:16 (4086) [INFO] * 2023-05-25 01:55:17 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-25 01:55:17 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-25 01:55:17 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-25 01:55:17 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-25 01:55:17 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-25 01:55:17 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-25 01:55:17 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-25 01:55:17 (4116) [INFO] * 2023-05-25 01:55:17 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-25 01:55:17 (4086) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-25 01:56:13 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-25 01:56:13 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-25 01:56:13 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-25 01:56:13 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-25 01:56:13 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-25 01:56:13 (4099) [INFO] yum --disablerepo= ... * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-25 01:56:13 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-25 01:56:13 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] yum-config-manager --disable * 2023-05-25 01:56:13 (4099) [INFO] or * 2023-05-25 01:56:13 (4099) [INFO] subscription-manager repos --disable= * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-25 01:56:13 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-25 01:56:13 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-25 01:56:13 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-25 01:56:13 (4099) [INFO] compromise: * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-25 01:56:13 (4099) [INFO] * 2023-05-25 01:56:13 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-25 01:56:13 (4116) [INFO] * 2023-05-25 01:56:13 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-25 01:56:13 (1720) [INFO] Checking /scripts/sysup * 2023-05-25 01:56:13 (4085) [INFO] Running: /scripts/sysup * 2023-05-25 01:56:13 (4086) [INFO] * 2023-05-25 01:56:14 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-25 01:56:16 (4099) [INFO] All Needed Packages are already installed. * 2023-05-25 01:56:16 (4116) [INFO] * 2023-05-25 01:56:20 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-25 01:56:20 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-25 02:03:23 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-25 02:03:23 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-25 02:03:24 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-25 02:03:24 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-25 02:03:24 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-25 02:03:24 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-25 02:03:24 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/baFKA4NT30/ea_profile.json * 2023-05-25 02:03:26 (2258) [INFO] Backed up EA4 profile to /tmp/baFKA4NT30/ea_profile.json * 2023-05-25 02:03:30 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-26 01:57:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-26 01:57:31 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-26 01:57:31 (1699) [INFO] Checking if your system is up to date: * 2023-05-26 01:57:31 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-26 01:57:31 (4086) [INFO] * 2023-05-26 01:57:32 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-26 01:57:32 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-26 01:57:32 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-26 01:57:32 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-26 01:57:32 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-26 01:57:32 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-26 01:57:33 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-26 01:57:33 (4116) [INFO] * 2023-05-26 01:57:33 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-26 01:57:33 (4086) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-26 01:58:28 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-26 01:58:28 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-26 01:58:28 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-26 01:58:28 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-26 01:58:28 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-26 01:58:28 (4099) [INFO] yum --disablerepo= ... * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-26 01:58:28 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-26 01:58:28 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] yum-config-manager --disable * 2023-05-26 01:58:28 (4099) [INFO] or * 2023-05-26 01:58:28 (4099) [INFO] subscription-manager repos --disable= * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-26 01:58:28 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-26 01:58:28 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-26 01:58:28 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-26 01:58:28 (4099) [INFO] compromise: * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-26 01:58:28 (4099) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-26 01:58:28 (4116) [INFO] * 2023-05-26 01:58:28 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-26 01:58:28 (1720) [INFO] Checking /scripts/sysup * 2023-05-26 01:58:28 (4085) [INFO] Running: /scripts/sysup * 2023-05-26 01:58:28 (4086) [INFO] * 2023-05-26 01:58:28 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-26 01:58:31 (4099) [INFO] All Needed Packages are already installed. * 2023-05-26 01:58:31 (4116) [INFO] * 2023-05-26 01:58:34 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-26 01:58:34 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-26 02:05:36 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-26 02:05:36 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-26 02:05:37 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-26 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-26 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-26 02:05:37 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-26 02:05:37 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F9FF59ZvMx/ea_profile.json * 2023-05-26 02:05:39 (2258) [INFO] Backed up EA4 profile to /tmp/F9FF59ZvMx/ea_profile.json * 2023-05-26 02:05:43 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-27 01:02:17 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-27 01:02:17 (1699) [INFO] Checking if your system is up to date: * 2023-05-27 01:02:17 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-27 01:02:17 (4086) [INFO] * 2023-05-27 01:02:18 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-27 01:02:18 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-27 01:02:18 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-27 01:02:18 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-27 01:02:18 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-27 01:02:18 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-27 01:02:19 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-27 01:02:19 (4116) [INFO] * 2023-05-27 01:02:19 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-27 01:02:19 (4086) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-27 01:03:14 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-27 01:03:14 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-27 01:03:14 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-27 01:03:14 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-27 01:03:14 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-27 01:03:14 (4099) [INFO] yum --disablerepo= ... * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-27 01:03:14 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-27 01:03:14 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] yum-config-manager --disable * 2023-05-27 01:03:14 (4099) [INFO] or * 2023-05-27 01:03:14 (4099) [INFO] subscription-manager repos --disable= * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-27 01:03:14 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-27 01:03:14 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-27 01:03:14 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-27 01:03:14 (4099) [INFO] compromise: * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-27 01:03:14 (4099) [INFO] * 2023-05-27 01:03:14 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-27 01:03:14 (4116) [INFO] * 2023-05-27 01:03:14 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-27 01:03:14 (1720) [INFO] Checking /scripts/sysup * 2023-05-27 01:03:14 (4085) [INFO] Running: /scripts/sysup * 2023-05-27 01:03:14 (4086) [INFO] * 2023-05-27 01:03:15 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-27 01:03:17 (4099) [INFO] All Needed Packages are already installed. * 2023-05-27 01:03:17 (4116) [INFO] * 2023-05-27 01:03:22 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-27 01:03:22 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-27 01:10:00 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-27 01:10:00 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-27 01:10:01 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-27 01:10:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-27 01:10:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-27 01:10:01 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-27 01:10:01 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X58JH8vjAg/ea_profile.json * 2023-05-27 01:10:04 (2258) [INFO] Backed up EA4 profile to /tmp/X58JH8vjAg/ea_profile.json * 2023-05-27 01:10:08 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-28 01:59:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-28 01:59:02 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-28 01:59:02 (1699) [INFO] Checking if your system is up to date: * 2023-05-28 01:59:02 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-28 01:59:02 (4086) [INFO] * 2023-05-28 01:59:03 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-28 01:59:03 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-28 01:59:03 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-28 01:59:03 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-28 01:59:03 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-28 01:59:03 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-28 01:59:04 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-28 01:59:04 (4116) [INFO] * 2023-05-28 01:59:04 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-28 01:59:04 (4086) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-28 01:59:59 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-28 01:59:59 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-28 01:59:59 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-28 01:59:59 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-28 01:59:59 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-28 01:59:59 (4099) [INFO] yum --disablerepo= ... * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-28 01:59:59 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-28 01:59:59 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] yum-config-manager --disable * 2023-05-28 01:59:59 (4099) [INFO] or * 2023-05-28 01:59:59 (4099) [INFO] subscription-manager repos --disable= * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-28 01:59:59 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-28 01:59:59 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-28 01:59:59 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-28 01:59:59 (4099) [INFO] compromise: * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-28 01:59:59 (4099) [INFO] * 2023-05-28 01:59:59 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-28 01:59:59 (4116) [INFO] * 2023-05-28 01:59:59 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-28 01:59:59 (1720) [INFO] Checking /scripts/sysup * 2023-05-28 01:59:59 (4085) [INFO] Running: /scripts/sysup * 2023-05-28 01:59:59 (4086) [INFO] * 2023-05-28 02:00:00 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-28 02:00:02 (4099) [INFO] All Needed Packages are already installed. * 2023-05-28 02:00:02 (4116) [INFO] * 2023-05-28 02:00:07 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-28 02:00:07 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-28 02:01:01 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-28 02:01:01 (1566) [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-05-28 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-28 02:01:01 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-28 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-28 02:01:02 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-28 02:01:02 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-28 02:01:02 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-28 02:01:02 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-28 02:01:02 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F81Cwjz1cZ/ea_profile.json * 2023-05-28 02:05:07 (2258) [INFO] Backed up EA4 profile to /tmp/F81Cwjz1cZ/ea_profile.json * 2023-05-28 02:05:10 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-29 01:57:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-29 01:57:55 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-29 01:57:55 (1699) [INFO] Checking if your system is up to date: * 2023-05-29 01:57:55 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-29 01:57:55 (4086) [INFO] * 2023-05-29 01:57:55 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-29 01:57:56 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-29 01:57:56 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-29 01:57:56 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-29 01:57:56 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-29 01:57:56 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-29 01:57:56 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-29 01:57:56 (4116) [INFO] * 2023-05-29 01:57:56 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-29 01:57:56 (4086) [INFO] * 2023-05-29 02:02:03 (4099) [INFO] * 2023-05-29 02:02:03 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-29 02:02:03 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-29 02:02:04 (4116) [INFO] * 2023-05-29 02:02:04 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-29 02:02:04 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-29 02:02:07 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-29 02:02:07 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-29 02:05:25 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-29 02:05:25 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-29 02:05:26 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-29 02:05:26 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-29 02:05:26 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-29 02:05:26 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-29 02:05:26 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Srf44qHfIC/ea_profile.json * 2023-05-29 02:05:28 (2258) [INFO] Backed up EA4 profile to /tmp/Srf44qHfIC/ea_profile.json * 2023-05-29 02:05:32 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-30 01:58:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-30 01:58:16 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-30 01:58:16 (1699) [INFO] Checking if your system is up to date: * 2023-05-30 01:58:16 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-30 01:58:16 (4086) [INFO] * 2023-05-30 01:58:16 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-30 01:58:17 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-30 01:58:17 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-30 01:58:17 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-30 01:58:17 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-30 01:58:17 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-30 01:58:17 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-30 01:58:17 (4116) [INFO] * 2023-05-30 01:58:17 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-30 01:58:17 (4086) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-30 01:59:12 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-30 01:59:12 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-30 01:59:12 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-30 01:59:12 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-30 01:59:12 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-30 01:59:12 (4099) [INFO] yum --disablerepo= ... * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-30 01:59:12 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-30 01:59:12 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] yum-config-manager --disable * 2023-05-30 01:59:12 (4099) [INFO] or * 2023-05-30 01:59:12 (4099) [INFO] subscription-manager repos --disable= * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-30 01:59:12 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-30 01:59:12 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-30 01:59:12 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-30 01:59:12 (4099) [INFO] compromise: * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-30 01:59:12 (4099) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-30 01:59:12 (4116) [INFO] * 2023-05-30 01:59:12 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-30 01:59:12 (1720) [INFO] Checking /scripts/sysup * 2023-05-30 01:59:12 (4085) [INFO] Running: /scripts/sysup * 2023-05-30 01:59:12 (4086) [INFO] * 2023-05-30 01:59:12 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-30 01:59:14 (4099) [INFO] All Needed Packages are already installed. * 2023-05-30 01:59:14 (4116) [INFO] * 2023-05-30 01:59:17 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-30 01:59:17 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-30 02:00:12 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-30 02:00:12 (1566) [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-05-30 02:00:12 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-30 02:00:12 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-30 02:00:12 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-30 02:00:13 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-30 02:00:13 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-30 02:00:13 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-30 02:00:13 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-30 02:00:13 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hCp69JAL0G/ea_profile.json * 2023-05-30 02:04:26 (2258) [INFO] Backed up EA4 profile to /tmp/hCp69JAL0G/ea_profile.json * 2023-05-30 02:04:28 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-31 02:02:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-05-31 02:02:34 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-31 02:02:34 (1699) [INFO] Checking if your system is up to date: * 2023-05-31 02:02:34 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-31 02:02:34 (4086) [INFO] * 2023-05-31 02:02:34 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-31 02:02:35 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-05-31 02:02:35 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-31 02:02:35 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-31 02:02:35 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-31 02:02:35 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-05-31 02:02:35 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-05-31 02:02:35 (4116) [INFO] * 2023-05-31 02:02:35 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-31 02:02:35 (4086) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] One of the configured repositories failed (Unknown), * 2023-05-31 02:03:30 (4099) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-05-31 02:03:30 (4099) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-05-31 02:03:30 (4099) [INFO] upstream. This is most often useful if you are using a newer * 2023-05-31 02:03:30 (4099) [INFO] distribution release than is supported by the repository (and the * 2023-05-31 02:03:30 (4099) [INFO] packages for the previous distribution release still work). * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] 3. Run the command with the repository temporarily disabled * 2023-05-31 02:03:30 (4099) [INFO] yum --disablerepo= ... * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-05-31 02:03:30 (4099) [INFO] will then just ignore the repository until you permanently enable it * 2023-05-31 02:03:30 (4099) [INFO] again or use --enablerepo for temporary usage: * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] yum-config-manager --disable * 2023-05-31 02:03:30 (4099) [INFO] or * 2023-05-31 02:03:30 (4099) [INFO] subscription-manager repos --disable= * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-05-31 02:03:30 (4099) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-05-31 02:03:30 (4099) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-05-31 02:03:30 (4099) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-05-31 02:03:30 (4099) [INFO] compromise: * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-05-31 02:03:30 (4099) [INFO] * 2023-05-31 02:03:30 (4099) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-05-31 02:03:30 (4116) [INFO] * 2023-05-31 02:03:30 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-31 02:03:30 (1720) [INFO] Checking /scripts/sysup * 2023-05-31 02:03:30 (4085) [INFO] Running: /scripts/sysup * 2023-05-31 02:03:30 (4086) [INFO] * 2023-05-31 02:03:31 (4099) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-05-31 02:03:33 (4099) [INFO] All Needed Packages are already installed. * 2023-05-31 02:03:33 (4116) [INFO] * 2023-05-31 02:03:36 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-05-31 02:03:36 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-05-31 02:04:30 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-31 02:04:30 (1566) [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-05-31 02:04:30 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-31 02:04:30 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-05-31 02:04:30 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-05-31 02:04:31 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-05-31 02:04:31 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-05-31 02:04:31 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-05-31 02:04:31 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-31 02:04:31 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D1_71OxLmF/ea_profile.json * 2023-05-31 02:08:49 (2258) [INFO] Backed up EA4 profile to /tmp/D1_71OxLmF/ea_profile.json * 2023-05-31 02:08:52 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-06-01 01:59:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-01 01:59:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-01 01:59:05 (1699) [INFO] Checking if your system is up to date: * 2023-06-01 01:59:05 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-06-01 01:59:05 (4086) [INFO] * 2023-06-01 01:59:05 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-01 01:59:05 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-01 01:59:05 (4099) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-01 01:59:05 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-01 01:59:05 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-01 01:59:05 (4099) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-01 01:59:06 (4099) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-01 01:59:06 (4116) [INFO] * 2023-06-01 01:59:06 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-01 01:59:06 (4086) [INFO] * 2023-06-01 02:03:20 (4099) [INFO] * 2023-06-01 02:03:20 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-01 02:03:20 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-01 02:03:21 (4116) [INFO] * 2023-06-01 02:03:21 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-01 02:03:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-01 02:03:24 (1624) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-01 02:03:24 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-01 02:06:44 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-01 02:06:44 (1566) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-06-01 02:06:44 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-01 02:06:44 (1767) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-01 02:06:44 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-01 02:06:45 (1119) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-01 02:06:45 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-01 02:06:45 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-01 02:06:45 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-01 02:06:45 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HIZ5ulASwS/ea_profile.json * 2023-06-01 02:06:47 (2258) [INFO] Backed up EA4 profile to /tmp/HIZ5ulASwS/ea_profile.json * 2023-06-01 02:06:51 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-06-02 01:57:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-02 01:57:49 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-02 01:57:49 (1700) [INFO] Checking if your system is up to date: * 2023-06-02 01:57:49 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-02 01:57:49 (4089) [INFO] * 2023-06-02 01:57:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-02 01:57:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-02 01:57:50 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-02 01:57:50 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-02 01:57:50 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-02 01:57:50 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-02 01:57:51 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-02 01:57:51 (4119) [INFO] * 2023-06-02 01:57:51 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-02 01:57:51 (4089) [INFO] * 2023-06-02 02:01:50 (4102) [INFO] * 2023-06-02 02:01:50 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-02 02:01:50 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-02 02:01:50 (4119) [INFO] * 2023-06-02 02:01:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-02 02:01:50 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-02 02:01:53 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-02 02:01:53 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-02 02:04:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-02 02:04:58 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-02 02:04:58 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-02 02:04:58 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-02 02:04:58 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-02 02:04:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-02 02:04:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hDlbsEOfo2/ea_profile.json * 2023-06-02 02:05:01 (2259) [INFO] Backed up EA4 profile to /tmp/hDlbsEOfo2/ea_profile.json * 2023-06-02 02:05:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-03 02:00:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-03 02:00:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-03 02:00:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-03 02:00:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-03 02:00:06 (4089) [INFO] * 2023-06-03 02:00:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-03 02:00:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-03 02:00:07 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-03 02:00:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-03 02:00:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-03 02:00:07 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-03 02:00:07 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-03 02:00:07 (4119) [INFO] * 2023-06-03 02:00:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-03 02:00:07 (4089) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-03 02:01:02 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-03 02:01:02 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-03 02:01:02 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-03 02:01:02 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-03 02:01:02 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-03 02:01:02 (4102) [INFO] yum --disablerepo= ... * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-03 02:01:02 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-03 02:01:02 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] yum-config-manager --disable * 2023-06-03 02:01:02 (4102) [INFO] or * 2023-06-03 02:01:02 (4102) [INFO] subscription-manager repos --disable= * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-03 02:01:02 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-03 02:01:02 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-03 02:01:02 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-03 02:01:02 (4102) [INFO] compromise: * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-03 02:01:02 (4102) [INFO] * 2023-06-03 02:01:02 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-03 02:01:02 (4119) [INFO] * 2023-06-03 02:01:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-03 02:01:02 (1721) [INFO] Checking /scripts/sysup * 2023-06-03 02:01:02 (4088) [INFO] Running: /scripts/sysup * 2023-06-03 02:01:02 (4089) [INFO] * 2023-06-03 02:01:03 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-03 02:01:05 (4102) [INFO] All Needed Packages are already installed. * 2023-06-03 02:01:05 (4119) [INFO] * 2023-06-03 02:01:09 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-03 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-03 02:08:20 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-03 02:08:20 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-03 02:08:21 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-03 02:08:21 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-03 02:08:21 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-03 02:08:21 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-03 02:08:21 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ARi4N8jO8k/ea_profile.json * 2023-06-03 02:08:23 (2259) [INFO] Backed up EA4 profile to /tmp/ARi4N8jO8k/ea_profile.json * 2023-06-03 02:08:27 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-04 01:55:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-04 01:56:01 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-04 01:56:01 (1700) [INFO] Checking if your system is up to date: * 2023-06-04 01:56:01 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-04 01:56:01 (4089) [INFO] * 2023-06-04 01:56:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-04 01:56:02 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-04 01:56:02 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-04 01:56:02 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-04 01:56:02 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-04 01:56:02 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-04 01:56:02 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-04 01:56:02 (4119) [INFO] * 2023-06-04 01:56:02 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-04 01:56:02 (4089) [INFO] * 2023-06-04 01:59:33 (4102) [INFO] * 2023-06-04 01:59:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-04 01:59:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-04 01:59:34 (4119) [INFO] * 2023-06-04 01:59:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-04 01:59:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-04 01:59:36 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-04 01:59:36 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-04 02:02:28 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-04 02:02:28 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-04 02:02:29 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-04 02:02:29 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-04 02:02:29 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-04 02:02:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-04 02:02:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UFX3iUCBPu/ea_profile.json * 2023-06-04 02:02:31 (2259) [INFO] Backed up EA4 profile to /tmp/UFX3iUCBPu/ea_profile.json * 2023-06-04 02:02:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-05 01:54:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-05 01:54:49 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-05 01:54:49 (1700) [INFO] Checking if your system is up to date: * 2023-06-05 01:54:49 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-05 01:54:49 (4089) [INFO] * 2023-06-05 01:54:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-05 01:54:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-05 01:54:50 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-05 01:54:50 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-05 01:54:50 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-05 01:54:50 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-05 01:54:50 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-05 01:54:50 (4119) [INFO] * 2023-06-05 01:54:50 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-05 01:54:50 (4089) [INFO] * 2023-06-05 01:58:19 (4102) [INFO] * 2023-06-05 01:58:19 (4102) [INFO] imunify-antivirus.noarch 7.1.3-1 imunify360 * 2023-06-05 01:58:19 (4102) [INFO] imunify-antivirus-cpanel.noarch 7.1.3-1 imunify360 * 2023-06-05 01:58:19 (4102) [INFO] imunify-common.x86_64 1.2.4-2.el7 imunify360 * 2023-06-05 01:58:19 (4102) [INFO] imunify360-venv.x86_64 2.1.0-1 imunify360 * 2023-06-05 01:58:19 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-05 01:58:19 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-05 01:58:19 (4119) [INFO] * 2023-06-05 01:58:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-05 01:58:19 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-05 01:58:22 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-05 01:58:22 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-05 02:01:08 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-05 02:01:08 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-05 02:01:09 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-05 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-05 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-05 02:01:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-05 02:01:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fyydBTrpZE/ea_profile.json * 2023-06-05 02:01:11 (2259) [INFO] Backed up EA4 profile to /tmp/fyydBTrpZE/ea_profile.json * 2023-06-05 02:01:15 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-06 01:58:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-06 01:58:54 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-06 01:58:54 (1700) [INFO] Checking if your system is up to date: * 2023-06-06 01:58:54 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-06 01:58:54 (4089) [INFO] * 2023-06-06 01:58:54 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-06 01:58:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-06 01:58:55 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-06 01:58:55 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-06 01:58:55 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-06 01:58:55 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-06 01:58:55 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-06 01:58:55 (4119) [INFO] * 2023-06-06 01:58:55 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-06 01:58:55 (4089) [INFO] * 2023-06-06 02:02:08 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/873e0867fdf5f655e57b1860286623f0470ab32e6aead49dad97e9ac08918354-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-06-06 02:02:08 (4102) [INFO] Trying other mirror. * 2023-06-06 02:02:08 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-06-06 02:02:08 (4102) [INFO] * 2023-06-06 02:02:08 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-06-06 02:02:08 (4102) [INFO] * 2023-06-06 02:02:08 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-06-06 02:02:08 (4102) [INFO] * 2023-06-06 02:02:25 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/873e0867fdf5f655e57b1860286623f0470ab32e6aead49dad97e9ac08918354-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-06-06 02:02:25 (4102) [INFO] Trying other mirror. * 2023-06-06 02:03:16 (4102) [INFO] * 2023-06-06 02:03:16 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-06 02:03:16 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-06 02:03:16 (4119) [INFO] * 2023-06-06 02:03:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-06 02:03:16 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-06 02:03:20 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-06 02:03:20 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-06 02:07:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-06 02:07:16 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/b6c3e953d43c38880d0bc2754aa3b5b48eac7122d727adff026dab39b6a13f2d-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/f15153a455e3ad1fadf866126b7d9633f657fe13343b68e749d5fdb7bceecf24-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/b6c3e953d43c38880d0bc2754aa3b5b48eac7122d727adff026dab39b6a13f2d-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/f15153a455e3ad1fadf866126b7d9633f657fe13343b68e749d5fdb7bceecf24-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. * 2023-06-06 02:07:16 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-06 02:07:16 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-06 02:07:16 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-06 02:07:17 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-06 02:07:17 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-06 02:07:17 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-06 02:07:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-06 02:07:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xB5_45CMWl/ea_profile.json * 2023-06-06 02:07:19 (2259) [INFO] Backed up EA4 profile to /tmp/xB5_45CMWl/ea_profile.json * 2023-06-06 02:07:23 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-07 01:58:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-07 01:58:30 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-07 01:58:30 (1700) [INFO] Checking if your system is up to date: * 2023-06-07 01:58:30 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-07 01:58:30 (4089) [INFO] * 2023-06-07 01:58:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-07 01:58:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-07 01:58:31 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-07 01:58:31 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-07 01:58:31 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-07 01:58:31 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-07 01:58:31 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-07 01:58:31 (4119) [INFO] * 2023-06-07 01:58:31 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-07 01:58:31 (4089) [INFO] * 2023-06-07 02:02:33 (4102) [INFO] * 2023-06-07 02:02:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-07 02:02:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-07 02:02:34 (4119) [INFO] * 2023-06-07 02:02:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-07 02:02:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-07 02:02:37 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-07 02:02:37 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-07 02:05:59 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-07 02:05:59 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-07 02:06:00 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-07 02:06:00 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-07 02:06:00 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-07 02:06:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-07 02:06:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xXoKH5yuCf/ea_profile.json * 2023-06-07 02:06:02 (2259) [INFO] Backed up EA4 profile to /tmp/xXoKH5yuCf/ea_profile.json * 2023-06-07 02:06:05 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-08 01:59:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-08 01:59:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-08 01:59:12 (1700) [INFO] Checking if your system is up to date: * 2023-06-08 01:59:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-08 01:59:12 (4089) [INFO] * 2023-06-08 01:59:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-08 01:59:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-08 01:59:13 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-08 01:59:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-08 01:59:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-08 01:59:13 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-08 01:59:14 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-08 01:59:14 (4119) [INFO] * 2023-06-08 01:59:14 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-08 01:59:14 (4089) [INFO] * 2023-06-08 02:02:41 (4102) [INFO] http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds') * 2023-06-08 02:02:41 (4102) [INFO] Trying other mirror. * 2023-06-08 02:03:13 (4102) [INFO] * 2023-06-08 02:03:13 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-08 02:03:13 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-08 02:03:13 (4119) [INFO] * 2023-06-08 02:03:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-08 02:03:13 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-08 02:03:17 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-08 02:03:17 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-08 02:06:19 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-08 02:06:19 (1567) [ERROR] http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/78c0e5530bc46d128e18eca9ff16b2d0651efdb33434408f8ff1db4d14f1bb99-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. * 2023-06-08 02:06:19 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-08 02:06:19 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-08 02:06:19 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-08 02:06:20 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-08 02:06:20 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-08 02:06:20 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-08 02:06:20 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-08 02:06:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ptPM5BpjdG/ea_profile.json * 2023-06-08 02:06:22 (2259) [INFO] Backed up EA4 profile to /tmp/ptPM5BpjdG/ea_profile.json * 2023-06-08 02:06:25 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-09 01:57:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-09 01:58:00 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-09 01:58:01 (1700) [INFO] Checking if your system is up to date: * 2023-06-09 01:58:01 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-09 01:58:01 (4089) [INFO] * 2023-06-09 01:58:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-09 01:58:01 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-09 01:58:01 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-09 01:58:01 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-09 01:58:01 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-09 01:58:01 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-09 01:58:02 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-09 01:58:02 (4119) [INFO] * 2023-06-09 01:58:02 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-09 01:58:02 (4089) [INFO] * 2023-06-09 02:01:59 (4102) [INFO] * 2023-06-09 02:01:59 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-09 02:01:59 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-09 02:01:59 (4119) [INFO] * 2023-06-09 02:01:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-09 02:01:59 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-09 02:02:03 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-09 02:02:03 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-09 02:05:07 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-09 02:05:07 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-09 02:05:08 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-09 02:05:08 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-09 02:05:08 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-09 02:05:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-09 02:05:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_YUQDhM_Qr/ea_profile.json * 2023-06-09 02:05:10 (2259) [INFO] Backed up EA4 profile to /tmp/_YUQDhM_Qr/ea_profile.json * 2023-06-09 02:05:13 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-10 01:59:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-10 01:59:25 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-10 01:59:25 (1700) [INFO] Checking if your system is up to date: * 2023-06-10 01:59:25 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-10 01:59:25 (4089) [INFO] * 2023-06-10 01:59:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-10 01:59:25 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-10 01:59:25 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-10 01:59:25 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-10 01:59:25 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-10 01:59:25 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-10 01:59:26 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-10 01:59:26 (4119) [INFO] * 2023-06-10 01:59:26 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-10 01:59:26 (4089) [INFO] * 2023-06-10 02:03:40 (4102) [INFO] * 2023-06-10 02:03:40 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-10 02:03:40 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-10 02:03:40 (4119) [INFO] * 2023-06-10 02:03:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-10 02:03:40 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-10 02:03:44 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-10 02:03:44 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-10 02:07:07 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-10 02:07:07 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-10 02:07:07 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-10 02:07:07 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-10 02:07:07 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-10 02:07:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-10 02:07:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AyzJJCpXpj/ea_profile.json * 2023-06-10 02:07:10 (2259) [INFO] Backed up EA4 profile to /tmp/AyzJJCpXpj/ea_profile.json * 2023-06-10 02:07:13 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-11 01:54:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-11 01:54:16 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-11 01:54:16 (1700) [INFO] Checking if your system is up to date: * 2023-06-11 01:54:16 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-11 01:54:16 (4089) [INFO] * 2023-06-11 01:54:16 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-11 01:54:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-11 01:54:17 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-11 01:54:17 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-11 01:54:17 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-11 01:54:17 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-11 01:54:17 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-11 01:54:17 (4119) [INFO] * 2023-06-11 01:54:17 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-11 01:54:17 (4089) [INFO] * 2023-06-11 01:58:08 (4102) [INFO] * 2023-06-11 01:58:08 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-11 01:58:08 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-11 01:58:08 (4119) [INFO] * 2023-06-11 01:58:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-11 01:58:08 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-11 01:58:11 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-11 01:58:11 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-11 02:01:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-11 02:01:00 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-11 02:01:01 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-11 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-11 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-11 02:01:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-11 02:01:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zQDb96Gbtl/ea_profile.json * 2023-06-11 02:01:03 (2259) [INFO] Backed up EA4 profile to /tmp/zQDb96Gbtl/ea_profile.json * 2023-06-11 02:01:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-12 01:51:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-12 01:51:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-12 01:51:10 (1700) [INFO] Checking if your system is up to date: * 2023-06-12 01:51:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-12 01:51:10 (4089) [INFO] * 2023-06-12 01:51:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-12 01:51:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-12 01:51:10 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-12 01:51:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-12 01:51:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-12 01:51:10 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-12 01:51:10 (4102) [INFO] Other repos take up 728 k of disk space (use --verbose for details) * 2023-06-12 01:51:10 (4119) [INFO] * 2023-06-12 01:51:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-12 01:51:10 (4089) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-12 01:52:06 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-12 01:52:06 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-12 01:52:06 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-12 01:52:06 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-12 01:52:06 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-12 01:52:06 (4102) [INFO] yum --disablerepo= ... * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-12 01:52:06 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-12 01:52:06 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] yum-config-manager --disable * 2023-06-12 01:52:06 (4102) [INFO] or * 2023-06-12 01:52:06 (4102) [INFO] subscription-manager repos --disable= * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-12 01:52:06 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-12 01:52:06 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-12 01:52:06 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-12 01:52:06 (4102) [INFO] compromise: * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-12 01:52:06 (4102) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-12 01:52:06 (4119) [INFO] * 2023-06-12 01:52:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-12 01:52:06 (1721) [INFO] Checking /scripts/sysup * 2023-06-12 01:52:06 (4088) [INFO] Running: /scripts/sysup * 2023-06-12 01:52:06 (4089) [INFO] * 2023-06-12 01:52:06 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-12 01:52:08 (4102) [INFO] All Needed Packages are already installed. * 2023-06-12 01:52:08 (4119) [INFO] * 2023-06-12 01:52:11 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-12 01:52:11 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-12 01:58:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-12 01:58:56 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-12 01:58:56 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-12 01:58:56 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-12 01:58:56 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-12 01:58:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-12 01:58:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MSs3ScrtqG/ea_profile.json * 2023-06-12 01:58:59 (2259) [INFO] Backed up EA4 profile to /tmp/MSs3ScrtqG/ea_profile.json * 2023-06-12 01:59:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-13 01:58:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-13 01:58:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-13 01:58:12 (1700) [INFO] Checking if your system is up to date: * 2023-06-13 01:58:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-13 01:58:12 (4089) [INFO] * 2023-06-13 01:58:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-13 01:58:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-13 01:58:13 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-13 01:58:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-13 01:58:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-13 01:58:13 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-13 01:58:13 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-13 01:58:13 (4119) [INFO] * 2023-06-13 01:58:13 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-13 01:58:13 (4089) [INFO] * 2023-06-13 02:02:12 (4102) [INFO] * 2023-06-13 02:02:12 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-13 02:02:12 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-13 02:02:12 (4119) [INFO] * 2023-06-13 02:02:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-13 02:02:12 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-13 02:02:16 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-13 02:02:16 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-13 02:05:19 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-13 02:05:19 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-13 02:05:20 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-13 02:05:20 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-13 02:05:20 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-13 02:05:20 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-13 02:05:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y6CYPSl1e4/ea_profile.json * 2023-06-13 02:05:22 (2259) [INFO] Backed up EA4 profile to /tmp/y6CYPSl1e4/ea_profile.json * 2023-06-13 02:05:26 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-14 01:52:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-14 01:52:57 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-14 01:52:57 (1700) [INFO] Checking if your system is up to date: * 2023-06-14 01:52:57 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-14 01:52:57 (4089) [INFO] * 2023-06-14 01:52:57 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-14 01:52:58 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-14 01:52:58 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-14 01:52:58 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-14 01:52:58 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-14 01:52:58 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-14 01:52:58 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-14 01:52:58 (4119) [INFO] * 2023-06-14 01:52:58 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-14 01:52:58 (4089) [INFO] * 2023-06-14 01:57:20 (4102) [INFO] * 2023-06-14 01:57:20 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-14 01:57:20 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-14 01:57:21 (4119) [INFO] * 2023-06-14 01:57:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-14 01:57:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-14 01:57:24 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-14 01:57:24 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-14 02:01:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-14 02:01:00 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-14 02:01:01 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-14 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-14 02:01:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-14 02:01:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-14 02:01:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HEwTXYa3fg/ea_profile.json * 2023-06-14 02:01:03 (2259) [INFO] Backed up EA4 profile to /tmp/HEwTXYa3fg/ea_profile.json * 2023-06-14 02:01:07 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-15 02:00:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-15 02:00:56 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-15 02:00:56 (1700) [INFO] Checking if your system is up to date: * 2023-06-15 02:00:56 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-15 02:00:56 (4089) [INFO] * 2023-06-15 02:00:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-15 02:00:57 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-15 02:00:57 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-15 02:00:57 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-15 02:00:57 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-15 02:00:57 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-15 02:00:57 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-15 02:00:57 (4119) [INFO] * 2023-06-15 02:00:57 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-15 02:00:57 (4089) [INFO] * 2023-06-15 02:05:06 (4102) [INFO] * 2023-06-15 02:05:06 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-15 02:05:06 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-15 02:05:06 (4119) [INFO] * 2023-06-15 02:05:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-15 02:05:06 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-15 02:05:09 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-15 02:05:09 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-15 02:08:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-15 02:08:49 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-15 02:08:50 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-15 02:08:50 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-15 02:08:50 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-15 02:08:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-15 02:08:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uA_JypRCbI/ea_profile.json * 2023-06-15 02:08:52 (2259) [INFO] Backed up EA4 profile to /tmp/uA_JypRCbI/ea_profile.json * 2023-06-15 02:08:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-16 01:57:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-16 01:57:13 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-16 01:57:13 (1700) [INFO] Checking if your system is up to date: * 2023-06-16 01:57:13 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-16 01:57:13 (4089) [INFO] * 2023-06-16 01:57:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-16 01:57:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-16 01:57:13 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-16 01:57:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-16 01:57:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-16 01:57:13 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-16 01:57:14 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-16 01:57:14 (4119) [INFO] * 2023-06-16 01:57:14 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-16 01:57:14 (4089) [INFO] * 2023-06-16 02:01:19 (4102) [INFO] * 2023-06-16 02:01:19 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-16 02:01:19 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-16 02:01:20 (4119) [INFO] * 2023-06-16 02:01:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-16 02:01:20 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-16 02:01:23 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-16 02:01:23 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-16 02:04:45 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-16 02:04:45 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-06-16 02:04:45 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-16 02:04:45 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-16 02:04:45 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-16 02:04:46 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-16 02:04:46 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-16 02:04:46 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-16 02:04:46 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-16 02:04:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yh0l0MBSpY/ea_profile.json * 2023-06-16 02:04:48 (2259) [INFO] Backed up EA4 profile to /tmp/yh0l0MBSpY/ea_profile.json * 2023-06-16 02:04:52 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-17 01:59:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-17 01:59:56 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-17 01:59:56 (1700) [INFO] Checking if your system is up to date: * 2023-06-17 01:59:56 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-17 01:59:56 (4089) [INFO] * 2023-06-17 01:59:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-17 01:59:57 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-17 01:59:57 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-17 01:59:57 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-17 01:59:57 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-17 01:59:57 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-17 01:59:57 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-17 01:59:57 (4119) [INFO] * 2023-06-17 01:59:57 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-17 01:59:57 (4089) [INFO] * 2023-06-17 02:04:26 (4102) [INFO] * 2023-06-17 02:04:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-17 02:04:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-17 02:04:26 (4119) [INFO] * 2023-06-17 02:04:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-17 02:04:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-17 02:04:30 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-17 02:04:30 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-17 02:08:09 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-17 02:08:09 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-17 02:08:10 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-17 02:08:10 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-17 02:08:10 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-17 02:08:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-17 02:08:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ImrCqlJndS/ea_profile.json * 2023-06-17 02:08:12 (2259) [INFO] Backed up EA4 profile to /tmp/ImrCqlJndS/ea_profile.json * 2023-06-17 02:08:16 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-18 02:00:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-18 02:00:46 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-18 02:00:46 (1700) [INFO] Checking if your system is up to date: * 2023-06-18 02:00:46 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-18 02:00:46 (4089) [INFO] * 2023-06-18 02:00:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-18 02:00:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-18 02:00:47 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-18 02:00:47 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-18 02:00:47 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-18 02:00:47 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-18 02:00:47 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-18 02:00:47 (4119) [INFO] * 2023-06-18 02:00:47 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-18 02:00:47 (4089) [INFO] * 2023-06-18 02:05:11 (4102) [INFO] * 2023-06-18 02:05:11 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-18 02:05:11 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-18 02:05:11 (4119) [INFO] * 2023-06-18 02:05:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-18 02:05:11 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-18 02:05:14 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-18 02:05:14 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-18 02:08:48 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-18 02:08:48 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-18 02:08:48 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-18 02:08:48 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-18 02:08:48 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-18 02:08:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-18 02:08:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d8hPuypsjS/ea_profile.json * 2023-06-18 02:08:50 (2259) [INFO] Backed up EA4 profile to /tmp/d8hPuypsjS/ea_profile.json * 2023-06-18 02:08:53 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-19 01:51:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-19 01:51:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-19 01:51:23 (1700) [INFO] Checking if your system is up to date: * 2023-06-19 01:51:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-19 01:51:23 (4089) [INFO] * 2023-06-19 01:51:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-19 01:51:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-19 01:51:24 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-19 01:51:24 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-19 01:51:24 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-19 01:51:24 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-19 01:51:24 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-19 01:51:24 (4119) [INFO] * 2023-06-19 01:51:24 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-19 01:51:24 (4089) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-19 01:52:19 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-19 01:52:19 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-19 01:52:19 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-19 01:52:19 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-19 01:52:19 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-19 01:52:19 (4102) [INFO] yum --disablerepo= ... * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-19 01:52:19 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-19 01:52:19 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] yum-config-manager --disable * 2023-06-19 01:52:19 (4102) [INFO] or * 2023-06-19 01:52:19 (4102) [INFO] subscription-manager repos --disable= * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-19 01:52:19 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-19 01:52:19 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-19 01:52:19 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-19 01:52:19 (4102) [INFO] compromise: * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-19 01:52:19 (4102) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-19 01:52:19 (4119) [INFO] * 2023-06-19 01:52:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-19 01:52:19 (1721) [INFO] Checking /scripts/sysup * 2023-06-19 01:52:19 (4088) [INFO] Running: /scripts/sysup * 2023-06-19 01:52:19 (4089) [INFO] * 2023-06-19 01:52:19 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-19 01:52:22 (4102) [INFO] All Needed Packages are already installed. * 2023-06-19 01:52:22 (4119) [INFO] * 2023-06-19 01:52:25 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-19 01:52:25 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-19 01:59:30 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-19 01:59:30 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-19 01:59:31 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-19 01:59:31 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-19 01:59:31 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-19 01:59:31 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-19 01:59:31 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zAFxVbf70O/ea_profile.json * 2023-06-19 01:59:33 (2259) [INFO] Backed up EA4 profile to /tmp/zAFxVbf70O/ea_profile.json * 2023-06-19 01:59:36 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-20 01:58:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-20 01:58:15 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-20 01:58:15 (1700) [INFO] Checking if your system is up to date: * 2023-06-20 01:58:15 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-20 01:58:15 (4089) [INFO] * 2023-06-20 01:58:15 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-20 01:58:15 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-20 01:58:15 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-20 01:58:15 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-20 01:58:15 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-20 01:58:15 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-20 01:58:16 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-20 01:58:16 (4119) [INFO] * 2023-06-20 01:58:16 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-20 01:58:16 (4089) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-20 01:59:12 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-20 01:59:12 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-20 01:59:12 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-20 01:59:12 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-20 01:59:12 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-20 01:59:12 (4102) [INFO] yum --disablerepo= ... * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-20 01:59:12 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-20 01:59:12 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] yum-config-manager --disable * 2023-06-20 01:59:12 (4102) [INFO] or * 2023-06-20 01:59:12 (4102) [INFO] subscription-manager repos --disable= * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-20 01:59:12 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-20 01:59:12 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-20 01:59:12 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-20 01:59:12 (4102) [INFO] compromise: * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-20 01:59:12 (4102) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-20 01:59:12 (4119) [INFO] * 2023-06-20 01:59:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-20 01:59:12 (1721) [INFO] Checking /scripts/sysup * 2023-06-20 01:59:12 (4088) [INFO] Running: /scripts/sysup * 2023-06-20 01:59:12 (4089) [INFO] * 2023-06-20 01:59:12 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-20 01:59:15 (4102) [INFO] All Needed Packages are already installed. * 2023-06-20 01:59:15 (4119) [INFO] * 2023-06-20 01:59:18 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-20 01:59:18 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-20 02:06:33 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-20 02:06:33 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-20 02:06:34 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-20 02:06:34 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-20 02:06:34 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-20 02:06:34 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-20 02:06:34 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QjQGW5UQUl/ea_profile.json * 2023-06-20 02:06:36 (2259) [INFO] Backed up EA4 profile to /tmp/QjQGW5UQUl/ea_profile.json * 2023-06-20 02:06:39 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-21 01:54:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-21 01:54:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-21 01:54:23 (1700) [INFO] Checking if your system is up to date: * 2023-06-21 01:54:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-21 01:54:23 (4089) [INFO] * 2023-06-21 01:54:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-21 01:54:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-21 01:54:24 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-21 01:54:24 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-21 01:54:24 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-21 01:54:24 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-21 01:54:24 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-21 01:54:24 (4119) [INFO] * 2023-06-21 01:54:24 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-21 01:54:24 (4089) [INFO] * 2023-06-21 01:58:32 (4102) [INFO] * 2023-06-21 01:58:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-21 01:58:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-21 01:58:33 (4119) [INFO] * 2023-06-21 01:58:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-21 01:58:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-21 01:58:36 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-21 01:58:36 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-21 02:01:53 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-21 02:01:53 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-21 02:01:54 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-21 02:01:54 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-21 02:01:54 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-21 02:01:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-21 02:01:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MmEcVRLVct/ea_profile.json * 2023-06-21 02:01:57 (2259) [INFO] Backed up EA4 profile to /tmp/MmEcVRLVct/ea_profile.json * 2023-06-21 02:02:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-22 01:59:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-22 01:59:31 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-22 01:59:31 (1700) [INFO] Checking if your system is up to date: * 2023-06-22 01:59:31 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-22 01:59:31 (4089) [INFO] * 2023-06-22 01:59:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-22 01:59:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-22 01:59:32 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-22 01:59:32 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-22 01:59:32 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-22 01:59:32 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-22 01:59:32 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-22 01:59:32 (4119) [INFO] * 2023-06-22 01:59:32 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-22 01:59:32 (4089) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-22 02:00:27 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-22 02:00:27 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-22 02:00:27 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-22 02:00:27 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-22 02:00:27 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-22 02:00:27 (4102) [INFO] yum --disablerepo= ... * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-22 02:00:27 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-22 02:00:27 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] yum-config-manager --disable * 2023-06-22 02:00:27 (4102) [INFO] or * 2023-06-22 02:00:27 (4102) [INFO] subscription-manager repos --disable= * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-22 02:00:27 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-22 02:00:27 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-22 02:00:27 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-22 02:00:27 (4102) [INFO] compromise: * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-22 02:00:27 (4102) [INFO] * 2023-06-22 02:00:27 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-22 02:00:27 (4119) [INFO] * 2023-06-22 02:00:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-22 02:00:27 (1721) [INFO] Checking /scripts/sysup * 2023-06-22 02:00:27 (4088) [INFO] Running: /scripts/sysup * 2023-06-22 02:00:27 (4089) [INFO] * 2023-06-22 02:00:28 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-22 02:00:30 (4102) [INFO] All Needed Packages are already installed. * 2023-06-22 02:00:30 (4119) [INFO] * 2023-06-22 02:00:33 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-22 02:00:33 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-22 02:07:37 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-22 02:07:37 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-22 02:07:38 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-22 02:07:38 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-22 02:07:38 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-22 02:07:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-22 02:07:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iXo8yUx1rc/ea_profile.json * 2023-06-22 02:07:40 (2259) [INFO] Backed up EA4 profile to /tmp/iXo8yUx1rc/ea_profile.json * 2023-06-22 02:07:43 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-23 01:58:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-23 01:58:22 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-23 01:58:22 (1700) [INFO] Checking if your system is up to date: * 2023-06-23 01:58:22 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-23 01:58:22 (4089) [INFO] * 2023-06-23 01:58:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-23 01:58:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-23 01:58:23 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-23 01:58:23 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-23 01:58:23 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-23 01:58:23 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-23 01:58:23 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-23 01:58:23 (4119) [INFO] * 2023-06-23 01:58:23 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-23 01:58:23 (4089) [INFO] * 2023-06-23 02:02:32 (4102) [INFO] * 2023-06-23 02:02:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-23 02:02:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-23 02:02:32 (4119) [INFO] * 2023-06-23 02:02:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-23 02:02:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-23 02:02:36 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-23 02:02:36 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-23 02:05:40 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-23 02:05:40 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-23 02:05:40 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-23 02:05:40 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-23 02:05:40 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-23 02:05:40 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-23 02:05:40 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UAp5gU2QNV/ea_profile.json * 2023-06-23 02:05:43 (2259) [INFO] Backed up EA4 profile to /tmp/UAp5gU2QNV/ea_profile.json * 2023-06-23 02:05:47 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-24 02:01:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-24 02:01:33 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-24 02:01:33 (1700) [INFO] Checking if your system is up to date: * 2023-06-24 02:01:33 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-24 02:01:33 (4089) [INFO] * 2023-06-24 02:01:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-24 02:01:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-24 02:01:34 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-24 02:01:34 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-24 02:01:34 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-24 02:01:34 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-24 02:01:34 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-24 02:01:34 (4119) [INFO] * 2023-06-24 02:01:34 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-24 02:01:34 (4089) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-24 02:02:30 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-24 02:02:30 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-24 02:02:30 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-24 02:02:30 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-24 02:02:30 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-24 02:02:30 (4102) [INFO] yum --disablerepo= ... * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-24 02:02:30 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-24 02:02:30 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] yum-config-manager --disable * 2023-06-24 02:02:30 (4102) [INFO] or * 2023-06-24 02:02:30 (4102) [INFO] subscription-manager repos --disable= * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-24 02:02:30 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-24 02:02:30 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-24 02:02:30 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-24 02:02:30 (4102) [INFO] compromise: * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-24 02:02:30 (4102) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-24 02:02:30 (4119) [INFO] * 2023-06-24 02:02:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-24 02:02:30 (1721) [INFO] Checking /scripts/sysup * 2023-06-24 02:02:30 (4088) [INFO] Running: /scripts/sysup * 2023-06-24 02:02:30 (4089) [INFO] * 2023-06-24 02:02:30 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-24 02:02:33 (4102) [INFO] All Needed Packages are already installed. * 2023-06-24 02:02:33 (4119) [INFO] * 2023-06-24 02:02:36 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-24 02:02:36 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-24 02:09:30 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-24 02:09:30 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-24 02:09:30 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-24 02:09:30 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-24 02:09:30 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-24 02:09:30 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-24 02:09:30 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FW5aoN7Vmp/ea_profile.json * 2023-06-24 02:09:33 (2259) [INFO] Backed up EA4 profile to /tmp/FW5aoN7Vmp/ea_profile.json * 2023-06-24 02:09:37 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-25 01:53:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-25 01:53:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-25 01:53:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-25 01:53:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-25 01:53:06 (4089) [INFO] * 2023-06-25 01:53:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-25 01:53:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-25 01:53:06 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-25 01:53:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-25 01:53:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-25 01:53:06 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-25 01:53:06 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-25 01:53:06 (4119) [INFO] * 2023-06-25 01:53:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-25 01:53:06 (4089) [INFO] * 2023-06-25 01:57:19 (4102) [INFO] * 2023-06-25 01:57:19 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-25 01:57:19 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-25 01:57:19 (4119) [INFO] * 2023-06-25 01:57:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-25 01:57:19 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-25 01:57:22 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-25 01:57:22 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-25 02:00:44 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-25 02:00:44 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-25 02:00:44 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-25 02:00:44 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-25 02:00:44 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-25 02:00:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-25 02:00:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/M66VUfiUNN/ea_profile.json * 2023-06-25 02:00:47 (2259) [INFO] Backed up EA4 profile to /tmp/M66VUfiUNN/ea_profile.json * 2023-06-25 02:00:50 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-26 01:58:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-26 01:58:19 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-26 01:58:19 (1700) [INFO] Checking if your system is up to date: * 2023-06-26 01:58:19 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-26 01:58:19 (4089) [INFO] * 2023-06-26 01:58:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-26 01:58:20 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-26 01:58:20 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-26 01:58:20 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-26 01:58:20 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-26 01:58:20 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-26 01:58:21 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-26 01:58:21 (4119) [INFO] * 2023-06-26 01:58:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-26 01:58:21 (4089) [INFO] * 2023-06-26 02:02:28 (4102) [INFO] * 2023-06-26 02:02:28 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-26 02:02:28 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-26 02:02:29 (4119) [INFO] * 2023-06-26 02:02:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-26 02:02:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-26 02:02:32 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-26 02:02:32 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-26 02:05:50 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-26 02:05:50 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-26 02:05:51 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-26 02:05:51 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-26 02:05:51 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-26 02:05:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-26 02:05:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PRb1aOppJe/ea_profile.json * 2023-06-26 02:05:53 (2259) [INFO] Backed up EA4 profile to /tmp/PRb1aOppJe/ea_profile.json * 2023-06-26 02:05:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-27 01:57:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-27 01:57:17 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-27 01:57:17 (1700) [INFO] Checking if your system is up to date: * 2023-06-27 01:57:17 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-27 01:57:17 (4089) [INFO] * 2023-06-27 01:57:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-27 01:57:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-27 01:57:18 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-27 01:57:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-27 01:57:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-27 01:57:18 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-27 01:57:18 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-27 01:57:18 (4119) [INFO] * 2023-06-27 01:57:18 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-27 01:57:18 (4089) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-06-27 01:58:13 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-06-27 01:58:13 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-06-27 01:58:13 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-06-27 01:58:13 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-06-27 01:58:13 (4102) [INFO] packages for the previous distribution release still work). * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-06-27 01:58:13 (4102) [INFO] yum --disablerepo= ... * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-06-27 01:58:13 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-06-27 01:58:13 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] yum-config-manager --disable * 2023-06-27 01:58:13 (4102) [INFO] or * 2023-06-27 01:58:13 (4102) [INFO] subscription-manager repos --disable= * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-06-27 01:58:13 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-06-27 01:58:13 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-06-27 01:58:13 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-06-27 01:58:13 (4102) [INFO] compromise: * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-06-27 01:58:13 (4102) [INFO] * 2023-06-27 01:58:13 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-06-27 01:58:13 (4119) [INFO] * 2023-06-27 01:58:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-27 01:58:13 (1721) [INFO] Checking /scripts/sysup * 2023-06-27 01:58:13 (4088) [INFO] Running: /scripts/sysup * 2023-06-27 01:58:13 (4089) [INFO] * 2023-06-27 01:58:14 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-06-27 01:58:16 (4102) [INFO] All Needed Packages are already installed. * 2023-06-27 01:58:16 (4119) [INFO] * 2023-06-27 01:58:18 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-27 01:58:18 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-27 01:59:13 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-27 01:59:13 (1567) [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-06-27 01:59:13 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-27 01:59:13 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-27 01:59:13 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-27 01:59:14 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-27 01:59:14 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-27 01:59:14 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-27 01:59:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-27 01:59:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c7YR41LR4d/ea_profile.json * 2023-06-27 02:03:31 (2259) [INFO] Backed up EA4 profile to /tmp/c7YR41LR4d/ea_profile.json * 2023-06-27 02:03:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-28 01:58:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-28 01:58:27 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-28 01:58:27 (1700) [INFO] Checking if your system is up to date: * 2023-06-28 01:58:27 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-28 01:58:27 (4089) [INFO] * 2023-06-28 01:58:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-28 01:58:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-28 01:58:28 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-28 01:58:28 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-28 01:58:28 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-28 01:58:28 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-28 01:58:28 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-28 01:58:28 (4119) [INFO] * 2023-06-28 01:58:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-28 01:58:28 (4089) [INFO] * 2023-06-28 02:02:42 (4102) [INFO] * 2023-06-28 02:02:42 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-28 02:02:42 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-28 02:02:42 (4119) [INFO] * 2023-06-28 02:02:42 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-28 02:02:42 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-28 02:02:46 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-28 02:02:46 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-28 02:06:11 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-28 02:06:11 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-28 02:06:12 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-28 02:06:12 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-28 02:06:12 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-28 02:06:12 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-28 02:06:12 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E5ZMxz3tGK/ea_profile.json * 2023-06-28 02:06:14 (2259) [INFO] Backed up EA4 profile to /tmp/E5ZMxz3tGK/ea_profile.json * 2023-06-28 02:06:18 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-29 01:58:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-29 01:58:40 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-29 01:58:40 (1700) [INFO] Checking if your system is up to date: * 2023-06-29 01:58:40 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-29 01:58:40 (4089) [INFO] * 2023-06-29 01:58:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-29 01:58:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-29 01:58:41 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-29 01:58:41 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-29 01:58:41 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-29 01:58:41 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-29 01:58:41 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-29 01:58:41 (4119) [INFO] * 2023-06-29 01:58:41 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-29 01:58:41 (4089) [INFO] * 2023-06-29 02:02:53 (4102) [INFO] * 2023-06-29 02:02:53 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-29 02:02:53 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-29 02:02:53 (4119) [INFO] * 2023-06-29 02:02:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-29 02:02:53 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-29 02:02:57 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-29 02:02:57 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-29 02:06:32 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-29 02:06:32 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-29 02:06:33 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-29 02:06:33 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-29 02:06:33 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-29 02:06:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-29 02:06:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hTH5AGHk_d/ea_profile.json * 2023-06-29 02:06:35 (2259) [INFO] Backed up EA4 profile to /tmp/hTH5AGHk_d/ea_profile.json * 2023-06-29 02:06:39 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-30 01:59:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-06-30 01:59:58 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-30 01:59:58 (1700) [INFO] Checking if your system is up to date: * 2023-06-30 01:59:58 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-30 01:59:58 (4089) [INFO] * 2023-06-30 01:59:58 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-30 01:59:58 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-06-30 01:59:58 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-30 01:59:58 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-30 01:59:58 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-30 01:59:58 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-06-30 01:59:58 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-06-30 01:59:58 (4119) [INFO] * 2023-06-30 01:59:58 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-30 01:59:58 (4089) [INFO] * 2023-06-30 02:04:31 (4102) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.raystedman.org/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2023-06-30 02:04:31 (4102) [INFO] Trying other mirror. * 2023-06-30 02:05:11 (4102) [INFO] * 2023-06-30 02:05:11 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-30 02:05:11 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-30 02:05:11 (4119) [INFO] * 2023-06-30 02:05:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-30 02:05:11 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-30 02:05:13 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-06-30 02:05:13 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-06-30 02:09:26 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-06-30 02:09:26 (1567) [ERROR] http://mirrors.raystedman.org/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.raystedman.org/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. * 2023-06-30 02:09:26 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-06-30 02:09:26 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-06-30 02:09:26 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-06-30 02:09:27 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-06-30 02:09:27 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-06-30 02:09:27 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-06-30 02:09:27 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-30 02:09:27 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YBSoYMq8QY/ea_profile.json * 2023-06-30 02:09:30 (2259) [INFO] Backed up EA4 profile to /tmp/YBSoYMq8QY/ea_profile.json * 2023-06-30 02:09:33 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-01 02:02:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-01 02:02:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-01 02:02:23 (1700) [INFO] Checking if your system is up to date: * 2023-07-01 02:02:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-01 02:02:23 (4089) [INFO] * 2023-07-01 02:02:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-01 02:02:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-01 02:02:24 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-01 02:02:24 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-01 02:02:24 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-01 02:02:24 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-01 02:02:24 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-01 02:02:24 (4119) [INFO] * 2023-07-01 02:02:24 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-01 02:02:24 (4089) [INFO] * 2023-07-01 02:06:26 (4102) [INFO] * 2023-07-01 02:06:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-01 02:06:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-01 02:06:26 (4119) [INFO] * 2023-07-01 02:06:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-01 02:06:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-01 02:06:29 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-01 02:06:29 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-01 02:09:23 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-01 02:09:23 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-01 02:09:24 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-01 02:09:24 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-01 02:09:24 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-01 02:09:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-01 02:09:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/btXDLWRnIc/ea_profile.json * 2023-07-01 02:09:26 (2259) [INFO] Backed up EA4 profile to /tmp/btXDLWRnIc/ea_profile.json * 2023-07-01 02:09:30 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-02 02:00:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-02 02:00:59 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-02 02:00:59 (1700) [INFO] Checking if your system is up to date: * 2023-07-02 02:00:59 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-02 02:00:59 (4089) [INFO] * 2023-07-02 02:00:59 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-02 02:01:00 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-02 02:01:00 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-02 02:01:00 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-02 02:01:00 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-02 02:01:00 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-02 02:01:00 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-02 02:01:00 (4119) [INFO] * 2023-07-02 02:01:00 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-02 02:01:00 (4089) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-02 02:01:55 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-02 02:01:55 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-02 02:01:55 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-02 02:01:55 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-02 02:01:55 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-02 02:01:55 (4102) [INFO] yum --disablerepo= ... * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-02 02:01:55 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-02 02:01:55 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] yum-config-manager --disable * 2023-07-02 02:01:55 (4102) [INFO] or * 2023-07-02 02:01:55 (4102) [INFO] subscription-manager repos --disable= * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-02 02:01:55 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-02 02:01:55 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-02 02:01:55 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-02 02:01:55 (4102) [INFO] compromise: * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-02 02:01:55 (4102) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-02 02:01:55 (4119) [INFO] * 2023-07-02 02:01:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-02 02:01:55 (1721) [INFO] Checking /scripts/sysup * 2023-07-02 02:01:55 (4088) [INFO] Running: /scripts/sysup * 2023-07-02 02:01:55 (4089) [INFO] * 2023-07-02 02:01:55 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-02 02:01:58 (4102) [INFO] All Needed Packages are already installed. * 2023-07-02 02:01:58 (4119) [INFO] * 2023-07-02 02:02:00 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-02 02:02:00 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-02 02:09:27 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-02 02:09:27 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-02 02:09:28 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-02 02:09:28 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-02 02:09:28 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-02 02:09:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-02 02:09:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8BMmxoUzvq/ea_profile.json * 2023-07-02 02:09:31 (2259) [INFO] Backed up EA4 profile to /tmp/8BMmxoUzvq/ea_profile.json * 2023-07-02 02:09:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-03 01:59:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-03 01:59:54 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-03 01:59:54 (1700) [INFO] Checking if your system is up to date: * 2023-07-03 01:59:54 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-03 01:59:54 (4089) [INFO] * 2023-07-03 01:59:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-03 01:59:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-03 01:59:55 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-03 01:59:55 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-03 01:59:55 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-03 01:59:55 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-03 01:59:56 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-03 01:59:56 (4119) [INFO] * 2023-07-03 01:59:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-03 01:59:56 (4089) [INFO] * 2023-07-03 02:03:51 (4102) [INFO] * 2023-07-03 02:03:51 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-03 02:03:51 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-03 02:03:51 (4119) [INFO] * 2023-07-03 02:03:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-03 02:03:51 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-03 02:03:54 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-03 02:03:54 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-03 02:07:08 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-03 02:07:08 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-03 02:07:09 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-03 02:07:09 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-03 02:07:09 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-03 02:07:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-03 02:07:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ylDmOLtQgu/ea_profile.json * 2023-07-03 02:07:11 (2259) [INFO] Backed up EA4 profile to /tmp/ylDmOLtQgu/ea_profile.json * 2023-07-03 02:07:13 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-04 01:57:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-04 01:57:59 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-04 01:57:59 (1700) [INFO] Checking if your system is up to date: * 2023-07-04 01:57:59 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-04 01:57:59 (4089) [INFO] * 2023-07-04 01:58:00 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-04 01:58:00 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-04 01:58:00 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-04 01:58:00 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-04 01:58:00 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-04 01:58:00 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-04 01:58:01 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-04 01:58:01 (4119) [INFO] * 2023-07-04 01:58:01 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-04 01:58:01 (4089) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-04 01:58:57 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-04 01:58:57 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-04 01:58:57 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-04 01:58:57 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-04 01:58:57 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-04 01:58:57 (4102) [INFO] yum --disablerepo= ... * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-04 01:58:57 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-04 01:58:57 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] yum-config-manager --disable * 2023-07-04 01:58:57 (4102) [INFO] or * 2023-07-04 01:58:57 (4102) [INFO] subscription-manager repos --disable= * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-04 01:58:57 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-04 01:58:57 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-04 01:58:57 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-04 01:58:57 (4102) [INFO] compromise: * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-04 01:58:57 (4102) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-04 01:58:57 (4119) [INFO] * 2023-07-04 01:58:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-04 01:58:57 (1721) [INFO] Checking /scripts/sysup * 2023-07-04 01:58:57 (4088) [INFO] Running: /scripts/sysup * 2023-07-04 01:58:57 (4089) [INFO] * 2023-07-04 01:58:57 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-04 01:59:00 (4102) [INFO] All Needed Packages are already installed. * 2023-07-04 01:59:00 (4119) [INFO] * 2023-07-04 01:59:04 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-04 01:59:04 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-04 02:06:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-04 02:06:00 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-04 02:06:01 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-04 02:06:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-04 02:06:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-04 02:06:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-04 02:06:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dbUEVv18nH/ea_profile.json * 2023-07-04 02:06:04 (2259) [INFO] Backed up EA4 profile to /tmp/dbUEVv18nH/ea_profile.json * 2023-07-04 02:06:09 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-05 01:58:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-05 01:58:17 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-05 01:58:17 (1700) [INFO] Checking if your system is up to date: * 2023-07-05 01:58:17 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-05 01:58:17 (4089) [INFO] * 2023-07-05 01:58:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-05 01:58:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-05 01:58:18 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-05 01:58:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-05 01:58:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-05 01:58:18 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-05 01:58:18 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-05 01:58:18 (4119) [INFO] * 2023-07-05 01:58:18 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-05 01:58:18 (4089) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-05 01:59:13 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-05 01:59:13 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-05 01:59:13 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-05 01:59:13 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-05 01:59:13 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-05 01:59:13 (4102) [INFO] yum --disablerepo= ... * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-05 01:59:13 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-05 01:59:13 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] yum-config-manager --disable * 2023-07-05 01:59:13 (4102) [INFO] or * 2023-07-05 01:59:13 (4102) [INFO] subscription-manager repos --disable= * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-05 01:59:13 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-05 01:59:13 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-05 01:59:13 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-05 01:59:13 (4102) [INFO] compromise: * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-05 01:59:13 (4102) [INFO] * 2023-07-05 01:59:13 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-05 01:59:13 (4119) [INFO] * 2023-07-05 01:59:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-05 01:59:13 (1721) [INFO] Checking /scripts/sysup * 2023-07-05 01:59:13 (4088) [INFO] Running: /scripts/sysup * 2023-07-05 01:59:13 (4089) [INFO] * 2023-07-05 01:59:14 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-05 01:59:16 (4102) [INFO] All Needed Packages are already installed. * 2023-07-05 01:59:16 (4119) [INFO] * 2023-07-05 01:59:18 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-05 01:59:18 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-05 02:00:12 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-05 02:00:12 (1567) [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-07-05 02:00:12 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-05 02:00:12 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-05 02:00:12 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-05 02:00:13 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-05 02:00:13 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-05 02:00:13 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-05 02:00:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-05 02:00:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DSxkzFdvCe/ea_profile.json * 2023-07-05 02:04:47 (2259) [INFO] Backed up EA4 profile to /tmp/DSxkzFdvCe/ea_profile.json * 2023-07-05 02:04:51 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-06 01:55:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-06 01:55:26 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-06 01:55:26 (1700) [INFO] Checking if your system is up to date: * 2023-07-06 01:55:26 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-06 01:55:26 (4089) [INFO] * 2023-07-06 01:55:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-06 01:55:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-06 01:55:27 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-06 01:55:27 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-06 01:55:27 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-06 01:55:27 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-06 01:55:28 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-06 01:55:28 (4119) [INFO] * 2023-07-06 01:55:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-06 01:55:28 (4089) [INFO] * 2023-07-06 01:59:20 (4102) [INFO] * 2023-07-06 01:59:20 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-06 01:59:20 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-06 01:59:21 (4119) [INFO] * 2023-07-06 01:59:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-06 01:59:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-06 01:59:24 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-06 01:59:24 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-06 02:02:25 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-06 02:02:25 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-06 02:02:26 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-06 02:02:26 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-06 02:02:26 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-06 02:02:26 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-06 02:02:26 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m8m1RB8zCN/ea_profile.json * 2023-07-06 02:02:28 (2259) [INFO] Backed up EA4 profile to /tmp/m8m1RB8zCN/ea_profile.json * 2023-07-06 02:02:33 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-07 01:56:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-07 01:56:45 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-07 01:56:45 (1700) [INFO] Checking if your system is up to date: * 2023-07-07 01:56:45 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-07 01:56:45 (4089) [INFO] * 2023-07-07 01:56:45 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-07 01:56:45 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-07 01:56:45 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-07 01:56:45 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-07 01:56:45 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-07 01:56:45 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-07 01:56:46 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-07 01:56:46 (4119) [INFO] * 2023-07-07 01:56:46 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-07 01:56:46 (4089) [INFO] * 2023-07-07 02:01:03 (4102) [INFO] * 2023-07-07 02:01:03 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-07 02:01:03 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-07 02:01:04 (4119) [INFO] * 2023-07-07 02:01:04 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-07 02:01:04 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-07 02:01:07 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-07 02:01:07 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-07 02:04:28 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-07 02:04:28 (1567) [ERROR] http://mirrors.seas.harvard.edu/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds') Trying other mirror. * 2023-07-07 02:04:28 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-07 02:04:28 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-07 02:04:28 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-07 02:04:29 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-07 02:04:29 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-07 02:04:29 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-07 02:04:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-07 02:04:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WKO1AqNSjD/ea_profile.json * 2023-07-07 02:04:31 (2259) [INFO] Backed up EA4 profile to /tmp/WKO1AqNSjD/ea_profile.json * 2023-07-07 02:04:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-08 00:53:41 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-08 00:53:41 (1700) [INFO] Checking if your system is up to date: * 2023-07-08 00:53:41 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-08 00:53:41 (4089) [INFO] * 2023-07-08 00:53:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-08 00:53:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-08 00:53:41 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-08 00:53:41 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-08 00:53:41 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-08 00:53:41 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-08 00:53:42 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-08 00:53:42 (4119) [INFO] * 2023-07-08 00:53:42 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-08 00:53:42 (4089) [INFO] * 2023-07-08 00:58:00 (4102) [INFO] * 2023-07-08 00:58:00 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-08 00:58:00 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-08 00:58:00 (4119) [INFO] * 2023-07-08 00:58:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-08 00:58:00 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-08 00:58:07 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-08 00:58:07 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-08 01:01:31 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-08 01:01:31 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-08 01:01:32 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-08 01:01:32 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-08 01:01:32 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-08 01:01:32 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-08 01:01:32 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NSJXnuqS4g/ea_profile.json * 2023-07-08 01:01:35 (2259) [INFO] Backed up EA4 profile to /tmp/NSJXnuqS4g/ea_profile.json * 2023-07-08 01:01:39 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-09 01:57:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-09 01:57:02 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-09 01:57:02 (1700) [INFO] Checking if your system is up to date: * 2023-07-09 01:57:02 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-09 01:57:02 (4089) [INFO] * 2023-07-09 01:57:02 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-09 01:57:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-09 01:57:03 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-09 01:57:03 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-09 01:57:03 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-09 01:57:03 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-09 01:57:03 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-09 01:57:03 (4119) [INFO] * 2023-07-09 01:57:03 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-09 01:57:03 (4089) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-09 01:57:58 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-09 01:57:58 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-09 01:57:58 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-09 01:57:58 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-09 01:57:58 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-09 01:57:58 (4102) [INFO] yum --disablerepo= ... * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-09 01:57:58 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-09 01:57:58 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] yum-config-manager --disable * 2023-07-09 01:57:58 (4102) [INFO] or * 2023-07-09 01:57:58 (4102) [INFO] subscription-manager repos --disable= * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-09 01:57:58 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-09 01:57:58 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-09 01:57:58 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-09 01:57:58 (4102) [INFO] compromise: * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-09 01:57:58 (4102) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-09 01:57:58 (4119) [INFO] * 2023-07-09 01:57:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-09 01:57:58 (1721) [INFO] Checking /scripts/sysup * 2023-07-09 01:57:58 (4088) [INFO] Running: /scripts/sysup * 2023-07-09 01:57:58 (4089) [INFO] * 2023-07-09 01:57:58 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-09 01:58:00 (4102) [INFO] All Needed Packages are already installed. * 2023-07-09 01:58:00 (4119) [INFO] * 2023-07-09 01:58:04 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-09 01:58:04 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-09 01:58:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-09 01:58:58 (1567) [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-07-09 01:58:58 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-09 01:58:58 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-09 01:58:58 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-09 01:58:59 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-09 01:58:59 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-09 01:58:59 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-09 01:58:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-09 01:58:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yS4tIU9kno/ea_profile.json * 2023-07-09 02:00:26 (297) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yS4tIU9kno/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2238. * 2023-07-09 02:00:26 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-10 01:55:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-10 01:55:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-10 01:55:10 (1700) [INFO] Checking if your system is up to date: * 2023-07-10 01:55:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-10 01:55:10 (4089) [INFO] * 2023-07-10 01:55:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-10 01:55:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-10 01:55:10 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-10 01:55:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-10 01:55:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-10 01:55:10 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-10 01:55:11 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-10 01:55:11 (4119) [INFO] * 2023-07-10 01:55:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-10 01:55:11 (4089) [INFO] * 2023-07-10 01:59:09 (4102) [INFO] * 2023-07-10 01:59:09 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-10 01:59:09 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-10 01:59:09 (4119) [INFO] * 2023-07-10 01:59:09 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-10 01:59:09 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-10 01:59:12 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-10 01:59:12 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-10 02:02:56 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-10 02:02:56 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-10 02:02:57 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-10 02:02:57 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-10 02:02:57 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-10 02:02:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-10 02:02:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Tw8hjdh98H/ea_profile.json * 2023-07-10 02:03:00 (2259) [INFO] Backed up EA4 profile to /tmp/Tw8hjdh98H/ea_profile.json * 2023-07-10 02:03:04 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-11 01:58:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-11 01:58:36 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-11 01:58:36 (1700) [INFO] Checking if your system is up to date: * 2023-07-11 01:58:36 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-11 01:58:36 (4089) [INFO] * 2023-07-11 01:58:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-11 01:58:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-11 01:58:36 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-11 01:58:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-11 01:58:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-11 01:58:36 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-11 01:58:37 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-11 01:58:37 (4119) [INFO] * 2023-07-11 01:58:37 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-11 01:58:37 (4089) [INFO] * 2023-07-11 02:02:38 (4102) [INFO] * 2023-07-11 02:02:38 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-11 02:02:38 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-11 02:02:38 (4119) [INFO] * 2023-07-11 02:02:38 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-11 02:02:38 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-11 02:02:42 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-11 02:02:42 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-11 02:05:33 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-11 02:05:33 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-11 02:05:34 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-11 02:05:34 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-11 02:05:34 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-11 02:05:34 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-11 02:05:34 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dYxNTtpouj/ea_profile.json * 2023-07-11 02:05:36 (2259) [INFO] Backed up EA4 profile to /tmp/dYxNTtpouj/ea_profile.json * 2023-07-11 02:05:40 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-12 01:56:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-12 01:56:39 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-12 01:56:39 (1700) [INFO] Checking if your system is up to date: * 2023-07-12 01:56:39 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-12 01:56:39 (4089) [INFO] * 2023-07-12 01:56:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-12 01:56:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-12 01:56:40 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-12 01:56:40 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-12 01:56:40 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-12 01:56:40 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-12 01:56:40 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-12 01:56:40 (4119) [INFO] * 2023-07-12 01:56:40 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-12 01:56:40 (4089) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-12 01:57:35 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-12 01:57:35 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-12 01:57:35 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-12 01:57:35 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-12 01:57:35 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-12 01:57:35 (4102) [INFO] yum --disablerepo= ... * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-12 01:57:35 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-12 01:57:35 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] yum-config-manager --disable * 2023-07-12 01:57:35 (4102) [INFO] or * 2023-07-12 01:57:35 (4102) [INFO] subscription-manager repos --disable= * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-12 01:57:35 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-12 01:57:35 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-12 01:57:35 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-12 01:57:35 (4102) [INFO] compromise: * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-12 01:57:35 (4102) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-12 01:57:35 (4119) [INFO] * 2023-07-12 01:57:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-12 01:57:35 (1721) [INFO] Checking /scripts/sysup * 2023-07-12 01:57:35 (4088) [INFO] Running: /scripts/sysup * 2023-07-12 01:57:35 (4089) [INFO] * 2023-07-12 01:57:35 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-12 01:57:37 (4102) [INFO] All Needed Packages are already installed. * 2023-07-12 01:57:37 (4119) [INFO] * 2023-07-12 01:57:41 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-12 01:57:41 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-12 02:05:07 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-12 02:05:07 (1567) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/1bfdb277295adb5fdf9add7f3dbc60968be3d4e9dda0ef36db85b50996eb8bd7-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/. * 2023-07-12 02:05:07 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-12 02:05:07 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-12 02:05:07 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-12 02:05:08 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-12 02:05:08 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-12 02:05:08 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-12 02:05:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-12 02:05:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8staL3_Vti/ea_profile.json * 2023-07-12 02:05:10 (2259) [INFO] Backed up EA4 profile to /tmp/8staL3_Vti/ea_profile.json * 2023-07-12 02:05:13 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-13 01:59:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-13 01:59:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-13 01:59:12 (1700) [INFO] Checking if your system is up to date: * 2023-07-13 01:59:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-13 01:59:12 (4089) [INFO] * 2023-07-13 01:59:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-13 01:59:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-13 01:59:13 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-13 01:59:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-13 01:59:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-13 01:59:13 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-13 01:59:13 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-13 01:59:13 (4119) [INFO] * 2023-07-13 01:59:13 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-13 01:59:13 (4089) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-13 02:00:09 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-13 02:00:09 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-13 02:00:09 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-13 02:00:09 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-13 02:00:09 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-13 02:00:09 (4102) [INFO] yum --disablerepo= ... * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-13 02:00:09 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-13 02:00:09 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] yum-config-manager --disable * 2023-07-13 02:00:09 (4102) [INFO] or * 2023-07-13 02:00:09 (4102) [INFO] subscription-manager repos --disable= * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-13 02:00:09 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-13 02:00:09 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-13 02:00:09 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-13 02:00:09 (4102) [INFO] compromise: * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-13 02:00:09 (4102) [INFO] * 2023-07-13 02:00:09 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-13 02:00:09 (4119) [INFO] * 2023-07-13 02:00:09 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-13 02:00:09 (1721) [INFO] Checking /scripts/sysup * 2023-07-13 02:00:09 (4088) [INFO] Running: /scripts/sysup * 2023-07-13 02:00:09 (4089) [INFO] * 2023-07-13 02:00:10 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-13 02:00:12 (4102) [INFO] All Needed Packages are already installed. * 2023-07-13 02:00:12 (4119) [INFO] * 2023-07-13 02:00:15 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-13 02:00:15 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-13 02:01:09 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-13 02:01:09 (1567) [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-07-13 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-13 02:01:09 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-13 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-13 02:01:10 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-13 02:01:10 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-13 02:01:10 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-13 02:01:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-13 02:01:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JA_EVghP1X/ea_profile.json * 2023-07-13 02:05:25 (2259) [INFO] Backed up EA4 profile to /tmp/JA_EVghP1X/ea_profile.json * 2023-07-13 02:05:29 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-14 02:01:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-14 02:01:55 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-14 02:01:55 (1700) [INFO] Checking if your system is up to date: * 2023-07-14 02:01:55 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-14 02:01:55 (4089) [INFO] * 2023-07-14 02:01:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-14 02:01:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-14 02:01:56 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-14 02:01:56 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-14 02:01:56 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-14 02:01:56 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-14 02:01:56 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-14 02:01:56 (4119) [INFO] * 2023-07-14 02:01:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-14 02:01:56 (4089) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-14 02:02:52 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-14 02:02:52 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-14 02:02:52 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-14 02:02:52 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-14 02:02:52 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-14 02:02:52 (4102) [INFO] yum --disablerepo= ... * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-14 02:02:52 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-14 02:02:52 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] yum-config-manager --disable * 2023-07-14 02:02:52 (4102) [INFO] or * 2023-07-14 02:02:52 (4102) [INFO] subscription-manager repos --disable= * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-14 02:02:52 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-14 02:02:52 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-14 02:02:52 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-14 02:02:52 (4102) [INFO] compromise: * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-14 02:02:52 (4102) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-14 02:02:52 (4119) [INFO] * 2023-07-14 02:02:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-14 02:02:52 (1721) [INFO] Checking /scripts/sysup * 2023-07-14 02:02:52 (4088) [INFO] Running: /scripts/sysup * 2023-07-14 02:02:52 (4089) [INFO] * 2023-07-14 02:02:52 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-14 02:02:54 (4102) [INFO] All Needed Packages are already installed. * 2023-07-14 02:02:54 (4119) [INFO] * 2023-07-14 02:02:57 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-14 02:02:57 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-14 02:10:21 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-14 02:10:21 (1567) [ERROR] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.5/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. * 2023-07-14 02:10:21 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-14 02:10:21 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-14 02:10:21 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-14 02:10:22 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-14 02:10:22 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-14 02:10:22 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-14 02:10:22 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-14 02:10:22 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W8qvTrkogM/ea_profile.json * 2023-07-14 02:10:24 (2259) [INFO] Backed up EA4 profile to /tmp/W8qvTrkogM/ea_profile.json * 2023-07-14 02:10:27 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-15 01:54:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-15 01:54:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-15 01:54:04 (1700) [INFO] Checking if your system is up to date: * 2023-07-15 01:54:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-15 01:54:04 (4089) [INFO] * 2023-07-15 01:54:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-15 01:54:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-15 01:54:04 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-15 01:54:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-15 01:54:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-15 01:54:04 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-15 01:54:04 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-15 01:54:04 (4119) [INFO] * 2023-07-15 01:54:04 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-15 01:54:04 (4089) [INFO] * 2023-07-15 01:56:58 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/deeeaa6a518897610167b12963c86b9a88d5fc928f2f1904b122b38add8c7983-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-07-15 01:56:58 (4102) [INFO] Trying other mirror. * 2023-07-15 01:56:58 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-07-15 01:56:58 (4102) [INFO] * 2023-07-15 01:56:58 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-07-15 01:56:58 (4102) [INFO] * 2023-07-15 01:56:58 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-07-15 01:56:58 (4102) [INFO] * 2023-07-15 01:57:58 (4102) [INFO] * 2023-07-15 01:57:58 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-15 01:57:58 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-15 01:57:58 (4119) [INFO] * 2023-07-15 01:57:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-15 01:57:58 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-15 01:58:01 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-15 01:58:01 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-15 02:01:21 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-15 02:01:21 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30196 milliseconds with 0 out of 0 bytes received') http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/accac4b206f44feac5c94d2f1f410b9973fa6ddaf58ca915aef5913b4b22ccae-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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-07-15 02:01:21 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-15 02:01:21 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-15 02:01:21 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-15 02:01:22 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-15 02:01:22 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-15 02:01:22 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-15 02:01:22 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-15 02:01:22 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7_2OJ1A1uH/ea_profile.json * 2023-07-15 02:01:25 (2259) [INFO] Backed up EA4 profile to /tmp/7_2OJ1A1uH/ea_profile.json * 2023-07-15 02:01:28 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-16 01:58:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-16 01:58:58 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-16 01:58:58 (1700) [INFO] Checking if your system is up to date: * 2023-07-16 01:58:58 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-16 01:58:58 (4089) [INFO] * 2023-07-16 01:58:59 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-16 01:58:59 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-16 01:58:59 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-16 01:58:59 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-16 01:58:59 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-16 01:58:59 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-16 01:58:59 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-16 01:58:59 (4119) [INFO] * 2023-07-16 01:58:59 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-16 01:58:59 (4089) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-16 01:59:55 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-16 01:59:55 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-16 01:59:55 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-16 01:59:55 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-16 01:59:55 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-16 01:59:55 (4102) [INFO] yum --disablerepo= ... * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-16 01:59:55 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-16 01:59:55 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] yum-config-manager --disable * 2023-07-16 01:59:55 (4102) [INFO] or * 2023-07-16 01:59:55 (4102) [INFO] subscription-manager repos --disable= * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-16 01:59:55 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-16 01:59:55 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-16 01:59:55 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-16 01:59:55 (4102) [INFO] compromise: * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-16 01:59:55 (4102) [INFO] * 2023-07-16 01:59:55 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-16 01:59:55 (4119) [INFO] * 2023-07-16 01:59:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-16 01:59:55 (1721) [INFO] Checking /scripts/sysup * 2023-07-16 01:59:55 (4088) [INFO] Running: /scripts/sysup * 2023-07-16 01:59:55 (4089) [INFO] * 2023-07-16 01:59:56 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-16 01:59:58 (4102) [INFO] All Needed Packages are already installed. * 2023-07-16 01:59:58 (4119) [INFO] * 2023-07-16 02:00:01 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-16 02:00:01 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-16 02:07:14 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-16 02:07:14 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-16 02:07:15 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-16 02:07:15 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-16 02:07:15 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-16 02:07:15 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-16 02:07:15 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TDy7rQ9fXp/ea_profile.json * 2023-07-16 02:07:18 (2259) [INFO] Backed up EA4 profile to /tmp/TDy7rQ9fXp/ea_profile.json * 2023-07-16 02:07:22 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-17 01:58:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-17 01:58:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-17 01:58:09 (1700) [INFO] Checking if your system is up to date: * 2023-07-17 01:58:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-17 01:58:09 (4089) [INFO] * 2023-07-17 01:58:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-17 01:58:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-17 01:58:10 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-17 01:58:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-17 01:58:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-17 01:58:10 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-17 01:58:10 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-17 01:58:10 (4119) [INFO] * 2023-07-17 01:58:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-17 01:58:10 (4089) [INFO] * 2023-07-17 02:02:18 (4102) [INFO] * 2023-07-17 02:02:18 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-17 02:02:18 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-17 02:02:18 (4119) [INFO] * 2023-07-17 02:02:18 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-17 02:02:18 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-17 02:02:21 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-17 02:02:21 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-17 02:05:37 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-17 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-17 02:05:37 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-17 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-17 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-17 02:05:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-17 02:05:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P1kSf1oOBq/ea_profile.json * 2023-07-17 02:05:39 (2259) [INFO] Backed up EA4 profile to /tmp/P1kSf1oOBq/ea_profile.json * 2023-07-17 02:05:42 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-18 00:59:30 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-18 00:59:30 (1700) [INFO] Checking if your system is up to date: * 2023-07-18 00:59:30 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-18 00:59:30 (4089) [INFO] * 2023-07-18 00:59:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-18 00:59:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-18 00:59:31 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-18 00:59:31 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-18 00:59:31 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-18 00:59:31 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-18 00:59:32 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-18 00:59:32 (4119) [INFO] * 2023-07-18 00:59:32 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-18 00:59:32 (4089) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-18 01:00:26 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-18 01:00:26 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-18 01:00:26 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-18 01:00:26 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-18 01:00:26 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-18 01:00:26 (4102) [INFO] yum --disablerepo= ... * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-18 01:00:26 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-18 01:00:26 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] yum-config-manager --disable * 2023-07-18 01:00:26 (4102) [INFO] or * 2023-07-18 01:00:26 (4102) [INFO] subscription-manager repos --disable= * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-18 01:00:26 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-18 01:00:26 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-18 01:00:26 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-18 01:00:26 (4102) [INFO] compromise: * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-18 01:00:26 (4102) [INFO] * 2023-07-18 01:00:26 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-18 01:00:27 (4119) [INFO] * 2023-07-18 01:00:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-18 01:00:27 (1721) [INFO] Checking /scripts/sysup * 2023-07-18 01:00:27 (4088) [INFO] Running: /scripts/sysup * 2023-07-18 01:00:27 (4089) [INFO] * 2023-07-18 01:00:27 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-18 01:00:29 (4102) [INFO] All Needed Packages are already installed. * 2023-07-18 01:00:29 (4119) [INFO] * 2023-07-18 01:00:33 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-18 01:00:33 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-18 01:01:27 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-18 01:01:27 (1567) [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-07-18 01:01:27 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-18 01:01:27 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-18 01:01:27 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-18 01:01:28 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-18 01:01:28 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-18 01:01:28 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-18 01:01:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-18 01:01:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p_osuGKTv4/ea_profile.json * 2023-07-18 01:06:02 (2259) [INFO] Backed up EA4 profile to /tmp/p_osuGKTv4/ea_profile.json * 2023-07-18 01:06:05 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-19 02:12:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-19 02:12:49 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-19 02:12:49 (1700) [INFO] Checking if your system is up to date: * 2023-07-19 02:12:49 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-19 02:12:49 (4089) [INFO] * 2023-07-19 02:12:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-19 02:12:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-19 02:12:50 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-19 02:12:50 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-19 02:12:50 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-19 02:12:50 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-19 02:12:51 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-19 02:12:51 (4119) [INFO] * 2023-07-19 02:12:51 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-19 02:12:51 (4089) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-19 02:13:46 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-19 02:13:46 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-19 02:13:46 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-19 02:13:46 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-19 02:13:46 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-19 02:13:46 (4102) [INFO] yum --disablerepo= ... * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-19 02:13:46 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-19 02:13:46 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] yum-config-manager --disable * 2023-07-19 02:13:46 (4102) [INFO] or * 2023-07-19 02:13:46 (4102) [INFO] subscription-manager repos --disable= * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-19 02:13:46 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-19 02:13:46 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-19 02:13:46 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-19 02:13:46 (4102) [INFO] compromise: * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-19 02:13:46 (4102) [INFO] * 2023-07-19 02:13:46 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-19 02:13:46 (4119) [INFO] * 2023-07-19 02:13:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-19 02:13:46 (1721) [INFO] Checking /scripts/sysup * 2023-07-19 02:13:46 (4088) [INFO] Running: /scripts/sysup * 2023-07-19 02:13:46 (4089) [INFO] * 2023-07-19 02:13:47 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-19 02:13:53 (4102) [INFO] All Needed Packages are already installed. * 2023-07-19 02:13:53 (4119) [INFO] * 2023-07-19 02:14:00 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-19 02:14:00 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-19 02:21:51 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-19 02:21:51 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-19 02:22:03 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-19 02:22:04 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-19 02:22:04 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-19 02:22:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-19 02:22:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lsqIzuxndS/ea_profile.json * 2023-07-19 02:22:11 (2259) [INFO] Backed up EA4 profile to /tmp/lsqIzuxndS/ea_profile.json * 2023-07-19 02:22:14 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-20 01:04:13 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-20 01:04:13 (1700) [INFO] Checking if your system is up to date: * 2023-07-20 01:04:13 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-20 01:04:13 (4089) [INFO] * 2023-07-20 01:04:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-20 01:04:14 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-20 01:04:14 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-20 01:04:14 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-20 01:04:14 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-20 01:04:14 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-20 01:04:14 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-20 01:04:14 (4119) [INFO] * 2023-07-20 01:04:14 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-20 01:04:14 (4089) [INFO] * 2023-07-20 01:08:44 (4102) [INFO] * 2023-07-20 01:08:44 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-20 01:08:44 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-20 01:08:44 (4119) [INFO] * 2023-07-20 01:08:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-20 01:08:44 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-20 01:08:47 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-20 01:08:47 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-20 01:12:23 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-20 01:12:23 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-20 01:12:24 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-20 01:12:24 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-20 01:12:24 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-20 01:12:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-20 01:12:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T1hMGgWvn2/ea_profile.json * 2023-07-20 01:12:27 (2259) [INFO] Backed up EA4 profile to /tmp/T1hMGgWvn2/ea_profile.json * 2023-07-20 01:12:30 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-21 01:55:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-21 01:55:48 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-21 01:55:48 (1700) [INFO] Checking if your system is up to date: * 2023-07-21 01:55:48 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-21 01:55:48 (4089) [INFO] * 2023-07-21 01:55:49 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-21 01:55:49 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-21 01:55:49 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-21 01:55:49 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-21 01:55:49 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-21 01:55:49 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-21 01:55:49 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-21 01:55:49 (4119) [INFO] * 2023-07-21 01:55:49 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-21 01:55:49 (4089) [INFO] * 2023-07-21 01:59:57 (4102) [INFO] * 2023-07-21 01:59:57 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-21 01:59:57 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-21 01:59:58 (4119) [INFO] * 2023-07-21 01:59:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-21 01:59:58 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-21 02:00:01 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-21 02:00:01 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-21 02:03:03 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-21 02:03:03 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-21 02:03:03 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-21 02:03:03 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-21 02:03:03 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-21 02:03:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-21 02:03:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5GrDwmZepr/ea_profile.json * 2023-07-21 02:03:06 (2259) [INFO] Backed up EA4 profile to /tmp/5GrDwmZepr/ea_profile.json * 2023-07-21 02:03:09 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-22 01:57:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-22 01:57:29 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-22 01:57:29 (1700) [INFO] Checking if your system is up to date: * 2023-07-22 01:57:29 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-22 01:57:29 (4089) [INFO] * 2023-07-22 01:57:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-22 01:57:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-22 01:57:30 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-22 01:57:30 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-22 01:57:30 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-22 01:57:30 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-22 01:57:30 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-22 01:57:30 (4119) [INFO] * 2023-07-22 01:57:30 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-22 01:57:30 (4089) [INFO] * 2023-07-22 02:01:29 (4102) [INFO] * 2023-07-22 02:01:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-22 02:01:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-22 02:01:29 (4119) [INFO] * 2023-07-22 02:01:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-22 02:01:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-22 02:01:32 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-22 02:01:32 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-22 02:04:51 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-22 02:04:51 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-22 02:04:51 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-22 02:04:51 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-22 02:04:51 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-22 02:04:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-22 02:04:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_idw6u_BcS/ea_profile.json * 2023-07-22 02:04:54 (2259) [INFO] Backed up EA4 profile to /tmp/_idw6u_BcS/ea_profile.json * 2023-07-22 02:04:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-23 02:02:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-23 02:02:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-23 02:02:08 (1700) [INFO] Checking if your system is up to date: * 2023-07-23 02:02:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-23 02:02:08 (4089) [INFO] * 2023-07-23 02:02:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-23 02:02:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-23 02:02:09 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-23 02:02:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-23 02:02:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-23 02:02:09 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-23 02:02:09 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-23 02:02:09 (4119) [INFO] * 2023-07-23 02:02:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-23 02:02:09 (4089) [INFO] * 2023-07-23 02:04:09 (4102) [INFO] http://repo1.sea.innoscale.net/centos/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to repo1.sea.innoscale.net:80; Operation now in progress" * 2023-07-23 02:04:09 (4102) [INFO] Trying other mirror. * 2023-07-23 02:05:50 (4102) [INFO] http://repo1.sea.innoscale.net/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] curl#7 - "Failed connect to repo1.sea.innoscale.net:80; Operation now in progress" * 2023-07-23 02:05:50 (4102) [INFO] Trying other mirror. * 2023-07-23 02:05:50 (4102) [INFO] http://repo1.sea.innoscale.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo1.sea.innoscale.net:80; Operation now in progress" * 2023-07-23 02:05:50 (4102) [INFO] Trying other mirror. * 2023-07-23 02:06:46 (4102) [INFO] * 2023-07-23 02:06:46 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-23 02:06:46 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-23 02:06:46 (4119) [INFO] * 2023-07-23 02:06:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-23 02:06:46 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-23 02:06:49 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-23 02:06:49 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-23 02:10:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-23 02:10:16 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30051 milliseconds with 0 out of 0 bytes received') https://download.imunify360.com/el/7/slot-2/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2023-07-23 02:10:16 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-23 02:10:16 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-23 02:10:16 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-23 02:10:16 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-23 02:10:16 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-23 02:10:16 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-23 02:10:16 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-23 02:10:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lG2_XWiv_z/ea_profile.json * 2023-07-23 02:10:18 (2259) [INFO] Backed up EA4 profile to /tmp/lG2_XWiv_z/ea_profile.json * 2023-07-23 02:10:23 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-24 02:02:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-24 02:02:38 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-24 02:02:38 (1700) [INFO] Checking if your system is up to date: * 2023-07-24 02:02:38 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-24 02:02:38 (4089) [INFO] * 2023-07-24 02:02:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-24 02:02:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-24 02:02:38 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-24 02:02:38 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-24 02:02:38 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-24 02:02:38 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-24 02:02:39 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-24 02:02:39 (4119) [INFO] * 2023-07-24 02:02:39 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-24 02:02:39 (4089) [INFO] * 2023-07-24 02:07:13 (4102) [INFO] * 2023-07-24 02:07:13 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-24 02:07:13 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-24 02:07:13 (4119) [INFO] * 2023-07-24 02:07:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-24 02:07:13 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-24 02:07:17 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-24 02:07:17 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-24 02:10:54 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-24 02:10:54 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-24 02:10:55 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-24 02:10:55 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-24 02:10:55 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-24 02:10:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-24 02:10:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Sqyb86Vf56/ea_profile.json * 2023-07-24 02:10:57 (2259) [INFO] Backed up EA4 profile to /tmp/Sqyb86Vf56/ea_profile.json * 2023-07-24 02:10:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-25 01:55:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-25 01:55:31 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-25 01:55:31 (1700) [INFO] Checking if your system is up to date: * 2023-07-25 01:55:31 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-25 01:55:31 (4089) [INFO] * 2023-07-25 01:55:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-25 01:55:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-25 01:55:31 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-25 01:55:31 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-25 01:55:31 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-25 01:55:31 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-25 01:55:31 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-25 01:55:31 (4119) [INFO] * 2023-07-25 01:55:31 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-25 01:55:31 (4089) [INFO] * 2023-07-25 01:57:53 (4102) [INFO] http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30000 milliseconds') * 2023-07-25 01:57:53 (4102) [INFO] Trying other mirror. * 2023-07-25 01:59:51 (4102) [INFO] * 2023-07-25 01:59:51 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-25 01:59:51 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-25 01:59:51 (4119) [INFO] * 2023-07-25 01:59:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-25 01:59:51 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-25 01:59:56 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-25 01:59:56 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-25 02:03:17 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-25 02:03:17 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30012 milliseconds with 0 out of 0 bytes received') http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/c7388bd59d1e5afd791b1dcca97c3a7863e093a0cfe937ae895030a09de53a9b-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/extras/x86_64/repodata/c7388bd59d1e5afd791b1dcca97c3a7863e093a0cfe937ae895030a09de53a9b-filelists.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') Trying other mirror. * 2023-07-25 02:03:17 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-25 02:03:17 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-25 02:03:17 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-25 02:03:18 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-25 02:03:18 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-25 02:03:18 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-25 02:03:18 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-25 02:03:18 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cMkdhmMNoT/ea_profile.json * 2023-07-25 02:03:20 (2259) [INFO] Backed up EA4 profile to /tmp/cMkdhmMNoT/ea_profile.json * 2023-07-25 02:03:22 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-26 02:01:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-26 02:01:03 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-26 02:01:03 (1700) [INFO] Checking if your system is up to date: * 2023-07-26 02:01:03 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-26 02:01:03 (4089) [INFO] * 2023-07-26 02:01:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-26 02:01:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-26 02:01:03 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-26 02:01:03 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-26 02:01:03 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-26 02:01:03 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-26 02:01:04 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-26 02:01:04 (4119) [INFO] * 2023-07-26 02:01:04 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-26 02:01:04 (4089) [INFO] * 2023-07-26 02:05:14 (4102) [INFO] * 2023-07-26 02:05:14 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-26 02:05:14 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-26 02:05:14 (4119) [INFO] * 2023-07-26 02:05:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-26 02:05:14 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-26 02:05:18 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-26 02:05:18 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-26 02:08:37 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-26 02:08:37 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30015 milliseconds with 0 out of 0 bytes received') * 2023-07-26 02:08:37 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-26 02:08:37 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-26 02:08:37 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-26 02:08:38 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-26 02:08:38 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-26 02:08:38 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-26 02:08:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-26 02:08:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Awb0kIKfdt/ea_profile.json * 2023-07-26 02:08:40 (2259) [INFO] Backed up EA4 profile to /tmp/Awb0kIKfdt/ea_profile.json * 2023-07-26 02:08:44 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-27 02:07:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-27 02:07:55 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-27 02:07:55 (1700) [INFO] Checking if your system is up to date: * 2023-07-27 02:07:55 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-27 02:07:55 (4089) [INFO] * 2023-07-27 02:07:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-27 02:07:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-27 02:07:55 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-27 02:07:55 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-27 02:07:55 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-27 02:07:55 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-27 02:07:56 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-27 02:07:56 (4119) [INFO] * 2023-07-27 02:07:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-27 02:07:56 (4089) [INFO] * 2023-07-27 02:11:21 (4102) [INFO] http://mirror.keystealth.org/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-07-27 02:11:21 (4102) [INFO] Trying other mirror. * 2023-07-27 02:11:36 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-07-27 02:11:36 (4102) [INFO] Trying other mirror. * 2023-07-27 02:11:52 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:11:52 (4102) [INFO] Trying other mirror. * 2023-07-27 02:11:53 (4102) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.7/wp-toolkit/repodata/4edbd5ff3217904c0847e588d6c048883aa3fa066360a275cea7241125f8d374-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:11:53 (4102) [INFO] Trying other mirror. * 2023-07-27 02:11:53 (4102) [INFO] http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-07-27 02:11:53 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:07 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:07 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:08 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:08 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:08 (4102) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:08 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:09 (4102) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:09 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:21 (4102) [INFO] http://ftp.osuosl.org/pub/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-07-27 02:12:21 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:24 (4102) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:24 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:25 (4102) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:25 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:40 (4102) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:40 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:56 (4102) [INFO] http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-07-27 02:12:56 (4102) [INFO] Trying other mirror. * 2023-07-27 02:12:56 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-07-27 02:12:56 (4102) [INFO] * 2023-07-27 02:12:56 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-07-27 02:12:56 (4102) [INFO] * 2023-07-27 02:12:56 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-07-27 02:12:56 (4102) [INFO] * 2023-07-27 02:12:57 (4102) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:12:57 (4102) [INFO] Trying other mirror. * 2023-07-27 02:13:12 (4102) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:13:12 (4102) [INFO] Trying other mirror. * 2023-07-27 02:13:28 (4102) [INFO] https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-07-27 02:13:28 (4102) [INFO] Trying other mirror. * 2023-07-27 02:13:43 (4102) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:13:43 (4102) [INFO] Trying other mirror. * 2023-07-27 02:13:44 (4102) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-07-27 02:13:44 (4102) [INFO] Trying other mirror. * 2023-07-27 02:13:47 (4102) [INFO] https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-07-27 02:13:47 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:03 (4102) [INFO] https://epel.mcn.us.ssimn.org/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden * 2023-07-27 02:14:03 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:03 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-07-27 02:14:03 (4102) [INFO] * 2023-07-27 02:14:03 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-07-27 02:14:03 (4102) [INFO] * 2023-07-27 02:14:03 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-07-27 02:14:03 (4102) [INFO] * 2023-07-27 02:14:03 (4102) [INFO] https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:03 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:18 (4102) [INFO] http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-07-27 02:14:18 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:19 (4102) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:19 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:20 (4102) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:20 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:22 (4102) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:22 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:37 (4102) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:37 (4102) [INFO] Trying other mirror. * 2023-07-27 02:14:52 (4102) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:14:52 (4102) [INFO] Trying other mirror. * 2023-07-27 02:15:23 (4102) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2023-07-27 02:15:23 (4102) [INFO] Trying other mirror. * 2023-07-27 02:15:38 (4102) [INFO] https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:15:38 (4102) [INFO] Trying other mirror. * 2023-07-27 02:15:54 (4102) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:15:54 (4102) [INFO] Trying other mirror. * 2023-07-27 02:15:54 (4102) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:15:54 (4102) [INFO] Trying other mirror. * 2023-07-27 02:16:10 (4102) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:16:10 (4102) [INFO] Trying other mirror. * 2023-07-27 02:16:25 (4102) [INFO] http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-07-27 02:16:25 (4102) [INFO] Trying other mirror. * 2023-07-27 02:16:41 (4102) [INFO] https://mirror.team-cymru.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:16:41 (4102) [INFO] Trying other mirror. * 2023-07-27 02:16:58 (4102) [INFO] https://mirror.servaxnet.com/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-07-27 02:16:58 (4102) [INFO] Trying other mirror. * 2023-07-27 02:16:58 (4102) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/ca0d6cba5376df6adaf253dfd89370fd472a7ed55da79d563e266d8a9a13e019-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-07-27 02:16:58 (4102) [INFO] Trying other mirror. * 2023-07-27 02:17:10 (4102) [INFO] * 2023-07-27 02:17:10 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-27 02:17:10 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-27 02:17:11 (4119) [INFO] * 2023-07-27 02:17:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-27 02:17:11 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-27 02:17:15 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-27 02:17:15 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-27 02:20:53 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-27 02:20:53 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-27 02:20:54 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-27 02:20:54 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-27 02:20:54 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-27 02:20:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-27 02:20:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S7d9Hv_FrX/ea_profile.json * 2023-07-27 02:20:57 (2259) [INFO] Backed up EA4 profile to /tmp/S7d9Hv_FrX/ea_profile.json * 2023-07-27 02:21:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-28 02:04:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-28 02:04:01 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-28 02:04:01 (1700) [INFO] Checking if your system is up to date: * 2023-07-28 02:04:01 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-28 02:04:01 (4089) [INFO] * 2023-07-28 02:04:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-28 02:04:02 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-28 02:04:02 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-28 02:04:02 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-28 02:04:02 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-28 02:04:02 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-28 02:04:02 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-28 02:04:03 (4119) [INFO] * 2023-07-28 02:04:03 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-28 02:04:03 (4089) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-28 02:04:57 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-28 02:04:57 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-28 02:04:57 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-28 02:04:57 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-28 02:04:57 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-28 02:04:57 (4102) [INFO] yum --disablerepo= ... * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-28 02:04:57 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-28 02:04:57 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] yum-config-manager --disable * 2023-07-28 02:04:57 (4102) [INFO] or * 2023-07-28 02:04:57 (4102) [INFO] subscription-manager repos --disable= * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-28 02:04:57 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-28 02:04:57 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-28 02:04:57 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-28 02:04:57 (4102) [INFO] compromise: * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-28 02:04:57 (4102) [INFO] * 2023-07-28 02:04:57 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-28 02:04:57 (4119) [INFO] * 2023-07-28 02:04:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-28 02:04:57 (1721) [INFO] Checking /scripts/sysup * 2023-07-28 02:04:57 (4088) [INFO] Running: /scripts/sysup * 2023-07-28 02:04:57 (4089) [INFO] * 2023-07-28 02:04:58 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-28 02:05:00 (4102) [INFO] All Needed Packages are already installed. * 2023-07-28 02:05:00 (4119) [INFO] * 2023-07-28 02:05:04 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-28 02:05:04 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-28 02:13:28 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-28 02:13:28 (1567) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.mirror.constant.com/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.arizona.edu/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos-distro.cavecreek.net/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.pit.teraswitch.com/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.atl.genesisadaptive.com/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://packages.oit.ncsu.edu/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://forksystems.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.steadfastnet.com/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.wcupa.edu/centos/7.9.2009/updates/x86_64/repodata/6df07470753b2bea2aaf6f798d9b03d8a1f0a8d483270e4398d43becb1cc3393-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-07-28 02:13:28 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-28 02:13:28 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-28 02:13:28 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-28 02:13:28 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-28 02:13:28 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-28 02:13:28 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-28 02:13:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-28 02:13:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XnJxEJg764/ea_profile.json * 2023-07-28 02:13:31 (2259) [INFO] Backed up EA4 profile to /tmp/XnJxEJg764/ea_profile.json * 2023-07-28 02:13:35 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-29 02:03:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-29 02:03:53 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-29 02:03:53 (1700) [INFO] Checking if your system is up to date: * 2023-07-29 02:03:53 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-29 02:03:53 (4089) [INFO] * 2023-07-29 02:03:54 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-29 02:03:54 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-29 02:03:54 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-29 02:03:54 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-29 02:03:54 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-29 02:03:54 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-29 02:03:55 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-29 02:03:55 (4119) [INFO] * 2023-07-29 02:03:55 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-29 02:03:55 (4089) [INFO] * 2023-07-29 02:08:10 (4102) [INFO] * 2023-07-29 02:08:10 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-29 02:08:10 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-29 02:08:10 (4119) [INFO] * 2023-07-29 02:08:10 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-29 02:08:10 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-29 02:08:13 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-29 02:08:13 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-29 02:11:38 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-29 02:11:38 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30065 milliseconds') * 2023-07-29 02:11:38 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-29 02:11:38 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-29 02:11:38 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-29 02:11:39 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-29 02:11:39 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-29 02:11:39 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-29 02:11:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-29 02:11:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9GiLnOLLQC/ea_profile.json * 2023-07-29 02:11:41 (2259) [INFO] Backed up EA4 profile to /tmp/9GiLnOLLQC/ea_profile.json * 2023-07-29 02:11:44 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-30 02:04:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-30 02:04:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-30 02:04:09 (1700) [INFO] Checking if your system is up to date: * 2023-07-30 02:04:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-30 02:04:09 (4089) [INFO] * 2023-07-30 02:04:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-30 02:04:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-30 02:04:09 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-30 02:04:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-30 02:04:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-30 02:04:09 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-30 02:04:10 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-30 02:04:10 (4119) [INFO] * 2023-07-30 02:04:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-30 02:04:10 (4089) [INFO] * 2023-07-30 02:08:02 (4102) [INFO] * 2023-07-30 02:08:02 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-30 02:08:02 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-30 02:08:02 (4119) [INFO] * 2023-07-30 02:08:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-30 02:08:02 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-30 02:08:05 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-30 02:08:05 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-30 02:11:06 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-30 02:11:06 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-07-30 02:11:06 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-30 02:11:06 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-30 02:11:06 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-30 02:11:06 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-30 02:11:06 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-30 02:11:06 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-30 02:11:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-30 02:11:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jfxrzQk8wf/ea_profile.json * 2023-07-30 02:11:08 (2259) [INFO] Backed up EA4 profile to /tmp/jfxrzQk8wf/ea_profile.json * 2023-07-30 02:11:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-31 01:54:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-07-31 01:54:51 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-31 01:54:51 (1700) [INFO] Checking if your system is up to date: * 2023-07-31 01:54:51 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-31 01:54:51 (4089) [INFO] * 2023-07-31 01:54:52 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-31 01:54:52 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-07-31 01:54:52 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-31 01:54:52 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-31 01:54:52 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-31 01:54:52 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-07-31 01:54:52 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-07-31 01:54:52 (4119) [INFO] * 2023-07-31 01:54:52 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-31 01:54:52 (4089) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-07-31 01:55:46 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-07-31 01:55:46 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-07-31 01:55:46 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-07-31 01:55:46 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-07-31 01:55:46 (4102) [INFO] packages for the previous distribution release still work). * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-07-31 01:55:46 (4102) [INFO] yum --disablerepo= ... * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-07-31 01:55:46 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-07-31 01:55:46 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] yum-config-manager --disable * 2023-07-31 01:55:46 (4102) [INFO] or * 2023-07-31 01:55:46 (4102) [INFO] subscription-manager repos --disable= * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-07-31 01:55:46 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-07-31 01:55:46 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-07-31 01:55:46 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-07-31 01:55:46 (4102) [INFO] compromise: * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-07-31 01:55:46 (4102) [INFO] * 2023-07-31 01:55:46 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-07-31 01:55:46 (4119) [INFO] * 2023-07-31 01:55:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-31 01:55:46 (1721) [INFO] Checking /scripts/sysup * 2023-07-31 01:55:46 (4088) [INFO] Running: /scripts/sysup * 2023-07-31 01:55:46 (4089) [INFO] * 2023-07-31 01:55:47 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-07-31 01:55:48 (4102) [INFO] All Needed Packages are already installed. * 2023-07-31 01:55:48 (4119) [INFO] * 2023-07-31 01:55:51 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-07-31 01:55:51 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-07-31 01:56:44 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-07-31 01:56:44 (1567) [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-07-31 01:56:44 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-07-31 01:56:44 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-07-31 01:56:44 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-07-31 01:56:45 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-07-31 01:56:45 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-07-31 01:56:45 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-07-31 01:56:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-31 01:56:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FAAdBwc_2d/ea_profile.json * 2023-07-31 02:00:33 (2259) [INFO] Backed up EA4 profile to /tmp/FAAdBwc_2d/ea_profile.json * 2023-07-31 02:00:35 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-01 02:05:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-01 02:05:21 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-01 02:05:21 (1700) [INFO] Checking if your system is up to date: * 2023-08-01 02:05:21 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-01 02:05:21 (4089) [INFO] * 2023-08-01 02:05:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-01 02:05:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-01 02:05:22 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-01 02:05:22 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-01 02:05:22 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-01 02:05:22 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-01 02:05:22 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-08-01 02:05:22 (4119) [INFO] * 2023-08-01 02:05:22 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-01 02:05:22 (4089) [INFO] * 2023-08-01 02:09:33 (4102) [INFO] * 2023-08-01 02:09:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-08-01 02:09:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-01 02:09:34 (4119) [INFO] * 2023-08-01 02:09:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-01 02:09:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-01 02:09:36 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-01 02:09:37 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-01 02:13:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-01 02:13:01 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-01 02:13:02 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-01 02:13:02 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-01 02:13:02 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-01 02:13:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-01 02:13:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wmwhRRWXOw/ea_profile.json * 2023-08-01 02:13:05 (2259) [INFO] Backed up EA4 profile to /tmp/wmwhRRWXOw/ea_profile.json * 2023-08-01 02:13:08 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-02 01:02:15 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-02 01:02:15 (1700) [INFO] Checking if your system is up to date: * 2023-08-02 01:02:15 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-02 01:02:15 (4089) [INFO] * 2023-08-02 01:02:15 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-02 01:02:16 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-02 01:02:16 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-02 01:02:16 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-02 01:02:16 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-02 01:02:16 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-02 01:02:16 (4102) [INFO] Other repos take up 724 k of disk space (use --verbose for details) * 2023-08-02 01:02:16 (4119) [INFO] * 2023-08-02 01:02:16 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-02 01:02:16 (4089) [INFO] * 2023-08-02 01:05:10 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/bb204cba75bd4e990c651342fb91777a3c1a69b55057f3877b70bdfc1beec26d-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-08-02 01:05:10 (4102) [INFO] Trying other mirror. * 2023-08-02 01:05:10 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-08-02 01:05:10 (4102) [INFO] * 2023-08-02 01:05:10 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-08-02 01:05:10 (4102) [INFO] * 2023-08-02 01:05:10 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-08-02 01:05:10 (4102) [INFO] * 2023-08-02 01:05:25 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/173471916b64a1cd020ad010851dd3f03357bff90dfdea045138e8955a9220bf-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-08-02 01:05:25 (4102) [INFO] Trying other mirror. * 2023-08-02 01:05:42 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/bb204cba75bd4e990c651342fb91777a3c1a69b55057f3877b70bdfc1beec26d-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-08-02 01:05:42 (4102) [INFO] Trying other mirror. * 2023-08-02 01:05:42 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/173471916b64a1cd020ad010851dd3f03357bff90dfdea045138e8955a9220bf-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-08-02 01:05:42 (4102) [INFO] Trying other mirror. * 2023-08-02 01:05:43 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/173471916b64a1cd020ad010851dd3f03357bff90dfdea045138e8955a9220bf-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-08-02 01:05:43 (4102) [INFO] Trying other mirror. * 2023-08-02 01:06:23 (4102) [INFO] * 2023-08-02 01:06:23 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-08-02 01:06:23 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-02 01:06:23 (4119) [INFO] * 2023-08-02 01:06:23 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-02 01:06:23 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-02 01:06:28 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-02 01:06:28 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-02 01:09:51 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-02 01:09:51 (1567) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/912f2fe04f6fa55cc061097985bdb9e11c38f927ed4ce0d19d1247fd628493fd-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/. * 2023-08-02 01:09:51 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-02 01:09:51 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-02 01:09:51 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-02 01:09:52 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-02 01:09:52 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-02 01:09:52 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-02 01:09:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-02 01:09:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pQJ3TyFfes/ea_profile.json * 2023-08-02 01:09:54 (2259) [INFO] Backed up EA4 profile to /tmp/pQJ3TyFfes/ea_profile.json * 2023-08-02 01:09:57 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-03 02:02:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-03 02:02:35 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-03 02:02:35 (1700) [INFO] Checking if your system is up to date: * 2023-08-03 02:02:35 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-03 02:02:35 (4089) [INFO] * 2023-08-03 02:02:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-03 02:02:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-03 02:02:36 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-03 02:02:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-03 02:02:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-03 02:02:36 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-03 02:02:36 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-03 02:02:36 (4119) [INFO] * 2023-08-03 02:02:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-03 02:02:36 (4089) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-03 02:03:32 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-03 02:03:32 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-03 02:03:32 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-03 02:03:32 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-03 02:03:32 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-03 02:03:32 (4102) [INFO] yum --disablerepo= ... * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-03 02:03:32 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-03 02:03:32 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] yum-config-manager --disable * 2023-08-03 02:03:32 (4102) [INFO] or * 2023-08-03 02:03:32 (4102) [INFO] subscription-manager repos --disable= * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-03 02:03:32 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-03 02:03:32 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-03 02:03:32 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-03 02:03:32 (4102) [INFO] compromise: * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-03 02:03:32 (4102) [INFO] * 2023-08-03 02:03:32 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-03 02:03:32 (4119) [INFO] * 2023-08-03 02:03:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-03 02:03:32 (1721) [INFO] Checking /scripts/sysup * 2023-08-03 02:03:32 (4088) [INFO] Running: /scripts/sysup * 2023-08-03 02:03:32 (4089) [INFO] * 2023-08-03 02:03:33 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-03 02:03:35 (4102) [INFO] All Needed Packages are already installed. * 2023-08-03 02:03:35 (4119) [INFO] * 2023-08-03 02:03:39 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-03 02:03:39 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-03 02:09:31 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-03 02:09:31 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-03 02:09:32 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-03 02:09:32 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-03 02:09:32 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-03 02:09:32 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-03 02:09:32 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0s62Ma9tkD/ea_profile.json * 2023-08-03 02:09:34 (2259) [INFO] Backed up EA4 profile to /tmp/0s62Ma9tkD/ea_profile.json * 2023-08-03 02:09:38 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-04 02:03:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-04 02:03:47 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-04 02:03:47 (1700) [INFO] Checking if your system is up to date: * 2023-08-04 02:03:47 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-04 02:03:47 (4089) [INFO] * 2023-08-04 02:03:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-04 02:03:48 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-04 02:03:48 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-04 02:03:48 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-04 02:03:48 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-04 02:03:48 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-04 02:03:48 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-04 02:03:48 (4119) [INFO] * 2023-08-04 02:03:48 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-04 02:03:48 (4089) [INFO] * 2023-08-04 02:07:39 (4102) [INFO] * 2023-08-04 02:07:39 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-04 02:07:39 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-04 02:07:40 (4119) [INFO] * 2023-08-04 02:07:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-04 02:07:40 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-04 02:07:43 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-04 02:07:43 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-04 02:10:43 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-04 02:10:43 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-04 02:10:44 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-04 02:10:44 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-04 02:10:44 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-04 02:10:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-04 02:10:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bobnH3Il_c/ea_profile.json * 2023-08-04 02:10:46 (2259) [INFO] Backed up EA4 profile to /tmp/bobnH3Il_c/ea_profile.json * 2023-08-04 02:10:49 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-05 02:04:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-05 02:04:14 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-05 02:04:14 (1700) [INFO] Checking if your system is up to date: * 2023-08-05 02:04:14 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-05 02:04:14 (4089) [INFO] * 2023-08-05 02:04:15 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-05 02:04:15 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-05 02:04:15 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-05 02:04:15 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-05 02:04:15 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-05 02:04:15 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-05 02:04:16 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-05 02:04:16 (4119) [INFO] * 2023-08-05 02:04:16 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-05 02:04:16 (4089) [INFO] * 2023-08-05 02:08:44 (4102) [INFO] * 2023-08-05 02:08:44 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-05 02:08:44 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-05 02:08:44 (4119) [INFO] * 2023-08-05 02:08:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-05 02:08:44 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-05 02:08:48 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-05 02:08:48 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-05 02:12:28 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-05 02:12:28 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-05 02:12:29 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-05 02:12:29 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-05 02:12:29 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-05 02:12:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-05 02:12:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CLCfYf1lQG/ea_profile.json * 2023-08-05 02:12:32 (2259) [INFO] Backed up EA4 profile to /tmp/CLCfYf1lQG/ea_profile.json * 2023-08-05 02:12:36 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-06 02:00:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-06 02:00:51 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-06 02:00:51 (1700) [INFO] Checking if your system is up to date: * 2023-08-06 02:00:51 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-06 02:00:51 (4089) [INFO] * 2023-08-06 02:00:52 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-06 02:00:52 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-06 02:00:52 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-06 02:00:52 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-06 02:00:52 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-06 02:00:52 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-06 02:00:53 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-06 02:00:53 (4119) [INFO] * 2023-08-06 02:00:53 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-06 02:00:53 (4089) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-06 02:01:47 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-06 02:01:47 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-06 02:01:47 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-06 02:01:47 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-06 02:01:47 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-06 02:01:47 (4102) [INFO] yum --disablerepo= ... * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-06 02:01:47 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-06 02:01:47 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] yum-config-manager --disable * 2023-08-06 02:01:47 (4102) [INFO] or * 2023-08-06 02:01:47 (4102) [INFO] subscription-manager repos --disable= * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-06 02:01:47 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-06 02:01:47 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-06 02:01:47 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-06 02:01:47 (4102) [INFO] compromise: * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-06 02:01:47 (4102) [INFO] * 2023-08-06 02:01:47 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-06 02:01:47 (4119) [INFO] * 2023-08-06 02:01:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-06 02:01:47 (1721) [INFO] Checking /scripts/sysup * 2023-08-06 02:01:47 (4088) [INFO] Running: /scripts/sysup * 2023-08-06 02:01:47 (4089) [INFO] * 2023-08-06 02:01:48 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-06 02:01:50 (4102) [INFO] All Needed Packages are already installed. * 2023-08-06 02:01:50 (4119) [INFO] * 2023-08-06 02:01:52 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-06 02:01:52 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-06 02:08:14 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-06 02:08:14 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-06 02:08:15 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-06 02:08:15 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-06 02:08:15 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-06 02:08:15 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-06 02:08:15 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WpaZIkCcRv/ea_profile.json * 2023-08-06 02:08:17 (2259) [INFO] Backed up EA4 profile to /tmp/WpaZIkCcRv/ea_profile.json * 2023-08-06 02:08:20 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-07 02:02:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-07 02:02:45 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-07 02:02:45 (1700) [INFO] Checking if your system is up to date: * 2023-08-07 02:02:45 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-07 02:02:45 (4089) [INFO] * 2023-08-07 02:02:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-07 02:02:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-07 02:02:46 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-07 02:02:46 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-07 02:02:46 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-07 02:02:46 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-07 02:02:46 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-07 02:02:46 (4119) [INFO] * 2023-08-07 02:02:46 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-07 02:02:46 (4089) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-07 02:03:41 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-07 02:03:41 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-07 02:03:41 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-07 02:03:41 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-07 02:03:41 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-07 02:03:41 (4102) [INFO] yum --disablerepo= ... * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-07 02:03:41 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-07 02:03:41 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] yum-config-manager --disable * 2023-08-07 02:03:41 (4102) [INFO] or * 2023-08-07 02:03:41 (4102) [INFO] subscription-manager repos --disable= * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-07 02:03:41 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-07 02:03:41 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-07 02:03:41 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-07 02:03:41 (4102) [INFO] compromise: * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-07 02:03:41 (4102) [INFO] * 2023-08-07 02:03:41 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-07 02:03:41 (4119) [INFO] * 2023-08-07 02:03:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-07 02:03:41 (1721) [INFO] Checking /scripts/sysup * 2023-08-07 02:03:41 (4088) [INFO] Running: /scripts/sysup * 2023-08-07 02:03:41 (4089) [INFO] * 2023-08-07 02:03:42 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-07 02:03:43 (4102) [INFO] All Needed Packages are already installed. * 2023-08-07 02:03:43 (4119) [INFO] * 2023-08-07 02:03:46 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-07 02:03:46 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-07 02:10:40 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-07 02:10:40 (1567) [ERROR] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-08-07 02:10:40 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-07 02:10:40 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-07 02:10:40 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-07 02:10:41 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-07 02:10:41 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-07 02:10:41 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-07 02:10:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-07 02:10:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V5UN73bCwt/ea_profile.json * 2023-08-07 02:10:43 (2259) [INFO] Backed up EA4 profile to /tmp/V5UN73bCwt/ea_profile.json * 2023-08-07 02:10:46 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-08 02:01:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-08 02:01:33 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-08 02:01:33 (1700) [INFO] Checking if your system is up to date: * 2023-08-08 02:01:33 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-08 02:01:33 (4089) [INFO] * 2023-08-08 02:01:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-08 02:01:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-08 02:01:33 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-08 02:01:33 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-08 02:01:33 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-08 02:01:33 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-08 02:01:34 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-08 02:01:34 (4119) [INFO] * 2023-08-08 02:01:34 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-08 02:01:34 (4089) [INFO] * 2023-08-08 02:05:21 (4102) [INFO] * 2023-08-08 02:05:21 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-08 02:05:21 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-08 02:05:22 (4119) [INFO] * 2023-08-08 02:05:22 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-08 02:05:22 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-08 02:05:26 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-08 02:05:26 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-08 02:08:24 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-08 02:08:24 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-08 02:08:25 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-08 02:08:25 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-08 02:08:25 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-08 02:08:25 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-08 02:08:25 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Rf9vGAHbk8/ea_profile.json * 2023-08-08 02:08:27 (2259) [INFO] Backed up EA4 profile to /tmp/Rf9vGAHbk8/ea_profile.json * 2023-08-08 02:08:31 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-09 02:02:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-09 02:02:38 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-09 02:02:38 (1700) [INFO] Checking if your system is up to date: * 2023-08-09 02:02:38 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-09 02:02:38 (4089) [INFO] * 2023-08-09 02:02:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-09 02:02:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-09 02:02:39 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-09 02:02:39 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-09 02:02:39 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-09 02:02:39 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-09 02:02:40 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-09 02:02:40 (4119) [INFO] * 2023-08-09 02:02:40 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-09 02:02:40 (4089) [INFO] * 2023-08-09 02:06:45 (4102) [INFO] * 2023-08-09 02:06:45 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-09 02:06:45 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-09 02:06:45 (4119) [INFO] * 2023-08-09 02:06:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-09 02:06:45 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-09 02:06:49 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-09 02:06:49 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-09 02:09:59 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-09 02:09:59 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-09 02:10:00 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-09 02:10:00 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-09 02:10:00 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-09 02:10:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-09 02:10:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dli0hmQcYn/ea_profile.json * 2023-08-09 02:10:02 (2259) [INFO] Backed up EA4 profile to /tmp/dli0hmQcYn/ea_profile.json * 2023-08-09 02:10:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-10 02:03:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-10 02:03:40 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-10 02:03:40 (1700) [INFO] Checking if your system is up to date: * 2023-08-10 02:03:40 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-10 02:03:40 (4089) [INFO] * 2023-08-10 02:03:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-10 02:03:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-10 02:03:41 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-10 02:03:41 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-10 02:03:41 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-10 02:03:41 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-10 02:03:41 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-10 02:03:41 (4119) [INFO] * 2023-08-10 02:03:41 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-10 02:03:41 (4089) [INFO] * 2023-08-10 02:07:53 (4102) [INFO] * 2023-08-10 02:07:53 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-10 02:07:53 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-10 02:07:53 (4119) [INFO] * 2023-08-10 02:07:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-10 02:07:53 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-10 02:07:57 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-10 02:07:57 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-10 02:11:36 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-10 02:11:36 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-10 02:11:37 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-10 02:11:37 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-10 02:11:37 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-10 02:11:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-10 02:11:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pu5DoQYpbq/ea_profile.json * 2023-08-10 02:11:40 (2259) [INFO] Backed up EA4 profile to /tmp/pu5DoQYpbq/ea_profile.json * 2023-08-10 02:11:43 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-11 02:01:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-11 02:01:26 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-11 02:01:26 (1700) [INFO] Checking if your system is up to date: * 2023-08-11 02:01:26 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-11 02:01:26 (4089) [INFO] * 2023-08-11 02:01:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-11 02:01:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-11 02:01:27 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-11 02:01:27 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-11 02:01:27 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-11 02:01:27 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-11 02:01:28 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-11 02:01:28 (4119) [INFO] * 2023-08-11 02:01:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-11 02:01:28 (4089) [INFO] * 2023-08-11 02:05:33 (4102) [INFO] * 2023-08-11 02:05:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-11 02:05:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-11 02:05:33 (4119) [INFO] * 2023-08-11 02:05:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-11 02:05:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-11 02:05:37 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-11 02:05:37 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-11 02:08:55 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-11 02:08:55 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-11 02:08:56 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-11 02:08:56 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-11 02:08:56 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-11 02:08:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-11 02:08:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ib6oBtCo8g/ea_profile.json * 2023-08-11 02:08:58 (2259) [INFO] Backed up EA4 profile to /tmp/Ib6oBtCo8g/ea_profile.json * 2023-08-11 02:09:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-12 02:02:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-12 02:02:14 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-12 02:02:14 (1700) [INFO] Checking if your system is up to date: * 2023-08-12 02:02:14 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-12 02:02:14 (4089) [INFO] * 2023-08-12 02:02:14 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-12 02:02:14 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-12 02:02:14 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-12 02:02:14 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-12 02:02:14 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-12 02:02:14 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-12 02:02:15 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-12 02:02:15 (4119) [INFO] * 2023-08-12 02:02:15 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-12 02:02:15 (4089) [INFO] * 2023-08-12 02:06:41 (4102) [INFO] * 2023-08-12 02:06:41 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-12 02:06:41 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-12 02:06:41 (4119) [INFO] * 2023-08-12 02:06:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-12 02:06:41 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-12 02:06:46 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-12 02:06:46 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-12 02:10:27 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-12 02:10:27 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-12 02:10:28 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-12 02:10:28 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-12 02:10:28 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-12 02:10:28 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-12 02:10:28 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bbn_uSM79x/ea_profile.json * 2023-08-12 02:10:30 (2259) [INFO] Backed up EA4 profile to /tmp/bbn_uSM79x/ea_profile.json * 2023-08-12 02:10:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-13 02:02:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-13 02:02:56 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-13 02:02:56 (1700) [INFO] Checking if your system is up to date: * 2023-08-13 02:02:56 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-13 02:02:56 (4089) [INFO] * 2023-08-13 02:02:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-13 02:02:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-13 02:02:56 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-13 02:02:56 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-13 02:02:56 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-13 02:02:56 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-13 02:02:56 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-13 02:02:56 (4119) [INFO] * 2023-08-13 02:02:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-13 02:02:56 (4089) [INFO] * 2023-08-13 02:07:19 (4102) [INFO] * 2023-08-13 02:07:19 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-13 02:07:19 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-13 02:07:19 (4119) [INFO] * 2023-08-13 02:07:19 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-13 02:07:19 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-13 02:07:22 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-13 02:07:22 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-13 02:10:54 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-13 02:10:54 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-13 02:10:55 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-13 02:10:55 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-13 02:10:55 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-13 02:10:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-13 02:10:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sTc9kWiVqG/ea_profile.json * 2023-08-13 02:10:57 (2259) [INFO] Backed up EA4 profile to /tmp/sTc9kWiVqG/ea_profile.json * 2023-08-13 02:11:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-14 02:00:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-14 02:00:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-14 02:00:07 (1700) [INFO] Checking if your system is up to date: * 2023-08-14 02:00:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-14 02:00:07 (4089) [INFO] * 2023-08-14 02:00:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-14 02:00:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-14 02:00:08 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-14 02:00:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-14 02:00:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-14 02:00:08 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-14 02:00:08 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-14 02:00:08 (4119) [INFO] * 2023-08-14 02:00:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-14 02:00:08 (4089) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-14 02:01:04 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-14 02:01:04 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-14 02:01:04 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-14 02:01:04 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-14 02:01:04 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-14 02:01:04 (4102) [INFO] yum --disablerepo= ... * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-14 02:01:04 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-14 02:01:04 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] yum-config-manager --disable * 2023-08-14 02:01:04 (4102) [INFO] or * 2023-08-14 02:01:04 (4102) [INFO] subscription-manager repos --disable= * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-14 02:01:04 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-14 02:01:04 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-14 02:01:04 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-14 02:01:04 (4102) [INFO] compromise: * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-14 02:01:04 (4102) [INFO] * 2023-08-14 02:01:04 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-14 02:01:04 (4119) [INFO] * 2023-08-14 02:01:04 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-14 02:01:04 (1721) [INFO] Checking /scripts/sysup * 2023-08-14 02:01:04 (4088) [INFO] Running: /scripts/sysup * 2023-08-14 02:01:04 (4089) [INFO] * 2023-08-14 02:01:05 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-14 02:01:07 (4102) [INFO] All Needed Packages are already installed. * 2023-08-14 02:01:07 (4119) [INFO] * 2023-08-14 02:01:09 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-14 02:01:09 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-14 02:06:38 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-14 02:06:38 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-14 02:06:39 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-14 02:06:39 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-14 02:06:39 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-14 02:06:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-14 02:06:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LpdVvoOqWf/ea_profile.json * 2023-08-14 02:06:40 (2259) [INFO] Backed up EA4 profile to /tmp/LpdVvoOqWf/ea_profile.json * 2023-08-14 02:06:43 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-15 02:08:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-15 02:08:41 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-15 02:08:41 (1700) [INFO] Checking if your system is up to date: * 2023-08-15 02:08:41 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-15 02:08:41 (4089) [INFO] * 2023-08-15 02:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-15 02:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-15 02:08:42 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-15 02:08:42 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-15 02:08:42 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-15 02:08:42 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-15 02:08:42 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-15 02:08:42 (4119) [INFO] * 2023-08-15 02:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-15 02:08:42 (4089) [INFO] * 2023-08-15 02:11:50 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/84d4a7453744486389333e6dc8871222dd6dc38e397588093178570499dec880-comps-Everything.x86_64.xml.gz: [Errno -1] Metadata file does not match checksum * 2023-08-15 02:11:50 (4102) [INFO] Trying other mirror. * 2023-08-15 02:11:50 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:11:50 (4102) [INFO] Trying other mirror. * 2023-08-15 02:11:51 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/c22ab7592423533974b81fc7aa72aa2c6797aad7a5ab179c22d111ddd9daa65a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:11:51 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:05 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:05 (4102) [INFO] http://mirrors.sonic.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-08-15 02:12:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:05 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-08-15 02:12:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:06 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:06 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:06 (4102) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:06 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:22 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:22 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:22 (4102) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:22 (4102) [INFO] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:23 (4102) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:23 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:38 (4102) [INFO] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:54 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:54 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:54 (4102) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:54 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:54 (4102) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:54 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:56 (4102) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:56 (4102) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:57 (4102) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:57 (4102) [INFO] Trying other mirror. * 2023-08-15 02:12:58 (4102) [INFO] http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:12:58 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:09 (4102) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:09 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:09 (4102) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:09 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:09 (4102) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:09 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:14 (4102) [INFO] https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:14 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:14 (4102) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:14 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:15 (4102) [INFO] https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:15 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:25 (4102) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:25 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:25 (4102) [INFO] http://reflector.westga.edu/repos/Fedora-EPEL/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:25 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:40 (4102) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:40 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:40 (4102) [INFO] https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:40 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:41 (4102) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:41 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:56 (4102) [INFO] https://mirror.usi.edu/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:56 (4102) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:13:57 (4102) [INFO] https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:13:57 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:12 (4102) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:12 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:13 (4102) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:13 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:13 (4102) [INFO] https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:13 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:13 (4102) [INFO] https://mirror.team-cymru.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:13 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:13 (4102) [INFO] http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:13 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:28 (4102) [INFO] http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:28 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:29 (4102) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:29 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:44 (4102) [INFO] https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:44 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:45 (4102) [INFO] https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:45 (4102) [INFO] Trying other mirror. * 2023-08-15 02:14:59 (4102) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:14:59 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:00 (4102) [INFO] https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:00 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:15 (4102) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:15 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:16 (4102) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:16 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:30 (4102) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:30 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:31 (4102) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:31 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:46 (4102) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:46 (4102) [INFO] Trying other mirror. * 2023-08-15 02:15:47 (4102) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:15:47 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:02 (4102) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:02 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:02 (4102) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:02 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:17 (4102) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:17 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:18 (4102) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:18 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:33 (4102) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:33 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:34 (4102) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:34 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:34 (4102) [INFO] http://mirror.siena.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:34 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:48 (4102) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:48 (4102) [INFO] Trying other mirror. * 2023-08-15 02:16:50 (4102) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:16:50 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:05 (4102) [INFO] https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:05 (4102) [INFO] http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:05 (4102) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:05 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:06 (4102) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:06 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:07 (4102) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:07 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:21 (4102) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:21 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:22 (4102) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:37 (4102) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:37 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:38 (4102) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:40 (4102) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:40 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:44 (4102) [INFO] https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:44 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:48 (4102) [INFO] https://epel.mcn.us.ssimn.org/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 403 - Forbidden * 2023-08-15 02:17:48 (4102) [INFO] Trying other mirror. * 2023-08-15 02:17:48 (4102) [INFO] To address this issue please refer to the below wiki article * 2023-08-15 02:17:48 (4102) [INFO] * 2023-08-15 02:17:48 (4102) [INFO] https://wiki.centos.org/yum-errors * 2023-08-15 02:17:48 (4102) [INFO] * 2023-08-15 02:17:48 (4102) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-08-15 02:17:48 (4102) [INFO] * 2023-08-15 02:17:53 (4102) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:17:53 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:03 (4102) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:03 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:18 (4102) [INFO] https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:18 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:23 (4102) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2023-08-15 02:18:23 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:34 (4102) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:34 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:35 (4102) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:35 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:38 (4102) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:50 (4102) [INFO] https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:50 (4102) [INFO] Trying other mirror. * 2023-08-15 02:18:53 (4102) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:18:53 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:06 (4102) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:06 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:06 (4102) [INFO] https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:06 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:09 (4102) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:09 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:22 (4102) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:22 (4102) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:22 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:24 (4102) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:24 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:25 (4102) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:25 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:38 (4102) [INFO] https://mirror.team-cymru.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:38 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:40 (4102) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:40 (4102) [INFO] Trying other mirror. * 2023-08-15 02:19:53 (4102) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:19:53 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:08 (4102) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:08 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:08 (4102) [INFO] https://mirror.usi.edu/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:08 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:23 (4102) [INFO] https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:23 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:24 (4102) [INFO] http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:24 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:24 (4102) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:24 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:24 (4102) [INFO] http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:24 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:39 (4102) [INFO] https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:39 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:39 (4102) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:39 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:54 (4102) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:54 (4102) [INFO] Trying other mirror. * 2023-08-15 02:20:55 (4102) [INFO] https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:20:55 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:09 (4102) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:09 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:10 (4102) [INFO] https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:10 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:24 (4102) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:24 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:25 (4102) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:25 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:40 (4102) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:40 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:41 (4102) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:41 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:55 (4102) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:55 (4102) [INFO] Trying other mirror. * 2023-08-15 02:21:56 (4102) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:21:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:10 (4102) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:10 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:11 (4102) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:11 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:25 (4102) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:25 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:26 (4102) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:26 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:41 (4102) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:41 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:42 (4102) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:42 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:42 (4102) [INFO] http://mirror.siena.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:42 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:56 (4102) [INFO] https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:56 (4102) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:56 (4102) [INFO] Trying other mirror. * 2023-08-15 02:22:57 (4102) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:22:57 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:11 (4102) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:11 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:12 (4102) [INFO] http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:12 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:12 (4102) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:12 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:13 (4102) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:13 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:27 (4102) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:27 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:28 (4102) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:28 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:42 (4102) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:42 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:43 (4102) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:43 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:43 (4102) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:43 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:44 (4102) [INFO] https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:23:44 (4102) [INFO] Trying other mirror. * 2023-08-15 02:23:45 (4102) [INFO] https://epel.mcn.us.ssimn.org/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden * 2023-08-15 02:23:45 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:00 (4102) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:00 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:12 (4102) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:12 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:15 (4102) [INFO] https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:15 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:27 (4102) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:27 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:31 (4102) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:31 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:32 (4102) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:32 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:42 (4102) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:42 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:42 (4102) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:42 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:47 (4102) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:47 (4102) [INFO] Trying other mirror. * 2023-08-15 02:24:58 (4102) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/ae22ddaf895a1f1a668a78b42a35f05d48fff0030457a4c75cadf6c56337bd33-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:24:58 (4102) [INFO] Trying other mirror. * 2023-08-15 02:25:02 (4102) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:25:02 (4102) [INFO] Trying other mirror. * 2023-08-15 02:25:02 (4102) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/1544e656daffd34311b99bcd43a9660a3f295d629ab169d60b2d3631d94e7ccd-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-08-15 02:25:02 (4102) [INFO] Trying other mirror. * 2023-08-15 02:25:30 (4102) [INFO] * 2023-08-15 02:25:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-15 02:25:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-15 02:25:30 (4119) [INFO] * 2023-08-15 02:25:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-15 02:25:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-15 02:25:33 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-15 02:25:33 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-16 02:01:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-16 02:01:37 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-16 02:01:37 (1700) [INFO] Checking if your system is up to date: * 2023-08-16 02:01:37 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-16 02:01:37 (4089) [INFO] * 2023-08-16 02:01:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-16 02:01:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-16 02:01:38 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-16 02:01:38 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-16 02:01:38 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-16 02:01:38 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-16 02:01:38 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-16 02:01:38 (4119) [INFO] * 2023-08-16 02:01:38 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-16 02:01:38 (4089) [INFO] * 2023-08-16 02:05:10 (4102) [INFO] http://mirrors.greenmountainaccess.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to mirrors.greenmountainaccess.net:80; Operation now in progress" * 2023-08-16 02:05:10 (4102) [INFO] Trying other mirror. * 2023-08-16 02:06:06 (4102) [INFO] * 2023-08-16 02:06:06 (4102) [INFO] imunify-auditd-log-reader.x86_64 2.6.2-1.el7 imunify360 * 2023-08-16 02:06:06 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-16 02:06:06 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-16 02:06:06 (4119) [INFO] * 2023-08-16 02:06:07 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-16 02:06:07 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-16 02:06:10 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-16 02:06:10 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-16 02:10:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-16 02:10:00 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30847 milliseconds') * 2023-08-16 02:10:00 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-16 02:10:00 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-16 02:10:00 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-16 02:10:01 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-16 02:10:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-16 02:10:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-16 02:10:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-16 02:10:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hvLG_qGZkK/ea_profile.json * 2023-08-16 02:10:05 (2259) [INFO] Backed up EA4 profile to /tmp/hvLG_qGZkK/ea_profile.json * 2023-08-16 02:10:10 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-17 02:05:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-17 02:05:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-17 02:05:05 (1700) [INFO] Checking if your system is up to date: * 2023-08-17 02:05:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-17 02:05:05 (4089) [INFO] * 2023-08-17 02:05:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-17 02:05:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-17 02:05:05 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-17 02:05:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-17 02:05:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-17 02:05:05 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-17 02:05:06 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-17 02:05:06 (4119) [INFO] * 2023-08-17 02:05:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-17 02:05:06 (4089) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-17 02:06:02 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-17 02:06:02 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-17 02:06:02 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-17 02:06:02 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-17 02:06:02 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-17 02:06:02 (4102) [INFO] yum --disablerepo= ... * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-17 02:06:02 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-17 02:06:02 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] yum-config-manager --disable * 2023-08-17 02:06:02 (4102) [INFO] or * 2023-08-17 02:06:02 (4102) [INFO] subscription-manager repos --disable= * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-17 02:06:02 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-17 02:06:02 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-17 02:06:02 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-17 02:06:02 (4102) [INFO] compromise: * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-17 02:06:02 (4102) [INFO] * 2023-08-17 02:06:02 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-17 02:06:02 (4119) [INFO] * 2023-08-17 02:06:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-17 02:06:02 (1721) [INFO] Checking /scripts/sysup * 2023-08-17 02:06:02 (4088) [INFO] Running: /scripts/sysup * 2023-08-17 02:06:02 (4089) [INFO] * 2023-08-17 02:06:03 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-17 02:06:04 (4102) [INFO] All Needed Packages are already installed. * 2023-08-17 02:06:04 (4119) [INFO] * 2023-08-17 02:06:08 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-17 02:06:08 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-17 02:07:02 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-17 02:07:02 (1567) [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-08-17 02:07:02 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-17 02:07:02 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-17 02:07:02 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-17 02:07:03 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-17 02:07:03 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-17 02:07:03 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-17 02:07:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-17 02:07:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2_TWGOPUJb/ea_profile.json * 2023-08-17 02:12:52 (2259) [INFO] Backed up EA4 profile to /tmp/2_TWGOPUJb/ea_profile.json * 2023-08-17 02:12:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-18 02:01:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-18 02:01:02 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-18 02:01:02 (1700) [INFO] Checking if your system is up to date: * 2023-08-18 02:01:02 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-18 02:01:02 (4089) [INFO] * 2023-08-18 02:01:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-18 02:01:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-18 02:01:03 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-18 02:01:03 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-18 02:01:03 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-18 02:01:03 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-18 02:01:03 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-18 02:01:03 (4119) [INFO] * 2023-08-18 02:01:03 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-18 02:01:03 (4089) [INFO] * 2023-08-18 02:04:59 (4102) [INFO] * 2023-08-18 02:04:59 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-18 02:04:59 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-18 02:04:59 (4119) [INFO] * 2023-08-18 02:04:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-18 02:04:59 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-18 02:05:04 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-18 02:05:04 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-18 02:08:05 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-18 02:08:05 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-18 02:08:06 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-18 02:08:06 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-18 02:08:06 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-18 02:08:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-18 02:08:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v1Nt99WrRK/ea_profile.json * 2023-08-18 02:08:07 (2259) [INFO] Backed up EA4 profile to /tmp/v1Nt99WrRK/ea_profile.json * 2023-08-18 02:08:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-19 02:07:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-19 02:07:33 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-19 02:07:33 (1700) [INFO] Checking if your system is up to date: * 2023-08-19 02:07:33 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-19 02:07:33 (4089) [INFO] * 2023-08-19 02:07:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-19 02:07:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-19 02:07:33 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-19 02:07:33 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-19 02:07:33 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-19 02:07:33 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-19 02:07:34 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-19 02:07:34 (4119) [INFO] * 2023-08-19 02:07:34 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-19 02:07:34 (4089) [INFO] * 2023-08-19 02:11:16 (4102) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-08-19 02:11:16 (4102) [INFO] Trying other mirror. * 2023-08-19 02:11:17 (4102) [INFO] http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-08-19 02:11:17 (4102) [INFO] Trying other mirror. * 2023-08-19 02:12:28 (4102) [INFO] * 2023-08-19 02:12:28 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-19 02:12:28 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-19 02:12:28 (4119) [INFO] * 2023-08-19 02:12:28 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-19 02:12:28 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-19 02:12:31 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-19 02:12:31 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-19 02:15:53 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-19 02:15:53 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-19 02:15:54 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-19 02:15:54 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-19 02:15:54 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-19 02:15:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-19 02:15:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RtrCGTWzWQ/ea_profile.json * 2023-08-19 02:15:56 (2259) [INFO] Backed up EA4 profile to /tmp/RtrCGTWzWQ/ea_profile.json * 2023-08-19 02:15:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-20 02:00:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-20 02:00:56 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-20 02:00:56 (1700) [INFO] Checking if your system is up to date: * 2023-08-20 02:00:56 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-20 02:00:56 (4089) [INFO] * 2023-08-20 02:00:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-20 02:00:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-20 02:00:56 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-20 02:00:56 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-20 02:00:56 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-20 02:00:56 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-20 02:00:56 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-20 02:00:56 (4119) [INFO] * 2023-08-20 02:00:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-20 02:00:56 (4089) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-20 02:01:51 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-20 02:01:51 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-20 02:01:51 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-20 02:01:51 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-20 02:01:51 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-20 02:01:51 (4102) [INFO] yum --disablerepo= ... * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-20 02:01:51 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-20 02:01:51 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] yum-config-manager --disable * 2023-08-20 02:01:51 (4102) [INFO] or * 2023-08-20 02:01:51 (4102) [INFO] subscription-manager repos --disable= * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-20 02:01:51 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-20 02:01:51 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-20 02:01:51 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-20 02:01:51 (4102) [INFO] compromise: * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-20 02:01:51 (4102) [INFO] * 2023-08-20 02:01:51 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-20 02:01:51 (4119) [INFO] * 2023-08-20 02:01:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-20 02:01:51 (1721) [INFO] Checking /scripts/sysup * 2023-08-20 02:01:51 (4088) [INFO] Running: /scripts/sysup * 2023-08-20 02:01:51 (4089) [INFO] * 2023-08-20 02:01:52 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-20 02:01:53 (4102) [INFO] All Needed Packages are already installed. * 2023-08-20 02:01:53 (4119) [INFO] * 2023-08-20 02:01:56 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-20 02:01:56 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-20 02:09:10 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-20 02:09:10 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-20 02:09:11 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-20 02:09:11 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-20 02:09:11 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-20 02:09:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-20 02:09:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CTV7zKUYK8/ea_profile.json * 2023-08-20 02:09:12 (2259) [INFO] Backed up EA4 profile to /tmp/CTV7zKUYK8/ea_profile.json * 2023-08-20 02:09:15 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-21 01:55:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-21 01:55:37 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-21 01:55:37 (1700) [INFO] Checking if your system is up to date: * 2023-08-21 01:55:37 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-21 01:55:37 (4089) [INFO] * 2023-08-21 01:55:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-21 01:55:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-21 01:55:37 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-21 01:55:37 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-21 01:55:37 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-21 01:55:37 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-21 01:55:37 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-21 01:55:37 (4119) [INFO] * 2023-08-21 01:55:37 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-21 01:55:37 (4089) [INFO] * 2023-08-21 01:59:59 (4102) [INFO] * 2023-08-21 01:59:59 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-21 01:59:59 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-21 01:59:59 (4119) [INFO] * 2023-08-21 01:59:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-21 01:59:59 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-21 02:00:02 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-21 02:00:02 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-21 02:03:30 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-21 02:03:30 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-21 02:03:31 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-21 02:03:31 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-21 02:03:31 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-21 02:03:31 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-21 02:03:31 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lGFYR1pCBy/ea_profile.json * 2023-08-21 02:03:33 (2259) [INFO] Backed up EA4 profile to /tmp/lGFYR1pCBy/ea_profile.json * 2023-08-21 02:03:35 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-22 02:08:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-22 02:08:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-22 02:08:20 (1700) [INFO] Checking if your system is up to date: * 2023-08-22 02:08:20 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-22 02:08:20 (4089) [INFO] * 2023-08-22 02:08:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-22 02:08:20 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-22 02:08:20 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-22 02:08:20 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-22 02:08:20 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-22 02:08:20 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-22 02:08:21 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-22 02:08:21 (4119) [INFO] * 2023-08-22 02:08:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-22 02:08:21 (4089) [INFO] * 2023-08-22 02:11:18 (4102) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-08-22 02:11:18 (4102) [INFO] Trying other mirror. * 2023-08-22 02:12:00 (4102) [INFO] * 2023-08-22 02:12:00 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-22 02:12:00 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-22 02:12:01 (4119) [INFO] * 2023-08-22 02:12:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-22 02:12:01 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-22 02:12:04 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-22 02:12:04 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-22 02:15:11 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-22 02:15:11 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-22 02:15:12 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-22 02:15:12 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-22 02:15:12 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-22 02:15:12 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-22 02:15:12 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/voyNmAXsYV/ea_profile.json * 2023-08-22 02:15:14 (2259) [INFO] Backed up EA4 profile to /tmp/voyNmAXsYV/ea_profile.json * 2023-08-22 02:15:18 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-23 02:01:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-23 02:01:35 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-23 02:01:35 (1700) [INFO] Checking if your system is up to date: * 2023-08-23 02:01:35 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-23 02:01:35 (4089) [INFO] * 2023-08-23 02:01:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-23 02:01:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-23 02:01:36 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-23 02:01:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-23 02:01:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-23 02:01:36 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-23 02:01:36 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-23 02:01:36 (4119) [INFO] * 2023-08-23 02:01:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-23 02:01:36 (4089) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-23 02:02:31 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-23 02:02:31 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-23 02:02:31 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-23 02:02:31 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-23 02:02:31 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-23 02:02:31 (4102) [INFO] yum --disablerepo= ... * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-23 02:02:31 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-23 02:02:31 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] yum-config-manager --disable * 2023-08-23 02:02:31 (4102) [INFO] or * 2023-08-23 02:02:31 (4102) [INFO] subscription-manager repos --disable= * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-23 02:02:31 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-23 02:02:31 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-23 02:02:31 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-23 02:02:31 (4102) [INFO] compromise: * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-23 02:02:31 (4102) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-23 02:02:31 (4119) [INFO] * 2023-08-23 02:02:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-23 02:02:31 (1721) [INFO] Checking /scripts/sysup * 2023-08-23 02:02:31 (4088) [INFO] Running: /scripts/sysup * 2023-08-23 02:02:31 (4089) [INFO] * 2023-08-23 02:02:31 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-23 02:02:34 (4102) [INFO] All Needed Packages are already installed. * 2023-08-23 02:02:34 (4119) [INFO] * 2023-08-23 02:02:37 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-23 02:02:37 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-23 02:03:32 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-23 02:03:32 (1567) [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-08-23 02:03:32 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-23 02:03:32 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-23 02:03:32 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-23 02:03:33 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-23 02:03:33 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-23 02:03:33 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-23 02:03:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-23 02:03:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fIgUOxqT14/ea_profile.json * 2023-08-23 02:08:05 (2259) [INFO] Backed up EA4 profile to /tmp/fIgUOxqT14/ea_profile.json * 2023-08-23 02:08:08 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-24 02:04:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-24 02:04:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-24 02:04:23 (1700) [INFO] Checking if your system is up to date: * 2023-08-24 02:04:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-24 02:04:23 (4089) [INFO] * 2023-08-24 02:04:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-24 02:04:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-24 02:04:24 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-24 02:04:24 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-24 02:04:24 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-24 02:04:24 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-24 02:04:24 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-24 02:04:24 (4119) [INFO] * 2023-08-24 02:04:24 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-24 02:04:24 (4089) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-24 02:05:20 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-24 02:05:20 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-24 02:05:20 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-24 02:05:20 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-24 02:05:20 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-24 02:05:20 (4102) [INFO] yum --disablerepo= ... * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-24 02:05:20 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-24 02:05:20 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] yum-config-manager --disable * 2023-08-24 02:05:20 (4102) [INFO] or * 2023-08-24 02:05:20 (4102) [INFO] subscription-manager repos --disable= * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-24 02:05:20 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-24 02:05:20 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-24 02:05:20 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-24 02:05:20 (4102) [INFO] compromise: * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-24 02:05:20 (4102) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-24 02:05:20 (4119) [INFO] * 2023-08-24 02:05:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-24 02:05:20 (1721) [INFO] Checking /scripts/sysup * 2023-08-24 02:05:20 (4088) [INFO] Running: /scripts/sysup * 2023-08-24 02:05:20 (4089) [INFO] * 2023-08-24 02:05:20 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-24 02:05:22 (4102) [INFO] All Needed Packages are already installed. * 2023-08-24 02:05:22 (4119) [INFO] * 2023-08-24 02:05:25 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-24 02:05:25 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-24 02:14:48 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-24 02:14:48 (1567) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/3fde828d8a28cf925fa35e434794a43899cda723eb0b66376539e6e4f8548220-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xtom.com/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.mirror.constant.com/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.fcix.net/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.usf.edu/pub/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.maine.edu/CentOS/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.san.fastserv.com/pub/linux/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.siena.edu/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ohioix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ziply.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/def784b6218227a7e7828d2fd58c58ab438a93d9e4be1e9c1b09478b7522ceb1-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-08-24 02:14:48 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-24 02:14:48 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-24 02:14:48 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-24 02:14:49 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-24 02:14:49 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-24 02:14:49 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-24 02:14:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-24 02:14:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fMdfXXV9B9/ea_profile.json * 2023-08-24 02:14:50 (2259) [INFO] Backed up EA4 profile to /tmp/fMdfXXV9B9/ea_profile.json * 2023-08-24 02:14:54 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-25 02:14:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-25 02:14:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-25 02:14:12 (1700) [INFO] Checking if your system is up to date: * 2023-08-25 02:14:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-25 02:14:12 (4089) [INFO] * 2023-08-25 02:14:12 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-25 02:14:12 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-25 02:14:12 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-25 02:14:12 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-25 02:14:12 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-25 02:14:12 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-25 02:14:13 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-25 02:14:13 (4119) [INFO] * 2023-08-25 02:14:13 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-25 02:14:13 (4089) [INFO] * 2023-08-25 02:18:20 (4102) [INFO] * 2023-08-25 02:18:20 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-25 02:18:20 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-25 02:18:20 (4119) [INFO] * 2023-08-25 02:18:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-25 02:18:20 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-25 02:18:23 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-25 02:18:23 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-25 02:21:42 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-25 02:21:42 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-25 02:21:43 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-25 02:21:43 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-25 02:21:43 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-25 02:21:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-25 02:21:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pt95Nm1afJ/ea_profile.json * 2023-08-25 02:21:46 (2259) [INFO] Backed up EA4 profile to /tmp/pt95Nm1afJ/ea_profile.json * 2023-08-25 02:21:50 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-26 02:09:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-26 02:09:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-26 02:09:09 (1700) [INFO] Checking if your system is up to date: * 2023-08-26 02:09:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-26 02:09:09 (4089) [INFO] * 2023-08-26 02:09:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-26 02:09:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-26 02:09:10 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-26 02:09:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-26 02:09:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-26 02:09:10 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-26 02:09:10 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-26 02:09:10 (4119) [INFO] * 2023-08-26 02:09:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-26 02:09:10 (4089) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-26 02:10:04 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-26 02:10:04 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-26 02:10:04 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-26 02:10:04 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-26 02:10:04 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-26 02:10:04 (4102) [INFO] yum --disablerepo= ... * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-26 02:10:04 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-26 02:10:04 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:04 (4102) [INFO] yum-config-manager --disable * 2023-08-26 02:10:04 (4102) [INFO] or * 2023-08-26 02:10:04 (4102) [INFO] subscription-manager repos --disable= * 2023-08-26 02:10:04 (4102) [INFO] * 2023-08-26 02:10:05 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-26 02:10:05 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-26 02:10:05 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-26 02:10:05 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-26 02:10:05 (4102) [INFO] compromise: * 2023-08-26 02:10:05 (4102) [INFO] * 2023-08-26 02:10:05 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-26 02:10:05 (4102) [INFO] * 2023-08-26 02:10:05 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-26 02:10:05 (4119) [INFO] * 2023-08-26 02:10:05 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-26 02:10:05 (1721) [INFO] Checking /scripts/sysup * 2023-08-26 02:10:05 (4088) [INFO] Running: /scripts/sysup * 2023-08-26 02:10:05 (4089) [INFO] * 2023-08-26 02:10:06 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-26 02:10:09 (4102) [INFO] All Needed Packages are already installed. * 2023-08-26 02:10:09 (4119) [INFO] * 2023-08-26 02:10:13 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-26 02:10:13 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-26 02:17:45 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-26 02:17:45 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-26 02:17:45 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-26 02:17:45 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-26 02:17:45 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-26 02:17:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-26 02:17:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qh2OhMvm37/ea_profile.json * 2023-08-26 02:17:47 (2259) [INFO] Backed up EA4 profile to /tmp/qh2OhMvm37/ea_profile.json * 2023-08-26 02:17:51 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-27 02:04:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-27 02:04:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-27 02:04:20 (1700) [INFO] Checking if your system is up to date: * 2023-08-27 02:04:20 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-27 02:04:20 (4089) [INFO] * 2023-08-27 02:04:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-27 02:04:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-27 02:04:21 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-27 02:04:21 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-27 02:04:21 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-27 02:04:21 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-27 02:04:21 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-27 02:04:21 (4119) [INFO] * 2023-08-27 02:04:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-27 02:04:21 (4089) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-27 02:05:17 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-27 02:05:17 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-27 02:05:17 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-27 02:05:17 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-27 02:05:17 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-27 02:05:17 (4102) [INFO] yum --disablerepo= ... * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-27 02:05:17 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-27 02:05:17 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] yum-config-manager --disable * 2023-08-27 02:05:17 (4102) [INFO] or * 2023-08-27 02:05:17 (4102) [INFO] subscription-manager repos --disable= * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-27 02:05:17 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-27 02:05:17 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-27 02:05:17 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-27 02:05:17 (4102) [INFO] compromise: * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-27 02:05:17 (4102) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-27 02:05:17 (4119) [INFO] * 2023-08-27 02:05:17 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-27 02:05:17 (1721) [INFO] Checking /scripts/sysup * 2023-08-27 02:05:17 (4088) [INFO] Running: /scripts/sysup * 2023-08-27 02:05:17 (4089) [INFO] * 2023-08-27 02:05:17 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-27 02:05:19 (4102) [INFO] All Needed Packages are already installed. * 2023-08-27 02:05:19 (4119) [INFO] * 2023-08-27 02:05:25 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-27 02:05:25 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-27 02:13:00 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-27 02:13:00 (1567) [ERROR] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftpmirror.your.org/pub/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cs.pitt.edu/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.tripadvisor.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.tripadvisor.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://tx-mirror.tier.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://la.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://packages.oit.ncsu.edu/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://veronanetworks.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.genesishosting.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-08-27 02:13:00 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-27 02:13:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-27 02:13:01 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-27 02:13:01 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-27 02:13:01 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-27 02:13:01 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-27 02:13:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-27 02:13:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IDupVgR23n/ea_profile.json * 2023-08-27 02:13:03 (2259) [INFO] Backed up EA4 profile to /tmp/IDupVgR23n/ea_profile.json * 2023-08-27 02:13:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-28 02:01:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-28 02:01:42 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-28 02:01:42 (1700) [INFO] Checking if your system is up to date: * 2023-08-28 02:01:42 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-28 02:01:42 (4089) [INFO] * 2023-08-28 02:01:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-28 02:01:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-28 02:01:43 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-28 02:01:43 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-28 02:01:43 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-28 02:01:43 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-28 02:01:43 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-28 02:01:43 (4119) [INFO] * 2023-08-28 02:01:43 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-28 02:01:43 (4089) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-28 02:02:41 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-28 02:02:41 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-28 02:02:41 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-28 02:02:41 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-28 02:02:41 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-28 02:02:41 (4102) [INFO] yum --disablerepo= ... * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-28 02:02:41 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-28 02:02:41 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] yum-config-manager --disable * 2023-08-28 02:02:41 (4102) [INFO] or * 2023-08-28 02:02:41 (4102) [INFO] subscription-manager repos --disable= * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-28 02:02:41 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-28 02:02:41 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-28 02:02:41 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-28 02:02:41 (4102) [INFO] compromise: * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-28 02:02:41 (4102) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-08-28 02:02:41 (4119) [INFO] * 2023-08-28 02:02:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-28 02:02:41 (1721) [INFO] Checking /scripts/sysup * 2023-08-28 02:02:41 (4088) [INFO] Running: /scripts/sysup * 2023-08-28 02:02:41 (4089) [INFO] * 2023-08-28 02:02:41 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-28 02:02:43 (4102) [INFO] All Needed Packages are already installed. * 2023-08-28 02:02:43 (4119) [INFO] * 2023-08-28 02:02:47 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-28 02:02:47 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-28 02:09:45 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-28 02:09:45 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-28 02:09:45 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-28 02:09:45 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-28 02:09:45 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-28 02:09:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-28 02:09:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gOXYcoOZzi/ea_profile.json * 2023-08-28 02:09:47 (2259) [INFO] Backed up EA4 profile to /tmp/gOXYcoOZzi/ea_profile.json * 2023-08-28 02:09:51 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-29 02:13:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-29 02:13:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-29 02:13:23 (1700) [INFO] Checking if your system is up to date: * 2023-08-29 02:13:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-29 02:13:23 (4089) [INFO] * 2023-08-29 02:13:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-29 02:13:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-29 02:13:23 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-29 02:13:23 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-29 02:13:24 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-29 02:13:24 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-29 02:13:24 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-29 02:13:24 (4119) [INFO] * 2023-08-29 02:13:24 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-29 02:13:24 (4089) [INFO] * 2023-08-29 02:17:34 (4102) [INFO] * 2023-08-29 02:17:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-29 02:17:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-29 02:17:34 (4119) [INFO] * 2023-08-29 02:17:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-29 02:17:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-29 02:17:38 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-29 02:17:38 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-29 02:20:53 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-29 02:20:53 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-29 02:20:54 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-29 02:20:54 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-29 02:20:54 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-29 02:20:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-29 02:20:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ekQo3h8Igr/ea_profile.json * 2023-08-29 02:20:56 (2259) [INFO] Backed up EA4 profile to /tmp/ekQo3h8Igr/ea_profile.json * 2023-08-29 02:21:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-30 02:02:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-30 02:02:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-30 02:02:04 (1700) [INFO] Checking if your system is up to date: * 2023-08-30 02:02:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-30 02:02:04 (4089) [INFO] * 2023-08-30 02:02:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-30 02:02:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-30 02:02:04 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-30 02:02:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-30 02:02:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-30 02:02:04 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-30 02:02:05 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-30 02:02:05 (4119) [INFO] * 2023-08-30 02:02:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-30 02:02:05 (4089) [INFO] * 2023-08-30 02:06:24 (4102) [INFO] * 2023-08-30 02:06:24 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-30 02:06:24 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-30 02:06:24 (4119) [INFO] * 2023-08-30 02:06:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-30 02:06:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-30 02:06:28 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-30 02:06:28 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-30 02:10:01 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-08-30 02:10:01 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2023-08-30 02:10:01 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-08-30 02:10:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-30 02:10:01 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-30 02:10:02 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-30 02:10:02 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-30 02:10:02 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-30 02:10:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-30 02:10:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fQF1mdsLoM/ea_profile.json * 2023-08-30 02:10:07 (2259) [INFO] Backed up EA4 profile to /tmp/fQF1mdsLoM/ea_profile.json * 2023-08-30 02:10:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-31 02:02:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-08-31 02:02:34 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-31 02:02:34 (1700) [INFO] Checking if your system is up to date: * 2023-08-31 02:02:34 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-31 02:02:34 (4089) [INFO] * 2023-08-31 02:02:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-31 02:02:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-08-31 02:02:35 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-31 02:02:35 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-31 02:02:35 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-31 02:02:35 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-08-31 02:02:36 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-08-31 02:02:36 (4119) [INFO] * 2023-08-31 02:02:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-31 02:02:36 (4089) [INFO] * 2023-08-31 02:06:30 (4102) [INFO] * 2023-08-31 02:06:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-31 02:06:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-31 02:06:30 (4119) [INFO] * 2023-08-31 02:06:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-31 02:06:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-31 02:06:34 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-08-31 02:06:34 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-08-31 02:09:38 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-08-31 02:09:38 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-08-31 02:09:39 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-08-31 02:09:39 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-08-31 02:09:39 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-08-31 02:09:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-31 02:09:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wrA6PHpUBx/ea_profile.json * 2023-08-31 02:09:42 (2259) [INFO] Backed up EA4 profile to /tmp/wrA6PHpUBx/ea_profile.json * 2023-08-31 02:09:46 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-01 01:59:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-01 01:59:27 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-01 01:59:27 (1700) [INFO] Checking if your system is up to date: * 2023-09-01 01:59:27 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-01 01:59:27 (4089) [INFO] * 2023-09-01 01:59:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-01 01:59:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-01 01:59:28 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-01 01:59:28 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-01 01:59:28 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-01 01:59:28 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-01 01:59:29 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-01 01:59:29 (4119) [INFO] * 2023-09-01 01:59:29 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-01 01:59:29 (4089) [INFO] * 2023-09-01 02:03:24 (4102) [INFO] * 2023-09-01 02:03:24 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-01 02:03:24 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-01 02:03:24 (4119) [INFO] * 2023-09-01 02:03:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-01 02:03:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-01 02:03:27 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-01 02:03:27 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-01 02:07:04 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-01 02:07:04 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-01 02:07:04 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-01 02:07:04 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-01 02:07:04 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-01 02:07:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-01 02:07:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TdFgcg6esz/ea_profile.json * 2023-09-01 02:07:07 (2259) [INFO] Backed up EA4 profile to /tmp/TdFgcg6esz/ea_profile.json * 2023-09-01 02:07:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-02 02:03:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-02 02:03:26 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-02 02:03:26 (1700) [INFO] Checking if your system is up to date: * 2023-09-02 02:03:26 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-02 02:03:26 (4089) [INFO] * 2023-09-02 02:03:27 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-02 02:03:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-02 02:03:27 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-02 02:03:27 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-02 02:03:27 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-02 02:03:27 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-02 02:03:28 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-02 02:03:28 (4119) [INFO] * 2023-09-02 02:03:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-02 02:03:28 (4089) [INFO] * 2023-09-02 02:14:10 (4102) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2023-09-02 02:14:10 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:10 (4102) [INFO] http://mirrors.mit.edu/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:10 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:11 (4102) [INFO] http://mirror.rackspace.com/CentOS/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:11 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:12 (4102) [INFO] http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:12 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:27 (4102) [INFO] http://coresite.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:27 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:42 (4102) [INFO] http://ftp.usf.edu/pub/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:42 (4102) [INFO] Trying other mirror. * 2023-09-02 02:14:58 (4102) [INFO] http://mirror.servaxnet.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:14:58 (4102) [INFO] Trying other mirror. * 2023-09-02 02:15:13 (4102) [INFO] http://paducahix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:15:13 (4102) [INFO] Trying other mirror. * 2023-09-02 02:15:28 (4102) [INFO] http://ziply.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:15:28 (4102) [INFO] Trying other mirror. * 2023-09-02 02:15:44 (4102) [INFO] http://opencolo.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-02 02:15:44 (4102) [INFO] Trying other mirror. * 2023-09-02 02:15:55 (4102) [INFO] * 2023-09-02 02:15:55 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-02 02:15:55 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-02 02:15:55 (4119) [INFO] * 2023-09-02 02:15:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-02 02:15:55 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-02 02:15:58 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-02 02:15:58 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-02 02:19:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-02 02:19:16 (1567) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/e38b7d0effa4856228aa5bdebd70bca661399d0c2202852fdedb051660509d2c-filelists.sqlite.bz2: [Errno 12] Timeout on http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/e38b7d0effa4856228aa5bdebd70bca661399d0c2202852fdedb051660509d2c-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. * 2023-09-02 02:19:16 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-02 02:19:16 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-02 02:19:16 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-02 02:19:17 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-02 02:19:17 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-02 02:19:17 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-02 02:19:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-02 02:19:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g61qHrZTY3/ea_profile.json * 2023-09-02 02:19:19 (2259) [INFO] Backed up EA4 profile to /tmp/g61qHrZTY3/ea_profile.json * 2023-09-02 02:19:22 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-03 02:02:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-03 02:02:54 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-03 02:02:54 (1700) [INFO] Checking if your system is up to date: * 2023-09-03 02:02:54 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-03 02:02:54 (4089) [INFO] * 2023-09-03 02:02:54 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-03 02:02:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-03 02:02:55 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-03 02:02:55 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-03 02:02:55 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-03 02:02:55 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-03 02:02:55 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-03 02:02:55 (4119) [INFO] * 2023-09-03 02:02:55 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-03 02:02:55 (4089) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-09-03 02:03:50 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-03 02:03:50 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-03 02:03:50 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-03 02:03:50 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-09-03 02:03:50 (4102) [INFO] packages for the previous distribution release still work). * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-03 02:03:50 (4102) [INFO] yum --disablerepo= ... * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-03 02:03:50 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-03 02:03:50 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] yum-config-manager --disable * 2023-09-03 02:03:50 (4102) [INFO] or * 2023-09-03 02:03:50 (4102) [INFO] subscription-manager repos --disable= * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-03 02:03:50 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-03 02:03:50 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-03 02:03:50 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-03 02:03:50 (4102) [INFO] compromise: * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-03 02:03:50 (4102) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-03 02:03:50 (4119) [INFO] * 2023-09-03 02:03:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-03 02:03:50 (1721) [INFO] Checking /scripts/sysup * 2023-09-03 02:03:50 (4088) [INFO] Running: /scripts/sysup * 2023-09-03 02:03:50 (4089) [INFO] * 2023-09-03 02:03:50 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-03 02:03:52 (4102) [INFO] All Needed Packages are already installed. * 2023-09-03 02:03:52 (4119) [INFO] * 2023-09-03 02:03:56 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-03 02:03:56 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-03 02:16:23 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-03 02:16:23 (1567) [ERROR] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/28e68d9969111fcd696bfb7ec46beb47aaf35536a112c1c5c19820c4f73fb761-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/edb180acbceeabf5b2e7e80e4981ff32c0abc169236ec09d6bc62853c95e1819-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.hostduplex.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.hivelocity.net/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.seas.harvard.edu/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.sonic.net/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repos.eggycrew.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. http://mirror.atl.genesisadaptive.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://packages.oit.ncsu.edu/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ix-denver.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.rackspace.com/CentOS/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://paducahix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://epel.mirror.constant.com/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.usi.edu/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://ord.mirror.rackspace.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.its.dal.ca/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.upr.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: (28, 'Connection timed out after 30009 milliseconds') Trying other mirror. http://mirror.siena.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.steadfastnet.com/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.wcupa.edu/epel/7/x86_64/repodata/8d104f70ce1a3050f065b37fbe64ef53c5635a6aaf229150debd5abc43703145-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-09-03 02:16:23 (153) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-03 02:16:23 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-03 02:16:23 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-03 02:16:24 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-03 02:16:24 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-03 02:16:24 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-03 02:16:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-03 02:16:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/P1Q8gpqAVj/ea_profile.json * 2023-09-03 02:16:25 (2259) [INFO] Backed up EA4 profile to /tmp/P1Q8gpqAVj/ea_profile.json * 2023-09-03 02:16:28 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-04 02:00:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-04 02:00:58 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-04 02:00:58 (1700) [INFO] Checking if your system is up to date: * 2023-09-04 02:00:58 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-04 02:00:58 (4089) [INFO] * 2023-09-04 02:00:58 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-04 02:00:58 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-04 02:00:58 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-04 02:00:58 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-04 02:00:58 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-04 02:00:58 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-04 02:00:59 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-04 02:00:59 (4119) [INFO] * 2023-09-04 02:00:59 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-04 02:00:59 (4089) [INFO] * 2023-09-04 02:04:47 (4102) [INFO] * 2023-09-04 02:04:47 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-04 02:04:47 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-04 02:04:47 (4119) [INFO] * 2023-09-04 02:04:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-04 02:04:47 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-04 02:04:50 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-04 02:04:50 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-04 02:07:45 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-04 02:07:45 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-04 02:07:46 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-04 02:07:46 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-04 02:07:46 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-04 02:07:46 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-04 02:07:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KHT6Aj6d6s/ea_profile.json * 2023-09-04 02:07:48 (2259) [INFO] Backed up EA4 profile to /tmp/KHT6Aj6d6s/ea_profile.json * 2023-09-04 02:07:52 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-05 01:58:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-05 01:58:11 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-05 01:58:11 (1700) [INFO] Checking if your system is up to date: * 2023-09-05 01:58:11 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-05 01:58:11 (4089) [INFO] * 2023-09-05 01:58:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-05 01:58:12 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-05 01:58:12 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-05 01:58:12 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-05 01:58:12 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-05 01:58:12 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-05 01:58:12 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-05 01:58:12 (4119) [INFO] * 2023-09-05 01:58:12 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-05 01:58:12 (4089) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-09-05 01:59:07 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-05 01:59:07 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-05 01:59:07 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-05 01:59:07 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-09-05 01:59:07 (4102) [INFO] packages for the previous distribution release still work). * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-05 01:59:07 (4102) [INFO] yum --disablerepo= ... * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-05 01:59:07 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-05 01:59:07 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] yum-config-manager --disable * 2023-09-05 01:59:07 (4102) [INFO] or * 2023-09-05 01:59:07 (4102) [INFO] subscription-manager repos --disable= * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-05 01:59:07 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-05 01:59:07 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-05 01:59:07 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-05 01:59:07 (4102) [INFO] compromise: * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-05 01:59:07 (4102) [INFO] * 2023-09-05 01:59:07 (4102) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-05 01:59:07 (4119) [INFO] * 2023-09-05 01:59:07 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-05 01:59:07 (1721) [INFO] Checking /scripts/sysup * 2023-09-05 01:59:07 (4088) [INFO] Running: /scripts/sysup * 2023-09-05 01:59:07 (4089) [INFO] * 2023-09-05 01:59:08 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-05 01:59:09 (4102) [INFO] All Needed Packages are already installed. * 2023-09-05 01:59:09 (4119) [INFO] * 2023-09-05 01:59:12 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-05 01:59:12 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-05 02:06:26 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-05 02:06:26 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-05 02:06:27 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-05 02:06:27 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-05 02:06:27 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-05 02:06:27 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-05 02:06:27 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_t8spadre5/ea_profile.json * 2023-09-05 02:06:30 (2259) [INFO] Backed up EA4 profile to /tmp/_t8spadre5/ea_profile.json * 2023-09-05 02:06:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-06 02:01:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-06 02:01:28 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-06 02:01:28 (1700) [INFO] Checking if your system is up to date: * 2023-09-06 02:01:28 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-06 02:01:28 (4089) [INFO] * 2023-09-06 02:01:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-06 02:01:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-06 02:01:29 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-06 02:01:29 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-06 02:01:29 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-06 02:01:29 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-06 02:01:29 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-06 02:01:29 (4119) [INFO] * 2023-09-06 02:01:29 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-06 02:01:29 (4089) [INFO] * 2023-09-06 02:05:55 (4102) [INFO] * 2023-09-06 02:05:55 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-06 02:05:55 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-06 02:05:55 (4119) [INFO] * 2023-09-06 02:05:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-06 02:05:55 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-06 02:05:59 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-06 02:05:59 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-06 02:09:31 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-06 02:09:31 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-06 02:09:32 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-06 02:09:32 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-06 02:09:32 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-06 02:09:32 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-06 02:09:32 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PNA9UnPlVG/ea_profile.json * 2023-09-06 02:09:34 (2259) [INFO] Backed up EA4 profile to /tmp/PNA9UnPlVG/ea_profile.json * 2023-09-06 02:09:38 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-07 02:02:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-07 02:02:39 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-07 02:02:39 (1700) [INFO] Checking if your system is up to date: * 2023-09-07 02:02:39 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-07 02:02:39 (4089) [INFO] * 2023-09-07 02:02:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-07 02:02:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-07 02:02:39 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-07 02:02:39 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-07 02:02:39 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-07 02:02:39 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-07 02:02:40 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-07 02:02:40 (4119) [INFO] * 2023-09-07 02:02:40 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-07 02:02:40 (4089) [INFO] * 2023-09-07 02:20:00 (4102) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-09-07 02:20:00 (4102) [INFO] Trying other mirror. * 2023-09-08 02:13:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-08 02:13:42 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-08 02:13:42 (1700) [INFO] Checking if your system is up to date: * 2023-09-08 02:13:42 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-08 02:13:42 (4089) [INFO] * 2023-09-08 02:13:43 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-08 02:13:43 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-08 02:13:43 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-08 02:13:43 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-08 02:13:43 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-08 02:13:43 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-08 02:13:43 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-08 02:13:43 (4119) [INFO] * 2023-09-08 02:13:43 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-08 02:13:43 (4089) [INFO] * 2023-09-08 02:18:12 (4102) [INFO] * 2023-09-08 02:18:12 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-08 02:18:12 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-08 02:18:12 (4119) [INFO] * 2023-09-08 02:18:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-08 02:18:12 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-08 02:18:17 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-08 02:18:17 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-08 02:21:49 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-08 02:21:49 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-08 02:21:50 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-08 02:21:50 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-08 02:21:50 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-08 02:21:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-08 02:21:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Xiw_Njfwa/ea_profile.json * 2023-09-08 02:21:51 (2259) [INFO] Backed up EA4 profile to /tmp/2Xiw_Njfwa/ea_profile.json * 2023-09-08 02:21:54 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-09 02:07:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-09 02:07:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-09 02:07:06 (1700) [INFO] Checking if your system is up to date: * 2023-09-09 02:07:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-09 02:07:06 (4089) [INFO] * 2023-09-09 02:07:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-09 02:07:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-09 02:07:07 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-09 02:07:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-09 02:07:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-09 02:07:07 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-09 02:07:08 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-09 02:07:08 (4119) [INFO] * 2023-09-09 02:07:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-09 02:07:08 (4089) [INFO] * 2023-09-09 02:10:22 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: [Errno -1] Metadata file does not match checksum * 2023-09-09 02:10:22 (4102) [INFO] Trying other mirror. * 2023-09-09 02:10:22 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:10:22 (4102) [INFO] Trying other mirror. * 2023-09-09 02:10:37 (4102) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:10:37 (4102) [INFO] Trying other mirror. * 2023-09-09 02:10:38 (4102) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:10:38 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:08 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:08 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:09 (4102) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:09 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:23 (4102) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:23 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:24 (4102) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:24 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:39 (4102) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 12] Timeout on https://repos.eggycrew.com/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: (28, 'Connection timed out after 30001 milliseconds') * 2023-09-09 02:11:39 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:39 (4102) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:39 (4102) [INFO] Trying other mirror. * 2023-09-09 02:11:55 (4102) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:11:55 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:09 (4102) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 12] Timeout on https://repos.eggycrew.com/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') * 2023-09-09 02:12:09 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:10 (4102) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:10 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:11 (4102) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:11 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:12 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:14 (4102) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:14 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:25 (4102) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:25 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:30 (4102) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:30 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:41 (4102) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:41 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:46 (4102) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:46 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:47 (4102) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-09-09 02:12:47 (4102) [INFO] Trying other mirror. * 2023-09-09 02:12:56 (4102) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:12:56 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:01 (4102) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:01 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:12 (4102) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:17 (4102) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:17 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:27 (4102) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:27 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:33 (4102) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:33 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:33 (4102) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:33 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:43 (4102) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:43 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:49 (4102) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:49 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:49 (4102) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:49 (4102) [INFO] Trying other mirror. * 2023-09-09 02:13:59 (4102) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:13:59 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:05 (4102) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:05 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:14 (4102) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:14 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:15 (4102) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:15 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:21 (4102) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:21 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:31 (4102) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:31 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:31 (4102) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:31 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:32 (4102) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:32 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:33 (4102) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:33 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:36 (4102) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:36 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:49 (4102) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:49 (4102) [INFO] Trying other mirror. * 2023-09-09 02:14:52 (4102) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:14:52 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:05 (4102) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:05 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:21 (4102) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:21 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:22 (4102) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: (28, 'Connection timed out after 30002 milliseconds') * 2023-09-09 02:15:22 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:36 (4102) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:36 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:38 (4102) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:38 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:52 (4102) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:52 (4102) [INFO] Trying other mirror. * 2023-09-09 02:15:54 (4102) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:15:54 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:09 (4102) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:09 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:10 (4102) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:10 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:24 (4102) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:24 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:24 (4102) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:24 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:24 (4102) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:24 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:25 (4102) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:25 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:25 (4102) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:25 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:40 (4102) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:40 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:40 (4102) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:40 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:55 (4102) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:55 (4102) [INFO] Trying other mirror. * 2023-09-09 02:16:55 (4102) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:16:55 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:10 (4102) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:10 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:11 (4102) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:11 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:26 (4102) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:26 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:26 (4102) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:26 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:41 (4102) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:41 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:41 (4102) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:41 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:41 (4102) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:41 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:56 (4102) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:56 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:56 (4102) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:56 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:56 (4102) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:56 (4102) [INFO] Trying other mirror. * 2023-09-09 02:17:56 (4102) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:17:56 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:11 (4102) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:11 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:12 (4102) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:12 (4102) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:12 (4102) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:12 (4102) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:12 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:27 (4102) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:27 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:27 (4102) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:27 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:42 (4102) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:42 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:43 (4102) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:43 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:58 (4102) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:58 (4102) [INFO] Trying other mirror. * 2023-09-09 02:18:58 (4102) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:18:58 (4102) [INFO] Trying other mirror. * 2023-09-09 02:19:13 (4102) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:19:13 (4102) [INFO] Trying other mirror. * 2023-09-09 02:19:28 (4102) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to d2lzkl7pfhq30w.cloudfront.net:443; Operation now in progress" * 2023-09-09 02:19:28 (4102) [INFO] Trying other mirror. * 2023-09-09 02:19:29 (4102) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/b9063fe34428eefca74f869c67df1c898f2f81cd4783fa017ed6ac07db0f189a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:19:29 (4102) [INFO] Trying other mirror. * 2023-09-09 02:19:43 (4102) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/e8c75f9bf57d0d0e3c1ac665bfafc149e9832963d9f32b0002107cbbc7f94826-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-09 02:19:43 (4102) [INFO] Trying other mirror. * 2023-09-09 02:19:56 (4102) [INFO] * 2023-09-09 02:19:56 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-09 02:19:56 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-09 02:19:56 (4119) [INFO] * 2023-09-09 02:19:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-09 02:19:56 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-09 02:20:00 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-09 02:20:00 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-09 02:23:22 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-09 02:23:22 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-09 02:23:23 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-09 02:23:23 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-09 02:23:23 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-09 02:23:23 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-09 02:23:23 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BWURmnsjsA/ea_profile.json * 2023-09-09 02:23:26 (2259) [INFO] Backed up EA4 profile to /tmp/BWURmnsjsA/ea_profile.json * 2023-09-09 02:23:31 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-10 02:03:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-10 02:03:38 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-10 02:03:38 (1700) [INFO] Checking if your system is up to date: * 2023-09-10 02:03:38 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-10 02:03:38 (4089) [INFO] * 2023-09-10 02:03:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-10 02:03:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-10 02:03:39 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-10 02:03:39 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-10 02:03:39 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-10 02:03:39 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-10 02:03:39 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-10 02:03:39 (4119) [INFO] * 2023-09-10 02:03:39 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-10 02:03:39 (4089) [INFO] * 2023-09-10 02:07:43 (4102) [INFO] * 2023-09-10 02:07:43 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-10 02:07:43 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-10 02:07:43 (4119) [INFO] * 2023-09-10 02:07:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-10 02:07:43 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-10 02:07:46 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-10 02:07:46 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-10 02:11:01 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-10 02:11:01 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-10 02:11:02 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-10 02:11:02 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-10 02:11:02 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-10 02:11:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-10 02:11:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RdNVB_QWWU/ea_profile.json * 2023-09-10 02:11:05 (2259) [INFO] Backed up EA4 profile to /tmp/RdNVB_QWWU/ea_profile.json * 2023-09-10 02:11:08 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-11 02:03:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-11 02:03:45 (153) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-11 02:03:45 (1700) [INFO] Checking if your system is up to date: * 2023-09-11 02:03:45 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-11 02:03:45 (4089) [INFO] * 2023-09-11 02:03:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-11 02:03:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-11 02:03:46 (4102) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-11 02:03:46 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-11 02:03:46 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-11 02:03:46 (4102) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-11 02:03:47 (4102) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-11 02:03:47 (4119) [INFO] * 2023-09-11 02:03:47 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-11 02:03:47 (4089) [INFO] * 2023-09-11 02:08:12 (4102) [INFO] * 2023-09-11 02:08:12 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-11 02:08:12 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-11 02:08:13 (4119) [INFO] * 2023-09-11 02:08:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-11 02:08:13 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-11 02:08:16 (1625) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-11 02:08:16 (153) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-11 02:11:57 (1768) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-11 02:11:57 (153) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-11 02:11:58 (1120) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-11 02:11:58 (153) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-11 02:11:58 (153) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-11 02:11:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-11 02:11:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HJ7FCtsAr3/ea_profile.json * 2023-09-11 02:12:00 (2259) [INFO] Backed up EA4 profile to /tmp/HJ7FCtsAr3/ea_profile.json * 2023-09-11 02:12:05 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-12 02:02:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-12 02:02:11 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-12 02:02:11 (1752) [INFO] Checking if your system is up to date: * 2023-09-12 02:02:11 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-12 02:02:11 (4229) [INFO] * 2023-09-12 02:02:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-12 02:02:12 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-12 02:02:12 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-12 02:02:12 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-12 02:02:12 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-12 02:02:12 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-12 02:02:13 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-12 02:02:13 (4259) [INFO] * 2023-09-12 02:02:13 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-12 02:02:13 (4229) [INFO] * 2023-09-12 02:06:20 (4242) [INFO] * 2023-09-12 02:06:20 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-12 02:06:20 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-12 02:06:20 (4259) [INFO] * 2023-09-12 02:06:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-12 02:06:20 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-12 02:06:25 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-12 02:06:25 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-12 02:09:41 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-12 02:09:41 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-12 02:09:42 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-12 02:09:42 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-12 02:09:42 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-12 02:09:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-12 02:09:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EwKe7A4HQh/ea_profile.json * 2023-09-12 02:09:44 (2293) [INFO] Backed up EA4 profile to /tmp/EwKe7A4HQh/ea_profile.json * 2023-09-12 02:09:48 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-13 02:01:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-13 02:01:37 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-13 02:01:37 (1752) [INFO] Checking if your system is up to date: * 2023-09-13 02:01:37 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-13 02:01:37 (4229) [INFO] * 2023-09-13 02:01:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-13 02:01:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-13 02:01:38 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-13 02:01:38 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-13 02:01:38 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-13 02:01:38 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-13 02:01:38 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-13 02:01:38 (4259) [INFO] * 2023-09-13 02:01:38 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-13 02:01:38 (4229) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-09-13 02:02:36 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-13 02:02:36 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-13 02:02:36 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-13 02:02:36 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-09-13 02:02:36 (4242) [INFO] packages for the previous distribution release still work). * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-13 02:02:36 (4242) [INFO] yum --disablerepo= ... * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-13 02:02:36 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-13 02:02:36 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] yum-config-manager --disable * 2023-09-13 02:02:36 (4242) [INFO] or * 2023-09-13 02:02:36 (4242) [INFO] subscription-manager repos --disable= * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-13 02:02:36 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-13 02:02:36 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-13 02:02:36 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-13 02:02:36 (4242) [INFO] compromise: * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-13 02:02:36 (4242) [INFO] * 2023-09-13 02:02:36 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-13 02:02:37 (4259) [INFO] * 2023-09-13 02:02:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-13 02:02:37 (1773) [INFO] Checking /scripts/sysup * 2023-09-13 02:02:37 (4228) [INFO] Running: /scripts/sysup * 2023-09-13 02:02:37 (4229) [INFO] * 2023-09-13 02:02:37 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-13 02:02:39 (4242) [INFO] All Needed Packages are already installed. * 2023-09-13 02:02:39 (4259) [INFO] * 2023-09-13 02:02:41 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-13 02:02:41 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-13 02:09:28 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-13 02:09:28 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-13 02:09:29 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-13 02:09:29 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-13 02:09:29 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-13 02:09:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-13 02:09:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/l7FjL2gNah/ea_profile.json * 2023-09-13 02:09:32 (2293) [INFO] Backed up EA4 profile to /tmp/l7FjL2gNah/ea_profile.json * 2023-09-13 02:09:36 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-14 02:12:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-14 02:12:35 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-14 02:12:35 (1752) [INFO] Checking if your system is up to date: * 2023-09-14 02:12:35 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-14 02:12:35 (4229) [INFO] * 2023-09-14 02:12:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-14 02:12:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-14 02:12:36 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-14 02:12:36 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-14 02:12:36 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-14 02:12:36 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-14 02:12:37 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-14 02:12:37 (4259) [INFO] * 2023-09-14 02:12:37 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-14 02:12:37 (4229) [INFO] * 2023-09-14 02:15:30 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/3f2952e5690b72eef6f3ce0f9852f814bff95a396a21a665ae84e6c2d2e47427-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-09-14 02:15:30 (4242) [INFO] Trying other mirror. * 2023-09-14 02:15:30 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-09-14 02:15:30 (4242) [INFO] * 2023-09-14 02:15:30 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-09-14 02:15:30 (4242) [INFO] * 2023-09-14 02:15:30 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-09-14 02:15:30 (4242) [INFO] * 2023-09-14 02:16:29 (4242) [INFO] * 2023-09-14 02:16:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-14 02:16:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-14 02:16:29 (4259) [INFO] * 2023-09-14 02:16:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-14 02:16:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-14 02:16:32 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-14 02:16:32 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-14 02:19:36 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-14 02:19:36 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30575 milliseconds') https://mirrors.sonic.net/epel/7/x86_64/repodata/4919d56e87c3c3386bf8993ec883674916bbdbe97a71653ebb73f90cbfe759f3-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/. * 2023-09-14 02:19:36 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-14 02:19:36 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-14 02:19:36 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-14 02:19:36 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-14 02:19:36 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-14 02:19:37 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-14 02:19:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-14 02:19:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0wu_0py5VM/ea_profile.json * 2023-09-14 02:19:39 (2293) [INFO] Backed up EA4 profile to /tmp/0wu_0py5VM/ea_profile.json * 2023-09-14 02:19:43 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-15 02:06:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-15 02:06:09 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-15 02:06:09 (1752) [INFO] Checking if your system is up to date: * 2023-09-15 02:06:09 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-15 02:06:09 (4229) [INFO] * 2023-09-15 02:06:10 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-15 02:06:10 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-15 02:06:10 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-15 02:06:10 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-15 02:06:10 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-15 02:06:10 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-15 02:06:11 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-15 02:06:11 (4259) [INFO] * 2023-09-15 02:06:11 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-15 02:06:11 (4229) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-09-15 02:07:06 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-15 02:07:06 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-15 02:07:06 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-15 02:07:06 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-09-15 02:07:06 (4242) [INFO] packages for the previous distribution release still work). * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-15 02:07:06 (4242) [INFO] yum --disablerepo= ... * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-15 02:07:06 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-15 02:07:06 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] yum-config-manager --disable * 2023-09-15 02:07:06 (4242) [INFO] or * 2023-09-15 02:07:06 (4242) [INFO] subscription-manager repos --disable= * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-15 02:07:06 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-15 02:07:06 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-15 02:07:06 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-15 02:07:06 (4242) [INFO] compromise: * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-15 02:07:06 (4242) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-15 02:07:06 (4259) [INFO] * 2023-09-15 02:07:06 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-15 02:07:06 (1773) [INFO] Checking /scripts/sysup * 2023-09-15 02:07:06 (4228) [INFO] Running: /scripts/sysup * 2023-09-15 02:07:06 (4229) [INFO] * 2023-09-15 02:07:06 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-15 02:07:09 (4242) [INFO] All Needed Packages are already installed. * 2023-09-15 02:07:09 (4259) [INFO] * 2023-09-15 02:07:13 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-15 02:07:13 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-16 02:02:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-16 02:02:26 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-16 02:02:26 (1752) [INFO] Checking if your system is up to date: * 2023-09-16 02:02:26 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-16 02:02:26 (4229) [INFO] * 2023-09-16 02:02:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-16 02:02:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-16 02:02:26 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-16 02:02:26 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-16 02:02:26 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-16 02:02:26 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-16 02:02:27 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-16 02:02:27 (4259) [INFO] * 2023-09-16 02:02:27 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-16 02:02:27 (4229) [INFO] * 2023-09-16 02:03:22 (4242) [INFO] * 2023-09-16 02:03:22 (4242) [INFO] * 2023-09-16 02:03:22 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-09-16 02:03:22 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-16 02:03:22 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-16 02:03:22 (4242) [INFO] * 2023-09-16 02:03:22 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-16 02:03:22 (4242) [INFO] * 2023-09-16 02:03:22 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-16 02:03:22 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-16 02:03:22 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-09-16 02:03:22 (4242) [INFO] packages for the previous distribution release still work). * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-16 02:03:23 (4242) [INFO] yum --disablerepo= ... * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-16 02:03:23 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-16 02:03:23 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] yum-config-manager --disable * 2023-09-16 02:03:23 (4242) [INFO] or * 2023-09-16 02:03:23 (4242) [INFO] subscription-manager repos --disable= * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-16 02:03:23 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-16 02:03:23 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-16 02:03:23 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-16 02:03:23 (4242) [INFO] compromise: * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-16 02:03:23 (4242) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-16 02:03:23 (4259) [INFO] * 2023-09-16 02:03:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-16 02:03:23 (1773) [INFO] Checking /scripts/sysup * 2023-09-16 02:03:23 (4228) [INFO] Running: /scripts/sysup * 2023-09-16 02:03:23 (4229) [INFO] * 2023-09-16 02:03:23 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-16 02:03:25 (4242) [INFO] All Needed Packages are already installed. * 2023-09-16 02:03:25 (4259) [INFO] * 2023-09-16 02:03:29 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-16 02:03:29 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-16 02:10:44 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-16 02:10:44 (1619) [ERROR] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.9/wp-toolkit/repodata/632d7cbb32fb1f88161f1c7076c01707d9953c8e4bb0495c00823763ca40ec5b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.9/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.web-ster.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. * 2023-09-16 02:10:44 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-16 02:10:44 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-16 02:10:44 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-16 02:10:45 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-16 02:10:45 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-16 02:10:45 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-16 02:10:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-16 02:10:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BiL7cUfTlv/ea_profile.json * 2023-09-16 02:10:48 (2293) [INFO] Backed up EA4 profile to /tmp/BiL7cUfTlv/ea_profile.json * 2023-09-16 02:10:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-17 02:02:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-17 02:02:37 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-17 02:02:37 (1752) [INFO] Checking if your system is up to date: * 2023-09-17 02:02:37 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-17 02:02:37 (4229) [INFO] * 2023-09-17 02:02:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-17 02:02:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-17 02:02:38 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-17 02:02:38 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-17 02:02:38 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-17 02:02:38 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-17 02:02:38 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-17 02:02:38 (4259) [INFO] * 2023-09-17 02:02:38 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-17 02:02:38 (4229) [INFO] * 2023-09-17 02:06:18 (4242) [INFO] * 2023-09-17 02:06:18 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-17 02:06:18 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-17 02:06:18 (4259) [INFO] * 2023-09-17 02:06:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-17 02:06:18 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-17 02:06:21 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-17 02:06:21 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-17 02:08:49 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-17 02:08:49 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-17 02:08:50 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-17 02:08:50 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-17 02:08:50 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-17 02:08:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-17 02:08:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AYZ3z_hqKK/ea_profile.json * 2023-09-17 02:08:52 (2293) [INFO] Backed up EA4 profile to /tmp/AYZ3z_hqKK/ea_profile.json * 2023-09-17 02:08:55 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-18 02:00:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-18 02:00:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-18 02:00:22 (1752) [INFO] Checking if your system is up to date: * 2023-09-18 02:00:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-18 02:00:22 (4229) [INFO] * 2023-09-18 02:00:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-18 02:00:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-18 02:00:23 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-18 02:00:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-18 02:00:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-18 02:00:23 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-18 02:00:23 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-18 02:00:23 (4259) [INFO] * 2023-09-18 02:00:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-18 02:00:23 (4229) [INFO] * 2023-09-18 02:04:15 (4242) [INFO] * 2023-09-18 02:04:15 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-18 02:04:15 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-18 02:04:15 (4259) [INFO] * 2023-09-18 02:04:15 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-18 02:04:15 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-18 02:04:18 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-18 02:04:18 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-18 02:07:16 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-18 02:07:16 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-18 02:07:16 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-18 02:07:16 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-18 02:07:16 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-18 02:07:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-18 02:07:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mbGzT1vnsz/ea_profile.json * 2023-09-18 02:07:18 (2293) [INFO] Backed up EA4 profile to /tmp/mbGzT1vnsz/ea_profile.json * 2023-09-18 02:07:22 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-19 02:01:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-19 02:01:43 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-19 02:01:43 (1752) [INFO] Checking if your system is up to date: * 2023-09-19 02:01:44 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-19 02:01:44 (4229) [INFO] * 2023-09-19 02:01:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-19 02:01:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-19 02:01:44 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-19 02:01:44 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-19 02:01:44 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-19 02:01:44 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-19 02:01:45 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-19 02:01:45 (4259) [INFO] * 2023-09-19 02:01:45 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-19 02:01:45 (4229) [INFO] * 2023-09-19 02:06:08 (4242) [INFO] * 2023-09-19 02:06:08 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-19 02:06:08 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-19 02:06:08 (4259) [INFO] * 2023-09-19 02:06:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-19 02:06:08 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-19 02:06:12 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-19 02:06:12 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-19 02:09:51 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-19 02:09:51 (1619) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2023-09-19 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-19 02:09:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-19 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-19 02:09:52 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-19 02:09:52 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-19 02:09:52 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-19 02:09:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-19 02:09:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7MR5z1uCky/ea_profile.json * 2023-09-19 02:09:54 (2293) [INFO] Backed up EA4 profile to /tmp/7MR5z1uCky/ea_profile.json * 2023-09-19 02:09:58 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-20 02:02:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-20 02:02:08 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-20 02:02:08 (1752) [INFO] Checking if your system is up to date: * 2023-09-20 02:02:08 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-20 02:02:08 (4229) [INFO] * 2023-09-20 02:02:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-20 02:02:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-20 02:02:09 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-20 02:02:09 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-20 02:02:09 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-20 02:02:09 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-20 02:02:10 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-20 02:02:10 (4259) [INFO] * 2023-09-20 02:02:10 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-20 02:02:10 (4229) [INFO] * 2023-09-20 02:06:37 (4242) [INFO] * 2023-09-20 02:06:37 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-20 02:06:37 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-20 02:06:37 (4259) [INFO] * 2023-09-20 02:06:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-20 02:06:37 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-20 02:06:40 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-20 02:06:40 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-20 02:10:19 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-20 02:10:19 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-20 02:10:20 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-20 02:10:20 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-20 02:10:20 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-20 02:10:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-20 02:10:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E2uoxE_QHU/ea_profile.json * 2023-09-20 02:10:22 (2293) [INFO] Backed up EA4 profile to /tmp/E2uoxE_QHU/ea_profile.json * 2023-09-20 02:10:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-21 02:06:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-21 02:06:20 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-21 02:06:20 (1752) [INFO] Checking if your system is up to date: * 2023-09-21 02:06:20 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-21 02:06:20 (4229) [INFO] * 2023-09-21 02:06:20 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-21 02:06:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-21 02:06:20 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-21 02:06:20 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-21 02:06:20 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-21 02:06:20 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-21 02:06:21 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-21 02:06:21 (4259) [INFO] * 2023-09-21 02:06:21 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-21 02:06:21 (4229) [INFO] * 2023-09-21 02:09:31 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/3a76f8e1548a15b0c5545ae90422142e03ffc015489e5243288a2e93ffb8e0f5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-09-21 02:09:31 (4242) [INFO] Trying other mirror. * 2023-09-21 02:09:31 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-09-21 02:09:31 (4242) [INFO] * 2023-09-21 02:09:31 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-09-21 02:09:31 (4242) [INFO] * 2023-09-21 02:09:31 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-09-21 02:09:31 (4242) [INFO] * 2023-09-21 02:10:03 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-09-21 02:10:03 (4242) [INFO] Trying other mirror. * 2023-09-21 02:10:27 (4242) [INFO] * 2023-09-21 02:10:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-21 02:10:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-21 02:10:28 (4259) [INFO] * 2023-09-21 02:10:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-21 02:10:28 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-21 02:10:32 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-21 02:10:32 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-21 02:14:06 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-21 02:14:06 (1619) [ERROR] https://mirrors.sonic.net/epel/7/x86_64/repodata/31fec9e5a94b8cf6f1d4771ee028d9c36797dbcd8153d0f6b373c2bdb8642fd4-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-09-21 02:14:06 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-21 02:14:06 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-21 02:14:06 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-21 02:14:07 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-21 02:14:07 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-21 02:14:07 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-21 02:14:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-21 02:14:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DjKPMW_7I6/ea_profile.json * 2023-09-21 02:14:10 (2293) [INFO] Backed up EA4 profile to /tmp/DjKPMW_7I6/ea_profile.json * 2023-09-21 02:14:13 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-22 02:03:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-22 02:03:16 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-22 02:03:16 (1752) [INFO] Checking if your system is up to date: * 2023-09-22 02:03:16 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-22 02:03:16 (4229) [INFO] * 2023-09-22 02:03:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-22 02:03:17 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-22 02:03:17 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-22 02:03:17 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-22 02:03:17 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-22 02:03:17 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-22 02:03:17 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-22 02:03:18 (4259) [INFO] * 2023-09-22 02:03:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-22 02:03:18 (4229) [INFO] * 2023-09-22 02:07:44 (4242) [INFO] * 2023-09-22 02:07:44 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-22 02:07:44 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-22 02:07:44 (4259) [INFO] * 2023-09-22 02:07:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-22 02:07:44 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-22 02:07:47 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-22 02:07:47 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-22 02:11:39 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-22 02:11:39 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-22 02:11:40 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-22 02:11:40 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-22 02:11:40 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-22 02:11:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-22 02:11:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uQ8e6cIsFW/ea_profile.json * 2023-09-22 02:11:42 (2293) [INFO] Backed up EA4 profile to /tmp/uQ8e6cIsFW/ea_profile.json * 2023-09-22 02:11:46 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-23 02:03:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-23 02:03:33 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-23 02:03:33 (1752) [INFO] Checking if your system is up to date: * 2023-09-23 02:03:33 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-23 02:03:33 (4229) [INFO] * 2023-09-23 02:03:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-23 02:03:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-23 02:03:34 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-23 02:03:34 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-23 02:03:34 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-23 02:03:34 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-23 02:03:34 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-23 02:03:35 (4259) [INFO] * 2023-09-23 02:03:35 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-23 02:03:35 (4229) [INFO] * 2023-09-23 02:07:34 (4242) [INFO] * 2023-09-23 02:07:34 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-23 02:07:34 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-23 02:07:35 (4259) [INFO] * 2023-09-23 02:07:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-23 02:07:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-23 02:07:39 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-23 02:07:39 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-23 02:10:32 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-23 02:10:32 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-23 02:10:33 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-23 02:10:33 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-23 02:10:33 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-23 02:10:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-23 02:10:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mnhFJrM6Oa/ea_profile.json * 2023-09-23 02:10:36 (2293) [INFO] Backed up EA4 profile to /tmp/mnhFJrM6Oa/ea_profile.json * 2023-09-23 02:10:39 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-24 02:03:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-24 02:03:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-24 02:03:24 (1752) [INFO] Checking if your system is up to date: * 2023-09-24 02:03:24 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-24 02:03:24 (4229) [INFO] * 2023-09-24 02:03:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-24 02:03:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-24 02:03:25 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-24 02:03:25 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-24 02:03:25 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-24 02:03:25 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-24 02:03:25 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-24 02:03:25 (4259) [INFO] * 2023-09-24 02:03:25 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-24 02:03:25 (4229) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-09-24 02:04:20 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-24 02:04:20 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-24 02:04:20 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-24 02:04:20 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-09-24 02:04:20 (4242) [INFO] packages for the previous distribution release still work). * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-24 02:04:20 (4242) [INFO] yum --disablerepo= ... * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-24 02:04:20 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-24 02:04:20 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] yum-config-manager --disable * 2023-09-24 02:04:20 (4242) [INFO] or * 2023-09-24 02:04:20 (4242) [INFO] subscription-manager repos --disable= * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-24 02:04:20 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-24 02:04:20 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-24 02:04:20 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-24 02:04:20 (4242) [INFO] compromise: * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-24 02:04:20 (4242) [INFO] * 2023-09-24 02:04:20 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-24 02:04:20 (4259) [INFO] * 2023-09-24 02:04:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-24 02:04:20 (1773) [INFO] Checking /scripts/sysup * 2023-09-24 02:04:20 (4228) [INFO] Running: /scripts/sysup * 2023-09-24 02:04:20 (4229) [INFO] * 2023-09-24 02:04:21 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-24 02:04:23 (4242) [INFO] All Needed Packages are already installed. * 2023-09-24 02:04:23 (4259) [INFO] * 2023-09-24 02:04:26 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-24 02:04:26 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-24 02:12:49 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-24 02:12:49 (1619) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.nodesdirect.com/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.datto.com/CentOS/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rit.edu/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.ocf.berkeley.edu/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.iu13.net/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos-distro.1gservers.com/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.us-midwest-1.nexcess.net/CentOS/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://abqix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nocix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/bad7185256423286eda3c6cba058ac3bdd3c5f5e60e3cc3e874cbc72548f5d19-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-09-24 02:12:49 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-24 02:12:49 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-24 02:12:49 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-24 02:12:50 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-24 02:12:50 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-24 02:12:50 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-24 02:12:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-24 02:12:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sxeadp0sIW/ea_profile.json * 2023-09-24 02:12:52 (2293) [INFO] Backed up EA4 profile to /tmp/sxeadp0sIW/ea_profile.json * 2023-09-24 02:12:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-25 01:59:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-25 01:59:33 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-25 01:59:33 (1752) [INFO] Checking if your system is up to date: * 2023-09-25 01:59:33 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-25 01:59:33 (4229) [INFO] * 2023-09-25 01:59:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-25 01:59:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-25 01:59:34 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-25 01:59:34 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-25 01:59:34 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-25 01:59:34 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-25 01:59:34 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-25 01:59:34 (4259) [INFO] * 2023-09-25 01:59:34 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-25 01:59:34 (4229) [INFO] * 2023-09-25 02:03:26 (4242) [INFO] * 2023-09-25 02:03:26 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-25 02:03:26 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-25 02:03:26 (4259) [INFO] * 2023-09-25 02:03:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-25 02:03:26 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-25 02:03:29 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-25 02:03:29 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-25 02:06:13 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-25 02:06:13 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-25 02:06:14 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-25 02:06:14 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-25 02:06:14 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-25 02:06:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-25 02:06:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Qwo3F6bJN4/ea_profile.json * 2023-09-25 02:06:16 (2293) [INFO] Backed up EA4 profile to /tmp/Qwo3F6bJN4/ea_profile.json * 2023-09-25 02:06:18 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-26 02:01:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-26 02:01:48 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-26 02:01:48 (1752) [INFO] Checking if your system is up to date: * 2023-09-26 02:01:48 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-26 02:01:48 (4229) [INFO] * 2023-09-26 02:01:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-26 02:01:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-26 02:01:49 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-26 02:01:49 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-26 02:01:49 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-26 02:01:49 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-26 02:01:49 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-26 02:01:49 (4259) [INFO] * 2023-09-26 02:01:49 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-26 02:01:49 (4229) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-09-26 02:02:45 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-09-26 02:02:45 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-09-26 02:02:45 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-09-26 02:02:45 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-09-26 02:02:45 (4242) [INFO] packages for the previous distribution release still work). * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-09-26 02:02:45 (4242) [INFO] yum --disablerepo= ... * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-09-26 02:02:45 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-09-26 02:02:45 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] yum-config-manager --disable * 2023-09-26 02:02:45 (4242) [INFO] or * 2023-09-26 02:02:45 (4242) [INFO] subscription-manager repos --disable= * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-09-26 02:02:45 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-09-26 02:02:45 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-09-26 02:02:45 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-09-26 02:02:45 (4242) [INFO] compromise: * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-09-26 02:02:45 (4242) [INFO] * 2023-09-26 02:02:45 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-09-26 02:02:45 (4259) [INFO] * 2023-09-26 02:02:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-26 02:02:45 (1773) [INFO] Checking /scripts/sysup * 2023-09-26 02:02:45 (4228) [INFO] Running: /scripts/sysup * 2023-09-26 02:02:45 (4229) [INFO] * 2023-09-26 02:02:46 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-09-26 02:02:48 (4242) [INFO] All Needed Packages are already installed. * 2023-09-26 02:02:48 (4259) [INFO] * 2023-09-26 02:02:52 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-26 02:02:52 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-26 02:09:39 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-26 02:09:39 (1619) [ERROR] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/a1ae205a704a9b88cbc17854b1e303132ec63e49016b8389ec27a29f6ad435e1-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/798a7339706024fe2948311176c4311b27aa72e5062aa487439fb2fab415345e-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/ce8d77385d68918c631772dd994e31538f1b03edee3359a51d662ee21488599b-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/dd23caa8275c5599ed9b7beaecc6fd3876396ea925d393d392e2e9019a3695d3-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/78ebf7688504922261483e0b13830a5d88bcc2985cd51babf50d52d6eb87544e-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2023-09-26 02:09:39 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-26 02:09:39 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-26 02:09:39 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-26 02:09:40 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-26 02:09:40 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-26 02:09:40 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-26 02:09:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-26 02:09:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/16KENmY5sD/ea_profile.json * 2023-09-26 02:09:41 (2293) [INFO] Backed up EA4 profile to /tmp/16KENmY5sD/ea_profile.json * 2023-09-26 02:09:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-27 02:00:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-27 02:00:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-27 02:00:49 (1752) [INFO] Checking if your system is up to date: * 2023-09-27 02:00:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-27 02:00:49 (4229) [INFO] * 2023-09-27 02:00:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-27 02:00:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-27 02:00:50 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-27 02:00:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-27 02:00:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-27 02:00:50 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-27 02:00:50 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-27 02:00:50 (4259) [INFO] * 2023-09-27 02:00:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-27 02:00:50 (4229) [INFO] * 2023-09-27 02:04:25 (4242) [INFO] * 2023-09-27 02:04:25 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-27 02:04:25 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-27 02:04:25 (4259) [INFO] * 2023-09-27 02:04:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-27 02:04:25 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-27 02:04:29 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-27 02:04:29 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-27 02:07:35 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-27 02:07:35 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-27 02:07:36 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-27 02:07:36 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-27 02:07:36 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-27 02:07:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-27 02:07:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eDV1RjLHYB/ea_profile.json * 2023-09-27 02:07:39 (2293) [INFO] Backed up EA4 profile to /tmp/eDV1RjLHYB/ea_profile.json * 2023-09-27 02:07:42 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-28 02:01:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-28 02:01:34 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-28 02:01:34 (1752) [INFO] Checking if your system is up to date: * 2023-09-28 02:01:34 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-28 02:01:34 (4229) [INFO] * 2023-09-28 02:01:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-28 02:01:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-28 02:01:35 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-28 02:01:35 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-28 02:01:35 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-28 02:01:35 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-28 02:01:35 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-28 02:01:35 (4259) [INFO] * 2023-09-28 02:01:35 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-28 02:01:35 (4229) [INFO] * 2023-09-28 02:05:31 (4242) [INFO] * 2023-09-28 02:05:31 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-28 02:05:31 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-28 02:05:31 (4259) [INFO] * 2023-09-28 02:05:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-28 02:05:31 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-28 02:05:34 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-28 02:05:34 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-28 02:08:41 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-28 02:08:41 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-28 02:08:42 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-28 02:08:42 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-28 02:08:42 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-28 02:08:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-28 02:08:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0JuHSxqYbx/ea_profile.json * 2023-09-28 02:08:45 (2293) [INFO] Backed up EA4 profile to /tmp/0JuHSxqYbx/ea_profile.json * 2023-09-28 02:08:49 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-29 01:59:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-29 01:59:52 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-29 01:59:52 (1752) [INFO] Checking if your system is up to date: * 2023-09-29 01:59:52 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-29 01:59:52 (4229) [INFO] * 2023-09-29 01:59:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-29 01:59:52 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-29 01:59:52 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-29 01:59:52 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-29 01:59:52 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-29 01:59:52 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-29 01:59:53 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-29 01:59:53 (4259) [INFO] * 2023-09-29 01:59:53 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-29 01:59:53 (4229) [INFO] * 2023-09-29 02:03:02 (4242) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/91495e579330470fb1bef143824e46c2eba2e380fa44ef6cb2a59082601b7702-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-09-29 02:03:02 (4242) [INFO] Trying other mirror. * 2023-09-29 02:03:02 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-09-29 02:03:02 (4242) [INFO] * 2023-09-29 02:03:02 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-09-29 02:03:02 (4242) [INFO] * 2023-09-29 02:03:02 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-09-29 02:03:02 (4242) [INFO] * 2023-09-29 02:03:59 (4242) [INFO] * 2023-09-29 02:03:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-29 02:03:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-29 02:03:59 (4259) [INFO] * 2023-09-29 02:03:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-29 02:03:59 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-29 02:04:04 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-29 02:04:04 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-29 02:07:37 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-09-29 02:07:37 (1619) [ERROR] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/36688a58bcbfabedc120b1d34a1be3ef597e83d134e9f316d9966b84b576e847-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/9e95b400751b5b789a606336a7a9aae51db6d9ede0c7f71cdc177b158a5ab984-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/54e1624b92dc757ff7ab0a3ff70fc22b4dbc8b5f754e66d77a30a4836942288c-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2023-09-29 02:07:37 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-09-29 02:07:37 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-29 02:07:37 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-29 02:07:38 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-29 02:07:38 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-29 02:07:38 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-29 02:07:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-29 02:07:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8JUEZIBZZy/ea_profile.json * 2023-09-29 02:07:41 (2293) [INFO] Backed up EA4 profile to /tmp/8JUEZIBZZy/ea_profile.json * 2023-09-29 02:07:46 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-30 02:05:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-09-30 02:05:03 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-30 02:05:03 (1752) [INFO] Checking if your system is up to date: * 2023-09-30 02:05:03 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-30 02:05:03 (4229) [INFO] * 2023-09-30 02:05:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-30 02:05:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-09-30 02:05:05 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-30 02:05:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-30 02:05:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-30 02:05:05 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-09-30 02:05:06 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-09-30 02:05:06 (4259) [INFO] * 2023-09-30 02:05:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-30 02:05:06 (4229) [INFO] * 2023-09-30 02:08:49 (4242) [INFO] * 2023-09-30 02:08:49 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-30 02:08:49 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-30 02:08:50 (4259) [INFO] * 2023-09-30 02:08:50 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-30 02:08:50 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-30 02:08:53 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-09-30 02:08:53 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-09-30 02:11:49 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-09-30 02:11:49 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-09-30 02:11:50 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-09-30 02:11:50 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-09-30 02:11:50 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-09-30 02:11:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-30 02:11:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ivmh2X0ewA/ea_profile.json * 2023-09-30 02:11:52 (2293) [INFO] Backed up EA4 profile to /tmp/ivmh2X0ewA/ea_profile.json * 2023-09-30 02:11:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-01 02:03:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-01 02:03:41 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-01 02:03:41 (1752) [INFO] Checking if your system is up to date: * 2023-10-01 02:03:41 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-01 02:03:41 (4229) [INFO] * 2023-10-01 02:03:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-01 02:03:42 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-01 02:03:42 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-01 02:03:42 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-01 02:03:42 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-01 02:03:42 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-01 02:03:42 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-01 02:03:42 (4259) [INFO] * 2023-10-01 02:03:42 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-01 02:03:42 (4229) [INFO] * 2023-10-01 02:06:52 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/b9532978573c6c6aabd6712c03a30821435877fa15655fe562331a5e8a88312d-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-01 02:06:52 (4242) [INFO] Trying other mirror. * 2023-10-01 02:06:52 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-10-01 02:06:52 (4242) [INFO] * 2023-10-01 02:06:52 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-10-01 02:06:52 (4242) [INFO] * 2023-10-01 02:06:52 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-10-01 02:06:52 (4242) [INFO] * 2023-10-01 02:07:54 (4242) [INFO] * 2023-10-01 02:07:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-01 02:07:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-01 02:07:55 (4259) [INFO] * 2023-10-01 02:07:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-01 02:07:55 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-01 02:07:58 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-01 02:07:58 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-01 02:11:33 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-01 02:11:33 (1619) [ERROR] https://mirrors.sonic.net/epel/7/x86_64/repodata/84edb59d1c81b5c813a045e481d03b90246908d753ccaea4d00ab9bd4608e5bb-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-10-01 02:11:33 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-01 02:11:33 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-01 02:11:33 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-01 02:11:33 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-01 02:11:33 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-01 02:11:33 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-01 02:11:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-01 02:11:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ow1LZ5Egcc/ea_profile.json * 2023-10-01 02:11:35 (2293) [INFO] Backed up EA4 profile to /tmp/Ow1LZ5Egcc/ea_profile.json * 2023-10-01 02:11:39 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-02 01:58:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-02 01:58:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-02 01:58:14 (1752) [INFO] Checking if your system is up to date: * 2023-10-02 01:58:14 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-02 01:58:14 (4229) [INFO] * 2023-10-02 01:58:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-02 01:58:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-02 01:58:14 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-02 01:58:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-02 01:58:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-02 01:58:14 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-02 01:58:15 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-02 01:58:15 (4259) [INFO] * 2023-10-02 01:58:15 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-02 01:58:15 (4229) [INFO] * 2023-10-02 02:14:29 (4242) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer" * 2023-10-02 02:14:29 (4242) [INFO] Trying other mirror. * 2023-10-02 02:14:45 (4242) [INFO] http://mirror.facebook.net/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-02 02:14:45 (4242) [INFO] Trying other mirror. * 2023-10-02 02:15:23 (4242) [INFO] * 2023-10-02 02:15:23 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-02 02:15:23 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-02 02:15:23 (4259) [INFO] * 2023-10-02 02:15:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-02 02:15:23 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-02 02:15:26 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-02 02:15:26 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-03 02:02:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-03 02:02:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-03 02:02:49 (1752) [INFO] Checking if your system is up to date: * 2023-10-03 02:02:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-03 02:02:49 (4229) [INFO] * 2023-10-03 02:02:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-03 02:02:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-03 02:02:50 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-03 02:02:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-03 02:02:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-03 02:02:50 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-03 02:02:50 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-03 02:02:50 (4259) [INFO] * 2023-10-03 02:02:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-03 02:02:50 (4229) [INFO] * 2023-10-03 02:07:10 (4242) [INFO] * 2023-10-03 02:07:10 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-03 02:07:10 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-03 02:07:11 (4259) [INFO] * 2023-10-03 02:07:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-03 02:07:11 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-03 02:07:15 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-03 02:07:15 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-03 02:10:37 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-03 02:10:37 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-03 02:10:38 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-03 02:10:38 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-03 02:10:38 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-03 02:10:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-03 02:10:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wohzqNQsLM/ea_profile.json * 2023-10-03 02:10:39 (2293) [INFO] Backed up EA4 profile to /tmp/wohzqNQsLM/ea_profile.json * 2023-10-03 02:10:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-04 01:07:57 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-04 01:07:57 (1752) [INFO] Checking if your system is up to date: * 2023-10-04 01:07:57 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-04 01:07:57 (4229) [INFO] * 2023-10-04 01:07:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-04 01:07:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-04 01:07:57 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-04 01:07:57 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-04 01:07:57 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-04 01:07:57 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-04 01:07:58 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-04 01:07:58 (4259) [INFO] * 2023-10-04 01:07:58 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-04 01:07:58 (4229) [INFO] * 2023-10-04 01:11:06 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:06 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:06 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-10-04 01:11:06 (4242) [INFO] * 2023-10-04 01:11:06 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-10-04 01:11:06 (4242) [INFO] * 2023-10-04 01:11:06 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-10-04 01:11:06 (4242) [INFO] * 2023-10-04 01:11:22 (4242) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:11:22 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:23 (4242) [INFO] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:11:23 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:23 (4242) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:23 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:24 (4242) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:24 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:25 (4242) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:25 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:37 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:11:37 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:38 (4242) [INFO] http://mirror.us.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-04 01:11:38 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:40 (4242) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:40 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:56 (4242) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:11:56 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:56 (4242) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:11:56 (4242) [INFO] Trying other mirror. * 2023-10-04 01:11:57 (4242) [INFO] http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:11:57 (4242) [INFO] Trying other mirror. * 2023-10-04 01:12:00 (4242) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:12:00 (4242) [INFO] Trying other mirror. * 2023-10-04 01:12:16 (4242) [INFO] https://mirror.team-cymru.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:12:16 (4242) [INFO] Trying other mirror. * 2023-10-04 01:12:32 (4242) [INFO] https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:12:32 (4242) [INFO] Trying other mirror. * 2023-10-04 01:12:47 (4242) [INFO] https://mirror.usi.edu/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:12:47 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:03 (4242) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:13:03 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:18 (4242) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:18 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:34 (4242) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:13:34 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:35 (4242) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:35 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:35 (4242) [INFO] https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:13:35 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:36 (4242) [INFO] https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:36 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:37 (4242) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:37 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:37 (4242) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:37 (4242) [INFO] Trying other mirror. * 2023-10-04 01:13:53 (4242) [INFO] https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:13:53 (4242) [INFO] Trying other mirror. * 2023-10-04 01:14:08 (4242) [INFO] http://ftp.cse.buffalo.edu/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:14:08 (4242) [INFO] Trying other mirror. * 2023-10-04 01:14:24 (4242) [INFO] https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:14:24 (4242) [INFO] Trying other mirror. * 2023-10-04 01:14:39 (4242) [INFO] https://ftp-nyc.osuosl.org/pub/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:14:39 (4242) [INFO] Trying other mirror. * 2023-10-04 01:14:55 (4242) [INFO] https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:14:55 (4242) [INFO] Trying other mirror. * 2023-10-04 01:15:11 (4242) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:15:11 (4242) [INFO] Trying other mirror. * 2023-10-04 01:15:27 (4242) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:15:27 (4242) [INFO] Trying other mirror. * 2023-10-04 01:15:42 (4242) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:15:42 (4242) [INFO] Trying other mirror. * 2023-10-04 01:15:43 (4242) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:15:43 (4242) [INFO] Trying other mirror. * 2023-10-04 01:15:58 (4242) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:15:58 (4242) [INFO] Trying other mirror. * 2023-10-04 01:16:14 (4242) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:16:14 (4242) [INFO] Trying other mirror. * 2023-10-04 01:16:29 (4242) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:16:29 (4242) [INFO] Trying other mirror. * 2023-10-04 01:16:45 (4242) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:16:45 (4242) [INFO] Trying other mirror. * 2023-10-04 01:17:00 (4242) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:17:00 (4242) [INFO] Trying other mirror. * 2023-10-04 01:17:16 (4242) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:17:16 (4242) [INFO] Trying other mirror. * 2023-10-04 01:17:32 (4242) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:17:32 (4242) [INFO] Trying other mirror. * 2023-10-04 01:17:47 (4242) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:17:47 (4242) [INFO] Trying other mirror. * 2023-10-04 01:18:03 (4242) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:18:03 (4242) [INFO] Trying other mirror. * 2023-10-04 01:18:18 (4242) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:18:18 (4242) [INFO] Trying other mirror. * 2023-10-04 01:18:34 (4242) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:18:34 (4242) [INFO] Trying other mirror. * 2023-10-04 01:18:49 (4242) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:18:49 (4242) [INFO] Trying other mirror. * 2023-10-04 01:18:50 (4242) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-10-04 01:18:50 (4242) [INFO] Trying other mirror. * 2023-10-04 01:19:05 (4242) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:19:05 (4242) [INFO] Trying other mirror. * 2023-10-04 01:19:21 (4242) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:19:21 (4242) [INFO] Trying other mirror. * 2023-10-04 01:19:37 (4242) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:19:37 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:07 (4242) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: (28, 'timed out before SSL handshake') * 2023-10-04 01:20:07 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:23 (4242) [INFO] https://na.edge.kernel.org/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:20:23 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:24 (4242) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:20:24 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:39 (4242) [INFO] https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:20:39 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:55 (4242) [INFO] http://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:20:55 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:55 (4242) [INFO] http://mirror.siena.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:20:55 (4242) [INFO] Trying other mirror. * 2023-10-04 01:20:56 (4242) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:20:56 (4242) [INFO] Trying other mirror. * 2023-10-04 01:21:11 (4242) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:21:11 (4242) [INFO] Trying other mirror. * 2023-10-04 01:21:27 (4242) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:21:27 (4242) [INFO] Trying other mirror. * 2023-10-04 01:21:43 (4242) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:21:43 (4242) [INFO] Trying other mirror. * 2023-10-04 01:21:58 (4242) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:21:58 (4242) [INFO] Trying other mirror. * 2023-10-04 01:21:59 (4242) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:21:59 (4242) [INFO] Trying other mirror. * 2023-10-04 01:22:14 (4242) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-10-04 01:22:14 (4242) [INFO] Trying other mirror. * 2023-10-04 01:22:14 (4242) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:22:14 (4242) [INFO] Trying other mirror. * 2023-10-04 01:22:30 (4242) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-10-04 01:22:30 (4242) [INFO] Trying other mirror. * 2023-10-04 01:22:46 (4242) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:22:46 (4242) [INFO] Trying other mirror. * 2023-10-04 01:22:46 (4242) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:22:46 (4242) [INFO] Trying other mirror. * 2023-10-04 01:23:02 (4242) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:23:02 (4242) [INFO] Trying other mirror. * 2023-10-04 01:23:02 (4242) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-10-04 01:23:02 (4242) [INFO] Trying other mirror. * 2023-10-04 01:23:18 (4242) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:23:18 (4242) [INFO] Trying other mirror. * 2023-10-04 01:23:33 (4242) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:23:33 (4242) [INFO] Trying other mirror. * 2023-10-04 01:23:49 (4242) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/0a43a9824ff6e9c8580b8032228537c87a3c970b6f96d89662db5c42ba702a0a-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-04 01:23:49 (4242) [INFO] Trying other mirror. * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-04 01:24:20 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-04 01:24:20 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-04 01:24:20 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-04 01:24:20 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-04 01:24:20 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-04 01:24:20 (4242) [INFO] yum --disablerepo= ... * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-04 01:24:20 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-04 01:24:20 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] yum-config-manager --disable * 2023-10-04 01:24:20 (4242) [INFO] or * 2023-10-04 01:24:20 (4242) [INFO] subscription-manager repos --disable= * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-04 01:24:20 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-04 01:24:20 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-04 01:24:20 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-04 01:24:20 (4242) [INFO] compromise: * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-04 01:24:20 (4242) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] updates: Check uncompressed DB failed * 2023-10-04 01:24:20 (4259) [INFO] * 2023-10-04 01:24:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-04 01:24:20 (1773) [INFO] Checking /scripts/sysup * 2023-10-04 01:24:20 (4228) [INFO] Running: /scripts/sysup * 2023-10-04 01:24:20 (4229) [INFO] * 2023-10-04 01:24:20 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-04 01:24:23 (4242) [INFO] All Needed Packages are already installed. * 2023-10-04 01:24:23 (4259) [INFO] * 2023-10-04 01:24:26 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-04 01:24:26 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-05 02:06:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-05 02:06:31 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-05 02:06:31 (1752) [INFO] Checking if your system is up to date: * 2023-10-05 02:06:31 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-05 02:06:31 (4229) [INFO] * 2023-10-05 02:06:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-05 02:06:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-05 02:06:32 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-05 02:06:32 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-05 02:06:32 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-05 02:06:32 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-05 02:06:32 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-05 02:06:32 (4259) [INFO] * 2023-10-05 02:06:32 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-05 02:06:32 (4229) [INFO] * 2023-10-05 02:09:16 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" * 2023-10-05 02:09:16 (4242) [INFO] Trying other mirror. * 2023-10-05 02:10:26 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-05 02:10:26 (4242) [INFO] Trying other mirror. * 2023-10-05 02:10:34 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-05 02:10:34 (4242) [INFO] Trying other mirror. * 2023-10-05 02:10:35 (4242) [INFO] http://mirror.mia11.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-05 02:10:35 (4242) [INFO] Trying other mirror. * 2023-10-05 02:11:29 (4242) [INFO] * 2023-10-05 02:11:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-05 02:11:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-05 02:11:30 (4259) [INFO] * 2023-10-05 02:11:30 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-05 02:11:30 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-05 02:11:32 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-05 02:11:32 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-05 02:15:07 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-05 02:15:07 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-05 02:15:07 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-05 02:15:07 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-05 02:15:07 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-05 02:15:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-05 02:15:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wqh09cqnJx/ea_profile.json * 2023-10-05 02:15:10 (2293) [INFO] Backed up EA4 profile to /tmp/wqh09cqnJx/ea_profile.json * 2023-10-05 02:15:13 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-06 02:00:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-06 02:00:38 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-06 02:00:38 (1752) [INFO] Checking if your system is up to date: * 2023-10-06 02:00:38 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-06 02:00:38 (4229) [INFO] * 2023-10-06 02:00:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-06 02:00:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-06 02:00:39 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-06 02:00:39 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-06 02:00:39 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-06 02:00:39 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-06 02:00:39 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-06 02:00:39 (4259) [INFO] * 2023-10-06 02:00:39 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-06 02:00:39 (4229) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-06 02:01:34 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-06 02:01:34 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-06 02:01:34 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-06 02:01:34 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-06 02:01:34 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-06 02:01:34 (4242) [INFO] yum --disablerepo= ... * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-06 02:01:34 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-06 02:01:34 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] yum-config-manager --disable * 2023-10-06 02:01:34 (4242) [INFO] or * 2023-10-06 02:01:34 (4242) [INFO] subscription-manager repos --disable= * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-06 02:01:34 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-06 02:01:34 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-06 02:01:34 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-06 02:01:34 (4242) [INFO] compromise: * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-06 02:01:34 (4242) [INFO] * 2023-10-06 02:01:34 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-10-06 02:01:34 (4259) [INFO] * 2023-10-06 02:01:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-06 02:01:34 (1773) [INFO] Checking /scripts/sysup * 2023-10-06 02:01:34 (4228) [INFO] Running: /scripts/sysup * 2023-10-06 02:01:34 (4229) [INFO] * 2023-10-06 02:01:35 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-06 02:01:37 (4242) [INFO] All Needed Packages are already installed. * 2023-10-06 02:01:37 (4259) [INFO] * 2023-10-06 02:01:40 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-06 02:01:40 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-06 02:10:01 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-06 02:10:01 (1619) [ERROR] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/5b0986bf73200f316e342ecd78c1d9e4cc545f38587c4751b287e49f88528155-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/0ce38ca5a7add1cf722d9423be92333380238bc9829968df0cc9ecda0d9b2a24-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. * 2023-10-06 02:10:01 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-06 02:10:01 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-06 02:10:01 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-06 02:10:02 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-06 02:10:02 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-06 02:10:02 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-06 02:10:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-06 02:10:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aVWlyMI3Z7/ea_profile.json * 2023-10-06 02:10:04 (2293) [INFO] Backed up EA4 profile to /tmp/aVWlyMI3Z7/ea_profile.json * 2023-10-06 02:10:07 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-07 02:08:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-07 02:08:34 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-07 02:08:34 (1752) [INFO] Checking if your system is up to date: * 2023-10-07 02:08:34 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-07 02:08:34 (4229) [INFO] * 2023-10-07 02:08:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-07 02:08:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-07 02:08:35 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-07 02:08:35 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-07 02:08:35 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-07 02:08:35 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-07 02:08:35 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-07 02:08:35 (4259) [INFO] * 2023-10-07 02:08:35 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-07 02:08:35 (4229) [INFO] * 2023-10-07 02:12:24 (4242) [INFO] * 2023-10-07 02:12:24 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-07 02:12:24 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-07 02:12:24 (4259) [INFO] * 2023-10-07 02:12:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-07 02:12:24 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-07 02:12:28 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-07 02:12:28 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-07 02:15:47 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-07 02:15:47 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-07 02:15:48 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-07 02:15:48 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-07 02:15:48 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-07 02:15:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-07 02:15:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E6s8MxPxxE/ea_profile.json * 2023-10-07 02:15:50 (2293) [INFO] Backed up EA4 profile to /tmp/E6s8MxPxxE/ea_profile.json * 2023-10-07 02:15:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-08 02:00:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-08 02:00:52 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-08 02:00:52 (1752) [INFO] Checking if your system is up to date: * 2023-10-08 02:00:52 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-08 02:00:52 (4229) [INFO] * 2023-10-08 02:00:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-08 02:00:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-08 02:00:53 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-08 02:00:53 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-08 02:00:53 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-08 02:00:53 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-08 02:00:53 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-08 02:00:53 (4259) [INFO] * 2023-10-08 02:00:53 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-08 02:00:53 (4229) [INFO] * 2023-10-08 02:04:05 (4242) [INFO] * 2023-10-08 02:04:05 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-08 02:04:05 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-08 02:04:05 (4259) [INFO] * 2023-10-08 02:04:05 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-08 02:04:05 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-08 02:04:08 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-08 02:04:08 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-08 02:06:37 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-08 02:06:37 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-08 02:06:38 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-08 02:06:38 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-08 02:06:38 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-08 02:06:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-08 02:06:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MKNVvHnLwH/ea_profile.json * 2023-10-08 02:06:40 (2293) [INFO] Backed up EA4 profile to /tmp/MKNVvHnLwH/ea_profile.json * 2023-10-08 02:06:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-09 01:59:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-09 01:59:40 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-09 01:59:40 (1752) [INFO] Checking if your system is up to date: * 2023-10-09 01:59:40 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-09 01:59:40 (4229) [INFO] * 2023-10-09 01:59:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-09 01:59:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-09 01:59:40 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-09 01:59:40 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-09 01:59:40 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-09 01:59:40 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-09 01:59:41 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-09 01:59:41 (4259) [INFO] * 2023-10-09 01:59:41 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-09 01:59:41 (4229) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-09 02:00:38 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-09 02:00:38 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-09 02:00:38 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-09 02:00:38 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-09 02:00:38 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-09 02:00:38 (4242) [INFO] yum --disablerepo= ... * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-09 02:00:38 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-09 02:00:38 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] yum-config-manager --disable * 2023-10-09 02:00:38 (4242) [INFO] or * 2023-10-09 02:00:38 (4242) [INFO] subscription-manager repos --disable= * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-09 02:00:38 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-09 02:00:38 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-09 02:00:38 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-09 02:00:38 (4242) [INFO] compromise: * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-09 02:00:38 (4242) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-10-09 02:00:38 (4259) [INFO] * 2023-10-09 02:00:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-09 02:00:38 (1773) [INFO] Checking /scripts/sysup * 2023-10-09 02:00:38 (4228) [INFO] Running: /scripts/sysup * 2023-10-09 02:00:38 (4229) [INFO] * 2023-10-09 02:00:38 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-09 02:00:40 (4242) [INFO] All Needed Packages are already installed. * 2023-10-09 02:00:40 (4259) [INFO] * 2023-10-09 02:00:44 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-09 02:00:44 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-09 02:06:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-09 02:06:56 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-09 02:06:57 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-09 02:06:57 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-09 02:06:57 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-09 02:06:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-09 02:06:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JGUtvnaeZp/ea_profile.json * 2023-10-09 02:06:59 (2293) [INFO] Backed up EA4 profile to /tmp/JGUtvnaeZp/ea_profile.json * 2023-10-09 02:07:02 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-10 02:03:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-10 02:03:03 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-10 02:03:03 (1752) [INFO] Checking if your system is up to date: * 2023-10-10 02:03:03 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-10 02:03:03 (4229) [INFO] * 2023-10-10 02:03:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-10 02:03:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-10 02:03:04 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-10 02:03:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-10 02:03:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-10 02:03:04 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-10 02:03:05 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-10 02:03:05 (4259) [INFO] * 2023-10-10 02:03:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-10 02:03:05 (4229) [INFO] * 2023-10-10 02:06:53 (4242) [INFO] * 2023-10-10 02:06:53 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-10 02:06:53 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-10 02:06:53 (4259) [INFO] * 2023-10-10 02:06:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-10 02:06:53 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-10 02:06:55 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-10 02:06:55 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-10 02:10:27 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-10 02:10:27 (1619) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2023-10-10 02:10:27 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-10 02:10:27 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-10 02:10:27 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-10 02:10:28 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-10 02:10:28 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-10 02:10:28 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-10 02:10:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-10 02:10:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mhk7la1Wxm/ea_profile.json * 2023-10-10 02:10:30 (2293) [INFO] Backed up EA4 profile to /tmp/mhk7la1Wxm/ea_profile.json * 2023-10-10 02:10:33 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-11 02:12:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-11 02:12:46 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-11 02:12:46 (1752) [INFO] Checking if your system is up to date: * 2023-10-11 02:12:46 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-11 02:12:46 (4229) [INFO] * 2023-10-11 02:12:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-11 02:12:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-11 02:12:46 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-11 02:12:46 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-11 02:12:46 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-11 02:12:46 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-11 02:12:47 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-11 02:12:47 (4259) [INFO] * 2023-10-11 02:12:47 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-11 02:12:47 (4229) [INFO] * 2023-10-11 02:17:10 (4242) [INFO] * 2023-10-11 02:17:10 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-11 02:17:10 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-11 02:17:10 (4259) [INFO] * 2023-10-11 02:17:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-11 02:17:10 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-11 02:17:13 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-11 02:17:13 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-11 02:21:06 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-11 02:21:06 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-10-11 02:21:06 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-11 02:21:06 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-11 02:21:06 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-11 02:21:07 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-11 02:21:07 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-11 02:21:07 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-11 02:21:07 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-11 02:21:07 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s9z5pbqSy8/ea_profile.json * 2023-10-11 02:21:10 (2293) [INFO] Backed up EA4 profile to /tmp/s9z5pbqSy8/ea_profile.json * 2023-10-11 02:21:14 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-12 02:12:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-12 02:12:07 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-12 02:12:07 (1752) [INFO] Checking if your system is up to date: * 2023-10-12 02:12:07 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-12 02:12:07 (4229) [INFO] * 2023-10-12 02:12:07 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-12 02:12:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-12 02:12:07 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-12 02:12:07 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-12 02:12:07 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-12 02:12:07 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-12 02:12:08 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-12 02:12:08 (4259) [INFO] * 2023-10-12 02:12:08 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-12 02:12:08 (4229) [INFO] * 2023-10-12 02:15:41 (4242) [INFO] * 2023-10-12 02:15:41 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-12 02:15:41 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-12 02:15:42 (4259) [INFO] * 2023-10-12 02:15:42 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-12 02:15:42 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-12 02:15:44 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-12 02:15:44 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-12 02:18:33 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-12 02:18:33 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-12 02:18:33 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-12 02:18:33 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-12 02:18:33 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-12 02:18:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-12 02:18:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bEGxk84YVM/ea_profile.json * 2023-10-12 02:18:36 (2293) [INFO] Backed up EA4 profile to /tmp/bEGxk84YVM/ea_profile.json * 2023-10-12 02:18:38 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-13 02:05:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-13 02:05:59 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-13 02:05:59 (1752) [INFO] Checking if your system is up to date: * 2023-10-13 02:05:59 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-13 02:05:59 (4229) [INFO] * 2023-10-13 02:06:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-13 02:06:00 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-13 02:06:00 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-13 02:06:00 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-13 02:06:00 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-13 02:06:00 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-13 02:06:01 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-13 02:06:01 (4259) [INFO] * 2023-10-13 02:06:01 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-13 02:06:01 (4229) [INFO] * 2023-10-13 02:09:17 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" * 2023-10-13 02:09:17 (4242) [INFO] Trying other mirror. * 2023-10-13 02:09:33 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-10-13 02:09:33 (4242) [INFO] Trying other mirror. * 2023-10-13 02:10:21 (4242) [INFO] * 2023-10-13 02:10:21 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-13 02:10:21 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-13 02:10:21 (4259) [INFO] * 2023-10-13 02:10:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-13 02:10:21 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-13 02:10:24 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-13 02:10:24 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-13 02:13:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-13 02:13:46 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-13 02:13:46 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-13 02:13:46 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-13 02:13:46 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-13 02:13:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-13 02:13:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/43MQLML1WU/ea_profile.json * 2023-10-13 02:13:49 (2293) [INFO] Backed up EA4 profile to /tmp/43MQLML1WU/ea_profile.json * 2023-10-13 02:13:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-14 01:58:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-14 01:58:55 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-14 01:58:55 (1752) [INFO] Checking if your system is up to date: * 2023-10-14 01:58:55 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-14 01:58:55 (4229) [INFO] * 2023-10-14 01:58:56 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-14 01:58:56 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-14 01:58:56 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-14 01:58:56 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-14 01:58:56 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-14 01:58:56 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-14 01:58:56 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-14 01:58:56 (4259) [INFO] * 2023-10-14 01:58:56 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-14 01:58:56 (4229) [INFO] * 2023-10-14 02:02:51 (4242) [INFO] * 2023-10-14 02:02:51 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-14 02:02:51 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-14 02:02:52 (4259) [INFO] * 2023-10-14 02:02:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-14 02:02:52 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-14 02:02:55 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-14 02:02:55 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-14 02:06:04 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-14 02:06:04 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-10-14 02:06:04 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-14 02:06:04 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-14 02:06:04 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-14 02:06:05 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-14 02:06:05 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-14 02:06:05 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-14 02:06:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-14 02:06:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qISBzlCgrd/ea_profile.json * 2023-10-14 02:06:07 (2293) [INFO] Backed up EA4 profile to /tmp/qISBzlCgrd/ea_profile.json * 2023-10-14 02:06:11 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-15 02:00:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-15 02:00:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-15 02:00:04 (1752) [INFO] Checking if your system is up to date: * 2023-10-15 02:00:04 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-15 02:00:04 (4229) [INFO] * 2023-10-15 02:00:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-15 02:00:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-15 02:00:05 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-15 02:00:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-15 02:00:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-15 02:00:05 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-15 02:00:05 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-15 02:00:05 (4259) [INFO] * 2023-10-15 02:00:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-15 02:00:05 (4229) [INFO] * 2023-10-15 02:04:18 (4242) [INFO] * 2023-10-15 02:04:18 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-15 02:04:18 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-15 02:04:18 (4259) [INFO] * 2023-10-15 02:04:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-15 02:04:18 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-15 02:04:22 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-15 02:04:22 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-15 02:07:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-15 02:07:51 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-15 02:07:52 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-15 02:07:52 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-15 02:07:52 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-15 02:07:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-15 02:07:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fu9_xMTUpp/ea_profile.json * 2023-10-15 02:07:54 (2293) [INFO] Backed up EA4 profile to /tmp/Fu9_xMTUpp/ea_profile.json * 2023-10-15 02:07:57 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-16 02:03:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-16 02:03:56 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-16 02:03:56 (1752) [INFO] Checking if your system is up to date: * 2023-10-16 02:03:56 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-16 02:03:56 (4229) [INFO] * 2023-10-16 02:03:56 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-16 02:03:56 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-16 02:03:56 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-16 02:03:56 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-16 02:03:56 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-16 02:03:56 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-16 02:03:56 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-16 02:03:56 (4259) [INFO] * 2023-10-16 02:03:56 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-16 02:03:56 (4229) [INFO] * 2023-10-16 02:07:46 (4242) [INFO] * 2023-10-16 02:07:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-16 02:07:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-16 02:07:46 (4259) [INFO] * 2023-10-16 02:07:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-16 02:07:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-16 02:07:49 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-16 02:07:49 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-16 02:11:11 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-16 02:11:11 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-16 02:11:12 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-16 02:11:12 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-16 02:11:12 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-16 02:11:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-16 02:11:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dvHEjQtMyd/ea_profile.json * 2023-10-16 02:11:14 (2293) [INFO] Backed up EA4 profile to /tmp/dvHEjQtMyd/ea_profile.json * 2023-10-16 02:11:17 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-17 02:01:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-17 02:01:15 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-17 02:01:15 (1752) [INFO] Checking if your system is up to date: * 2023-10-17 02:01:15 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-17 02:01:15 (4229) [INFO] * 2023-10-17 02:01:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-17 02:01:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-17 02:01:16 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-17 02:01:16 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-17 02:01:16 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-17 02:01:16 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-17 02:01:16 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-17 02:01:16 (4259) [INFO] * 2023-10-17 02:01:16 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-17 02:01:16 (4229) [INFO] * 2023-10-17 02:05:34 (4242) [INFO] * 2023-10-17 02:05:34 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-17 02:05:34 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-17 02:05:35 (4259) [INFO] * 2023-10-17 02:05:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-17 02:05:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-17 02:05:37 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-17 02:05:37 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-17 02:08:35 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-17 02:08:35 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-17 02:08:36 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-17 02:08:36 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-17 02:08:36 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-17 02:08:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-17 02:08:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xlJx58hTj8/ea_profile.json * 2023-10-17 02:08:38 (2293) [INFO] Backed up EA4 profile to /tmp/xlJx58hTj8/ea_profile.json * 2023-10-17 02:08:41 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-18 02:01:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-18 02:01:47 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-18 02:01:47 (1752) [INFO] Checking if your system is up to date: * 2023-10-18 02:01:47 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-18 02:01:47 (4229) [INFO] * 2023-10-18 02:01:48 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-18 02:01:48 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-18 02:01:48 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-18 02:01:48 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-18 02:01:48 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-18 02:01:48 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-18 02:01:48 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-18 02:01:48 (4259) [INFO] * 2023-10-18 02:01:48 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-18 02:01:48 (4229) [INFO] * 2023-10-18 02:06:07 (4242) [INFO] * 2023-10-18 02:06:07 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-18 02:06:07 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-18 02:06:07 (4259) [INFO] * 2023-10-18 02:06:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-18 02:06:07 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-18 02:06:09 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-18 02:06:09 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-18 02:09:40 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-18 02:09:40 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-18 02:09:40 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-18 02:09:40 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-18 02:09:41 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-18 02:09:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-18 02:09:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tC5iJKGFvn/ea_profile.json * 2023-10-18 02:09:43 (2293) [INFO] Backed up EA4 profile to /tmp/tC5iJKGFvn/ea_profile.json * 2023-10-18 02:09:46 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-19 02:11:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-19 02:11:57 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-19 02:11:57 (1752) [INFO] Checking if your system is up to date: * 2023-10-19 02:11:57 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-19 02:11:57 (4229) [INFO] * 2023-10-19 02:11:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-19 02:11:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-19 02:11:57 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-19 02:11:57 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-19 02:11:57 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-19 02:11:57 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-19 02:11:58 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-19 02:11:58 (4259) [INFO] * 2023-10-19 02:11:58 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-19 02:11:58 (4229) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-19 02:12:52 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-19 02:12:52 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-19 02:12:52 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-19 02:12:52 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-19 02:12:52 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-19 02:12:52 (4242) [INFO] yum --disablerepo= ... * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-19 02:12:52 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-19 02:12:52 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] yum-config-manager --disable * 2023-10-19 02:12:52 (4242) [INFO] or * 2023-10-19 02:12:52 (4242) [INFO] subscription-manager repos --disable= * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-19 02:12:52 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-19 02:12:52 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-19 02:12:52 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-19 02:12:52 (4242) [INFO] compromise: * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-19 02:12:52 (4242) [INFO] * 2023-10-19 02:12:52 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-10-19 02:12:53 (4259) [INFO] * 2023-10-19 02:12:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-19 02:12:53 (1773) [INFO] Checking /scripts/sysup * 2023-10-19 02:12:53 (4228) [INFO] Running: /scripts/sysup * 2023-10-19 02:12:53 (4229) [INFO] * 2023-10-19 02:12:53 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-19 02:12:55 (4242) [INFO] All Needed Packages are already installed. * 2023-10-19 02:12:55 (4259) [INFO] * 2023-10-19 02:12:58 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-19 02:12:58 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-19 02:20:07 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-19 02:20:07 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-19 02:20:08 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-19 02:20:08 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-19 02:20:08 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-19 02:20:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-19 02:20:08 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Sb5NUHm1if/ea_profile.json * 2023-10-19 02:20:10 (2293) [INFO] Backed up EA4 profile to /tmp/Sb5NUHm1if/ea_profile.json * 2023-10-19 02:20:14 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-20 02:04:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-20 02:04:45 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-20 02:04:45 (1752) [INFO] Checking if your system is up to date: * 2023-10-20 02:04:45 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-20 02:04:45 (4229) [INFO] * 2023-10-20 02:04:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-20 02:04:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-20 02:04:46 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-20 02:04:46 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-20 02:04:46 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-20 02:04:46 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-20 02:04:46 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-20 02:04:46 (4259) [INFO] * 2023-10-20 02:04:46 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-20 02:04:46 (4229) [INFO] * 2023-10-20 02:08:59 (4242) [INFO] * 2023-10-20 02:08:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-20 02:08:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-20 02:09:00 (4259) [INFO] * 2023-10-20 02:09:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-20 02:09:00 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-20 02:09:03 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-20 02:09:03 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-20 02:12:20 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-20 02:12:20 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-20 02:12:21 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-20 02:12:21 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-20 02:12:21 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-20 02:12:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-20 02:12:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qZJBbVBNlT/ea_profile.json * 2023-10-20 02:12:23 (2293) [INFO] Backed up EA4 profile to /tmp/qZJBbVBNlT/ea_profile.json * 2023-10-20 02:12:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-21 02:03:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-21 02:03:42 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-21 02:03:42 (1752) [INFO] Checking if your system is up to date: * 2023-10-21 02:03:42 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-21 02:03:42 (4229) [INFO] * 2023-10-21 02:03:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-21 02:03:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-21 02:03:43 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-21 02:03:43 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-21 02:03:43 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-21 02:03:43 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-21 02:03:43 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-21 02:03:43 (4259) [INFO] * 2023-10-21 02:03:43 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-21 02:03:43 (4229) [INFO] * 2023-10-21 02:07:46 (4242) [INFO] * 2023-10-21 02:07:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-21 02:07:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-21 02:07:46 (4259) [INFO] * 2023-10-21 02:07:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-21 02:07:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-21 02:07:50 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-21 02:07:50 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-21 02:10:45 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-21 02:10:45 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-21 02:10:46 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-21 02:10:46 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-21 02:10:46 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-21 02:10:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-21 02:10:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4MrbpuTCQ8/ea_profile.json * 2023-10-21 02:10:49 (2293) [INFO] Backed up EA4 profile to /tmp/4MrbpuTCQ8/ea_profile.json * 2023-10-21 02:10:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-22 02:02:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-22 02:02:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-22 02:02:49 (1752) [INFO] Checking if your system is up to date: * 2023-10-22 02:02:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-22 02:02:49 (4229) [INFO] * 2023-10-22 02:02:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-22 02:02:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-22 02:02:49 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-22 02:02:49 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-22 02:02:49 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-22 02:02:49 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-22 02:02:50 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-22 02:02:50 (4259) [INFO] * 2023-10-22 02:02:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-22 02:02:50 (4229) [INFO] * 2023-10-22 02:07:18 (4242) [INFO] * 2023-10-22 02:07:18 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-22 02:07:18 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-22 02:07:18 (4259) [INFO] * 2023-10-22 02:07:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-22 02:07:18 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-22 02:07:22 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-22 02:07:22 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-22 02:10:53 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-22 02:10:53 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-22 02:10:54 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-22 02:10:54 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-22 02:10:54 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-22 02:10:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-22 02:10:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nx2rvdQmMZ/ea_profile.json * 2023-10-22 02:10:56 (2293) [INFO] Backed up EA4 profile to /tmp/nx2rvdQmMZ/ea_profile.json * 2023-10-22 02:11:00 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-23 02:01:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-23 02:01:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-23 02:01:14 (1752) [INFO] Checking if your system is up to date: * 2023-10-23 02:01:14 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-23 02:01:14 (4229) [INFO] * 2023-10-23 02:01:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-23 02:01:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-23 02:01:14 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-23 02:01:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-23 02:01:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-23 02:01:14 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-23 02:01:15 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-23 02:01:15 (4259) [INFO] * 2023-10-23 02:01:15 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-23 02:01:15 (4229) [INFO] * 2023-10-23 02:04:38 (4242) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/ae69a9e1c0be9bb44fed4ac09813c202abdc9714bb747ad1e706226bd671c992-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-10-23 02:04:38 (4242) [INFO] Trying other mirror. * 2023-10-23 02:04:38 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-10-23 02:04:38 (4242) [INFO] * 2023-10-23 02:04:38 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-10-23 02:04:38 (4242) [INFO] * 2023-10-23 02:04:38 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-10-23 02:04:38 (4242) [INFO] * 2023-10-23 02:05:38 (4242) [INFO] * 2023-10-23 02:05:38 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-23 02:05:38 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-23 02:05:38 (4259) [INFO] * 2023-10-23 02:05:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-23 02:05:38 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-23 02:05:41 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-23 02:05:41 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-23 02:09:24 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-23 02:09:24 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-23 02:09:25 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-23 02:09:25 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-23 02:09:25 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-23 02:09:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-23 02:09:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4GZVx_4hOw/ea_profile.json * 2023-10-23 02:09:27 (2293) [INFO] Backed up EA4 profile to /tmp/4GZVx_4hOw/ea_profile.json * 2023-10-23 02:09:30 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-24 01:59:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-24 01:59:44 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-24 01:59:44 (1752) [INFO] Checking if your system is up to date: * 2023-10-24 01:59:44 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-24 01:59:44 (4229) [INFO] * 2023-10-24 01:59:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-24 01:59:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-24 01:59:44 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-24 01:59:44 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-24 01:59:44 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-24 01:59:44 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-24 01:59:45 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-24 01:59:45 (4259) [INFO] * 2023-10-24 01:59:45 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-24 01:59:45 (4229) [INFO] * 2023-10-24 02:03:40 (4242) [INFO] * 2023-10-24 02:03:40 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-24 02:03:40 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-24 02:03:41 (4259) [INFO] * 2023-10-24 02:03:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-24 02:03:41 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-24 02:03:43 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-24 02:03:43 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-24 02:06:43 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-24 02:06:43 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-24 02:06:43 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-24 02:06:43 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-24 02:06:43 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-24 02:06:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-24 02:06:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/77TR7ZLP2I/ea_profile.json * 2023-10-24 02:06:45 (2293) [INFO] Backed up EA4 profile to /tmp/77TR7ZLP2I/ea_profile.json * 2023-10-24 02:06:47 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-25 02:02:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-25 02:02:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-25 02:02:22 (1752) [INFO] Checking if your system is up to date: * 2023-10-25 02:02:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-25 02:02:22 (4229) [INFO] * 2023-10-25 02:02:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-25 02:02:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-25 02:02:23 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-25 02:02:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-25 02:02:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-25 02:02:23 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-25 02:02:23 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-25 02:02:23 (4259) [INFO] * 2023-10-25 02:02:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-25 02:02:23 (4229) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-25 02:03:18 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-25 02:03:18 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-25 02:03:18 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-25 02:03:18 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-25 02:03:18 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-25 02:03:18 (4242) [INFO] yum --disablerepo= ... * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-25 02:03:18 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-25 02:03:18 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] yum-config-manager --disable * 2023-10-25 02:03:18 (4242) [INFO] or * 2023-10-25 02:03:18 (4242) [INFO] subscription-manager repos --disable= * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-25 02:03:18 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-25 02:03:18 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-25 02:03:18 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-25 02:03:18 (4242) [INFO] compromise: * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-25 02:03:18 (4242) [INFO] * 2023-10-25 02:03:18 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-10-25 02:03:18 (4259) [INFO] * 2023-10-25 02:03:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-25 02:03:18 (1773) [INFO] Checking /scripts/sysup * 2023-10-25 02:03:18 (4228) [INFO] Running: /scripts/sysup * 2023-10-25 02:03:18 (4229) [INFO] * 2023-10-25 02:03:19 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-25 02:03:21 (4242) [INFO] All Needed Packages are already installed. * 2023-10-25 02:03:21 (4259) [INFO] * 2023-10-25 02:03:24 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-25 02:03:24 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-25 02:09:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-25 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-25 02:09:51 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-25 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-25 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-25 02:09:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-25 02:09:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DCLunm_seT/ea_profile.json * 2023-10-25 02:09:53 (2293) [INFO] Backed up EA4 profile to /tmp/DCLunm_seT/ea_profile.json * 2023-10-25 02:09:55 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-26 02:00:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-26 02:01:01 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-26 02:01:01 (1752) [INFO] Checking if your system is up to date: * 2023-10-26 02:01:01 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-26 02:01:01 (4229) [INFO] * 2023-10-26 02:01:01 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-26 02:01:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-26 02:01:02 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-26 02:01:02 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-26 02:01:02 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-26 02:01:02 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-26 02:01:02 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-26 02:01:02 (4259) [INFO] * 2023-10-26 02:01:02 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-26 02:01:02 (4229) [INFO] * 2023-10-26 02:05:17 (4242) [INFO] * 2023-10-26 02:05:17 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-26 02:05:17 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-26 02:05:18 (4259) [INFO] * 2023-10-26 02:05:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-26 02:05:18 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-26 02:05:21 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-26 02:05:21 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-26 02:08:40 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-26 02:08:40 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-26 02:08:40 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-26 02:08:40 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-26 02:08:40 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-26 02:08:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-26 02:08:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DRiP3F55Pr/ea_profile.json * 2023-10-26 02:08:43 (2293) [INFO] Backed up EA4 profile to /tmp/DRiP3F55Pr/ea_profile.json * 2023-10-26 02:08:47 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-27 02:14:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-27 02:14:46 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-27 02:14:46 (1752) [INFO] Checking if your system is up to date: * 2023-10-27 02:14:46 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-27 02:14:46 (4229) [INFO] * 2023-10-27 02:14:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-27 02:14:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-27 02:14:47 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-27 02:14:47 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-27 02:14:47 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-27 02:14:47 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-27 02:14:48 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-27 02:14:48 (4259) [INFO] * 2023-10-27 02:14:48 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-27 02:14:48 (4229) [INFO] * 2023-10-27 02:18:58 (4242) [INFO] * 2023-10-27 02:18:58 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-27 02:18:58 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-27 02:18:58 (4259) [INFO] * 2023-10-27 02:18:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-27 02:18:58 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-27 02:19:01 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-27 02:19:01 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-27 02:22:24 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-27 02:22:24 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-27 02:22:24 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-27 02:22:24 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-27 02:22:24 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-27 02:22:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-27 02:22:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oCjeqMw6tD/ea_profile.json * 2023-10-27 02:22:26 (2293) [INFO] Backed up EA4 profile to /tmp/oCjeqMw6tD/ea_profile.json * 2023-10-27 02:22:30 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-28 02:07:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-28 02:07:42 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-28 02:07:42 (1752) [INFO] Checking if your system is up to date: * 2023-10-28 02:07:42 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-28 02:07:42 (4229) [INFO] * 2023-10-28 02:07:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-28 02:07:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-28 02:07:43 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-28 02:07:43 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-28 02:07:43 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-28 02:07:43 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-28 02:07:43 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-28 02:07:44 (4259) [INFO] * 2023-10-28 02:07:44 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-28 02:07:44 (4229) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-10-28 02:08:39 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-10-28 02:08:39 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-10-28 02:08:39 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-10-28 02:08:39 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-10-28 02:08:39 (4242) [INFO] packages for the previous distribution release still work). * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-10-28 02:08:39 (4242) [INFO] yum --disablerepo= ... * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-10-28 02:08:39 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-10-28 02:08:39 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] yum-config-manager --disable * 2023-10-28 02:08:39 (4242) [INFO] or * 2023-10-28 02:08:39 (4242) [INFO] subscription-manager repos --disable= * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-10-28 02:08:39 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-10-28 02:08:39 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-10-28 02:08:39 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-10-28 02:08:39 (4242) [INFO] compromise: * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-10-28 02:08:39 (4242) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-10-28 02:08:39 (4259) [INFO] * 2023-10-28 02:08:39 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-28 02:08:39 (1773) [INFO] Checking /scripts/sysup * 2023-10-28 02:08:39 (4228) [INFO] Running: /scripts/sysup * 2023-10-28 02:08:39 (4229) [INFO] * 2023-10-28 02:08:39 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-10-28 02:08:42 (4242) [INFO] All Needed Packages are already installed. * 2023-10-28 02:08:42 (4259) [INFO] * 2023-10-28 02:08:45 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-28 02:08:45 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-28 02:17:15 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-28 02:17:15 (1619) [ERROR] http://mirrors.xtom.com/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/53c25d614946de9fa70c240f5506068ae4f3ebf0bc14a70dccd970e981aa8a3a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xmission.com/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xmission.com/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.keystealth.org/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux.mirrors.es.net/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://or-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo.ialab.dsu.edu/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://distro.ibiblio.org/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rit.edu/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.nodesdirect.com/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.us-midwest-1.nexcess.net/CentOS/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://southfront.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://southfront.mm.fcix.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://veronanetworks.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ziply.mm.fcix.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.steadfastnet.com/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ohioix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/8a7a425420040427172229ca4a1fd3dcb4396f8a2812760b23dcf69a68aa92b6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable 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 extras: Check uncompressed DB failed * 2023-10-28 02:17:15 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-28 02:17:15 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-28 02:17:15 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-28 02:17:16 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-28 02:17:16 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-28 02:17:16 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-28 02:17:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-28 02:17:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qoAnx6Zolx/ea_profile.json * 2023-10-28 02:20:15 (2293) [INFO] Backed up EA4 profile to /tmp/qoAnx6Zolx/ea_profile.json * 2023-10-28 02:20:19 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-29 02:03:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-29 02:03:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-29 02:03:22 (1752) [INFO] Checking if your system is up to date: * 2023-10-29 02:03:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-29 02:03:22 (4229) [INFO] * 2023-10-29 02:03:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-29 02:03:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-29 02:03:23 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-29 02:03:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-29 02:03:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-29 02:03:23 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-29 02:03:23 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-29 02:03:23 (4259) [INFO] * 2023-10-29 02:03:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-29 02:03:23 (4229) [INFO] * 2023-10-29 02:07:44 (4242) [INFO] * 2023-10-29 02:07:44 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-29 02:07:44 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-29 02:07:45 (4259) [INFO] * 2023-10-29 02:07:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-29 02:07:45 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-29 02:07:48 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-29 02:07:48 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-29 02:11:39 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-29 02:11:39 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-29 02:11:39 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-29 02:11:39 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-29 02:11:39 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-29 02:11:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-29 02:11:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gw08X3Pa3U/ea_profile.json * 2023-10-29 02:11:42 (2293) [INFO] Backed up EA4 profile to /tmp/gw08X3Pa3U/ea_profile.json * 2023-10-29 02:11:45 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-30 01:54:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-30 01:54:38 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-30 01:54:38 (1752) [INFO] Checking if your system is up to date: * 2023-10-30 01:54:38 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-30 01:54:38 (4229) [INFO] * 2023-10-30 01:54:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-30 01:54:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-30 01:54:39 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-30 01:54:39 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-30 01:54:39 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-30 01:54:39 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-30 01:54:39 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-30 01:54:39 (4259) [INFO] * 2023-10-30 01:54:39 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-30 01:54:39 (4229) [INFO] * 2023-10-30 01:58:45 (4242) [INFO] * 2023-10-30 01:58:45 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-30 01:58:45 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-30 01:58:45 (4259) [INFO] * 2023-10-30 01:58:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-30 01:58:45 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-30 01:58:49 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-30 01:58:49 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-30 02:02:17 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-10-30 02:02:17 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30595 milliseconds') * 2023-10-30 02:02:17 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-10-30 02:02:17 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-30 02:02:17 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-30 02:02:18 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-30 02:02:18 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-30 02:02:18 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-30 02:02:18 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-30 02:02:18 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/by0H7MAs0j/ea_profile.json * 2023-10-30 02:02:20 (2293) [INFO] Backed up EA4 profile to /tmp/by0H7MAs0j/ea_profile.json * 2023-10-30 02:02:23 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-31 01:58:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-10-31 01:58:30 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-31 01:58:30 (1752) [INFO] Checking if your system is up to date: * 2023-10-31 01:58:30 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-31 01:58:30 (4229) [INFO] * 2023-10-31 01:58:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-31 01:58:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-10-31 01:58:31 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-31 01:58:31 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-31 01:58:31 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-31 01:58:31 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-10-31 01:58:31 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-10-31 01:58:31 (4259) [INFO] * 2023-10-31 01:58:31 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-31 01:58:31 (4229) [INFO] * 2023-10-31 02:02:54 (4242) [INFO] * 2023-10-31 02:02:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-31 02:02:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-31 02:02:54 (4259) [INFO] * 2023-10-31 02:02:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-31 02:02:54 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-31 02:02:57 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-10-31 02:02:57 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-10-31 02:06:26 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-10-31 02:06:26 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-10-31 02:06:27 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-10-31 02:06:27 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-10-31 02:06:27 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-10-31 02:06:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-31 02:06:27 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gbUbeBaj9f/ea_profile.json * 2023-10-31 02:06:29 (2293) [INFO] Backed up EA4 profile to /tmp/gbUbeBaj9f/ea_profile.json * 2023-10-31 02:06:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-01 01:55:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-01 01:55:12 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-01 01:55:12 (1752) [INFO] Checking if your system is up to date: * 2023-11-01 01:55:12 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-01 01:55:12 (4229) [INFO] * 2023-11-01 01:55:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-01 01:55:13 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-01 01:55:13 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-01 01:55:13 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-01 01:55:13 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-01 01:55:13 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-01 01:55:13 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-01 01:55:13 (4259) [INFO] * 2023-11-01 01:55:13 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-01 01:55:13 (4229) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-01 01:56:08 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-01 01:56:08 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-01 01:56:08 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-01 01:56:08 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-01 01:56:08 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-01 01:56:08 (4242) [INFO] yum --disablerepo= ... * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-01 01:56:08 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-01 01:56:08 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] yum-config-manager --disable * 2023-11-01 01:56:08 (4242) [INFO] or * 2023-11-01 01:56:08 (4242) [INFO] subscription-manager repos --disable= * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-01 01:56:08 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-01 01:56:08 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-01 01:56:08 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-01 01:56:08 (4242) [INFO] compromise: * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-01 01:56:08 (4242) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-01 01:56:08 (4259) [INFO] * 2023-11-01 01:56:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-01 01:56:08 (1773) [INFO] Checking /scripts/sysup * 2023-11-01 01:56:08 (4228) [INFO] Running: /scripts/sysup * 2023-11-01 01:56:08 (4229) [INFO] * 2023-11-01 01:56:08 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-01 01:56:11 (4242) [INFO] All Needed Packages are already installed. * 2023-11-01 01:56:11 (4259) [INFO] * 2023-11-01 01:56:14 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-01 01:56:14 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-01 02:02:58 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-01 02:02:58 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-01 02:02:58 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-01 02:02:58 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-01 02:02:58 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-01 02:02:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-01 02:02:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GdmRY1Fxi0/ea_profile.json * 2023-11-01 02:03:00 (2293) [INFO] Backed up EA4 profile to /tmp/GdmRY1Fxi0/ea_profile.json * 2023-11-01 02:03:03 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-02 01:56:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-02 01:56:39 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-02 01:56:39 (1752) [INFO] Checking if your system is up to date: * 2023-11-02 01:56:39 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-02 01:56:39 (4229) [INFO] * 2023-11-02 01:56:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-02 01:56:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-02 01:56:39 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-02 01:56:39 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-02 01:56:39 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-02 01:56:39 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-02 01:56:39 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-02 01:56:39 (4259) [INFO] * 2023-11-02 01:56:39 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-02 01:56:39 (4229) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-02 01:57:34 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-02 01:57:34 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-02 01:57:34 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-02 01:57:34 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-02 01:57:34 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-02 01:57:34 (4242) [INFO] yum --disablerepo= ... * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-02 01:57:34 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-02 01:57:34 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] yum-config-manager --disable * 2023-11-02 01:57:34 (4242) [INFO] or * 2023-11-02 01:57:34 (4242) [INFO] subscription-manager repos --disable= * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-02 01:57:34 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-02 01:57:34 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-02 01:57:34 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-02 01:57:34 (4242) [INFO] compromise: * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-02 01:57:34 (4242) [INFO] * 2023-11-02 01:57:34 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-02 01:57:34 (4259) [INFO] * 2023-11-02 01:57:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-02 01:57:34 (1773) [INFO] Checking /scripts/sysup * 2023-11-02 01:57:34 (4228) [INFO] Running: /scripts/sysup * 2023-11-02 01:57:34 (4229) [INFO] * 2023-11-02 01:57:35 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-02 01:57:37 (4242) [INFO] All Needed Packages are already installed. * 2023-11-02 01:57:37 (4259) [INFO] * 2023-11-02 01:57:40 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-02 01:57:40 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-02 02:13:51 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-02 02:13:51 (1619) [ERROR] http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/17e897ceb46e0f3f437721ccf2ed53bdce3e625d6dd4afe6d06d00d7958a4b20-filelists.sqlite.bz2: [Errno 14] curl#18 - "transfer closed with 7975124 bytes remaining to read" Trying other mirror. * 2023-11-02 02:13:51 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-02 02:13:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-02 02:13:51 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-02 02:13:52 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-02 02:13:52 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-02 02:13:52 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-02 02:13:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-02 02:13:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ke_0iwEGP7/ea_profile.json * 2023-11-02 02:13:53 (2293) [INFO] Backed up EA4 profile to /tmp/ke_0iwEGP7/ea_profile.json * 2023-11-02 02:13:57 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-03 02:00:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-03 02:00:57 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-03 02:00:57 (1752) [INFO] Checking if your system is up to date: * 2023-11-03 02:00:57 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-03 02:00:57 (4229) [INFO] * 2023-11-03 02:00:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-03 02:00:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-03 02:00:57 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-03 02:00:57 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-03 02:00:57 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-03 02:00:57 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-03 02:00:57 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-03 02:00:57 (4259) [INFO] * 2023-11-03 02:00:57 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-03 02:00:57 (4229) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-03 02:01:52 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-03 02:01:52 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-03 02:01:52 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-03 02:01:52 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-03 02:01:52 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-03 02:01:52 (4242) [INFO] yum --disablerepo= ... * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-03 02:01:52 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-03 02:01:52 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] yum-config-manager --disable * 2023-11-03 02:01:52 (4242) [INFO] or * 2023-11-03 02:01:52 (4242) [INFO] subscription-manager repos --disable= * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-03 02:01:52 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-03 02:01:52 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-03 02:01:52 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-03 02:01:52 (4242) [INFO] compromise: * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-03 02:01:52 (4242) [INFO] * 2023-11-03 02:01:52 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-03 02:01:52 (4259) [INFO] * 2023-11-03 02:01:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-03 02:01:52 (1773) [INFO] Checking /scripts/sysup * 2023-11-03 02:01:52 (4228) [INFO] Running: /scripts/sysup * 2023-11-03 02:01:52 (4229) [INFO] * 2023-11-03 02:01:53 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-03 02:01:55 (4242) [INFO] All Needed Packages are already installed. * 2023-11-03 02:01:55 (4259) [INFO] * 2023-11-03 02:01:58 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-03 02:01:58 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-03 02:08:44 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-03 02:08:44 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-03 02:08:45 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-03 02:08:45 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-03 02:08:45 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-03 02:08:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-03 02:08:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rwEQRDoK9S/ea_profile.json * 2023-11-03 02:08:47 (2293) [INFO] Backed up EA4 profile to /tmp/rwEQRDoK9S/ea_profile.json * 2023-11-03 02:08:50 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-04 02:04:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-04 02:04:30 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-04 02:04:30 (1752) [INFO] Checking if your system is up to date: * 2023-11-04 02:04:30 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-04 02:04:30 (4229) [INFO] * 2023-11-04 02:04:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-04 02:04:30 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-04 02:04:30 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-04 02:04:30 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-04 02:04:30 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-04 02:04:30 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-04 02:04:31 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-04 02:04:31 (4259) [INFO] * 2023-11-04 02:04:31 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-04 02:04:31 (4229) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-04 02:05:26 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-04 02:05:26 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-04 02:05:26 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-04 02:05:26 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-04 02:05:26 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-04 02:05:26 (4242) [INFO] yum --disablerepo= ... * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-04 02:05:26 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-04 02:05:26 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] yum-config-manager --disable * 2023-11-04 02:05:26 (4242) [INFO] or * 2023-11-04 02:05:26 (4242) [INFO] subscription-manager repos --disable= * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-04 02:05:26 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-04 02:05:26 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-04 02:05:26 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-04 02:05:26 (4242) [INFO] compromise: * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-04 02:05:26 (4242) [INFO] * 2023-11-04 02:05:26 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-04 02:05:26 (4259) [INFO] * 2023-11-04 02:05:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-04 02:05:26 (1773) [INFO] Checking /scripts/sysup * 2023-11-04 02:05:26 (4228) [INFO] Running: /scripts/sysup * 2023-11-04 02:05:26 (4229) [INFO] * 2023-11-04 02:05:27 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-04 02:05:29 (4242) [INFO] All Needed Packages are already installed. * 2023-11-04 02:05:29 (4259) [INFO] * 2023-11-04 02:05:33 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-04 02:05:33 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-04 02:06:27 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-04 02:06:27 (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-04 02:06:27 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-04 02:06:27 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-04 02:06:27 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-04 02:06:28 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-04 02:06:28 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-04 02:06:28 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-04 02:06:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-04 02:06:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RXcrmoxBhS/ea_profile.json * 2023-11-04 02:12:24 (2293) [INFO] Backed up EA4 profile to /tmp/RXcrmoxBhS/ea_profile.json * 2023-11-04 02:12:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-05 01:55:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-05 01:55:57 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-05 01:55:57 (1752) [INFO] Checking if your system is up to date: * 2023-11-05 01:55:57 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-05 01:55:57 (4229) [INFO] * 2023-11-05 01:55:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-05 01:55:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-05 01:55:57 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-05 01:55:57 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-05 01:55:57 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-05 01:55:57 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-05 01:55:57 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-05 01:55:57 (4259) [INFO] * 2023-11-05 01:55:57 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-05 01:55:57 (4229) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-05 01:56:52 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-05 01:56:52 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-05 01:56:52 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-05 01:56:52 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-05 01:56:52 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-05 01:56:52 (4242) [INFO] yum --disablerepo= ... * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-05 01:56:52 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-05 01:56:52 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] yum-config-manager --disable * 2023-11-05 01:56:52 (4242) [INFO] or * 2023-11-05 01:56:52 (4242) [INFO] subscription-manager repos --disable= * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-05 01:56:52 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-05 01:56:52 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-05 01:56:52 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-05 01:56:52 (4242) [INFO] compromise: * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-05 01:56:52 (4242) [INFO] * 2023-11-05 01:56:52 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-05 01:56:52 (4259) [INFO] * 2023-11-05 01:56:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-05 01:56:52 (1773) [INFO] Checking /scripts/sysup * 2023-11-05 01:56:52 (4228) [INFO] Running: /scripts/sysup * 2023-11-05 01:56:52 (4229) [INFO] * 2023-11-05 01:56:53 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-05 01:56:55 (4242) [INFO] All Needed Packages are already installed. * 2023-11-05 01:56:55 (4259) [INFO] * 2023-11-05 01:56:58 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-05 01:56:58 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-05 01:03:44 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-05 01:03:44 (1619) [ERROR] http://mirror.math.princeton.edu/pub/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on http://mirror.math.princeton.edu/pub/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30001 milliseconds') Trying other mirror. * 2023-11-05 01:03:44 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-05 01:03:44 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-05 01:03:44 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-05 01:03:45 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-05 01:03:45 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-05 01:03:45 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-05 01:03:45 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-05 01:03:45 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8w4Gd_NXSV/ea_profile.json * 2023-11-05 01:03:46 (2293) [INFO] Backed up EA4 profile to /tmp/8w4Gd_NXSV/ea_profile.json * 2023-11-05 01:03:49 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-06 02:02:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-06 02:02:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-06 02:02:04 (1752) [INFO] Checking if your system is up to date: * 2023-11-06 02:02:04 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-06 02:02:04 (4229) [INFO] * 2023-11-06 02:02:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-06 02:02:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-06 02:02:04 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-06 02:02:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-06 02:02:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-06 02:02:04 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-06 02:02:05 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-06 02:02:05 (4259) [INFO] * 2023-11-06 02:02:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-06 02:02:05 (4229) [INFO] * 2023-11-06 02:06:20 (4242) [INFO] * 2023-11-06 02:06:20 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-06 02:06:20 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-06 02:06:21 (4259) [INFO] * 2023-11-06 02:06:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-06 02:06:21 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-06 02:06:22 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-06 02:06:22 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-06 02:09:51 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-06 02:09:51 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-06 02:09:52 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-06 02:09:52 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-06 02:09:52 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-06 02:09:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-06 02:09:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vqqmYenQfT/ea_profile.json * 2023-11-06 02:09:53 (2293) [INFO] Backed up EA4 profile to /tmp/vqqmYenQfT/ea_profile.json * 2023-11-06 02:09:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-07 01:58:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-07 01:58:53 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-07 01:58:53 (1752) [INFO] Checking if your system is up to date: * 2023-11-07 01:58:53 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-07 01:58:53 (4229) [INFO] * 2023-11-07 01:58:53 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-07 01:58:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-07 01:58:54 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-07 01:58:54 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-07 01:58:54 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-07 01:58:54 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-07 01:58:54 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-07 01:58:54 (4259) [INFO] * 2023-11-07 01:58:54 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-07 01:58:54 (4229) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-07 01:59:48 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-07 01:59:48 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-07 01:59:48 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-07 01:59:48 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-07 01:59:48 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-07 01:59:48 (4242) [INFO] yum --disablerepo= ... * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-07 01:59:48 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-07 01:59:48 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] yum-config-manager --disable * 2023-11-07 01:59:48 (4242) [INFO] or * 2023-11-07 01:59:48 (4242) [INFO] subscription-manager repos --disable= * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-07 01:59:48 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-07 01:59:48 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-07 01:59:48 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-07 01:59:48 (4242) [INFO] compromise: * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-07 01:59:48 (4242) [INFO] * 2023-11-07 01:59:48 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-07 01:59:48 (4259) [INFO] * 2023-11-07 01:59:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-07 01:59:48 (1773) [INFO] Checking /scripts/sysup * 2023-11-07 01:59:48 (4228) [INFO] Running: /scripts/sysup * 2023-11-07 01:59:48 (4229) [INFO] * 2023-11-07 01:59:49 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-07 01:59:51 (4242) [INFO] All Needed Packages are already installed. * 2023-11-07 01:59:51 (4259) [INFO] * 2023-11-07 01:59:54 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-07 01:59:54 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-07 02:08:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-07 02:08:10 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-07 02:08:11 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-07 02:08:11 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-07 02:08:11 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-07 02:08:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-07 02:08:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oHyDPdjwGJ/ea_profile.json * 2023-11-07 02:08:14 (2293) [INFO] Backed up EA4 profile to /tmp/oHyDPdjwGJ/ea_profile.json * 2023-11-07 02:08:17 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-08 01:54:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-08 01:54:42 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-08 01:54:42 (1752) [INFO] Checking if your system is up to date: * 2023-11-08 01:54:42 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-08 01:54:42 (4229) [INFO] * 2023-11-08 01:54:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-08 01:54:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-08 01:54:43 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-08 01:54:43 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-08 01:54:43 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-08 01:54:43 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-08 01:54:44 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-08 01:54:44 (4259) [INFO] * 2023-11-08 01:54:44 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-08 01:54:44 (4229) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-08 01:55:40 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-08 01:55:40 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-08 01:55:40 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-08 01:55:40 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-08 01:55:40 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-08 01:55:40 (4242) [INFO] yum --disablerepo= ... * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-08 01:55:40 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-08 01:55:40 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] yum-config-manager --disable * 2023-11-08 01:55:40 (4242) [INFO] or * 2023-11-08 01:55:40 (4242) [INFO] subscription-manager repos --disable= * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-08 01:55:40 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-08 01:55:40 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-08 01:55:40 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-08 01:55:40 (4242) [INFO] compromise: * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-08 01:55:40 (4242) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-08 01:55:40 (4259) [INFO] * 2023-11-08 01:55:40 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-08 01:55:40 (1773) [INFO] Checking /scripts/sysup * 2023-11-08 01:55:40 (4228) [INFO] Running: /scripts/sysup * 2023-11-08 01:55:40 (4229) [INFO] * 2023-11-08 01:55:40 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-08 01:55:42 (4242) [INFO] All Needed Packages are already installed. * 2023-11-08 01:55:42 (4259) [INFO] * 2023-11-08 01:55:44 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-08 01:55:44 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-08 02:03:15 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-08 02:03:15 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-08 02:03:16 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-08 02:03:16 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-08 02:03:16 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-08 02:03:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-08 02:03:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EU3Pgduo_e/ea_profile.json * 2023-11-08 02:03:17 (2293) [INFO] Backed up EA4 profile to /tmp/EU3Pgduo_e/ea_profile.json * 2023-11-08 02:03:20 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-09 02:09:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-09 02:09:37 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-09 02:09:37 (1752) [INFO] Checking if your system is up to date: * 2023-11-09 02:09:37 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-09 02:09:37 (4229) [INFO] * 2023-11-09 02:09:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-09 02:09:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-09 02:09:37 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-09 02:09:37 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-09 02:09:37 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-09 02:09:37 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-09 02:09:37 (4242) [INFO] Other repos take up 784 k of disk space (use --verbose for details) * 2023-11-09 02:09:37 (4259) [INFO] * 2023-11-09 02:09:37 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-09 02:09:37 (4229) [INFO] * 2023-11-09 02:11:59 (4242) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/748f422618d1cf4753622efb58005e55a0412282a1a3db57c5e5d9f3a248c2ad-comps-Everything.x86_64.xml.gz: [Errno -1] Metadata file does not match checksum * 2023-11-09 02:11:59 (4242) [INFO] Trying other mirror. * 2023-11-09 02:11:59 (4242) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:11:59 (4242) [INFO] Trying other mirror. * 2023-11-09 02:11:59 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/47688c54b5eff305368e26641ae78b4cf783251364720a5a1748cd88b605877e-updateinfo.xml.bz2: [Errno -1] Metadata file does not match checksum * 2023-11-09 02:11:59 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:00 (4242) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:00 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:15 (4242) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:15 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:16 (4242) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-11-09 02:12:16 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:16 (4242) [INFO] To address this issue please refer to the below wiki article * 2023-11-09 02:12:16 (4242) [INFO] * 2023-11-09 02:12:16 (4242) [INFO] https://wiki.centos.org/yum-errors * 2023-11-09 02:12:16 (4242) [INFO] * 2023-11-09 02:12:16 (4242) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-11-09 02:12:16 (4242) [INFO] * 2023-11-09 02:12:16 (4242) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:16 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:32 (4242) [INFO] https://mirror.servaxnet.com/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:32 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:33 (4242) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:33 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:33 (4242) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:33 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:49 (4242) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:49 (4242) [INFO] Trying other mirror. * 2023-11-09 02:12:50 (4242) [INFO] https://repo.ialab.dsu.edu/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:12:50 (4242) [INFO] Trying other mirror. * 2023-11-09 02:13:06 (4242) [INFO] https://mirror.usi.edu/pub/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:13:06 (4242) [INFO] Trying other mirror. * 2023-11-09 02:13:21 (4242) [INFO] https://mirror.csclub.uwaterloo.ca/fedora/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:13:21 (4242) [INFO] Trying other mirror. * 2023-11-09 02:13:37 (4242) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-11-09 02:13:37 (4242) [INFO] Trying other mirror. * 2023-11-09 02:13:38 (4242) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:13:38 (4242) [INFO] Trying other mirror. * 2023-11-09 02:13:54 (4242) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:13:54 (4242) [INFO] Trying other mirror. * 2023-11-09 02:14:09 (4242) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:14:09 (4242) [INFO] Trying other mirror. * 2023-11-09 02:14:25 (4242) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:14:25 (4242) [INFO] Trying other mirror. * 2023-11-09 02:14:40 (4242) [INFO] https://epel.mirror.shastacoe.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-11-09 02:14:40 (4242) [INFO] Trying other mirror. * 2023-11-09 02:14:56 (4242) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:14:56 (4242) [INFO] Trying other mirror. * 2023-11-09 02:14:56 (4242) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:14:56 (4242) [INFO] Trying other mirror. * 2023-11-09 02:15:12 (4242) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:15:12 (4242) [INFO] Trying other mirror. * 2023-11-09 02:15:28 (4242) [INFO] https://ftp-chi.osuosl.org/pub/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:15:28 (4242) [INFO] Trying other mirror. * 2023-11-09 02:15:43 (4242) [INFO] https://nullroute.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:15:43 (4242) [INFO] Trying other mirror. * 2023-11-09 02:15:59 (4242) [INFO] https://atl.mirrors.knownhost.com/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:15:59 (4242) [INFO] Trying other mirror. * 2023-11-09 02:16:15 (4242) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:16:15 (4242) [INFO] Trying other mirror. * 2023-11-09 02:16:30 (4242) [INFO] https://irltoolkit.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:16:30 (4242) [INFO] Trying other mirror. * 2023-11-09 02:16:46 (4242) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:16:46 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:01 (4242) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:17:01 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:17 (4242) [INFO] https://bungi.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-11-09 02:17:17 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:33 (4242) [INFO] https://mnvoip.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:17:33 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:48 (4242) [INFO] https://nocix.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:17:48 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:49 (4242) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:17:49 (4242) [INFO] Trying other mirror. * 2023-11-09 02:17:50 (4242) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:17:50 (4242) [INFO] Trying other mirror. * 2023-11-09 02:18:06 (4242) [INFO] https://na.edge.kernel.org/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:18:06 (4242) [INFO] Trying other mirror. * 2023-11-09 02:18:21 (4242) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:18:21 (4242) [INFO] Trying other mirror. * 2023-11-09 02:18:51 (4242) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2023-11-09 02:18:51 (4242) [INFO] Trying other mirror. * 2023-11-09 02:18:52 (4242) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:18:52 (4242) [INFO] Trying other mirror. * 2023-11-09 02:19:08 (4242) [INFO] https://muug.ca/mirror/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:19:08 (4242) [INFO] Trying other mirror. * 2023-11-09 02:19:23 (4242) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:19:23 (4242) [INFO] Trying other mirror. * 2023-11-09 02:19:23 (4242) [INFO] http://mirrors.vcea.wsu.edu/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2023-11-09 02:19:23 (4242) [INFO] Trying other mirror. * 2023-11-09 02:19:39 (4242) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:19:39 (4242) [INFO] Trying other mirror. * 2023-11-09 02:19:55 (4242) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:19:55 (4242) [INFO] Trying other mirror. * 2023-11-09 02:20:10 (4242) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:20:10 (4242) [INFO] Trying other mirror. * 2023-11-09 02:20:26 (4242) [INFO] https://veronanetworks.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:20:26 (4242) [INFO] Trying other mirror. * 2023-11-09 02:20:41 (4242) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:20:41 (4242) [INFO] Trying other mirror. * 2023-11-09 02:20:57 (4242) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:20:57 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:12 (4242) [INFO] https://ohioix.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:12 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:13 (4242) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:13 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:28 (4242) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:28 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:44 (4242) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:44 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:44 (4242) [INFO] https://ridgewireless.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:44 (4242) [INFO] Trying other mirror. * 2023-11-09 02:21:45 (4242) [INFO] https://volico.mm.fcix.net/epel/7/x86_64/repodata/84c7ba863e165a56e8930fca59e582a20be06a449f84a63d78e0401aad1fc6ed-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-11-09 02:21:45 (4242) [INFO] Trying other mirror. * 2023-11-09 02:22:09 (4242) [INFO] * 2023-11-09 02:22:09 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-09 02:22:09 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-09 02:22:09 (4259) [INFO] * 2023-11-09 02:22:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-09 02:22:09 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-09 02:22:12 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-09 02:22:12 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-09 02:25:56 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-09 02:25:56 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30557 milliseconds') * 2023-11-09 02:25:56 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-09 02:25:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-09 02:25:56 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-09 02:25:57 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-09 02:25:57 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-09 02:25:57 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-09 02:25:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-09 02:25:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y9jejZ7zQ9/ea_profile.json * 2023-11-09 02:25:59 (2293) [INFO] Backed up EA4 profile to /tmp/y9jejZ7zQ9/ea_profile.json * 2023-11-09 02:26:04 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-10 02:00:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-10 02:00:44 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-10 02:00:44 (1752) [INFO] Checking if your system is up to date: * 2023-11-10 02:00:44 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-10 02:00:44 (4229) [INFO] * 2023-11-10 02:00:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-10 02:00:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-10 02:00:45 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-10 02:00:45 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-10 02:00:45 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-10 02:00:45 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-10 02:00:46 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-10 02:00:46 (4259) [INFO] * 2023-11-10 02:00:46 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-10 02:00:46 (4229) [INFO] * 2023-11-10 02:05:00 (4242) [INFO] * 2023-11-10 02:05:00 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-10 02:05:00 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-10 02:05:01 (4259) [INFO] * 2023-11-10 02:05:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-10 02:05:01 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-10 02:05:05 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-10 02:05:05 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-10 02:08:29 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-10 02:08:29 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30533 milliseconds') * 2023-11-10 02:08:29 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-10 02:08:29 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-10 02:08:29 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-10 02:08:30 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-10 02:08:30 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-10 02:08:30 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-10 02:08:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-10 02:08:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Or4jEY6nTA/ea_profile.json * 2023-11-10 02:08:32 (2293) [INFO] Backed up EA4 profile to /tmp/Or4jEY6nTA/ea_profile.json * 2023-11-10 02:08:36 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-11 02:04:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-11 02:04:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-11 02:04:49 (1752) [INFO] Checking if your system is up to date: * 2023-11-11 02:04:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-11 02:04:49 (4229) [INFO] * 2023-11-11 02:04:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-11 02:04:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-11 02:04:50 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-11 02:04:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-11 02:04:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-11 02:04:50 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-11 02:04:50 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-11 02:04:50 (4259) [INFO] * 2023-11-11 02:04:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-11 02:04:50 (4229) [INFO] * 2023-11-11 02:08:51 (4242) [INFO] * 2023-11-11 02:08:51 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-11 02:08:51 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-11 02:08:51 (4259) [INFO] * 2023-11-11 02:08:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-11 02:08:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-11 02:09:05 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-11 02:09:05 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-11 02:11:54 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-11 02:11:54 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-11 02:11:55 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-11 02:11:55 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-11 02:11:55 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-11 02:11:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-11 02:11:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c5x7LO5sen/ea_profile.json * 2023-11-11 02:11:57 (2293) [INFO] Backed up EA4 profile to /tmp/c5x7LO5sen/ea_profile.json * 2023-11-11 02:12:01 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-12 02:02:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-12 02:02:53 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-12 02:02:53 (1752) [INFO] Checking if your system is up to date: * 2023-11-12 02:02:53 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-12 02:02:53 (4229) [INFO] * 2023-11-12 02:02:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-12 02:02:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-12 02:02:54 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-12 02:02:54 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-12 02:02:54 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-12 02:02:54 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-12 02:02:55 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-12 02:02:55 (4259) [INFO] * 2023-11-12 02:02:55 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-12 02:02:55 (4229) [INFO] * 2023-11-12 02:06:47 (4242) [INFO] * 2023-11-12 02:06:47 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-12 02:06:47 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-12 02:06:47 (4259) [INFO] * 2023-11-12 02:06:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-12 02:06:47 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-12 02:06:50 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-12 02:06:50 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-12 02:09:38 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-12 02:09:38 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-12 02:09:38 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-12 02:09:38 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-12 02:09:38 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-12 02:09:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-12 02:09:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XCyDfnxICO/ea_profile.json * 2023-11-12 02:09:40 (2293) [INFO] Backed up EA4 profile to /tmp/XCyDfnxICO/ea_profile.json * 2023-11-12 02:09:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-13 02:01:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-13 02:01:15 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-13 02:01:15 (1752) [INFO] Checking if your system is up to date: * 2023-11-13 02:01:15 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-13 02:01:15 (4229) [INFO] * 2023-11-13 02:01:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-13 02:01:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-13 02:01:15 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-13 02:01:15 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-13 02:01:15 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-13 02:01:15 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-13 02:01:16 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-13 02:01:16 (4259) [INFO] * 2023-11-13 02:01:16 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-13 02:01:16 (4229) [INFO] * 2023-11-13 02:02:59 (4242) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" * 2023-11-13 02:02:59 (4242) [INFO] Trying other mirror. * 2023-11-13 02:05:06 (4242) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" * 2023-11-13 02:05:06 (4242) [INFO] Trying other mirror. * 2023-11-13 02:05:47 (4242) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-11-13 02:05:47 (4242) [INFO] Trying other mirror. * 2023-11-13 02:06:17 (4242) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-11-13 02:06:17 (4242) [INFO] Trying other mirror. * 2023-11-13 02:06:47 (4242) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-11-13 02:06:47 (4242) [INFO] Trying other mirror. * 2023-11-13 02:07:31 (4242) [INFO] * 2023-11-13 02:07:31 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-13 02:07:31 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-13 02:07:31 (4259) [INFO] * 2023-11-13 02:07:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-13 02:07:31 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-13 02:07:35 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-13 02:07:35 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-13 02:13:16 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-13 02:13:16 (1619) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/0e077b657485f248d60309bb42162f529dd947ec339f3c08fab284ef53419308-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/0e077b657485f248d60309bb42162f529dd947ec339f3c08fab284ef53419308-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. * 2023-11-13 02:13:16 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-13 02:13:16 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-13 02:13:16 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-13 02:13:16 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-13 02:13:16 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-13 02:13:16 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-13 02:13:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-13 02:13:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8J5Lsfou_R/ea_profile.json * 2023-11-13 02:13:18 (2293) [INFO] Backed up EA4 profile to /tmp/8J5Lsfou_R/ea_profile.json * 2023-11-13 02:13:20 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-14 02:04:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-14 02:04:57 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-14 02:04:57 (1752) [INFO] Checking if your system is up to date: * 2023-11-14 02:04:57 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-14 02:04:57 (4229) [INFO] * 2023-11-14 02:04:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-14 02:04:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-14 02:04:57 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-14 02:04:57 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-14 02:04:57 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-14 02:04:57 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-14 02:04:58 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-14 02:04:58 (4259) [INFO] * 2023-11-14 02:04:58 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-14 02:04:58 (4229) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-14 02:05:53 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-14 02:05:53 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-14 02:05:53 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-14 02:05:53 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-14 02:05:53 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-14 02:05:53 (4242) [INFO] yum --disablerepo= ... * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-14 02:05:53 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-14 02:05:53 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] yum-config-manager --disable * 2023-11-14 02:05:53 (4242) [INFO] or * 2023-11-14 02:05:53 (4242) [INFO] subscription-manager repos --disable= * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-14 02:05:53 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-14 02:05:53 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-14 02:05:53 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-14 02:05:53 (4242) [INFO] compromise: * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-14 02:05:53 (4242) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-14 02:05:53 (4259) [INFO] * 2023-11-14 02:05:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-14 02:05:53 (1773) [INFO] Checking /scripts/sysup * 2023-11-14 02:05:53 (4228) [INFO] Running: /scripts/sysup * 2023-11-14 02:05:53 (4229) [INFO] * 2023-11-14 02:05:53 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-14 02:05:55 (4242) [INFO] All Needed Packages are already installed. * 2023-11-14 02:05:55 (4259) [INFO] * 2023-11-14 02:05:58 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-14 02:05:58 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-14 02:06:54 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-14 02:06:54 (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-14 02:06:54 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-14 02:06:54 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-14 02:06:54 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-14 02:06:54 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-14 02:06:54 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-14 02:06:54 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-14 02:06:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-14 02:06:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v00gKsqEYr/ea_profile.json * 2023-11-14 02:10:43 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v00gKsqEYr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272. * 2023-11-14 02:10:43 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-15 02:05:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-15 02:05:45 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-15 02:05:45 (1752) [INFO] Checking if your system is up to date: * 2023-11-15 02:05:45 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-15 02:05:45 (4229) [INFO] * 2023-11-15 02:05:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-15 02:05:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-15 02:05:46 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-15 02:05:46 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-15 02:05:46 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-15 02:05:46 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-15 02:05:46 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-15 02:05:46 (4259) [INFO] * 2023-11-15 02:05:46 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-15 02:05:46 (4229) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-15 02:06:42 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-15 02:06:42 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-15 02:06:42 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-15 02:06:42 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-15 02:06:42 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-15 02:06:42 (4242) [INFO] yum --disablerepo= ... * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-15 02:06:42 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-15 02:06:42 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] yum-config-manager --disable * 2023-11-15 02:06:42 (4242) [INFO] or * 2023-11-15 02:06:42 (4242) [INFO] subscription-manager repos --disable= * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-15 02:06:42 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-15 02:06:42 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-15 02:06:42 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-15 02:06:42 (4242) [INFO] compromise: * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-15 02:06:42 (4242) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-15 02:06:42 (4259) [INFO] * 2023-11-15 02:06:42 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-15 02:06:42 (1773) [INFO] Checking /scripts/sysup * 2023-11-15 02:06:42 (4228) [INFO] Running: /scripts/sysup * 2023-11-15 02:06:42 (4229) [INFO] * 2023-11-15 02:06:42 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-15 02:06:43 (4242) [INFO] All Needed Packages are already installed. * 2023-11-15 02:06:43 (4259) [INFO] * 2023-11-15 02:06:45 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-15 02:06:45 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-15 02:07:40 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-15 02:07:40 (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 02:07:40 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-15 02:07:40 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-15 02:07:40 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-15 02:07:40 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-15 02:07:40 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-15 02:07:40 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-15 02:07:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-15 02:07:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5C4p6PnBWT/ea_profile.json * 2023-11-15 02:20:44 (2293) [INFO] Backed up EA4 profile to /tmp/5C4p6PnBWT/ea_profile.json * 2023-11-15 02:20:46 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-16 02:02:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-16 02:02:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-16 02:02:24 (1752) [INFO] Checking if your system is up to date: * 2023-11-16 02:02:24 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-16 02:02:24 (4229) [INFO] * 2023-11-16 02:02:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-16 02:02:24 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-16 02:02:24 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-16 02:02:24 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-16 02:02:24 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-16 02:02:24 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-16 02:02:25 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-16 02:02:25 (4259) [INFO] * 2023-11-16 02:02:25 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-16 02:02:25 (4229) [INFO] * 2023-11-16 02:06:35 (4242) [INFO] * 2023-11-16 02:06:35 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-16 02:06:35 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-16 02:06:35 (4259) [INFO] * 2023-11-16 02:06:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-16 02:06:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-16 02:06:38 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-16 02:06:38 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-16 02:10:20 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-16 02:10:20 (1619) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. * 2023-11-16 02:10:20 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-16 02:10:20 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-16 02:10:20 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-16 02:10:21 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-16 02:10:21 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-16 02:10:21 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-16 02:10:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-16 02:10:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EM5D47hVQ9/ea_profile.json * 2023-11-16 02:10:23 (2293) [INFO] Backed up EA4 profile to /tmp/EM5D47hVQ9/ea_profile.json * 2023-11-16 02:10:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-17 02:01:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-17 02:01:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-17 02:01:24 (1752) [INFO] Checking if your system is up to date: * 2023-11-17 02:01:24 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-17 02:01:24 (4229) [INFO] * 2023-11-17 02:01:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-17 02:01:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-17 02:01:25 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-17 02:01:25 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-17 02:01:25 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-17 02:01:25 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-17 02:01:26 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-17 02:01:26 (4259) [INFO] * 2023-11-17 02:01:26 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-17 02:01:26 (4229) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-17 02:02:21 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-17 02:02:21 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-17 02:02:21 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-17 02:02:21 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-17 02:02:21 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-17 02:02:21 (4242) [INFO] yum --disablerepo= ... * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-17 02:02:21 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-17 02:02:21 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] yum-config-manager --disable * 2023-11-17 02:02:21 (4242) [INFO] or * 2023-11-17 02:02:21 (4242) [INFO] subscription-manager repos --disable= * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-17 02:02:21 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-17 02:02:21 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-17 02:02:21 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-17 02:02:21 (4242) [INFO] compromise: * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-17 02:02:21 (4242) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-17 02:02:21 (4259) [INFO] * 2023-11-17 02:02:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-17 02:02:21 (1773) [INFO] Checking /scripts/sysup * 2023-11-17 02:02:21 (4228) [INFO] Running: /scripts/sysup * 2023-11-17 02:02:21 (4229) [INFO] * 2023-11-17 02:02:21 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-17 02:02:24 (4242) [INFO] All Needed Packages are already installed. * 2023-11-17 02:02:24 (4259) [INFO] * 2023-11-17 02:02:27 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-17 02:02:27 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-17 02:09:49 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-17 02:09:49 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-17 02:09:50 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-17 02:09:50 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-17 02:09:50 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-17 02:09:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-17 02:09:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fBlgZ83xCx/ea_profile.json * 2023-11-17 02:09:52 (2293) [INFO] Backed up EA4 profile to /tmp/fBlgZ83xCx/ea_profile.json * 2023-11-17 02:09:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-18 02:04:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-18 02:04:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-18 02:04:05 (1752) [INFO] Checking if your system is up to date: * 2023-11-18 02:04:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-18 02:04:05 (4229) [INFO] * 2023-11-18 02:04:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-18 02:04:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-18 02:04:06 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-18 02:04:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-18 02:04:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-18 02:04:06 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-18 02:04:06 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-18 02:04:06 (4259) [INFO] * 2023-11-18 02:04:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-18 02:04:06 (4229) [INFO] * 2023-11-18 02:08:17 (4242) [INFO] * 2023-11-18 02:08:17 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-18 02:08:17 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-18 02:08:18 (4259) [INFO] * 2023-11-18 02:08:18 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-18 02:08:18 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-18 02:08:21 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-18 02:08:21 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-18 02:11:46 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-18 02:11:46 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') * 2023-11-18 02:11:46 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-18 02:11:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-18 02:11:46 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-18 02:11:47 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-18 02:11:47 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-18 02:11:47 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-18 02:11:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-18 02:11:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6iQL4jkuPS/ea_profile.json * 2023-11-18 02:11:49 (2293) [INFO] Backed up EA4 profile to /tmp/6iQL4jkuPS/ea_profile.json * 2023-11-18 02:11:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-19 01:58:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-19 01:58:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-19 01:58:24 (1752) [INFO] Checking if your system is up to date: * 2023-11-19 01:58:24 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-19 01:58:24 (4229) [INFO] * 2023-11-19 01:58:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-19 01:58:24 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-19 01:58:24 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-19 01:58:24 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-19 01:58:24 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-19 01:58:24 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-19 01:58:25 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-19 01:58:25 (4259) [INFO] * 2023-11-19 01:58:25 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-19 01:58:25 (4229) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-19 01:59:19 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-19 01:59:19 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-19 01:59:19 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-19 01:59:19 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-19 01:59:19 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-19 01:59:19 (4242) [INFO] yum --disablerepo= ... * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-19 01:59:19 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-19 01:59:19 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] yum-config-manager --disable * 2023-11-19 01:59:19 (4242) [INFO] or * 2023-11-19 01:59:19 (4242) [INFO] subscription-manager repos --disable= * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-19 01:59:19 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-19 01:59:19 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-19 01:59:19 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-19 01:59:19 (4242) [INFO] compromise: * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-19 01:59:19 (4242) [INFO] * 2023-11-19 01:59:19 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-19 01:59:19 (4259) [INFO] * 2023-11-19 01:59:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-19 01:59:19 (1773) [INFO] Checking /scripts/sysup * 2023-11-19 01:59:19 (4228) [INFO] Running: /scripts/sysup * 2023-11-19 01:59:19 (4229) [INFO] * 2023-11-19 01:59:20 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-19 01:59:22 (4242) [INFO] All Needed Packages are already installed. * 2023-11-19 01:59:22 (4259) [INFO] * 2023-11-19 01:59:24 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-19 01:59:24 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-19 02:06:37 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-19 02:06:37 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-19 02:06:37 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-19 02:06:37 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-19 02:06:37 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-19 02:06:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-19 02:06:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IL914NNB8r/ea_profile.json * 2023-11-19 02:06:40 (2293) [INFO] Backed up EA4 profile to /tmp/IL914NNB8r/ea_profile.json * 2023-11-19 02:06:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-20 02:01:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-20 02:01:30 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-20 02:01:30 (1752) [INFO] Checking if your system is up to date: * 2023-11-20 02:01:30 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-20 02:01:30 (4229) [INFO] * 2023-11-20 02:01:30 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-20 02:01:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-20 02:01:31 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-20 02:01:31 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-20 02:01:31 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-20 02:01:31 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-20 02:01:31 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-20 02:01:31 (4259) [INFO] * 2023-11-20 02:01:31 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-20 02:01:31 (4229) [INFO] * 2023-11-20 02:05:29 (4242) [INFO] * 2023-11-20 02:05:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-20 02:05:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-20 02:05:29 (4259) [INFO] * 2023-11-20 02:05:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-20 02:05:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-20 02:05:31 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-20 02:05:31 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-20 02:08:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-20 02:08:46 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-20 02:08:47 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-20 02:08:47 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-20 02:08:47 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-20 02:08:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-20 02:08:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j4gNrUsYxb/ea_profile.json * 2023-11-20 02:08:49 (2293) [INFO] Backed up EA4 profile to /tmp/j4gNrUsYxb/ea_profile.json * 2023-11-20 02:08:52 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-21 02:01:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-21 02:01:20 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-21 02:01:20 (1752) [INFO] Checking if your system is up to date: * 2023-11-21 02:01:20 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-21 02:01:20 (4229) [INFO] * 2023-11-21 02:01:20 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-21 02:01:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-21 02:01:20 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-21 02:01:20 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-21 02:01:20 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-21 02:01:20 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-21 02:01:21 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-21 02:01:21 (4259) [INFO] * 2023-11-21 02:01:21 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-21 02:01:21 (4229) [INFO] * 2023-11-21 02:05:46 (4242) [INFO] * 2023-11-21 02:05:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-21 02:05:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-21 02:05:46 (4259) [INFO] * 2023-11-21 02:05:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-21 02:05:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-21 02:05:49 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-21 02:05:49 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-21 02:09:24 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-21 02:09:24 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-21 02:09:25 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-21 02:09:25 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-21 02:09:25 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-21 02:09:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-21 02:09:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2RANAKkmkD/ea_profile.json * 2023-11-21 02:09:27 (2293) [INFO] Backed up EA4 profile to /tmp/2RANAKkmkD/ea_profile.json * 2023-11-21 02:09:30 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-22 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-22 02:02:09 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-22 02:02:09 (1752) [INFO] Checking if your system is up to date: * 2023-11-22 02:02:09 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-22 02:02:09 (4229) [INFO] * 2023-11-22 02:02:10 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-22 02:02:10 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-22 02:02:10 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-22 02:02:10 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-22 02:02:10 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-22 02:02:10 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-22 02:02:10 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-22 02:02:10 (4259) [INFO] * 2023-11-22 02:02:10 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-22 02:02:10 (4229) [INFO] * 2023-11-22 02:06:20 (4242) [INFO] * 2023-11-22 02:06:20 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-22 02:06:20 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-22 02:06:20 (4259) [INFO] * 2023-11-22 02:06:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-22 02:06:20 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-22 02:06:24 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-22 02:06:24 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-22 02:09:42 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-22 02:09:42 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-22 02:09:43 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-22 02:09:43 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-22 02:09:43 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-22 02:09:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-22 02:09:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHg_qc2uyc/ea_profile.json * 2023-11-22 02:09:45 (2293) [INFO] Backed up EA4 profile to /tmp/DHg_qc2uyc/ea_profile.json * 2023-11-22 02:09:48 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-23 02:01:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-23 02:01:58 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-23 02:01:58 (1752) [INFO] Checking if your system is up to date: * 2023-11-23 02:01:58 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-23 02:01:58 (4229) [INFO] * 2023-11-23 02:01:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-23 02:01:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-23 02:01:58 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-23 02:01:58 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-23 02:01:58 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-23 02:01:58 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-23 02:01:59 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-23 02:01:59 (4259) [INFO] * 2023-11-23 02:01:59 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-23 02:01:59 (4229) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-23 02:02:54 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-23 02:02:54 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-23 02:02:54 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-23 02:02:54 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-23 02:02:54 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-23 02:02:54 (4242) [INFO] yum --disablerepo= ... * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-23 02:02:54 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-23 02:02:54 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] yum-config-manager --disable * 2023-11-23 02:02:54 (4242) [INFO] or * 2023-11-23 02:02:54 (4242) [INFO] subscription-manager repos --disable= * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-23 02:02:54 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-23 02:02:54 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-23 02:02:54 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-23 02:02:54 (4242) [INFO] compromise: * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-23 02:02:54 (4242) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-23 02:02:54 (4259) [INFO] * 2023-11-23 02:02:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-23 02:02:54 (1773) [INFO] Checking /scripts/sysup * 2023-11-23 02:02:54 (4228) [INFO] Running: /scripts/sysup * 2023-11-23 02:02:54 (4229) [INFO] * 2023-11-23 02:02:54 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-23 02:02:56 (4242) [INFO] All Needed Packages are already installed. * 2023-11-23 02:02:56 (4259) [INFO] * 2023-11-23 02:03:00 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-23 02:03:00 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-23 02:09:48 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-23 02:09:48 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-23 02:09:48 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-23 02:09:48 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-23 02:09:48 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-23 02:09:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-23 02:09:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uAZWInePpH/ea_profile.json * 2023-11-23 02:09:51 (2293) [INFO] Backed up EA4 profile to /tmp/uAZWInePpH/ea_profile.json * 2023-11-23 02:09:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-24 01:59:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-24 01:59:01 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-24 01:59:01 (1752) [INFO] Checking if your system is up to date: * 2023-11-24 01:59:01 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-24 01:59:01 (4229) [INFO] * 2023-11-24 01:59:02 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-24 01:59:03 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-24 01:59:03 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-24 01:59:03 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-24 01:59:03 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-24 01:59:03 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-24 01:59:03 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-24 01:59:03 (4259) [INFO] * 2023-11-24 01:59:03 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-24 01:59:03 (4229) [INFO] * 2023-11-24 02:03:27 (4242) [INFO] * 2023-11-24 02:03:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-24 02:03:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-24 02:03:27 (4259) [INFO] * 2023-11-24 02:03:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-24 02:03:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-24 02:03:30 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-24 02:03:30 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-24 02:07:01 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-24 02:07:01 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-24 02:07:02 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-24 02:07:02 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-24 02:07:02 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-24 02:07:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-24 02:07:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mnvrKFFcHZ/ea_profile.json * 2023-11-24 02:07:04 (2293) [INFO] Backed up EA4 profile to /tmp/mnvrKFFcHZ/ea_profile.json * 2023-11-24 02:07:06 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-25 02:14:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-25 02:15:00 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-25 02:15:00 (1752) [INFO] Checking if your system is up to date: * 2023-11-25 02:15:00 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-25 02:15:00 (4229) [INFO] * 2023-11-25 02:15:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-25 02:15:01 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-25 02:15:01 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-25 02:15:01 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-25 02:15:01 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-25 02:15:01 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-25 02:15:01 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-25 02:15:01 (4259) [INFO] * 2023-11-25 02:15:01 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-25 02:15:01 (4229) [INFO] * 2023-11-25 02:19:10 (4242) [INFO] * 2023-11-25 02:19:10 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-25 02:19:10 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-25 02:19:10 (4259) [INFO] * 2023-11-25 02:19:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-25 02:19:10 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-25 02:19:13 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-25 02:19:13 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-25 02:22:33 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-25 02:22:33 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-25 02:22:33 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-25 02:22:33 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-25 02:22:33 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-25 02:22:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-25 02:22:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6lXbZO6mfu/ea_profile.json * 2023-11-25 02:22:36 (2293) [INFO] Backed up EA4 profile to /tmp/6lXbZO6mfu/ea_profile.json * 2023-11-25 02:22:38 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-26 02:02:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-26 02:02:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-26 02:02:22 (1752) [INFO] Checking if your system is up to date: * 2023-11-26 02:02:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-26 02:02:22 (4229) [INFO] * 2023-11-26 02:02:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-26 02:02:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-26 02:02:23 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-26 02:02:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-26 02:02:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-26 02:02:23 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-26 02:02:23 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-26 02:02:23 (4259) [INFO] * 2023-11-26 02:02:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-26 02:02:23 (4229) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-26 02:03:19 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-26 02:03:19 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-26 02:03:19 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-26 02:03:19 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-26 02:03:19 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-26 02:03:19 (4242) [INFO] yum --disablerepo= ... * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-26 02:03:19 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-26 02:03:19 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] yum-config-manager --disable * 2023-11-26 02:03:19 (4242) [INFO] or * 2023-11-26 02:03:19 (4242) [INFO] subscription-manager repos --disable= * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-26 02:03:19 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-26 02:03:19 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-26 02:03:19 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-26 02:03:19 (4242) [INFO] compromise: * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-26 02:03:19 (4242) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-26 02:03:19 (4259) [INFO] * 2023-11-26 02:03:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-26 02:03:19 (1773) [INFO] Checking /scripts/sysup * 2023-11-26 02:03:19 (4228) [INFO] Running: /scripts/sysup * 2023-11-26 02:03:19 (4229) [INFO] * 2023-11-26 02:03:19 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-26 02:03:21 (4242) [INFO] All Needed Packages are already installed. * 2023-11-26 02:03:21 (4259) [INFO] * 2023-11-26 02:03:24 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-26 02:03:24 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-26 02:04:18 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-26 02:04:18 (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-26 02:04:18 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-26 02:04:18 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-26 02:04:18 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-26 02:04:19 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-26 02:04:19 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-26 02:04:19 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-26 02:04:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-26 02:04:19 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OwwWujZdKy/ea_profile.json * 2023-11-26 02:08:47 (2293) [INFO] Backed up EA4 profile to /tmp/OwwWujZdKy/ea_profile.json * 2023-11-26 02:08:50 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-27 02:01:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-27 02:01:53 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-27 02:01:53 (1752) [INFO] Checking if your system is up to date: * 2023-11-27 02:01:53 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-27 02:01:53 (4229) [INFO] * 2023-11-27 02:01:53 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-27 02:01:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-27 02:01:53 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-27 02:01:53 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-27 02:01:53 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-27 02:01:53 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-27 02:01:53 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-27 02:01:53 (4259) [INFO] * 2023-11-27 02:01:53 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-27 02:01:53 (4229) [INFO] * 2023-11-27 02:06:12 (4242) [INFO] * 2023-11-27 02:06:12 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-27 02:06:12 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-27 02:06:12 (4259) [INFO] * 2023-11-27 02:06:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-27 02:06:12 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-27 02:06:16 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-27 02:06:16 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-27 02:09:47 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-27 02:09:47 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30072 milliseconds') * 2023-11-27 02:09:47 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-27 02:09:47 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-27 02:09:47 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-27 02:09:48 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-27 02:09:48 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-27 02:09:48 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-27 02:09:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-27 02:09:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z1psyWQAKz/ea_profile.json * 2023-11-27 02:09:49 (2293) [INFO] Backed up EA4 profile to /tmp/z1psyWQAKz/ea_profile.json * 2023-11-27 02:09:52 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-28 01:02:03 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-28 01:02:03 (1752) [INFO] Checking if your system is up to date: * 2023-11-28 01:02:03 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-28 01:02:03 (4229) [INFO] * 2023-11-28 01:02:03 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-28 01:02:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-28 01:02:04 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-28 01:02:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-28 01:02:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-28 01:02:04 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-28 01:02:04 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-28 01:02:04 (4259) [INFO] * 2023-11-28 01:02:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-28 01:02:04 (4229) [INFO] * 2023-11-28 01:06:28 (4242) [INFO] * 2023-11-28 01:06:28 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-28 01:06:28 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-28 01:06:28 (4259) [INFO] * 2023-11-28 01:06:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-28 01:06:28 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-28 01:06:33 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-28 01:06:33 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-28 01:10:14 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-28 01:10:14 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-28 01:10:15 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-28 01:10:15 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-28 01:10:15 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-28 01:10:15 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-28 01:10:15 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QVWKs8BlBh/ea_profile.json * 2023-11-28 01:10:17 (2293) [INFO] Backed up EA4 profile to /tmp/QVWKs8BlBh/ea_profile.json * 2023-11-28 01:10:21 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-29 02:01:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-29 02:01:02 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-29 02:01:02 (1752) [INFO] Checking if your system is up to date: * 2023-11-29 02:01:02 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-29 02:01:02 (4229) [INFO] * 2023-11-29 02:01:02 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-29 02:01:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-29 02:01:02 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-29 02:01:02 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-29 02:01:02 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-29 02:01:02 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-29 02:01:03 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-29 02:01:03 (4259) [INFO] * 2023-11-29 02:01:03 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-29 02:01:03 (4229) [INFO] * 2023-11-29 02:05:26 (4242) [INFO] * 2023-11-29 02:05:26 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-29 02:05:26 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-29 02:05:27 (4259) [INFO] * 2023-11-29 02:05:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-29 02:05:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-29 02:05:30 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-29 02:05:30 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-29 02:09:03 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-29 02:09:03 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-29 02:09:04 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-29 02:09:04 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-29 02:09:04 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-29 02:09:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-29 02:09:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kaF1JM9lb3/ea_profile.json * 2023-11-29 02:09:06 (2293) [INFO] Backed up EA4 profile to /tmp/kaF1JM9lb3/ea_profile.json * 2023-11-29 02:09:09 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-30 01:59:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-11-30 01:59:58 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-30 01:59:58 (1752) [INFO] Checking if your system is up to date: * 2023-11-30 01:59:58 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-30 01:59:58 (4229) [INFO] * 2023-11-30 01:59:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-30 01:59:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-11-30 01:59:58 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-30 01:59:58 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-30 01:59:58 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-30 01:59:58 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-11-30 01:59:59 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-11-30 01:59:59 (4259) [INFO] * 2023-11-30 01:59:59 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-30 01:59:59 (4229) [INFO] * 2023-11-30 02:04:08 (4242) [INFO] * 2023-11-30 02:04:08 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-30 02:04:08 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-30 02:04:08 (4259) [INFO] * 2023-11-30 02:04:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-30 02:04:08 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-30 02:04:11 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-11-30 02:04:11 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-11-30 02:07:42 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-11-30 02:07:42 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-11-30 02:07:42 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-11-30 02:07:42 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-11-30 02:07:42 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-11-30 02:07:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-30 02:07:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rx0mfMIlC_/ea_profile.json * 2023-11-30 02:07:44 (2293) [INFO] Backed up EA4 profile to /tmp/rx0mfMIlC_/ea_profile.json * 2023-11-30 02:07:48 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-01 02:05:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-01 02:05:13 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-01 02:05:13 (1752) [INFO] Checking if your system is up to date: * 2023-12-01 02:05:13 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-01 02:05:13 (4229) [INFO] * 2023-12-01 02:05:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-01 02:05:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-01 02:05:14 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-01 02:05:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-01 02:05:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-01 02:05:14 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-01 02:05:15 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-01 02:05:15 (4259) [INFO] * 2023-12-01 02:05:15 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-01 02:05:15 (4229) [INFO] * 2023-12-01 02:09:29 (4242) [INFO] * 2023-12-01 02:09:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-01 02:09:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-01 02:09:29 (4259) [INFO] * 2023-12-01 02:09:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-01 02:09:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-01 02:09:33 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-01 02:09:33 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-01 02:13:10 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-01 02:13:10 (1619) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30536 milliseconds') * 2023-12-01 02:13:10 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-01 02:13:10 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-01 02:13:10 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-01 02:13:10 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-01 02:13:10 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-01 02:13:10 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-01 02:13:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-01 02:13:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/69NZ9iHqJl/ea_profile.json * 2023-12-01 02:13:12 (2293) [INFO] Backed up EA4 profile to /tmp/69NZ9iHqJl/ea_profile.json * 2023-12-01 02:13:16 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-02 02:05:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-02 02:05:46 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-02 02:05:46 (1752) [INFO] Checking if your system is up to date: * 2023-12-02 02:05:46 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-02 02:05:46 (4229) [INFO] * 2023-12-02 02:05:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-02 02:05:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-02 02:05:47 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-02 02:05:47 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-02 02:05:47 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-02 02:05:47 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-02 02:05:47 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-02 02:05:47 (4259) [INFO] * 2023-12-02 02:05:47 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-02 02:05:47 (4229) [INFO] * 2023-12-02 02:09:27 (4242) [INFO] http://103.17.8.8/cpanelsync/repos/CentOS/7/EA4/repodata/d6f5ce14bb7c54caa2c9b9942c1a324bad2da3ed7acef53e230cf100642cb3b6-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-02 02:09:27 (4242) [INFO] Trying other mirror. * 2023-12-02 02:09:28 (4242) [INFO] http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-02 02:09:28 (4242) [INFO] Trying other mirror. * 2023-12-02 02:09:42 (4242) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-02 02:09:42 (4242) [INFO] Trying other mirror. * 2023-12-02 02:09:43 (4242) [INFO] http://184.94.196.94/cpanelsync/repos/CentOS/7/EA4/repodata/d6f5ce14bb7c54caa2c9b9942c1a324bad2da3ed7acef53e230cf100642cb3b6-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-02 02:09:43 (4242) [INFO] Trying other mirror. * 2023-12-02 02:09:44 (4242) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-02 02:09:44 (4242) [INFO] Trying other mirror. * 2023-12-02 02:10:44 (4242) [INFO] * 2023-12-02 02:10:44 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-02 02:10:44 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-02 02:10:44 (4259) [INFO] * 2023-12-02 02:10:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-02 02:10:44 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-02 02:10:48 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-02 02:10:48 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-02 02:14:34 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-02 02:14:34 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-02 02:14:35 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-02 02:14:35 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-02 02:14:35 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-02 02:14:35 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-02 02:14:35 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zVSs4Qjo3s/ea_profile.json * 2023-12-02 02:14:37 (2293) [INFO] Backed up EA4 profile to /tmp/zVSs4Qjo3s/ea_profile.json * 2023-12-02 02:14:42 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-03 02:06:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-03 02:06:40 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-03 02:06:40 (1752) [INFO] Checking if your system is up to date: * 2023-12-03 02:06:40 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-03 02:06:40 (4229) [INFO] * 2023-12-03 02:06:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-03 02:06:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-03 02:06:41 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-03 02:06:41 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-03 02:06:41 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-03 02:06:41 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-03 02:06:41 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-03 02:06:42 (4259) [INFO] * 2023-12-03 02:06:42 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-03 02:06:42 (4229) [INFO] * 2023-12-03 02:10:25 (4242) [INFO] http://mirror.us.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-03 02:10:25 (4242) [INFO] Trying other mirror. * 2023-12-03 02:10:26 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2023-12-03 02:10:26 (4242) [INFO] Trying other mirror. * 2023-12-03 02:10:41 (4242) [INFO] http://mirror.keystealth.org/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:10:41 (4242) [INFO] Trying other mirror. * 2023-12-03 02:10:41 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/wp-toolkit/repodata/f6489a31962cb070b7494bc283d6303983e10275d589f623bb4f29067abbc0a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:10:41 (4242) [INFO] Trying other mirror. * 2023-12-03 02:10:41 (4242) [INFO] http://mirror.math.princeton.edu/pub/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:10:41 (4242) [INFO] Trying other mirror. * 2023-12-03 02:10:42 (4242) [INFO] http://mirror.cs.pitt.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:10:42 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:05 (4242) [INFO] http://ftp.osuosl.org/pub/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:05 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:05 (4242) [INFO] http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:05 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:05 (4242) [INFO] http://mirror.siena.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:05 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:21 (4242) [INFO] http://mirror.servaxnet.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:21 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:37 (4242) [INFO] http://mirror.vacares.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:37 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:52 (4242) [INFO] http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:52 (4242) [INFO] Trying other mirror. * 2023-12-03 02:11:52 (4242) [INFO] http://volico.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2023-12-03 02:11:52 (4242) [INFO] Trying other mirror. * 2023-12-03 02:12:20 (4242) [INFO] * 2023-12-03 02:12:20 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-03 02:12:20 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-03 02:12:20 (4259) [INFO] * 2023-12-03 02:12:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-03 02:12:20 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-03 02:12:23 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-03 02:12:23 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-03 02:15:52 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-03 02:15:52 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-03 02:15:52 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-03 02:15:52 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-03 02:15:52 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-03 02:15:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-03 02:15:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TH8XULJEgf/ea_profile.json * 2023-12-03 02:15:55 (2293) [INFO] Backed up EA4 profile to /tmp/TH8XULJEgf/ea_profile.json * 2023-12-03 02:15:59 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-04 02:01:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-04 02:01:02 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-04 02:01:02 (1752) [INFO] Checking if your system is up to date: * 2023-12-04 02:01:02 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-04 02:01:02 (4229) [INFO] * 2023-12-04 02:01:03 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-04 02:01:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-04 02:01:04 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-04 02:01:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-04 02:01:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-04 02:01:04 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-04 02:01:04 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-04 02:01:04 (4259) [INFO] * 2023-12-04 02:01:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-04 02:01:04 (4229) [INFO] * 2023-12-04 02:05:23 (4242) [INFO] * 2023-12-04 02:05:23 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-04 02:05:23 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-04 02:05:23 (4259) [INFO] * 2023-12-04 02:05:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-04 02:05:23 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-04 02:05:26 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-04 02:05:26 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-04 02:08:56 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-04 02:08:56 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-04 02:08:57 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-04 02:08:57 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-04 02:08:57 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-04 02:08:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-04 02:08:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3H0MMAhMUX/ea_profile.json * 2023-12-04 02:08:59 (2293) [INFO] Backed up EA4 profile to /tmp/3H0MMAhMUX/ea_profile.json * 2023-12-04 02:09:02 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-05 02:02:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-05 02:02:16 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-05 02:02:16 (1752) [INFO] Checking if your system is up to date: * 2023-12-05 02:02:16 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-05 02:02:16 (4229) [INFO] * 2023-12-05 02:02:17 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-05 02:02:17 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-05 02:02:17 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-05 02:02:17 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-05 02:02:17 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-05 02:02:17 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-05 02:02:18 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-05 02:02:18 (4259) [INFO] * 2023-12-05 02:02:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-05 02:02:18 (4229) [INFO] * 2023-12-05 02:06:45 (4242) [INFO] * 2023-12-05 02:06:45 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-05 02:06:45 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-05 02:06:45 (4259) [INFO] * 2023-12-05 02:06:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-05 02:06:45 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-05 02:06:48 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-05 02:06:48 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-05 02:10:25 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-05 02:10:25 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-05 02:10:26 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-05 02:10:26 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-05 02:10:26 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-05 02:10:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-05 02:10:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iXVbzpY8zc/ea_profile.json * 2023-12-05 02:10:28 (2293) [INFO] Backed up EA4 profile to /tmp/iXVbzpY8zc/ea_profile.json * 2023-12-05 02:10:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-06 02:00:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-06 02:00:46 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-06 02:00:46 (1752) [INFO] Checking if your system is up to date: * 2023-12-06 02:00:46 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-06 02:00:46 (4229) [INFO] * 2023-12-06 02:00:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-06 02:00:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-06 02:00:47 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-06 02:00:47 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-06 02:00:47 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-06 02:00:47 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-06 02:00:47 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-06 02:00:47 (4259) [INFO] * 2023-12-06 02:00:47 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-06 02:00:47 (4229) [INFO] * 2023-12-06 02:05:05 (4242) [INFO] * 2023-12-06 02:05:05 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-06 02:05:05 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-06 02:05:05 (4259) [INFO] * 2023-12-06 02:05:05 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-06 02:05:05 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-06 02:05:09 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-06 02:05:09 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-06 02:08:43 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-06 02:08:43 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-06 02:08:44 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-06 02:08:44 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-06 02:08:44 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-06 02:08:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-06 02:08:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AcRqX6rebu/ea_profile.json * 2023-12-06 02:08:46 (2293) [INFO] Backed up EA4 profile to /tmp/AcRqX6rebu/ea_profile.json * 2023-12-06 02:08:51 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-07 02:04:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-07 02:04:48 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-07 02:04:48 (1752) [INFO] Checking if your system is up to date: * 2023-12-07 02:04:48 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-07 02:04:48 (4229) [INFO] * 2023-12-07 02:04:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-07 02:04:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-07 02:04:49 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-07 02:04:49 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-07 02:04:49 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-07 02:04:49 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-07 02:04:50 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-07 02:04:50 (4259) [INFO] * 2023-12-07 02:04:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-07 02:04:50 (4229) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-12-07 02:05:45 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-07 02:05:45 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-07 02:05:45 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-07 02:05:45 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-12-07 02:05:45 (4242) [INFO] packages for the previous distribution release still work). * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-07 02:05:45 (4242) [INFO] yum --disablerepo= ... * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-07 02:05:45 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-07 02:05:45 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] yum-config-manager --disable * 2023-12-07 02:05:45 (4242) [INFO] or * 2023-12-07 02:05:45 (4242) [INFO] subscription-manager repos --disable= * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-07 02:05:45 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-07 02:05:45 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-07 02:05:45 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-07 02:05:45 (4242) [INFO] compromise: * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-07 02:05:45 (4242) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-07 02:05:45 (4259) [INFO] * 2023-12-07 02:05:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-07 02:05:45 (1773) [INFO] Checking /scripts/sysup * 2023-12-07 02:05:45 (4228) [INFO] Running: /scripts/sysup * 2023-12-07 02:05:45 (4229) [INFO] * 2023-12-07 02:05:45 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-07 02:05:48 (4242) [INFO] All Needed Packages are already installed. * 2023-12-07 02:05:48 (4259) [INFO] * 2023-12-07 02:05:51 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-07 02:05:51 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-07 02:13:46 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-07 02:13:46 (1619) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/dbe428cc1365892da689894e50519822cb3c19209a842773363fd372e7a6d15d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.us.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.oit.uci.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/wp-toolkit/repodata/f6489a31962cb070b7494bc283d6303983e10275d589f623bb4f29067abbc0a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.nodesdirect.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rcs.alaska.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://mirror.ash.fastserv.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.pit.teraswitch.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo.ialab.dsu.edu/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-12-07 02:13:46 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-07 02:13:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-07 02:13:47 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-07 02:13:47 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-07 02:13:47 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-07 02:13:47 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-07 02:13:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-07 02:13:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N5zDhir7uK/ea_profile.json * 2023-12-07 02:13:50 (2293) [INFO] Backed up EA4 profile to /tmp/N5zDhir7uK/ea_profile.json * 2023-12-07 02:13:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-08 02:16:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-08 02:16:58 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-08 02:16:58 (1752) [INFO] Checking if your system is up to date: * 2023-12-08 02:16:58 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-08 02:16:58 (4229) [INFO] * 2023-12-08 02:16:59 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-08 02:16:59 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-08 02:16:59 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-08 02:16:59 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-08 02:16:59 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-08 02:16:59 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-08 02:16:59 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-08 02:16:59 (4259) [INFO] * 2023-12-08 02:16:59 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-08 02:16:59 (4229) [INFO] * 2023-12-08 02:21:25 (4242) [INFO] * 2023-12-08 02:21:25 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-08 02:21:25 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-08 02:21:25 (4259) [INFO] * 2023-12-08 02:21:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-08 02:21:25 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-08 02:21:29 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-08 02:21:29 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-08 02:25:08 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-08 02:25:08 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-08 02:25:09 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-08 02:25:09 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-08 02:25:09 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-08 02:25:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-08 02:25:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yWDNbTE7Nm/ea_profile.json * 2023-12-08 02:25:12 (2293) [INFO] Backed up EA4 profile to /tmp/yWDNbTE7Nm/ea_profile.json * 2023-12-08 02:25:16 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-09 01:57:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-09 01:57:16 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-09 01:57:16 (1752) [INFO] Checking if your system is up to date: * 2023-12-09 01:57:16 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-09 01:57:16 (4229) [INFO] * 2023-12-09 01:57:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-09 01:57:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-09 01:57:16 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-09 01:57:16 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-09 01:57:16 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-09 01:57:16 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-09 01:57:17 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-09 01:57:17 (4259) [INFO] * 2023-12-09 01:57:17 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-09 01:57:17 (4229) [INFO] * 2023-12-09 02:01:46 (4242) [INFO] * 2023-12-09 02:01:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-09 02:01:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-09 02:01:47 (4259) [INFO] * 2023-12-09 02:01:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-09 02:01:47 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-09 02:01:52 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-09 02:01:52 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-09 02:05:13 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-09 02:05:13 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-09 02:05:14 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-09 02:05:14 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-09 02:05:14 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-09 02:05:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-09 02:05:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E09MwQ3hgU/ea_profile.json * 2023-12-09 02:05:16 (2293) [INFO] Backed up EA4 profile to /tmp/E09MwQ3hgU/ea_profile.json * 2023-12-09 02:05:20 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-10 02:03:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-10 02:03:12 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-10 02:03:12 (1752) [INFO] Checking if your system is up to date: * 2023-12-10 02:03:12 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-10 02:03:12 (4229) [INFO] * 2023-12-10 02:03:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-10 02:03:12 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-10 02:03:12 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-10 02:03:12 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-10 02:03:12 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-10 02:03:12 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-10 02:03:13 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-10 02:03:13 (4259) [INFO] * 2023-12-10 02:03:13 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-10 02:03:13 (4229) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-12-10 02:04:08 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-10 02:04:08 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-10 02:04:08 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-10 02:04:08 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-12-10 02:04:08 (4242) [INFO] packages for the previous distribution release still work). * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-10 02:04:08 (4242) [INFO] yum --disablerepo= ... * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-10 02:04:08 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-10 02:04:08 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] yum-config-manager --disable * 2023-12-10 02:04:08 (4242) [INFO] or * 2023-12-10 02:04:08 (4242) [INFO] subscription-manager repos --disable= * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-10 02:04:08 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-10 02:04:08 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-10 02:04:08 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-10 02:04:08 (4242) [INFO] compromise: * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-10 02:04:08 (4242) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-10 02:04:08 (4259) [INFO] * 2023-12-10 02:04:08 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-10 02:04:08 (1773) [INFO] Checking /scripts/sysup * 2023-12-10 02:04:08 (4228) [INFO] Running: /scripts/sysup * 2023-12-10 02:04:08 (4229) [INFO] * 2023-12-10 02:04:08 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-10 02:04:10 (4242) [INFO] All Needed Packages are already installed. * 2023-12-10 02:04:10 (4259) [INFO] * 2023-12-10 02:04:13 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-10 02:04:13 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-10 02:12:46 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-10 02:12:46 (1619) [ERROR] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xtom.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/wp-toolkit/repodata/f6489a31962cb070b7494bc283d6303983e10275d589f623bb4f29067abbc0a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://us.mirrors.virtono.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.raystedman.org/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://abqix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.servaxnet.com/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://tx-mirror.tier.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ziply.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/CentOS/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.facebook.net/centos/7.9.2009/updates/x86_64/repodata/9d63e12160d1e95c6f8404f6d170cf2655a72ecbffe51e4171cc74765331a84a-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-12-10 02:12:46 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-10 02:12:46 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-10 02:12:46 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-10 02:12:46 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-10 02:12:46 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-10 02:12:46 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-10 02:12:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-10 02:12:46 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aBj3i30fyT/ea_profile.json * 2023-12-10 02:12:49 (2293) [INFO] Backed up EA4 profile to /tmp/aBj3i30fyT/ea_profile.json * 2023-12-10 02:12:52 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-11 02:03:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-11 02:03:50 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-11 02:03:50 (1752) [INFO] Checking if your system is up to date: * 2023-12-11 02:03:50 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-11 02:03:50 (4229) [INFO] * 2023-12-11 02:03:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-11 02:03:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-11 02:03:50 (4242) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-11 02:03:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-11 02:03:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-11 02:03:50 (4242) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-11 02:03:51 (4242) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-11 02:03:51 (4259) [INFO] * 2023-12-11 02:03:51 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-11 02:03:51 (4229) [INFO] * 2023-12-11 02:07:59 (4242) [INFO] * 2023-12-11 02:07:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-11 02:07:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-11 02:07:59 (4259) [INFO] * 2023-12-11 02:07:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-11 02:07:59 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-11 02:08:03 (1677) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-11 02:08:03 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-11 02:11:20 (1820) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-11 02:11:20 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-11 02:11:21 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-11 02:11:21 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-11 02:11:21 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-11 02:11:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-11 02:11:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5UUil10osF/ea_profile.json * 2023-12-11 02:11:23 (2293) [INFO] Backed up EA4 profile to /tmp/5UUil10osF/ea_profile.json * 2023-12-11 02:11:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-12 02:03:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-12 02:03:10 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-12 02:03:10 (1753) [INFO] Checking if your system is up to date: * 2023-12-12 02:03:10 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-12 02:03:10 (4230) [INFO] * 2023-12-12 02:03:11 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-12 02:03:11 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-12 02:03:11 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-12 02:03:11 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-12 02:03:11 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-12 02:03:11 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-12 02:03:12 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-12 02:03:12 (4260) [INFO] * 2023-12-12 02:03:12 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-12 02:03:12 (4230) [INFO] * 2023-12-12 02:07:33 (4243) [INFO] * 2023-12-12 02:07:33 (4243) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-12 02:07:33 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-12 02:07:34 (4260) [INFO] * 2023-12-12 02:07:34 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-12 02:07:34 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-12 02:07:37 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-12 02:07:37 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-12 02:11:20 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-12 02:11:20 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-12 02:11:21 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-12 02:11:21 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-12 02:11:21 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-12 02:11:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-12 02:11:21 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sLn7ANIiVI/ea_profile.json * 2023-12-12 02:11:23 (2294) [INFO] Backed up EA4 profile to /tmp/sLn7ANIiVI/ea_profile.json * 2023-12-12 02:11:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-13 02:02:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-13 02:02:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-13 02:02:19 (1753) [INFO] Checking if your system is up to date: * 2023-12-13 02:02:19 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-13 02:02:19 (4230) [INFO] * 2023-12-13 02:02:19 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-13 02:02:19 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-13 02:02:19 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-13 02:02:19 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-13 02:02:19 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-13 02:02:19 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-13 02:02:20 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-13 02:02:20 (4260) [INFO] * 2023-12-13 02:02:20 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-13 02:02:20 (4230) [INFO] * 2023-12-13 02:06:15 (4243) [INFO] * 2023-12-13 02:06:15 (4243) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-13 02:06:15 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-13 02:06:15 (4260) [INFO] * 2023-12-13 02:06:15 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-13 02:06:15 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-13 02:06:18 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-13 02:06:18 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-13 02:09:23 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-13 02:09:23 (1620) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2023-12-13 02:09:23 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-13 02:09:23 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-13 02:09:23 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-13 02:09:24 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-13 02:09:24 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-13 02:09:24 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-13 02:09:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-13 02:09:24 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OlnRj6EQA4/ea_profile.json * 2023-12-13 02:09:26 (2294) [INFO] Backed up EA4 profile to /tmp/OlnRj6EQA4/ea_profile.json * 2023-12-13 02:09:31 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-14 02:11:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-14 02:11:23 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-14 02:11:23 (1753) [INFO] Checking if your system is up to date: * 2023-12-14 02:11:23 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-14 02:11:24 (4230) [INFO] * 2023-12-14 02:11:24 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-14 02:11:24 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-14 02:11:24 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-14 02:11:24 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-14 02:11:24 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-14 02:11:24 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-14 02:11:25 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-14 02:11:25 (4260) [INFO] * 2023-12-14 02:11:25 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-14 02:11:25 (4230) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] One of the configured repositories failed (Unknown), * 2023-12-14 02:12:20 (4243) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-14 02:12:20 (4243) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-14 02:12:20 (4243) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-14 02:12:20 (4243) [INFO] distribution release than is supported by the repository (and the * 2023-12-14 02:12:20 (4243) [INFO] packages for the previous distribution release still work). * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-14 02:12:20 (4243) [INFO] yum --disablerepo= ... * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-14 02:12:20 (4243) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-14 02:12:20 (4243) [INFO] again or use --enablerepo for temporary usage: * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] yum-config-manager --disable * 2023-12-14 02:12:20 (4243) [INFO] or * 2023-12-14 02:12:20 (4243) [INFO] subscription-manager repos --disable= * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-14 02:12:20 (4243) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-14 02:12:20 (4243) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-14 02:12:20 (4243) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-14 02:12:20 (4243) [INFO] compromise: * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-14 02:12:20 (4243) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-14 02:12:20 (4260) [INFO] * 2023-12-14 02:12:20 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-14 02:12:20 (1774) [INFO] Checking /scripts/sysup * 2023-12-14 02:12:20 (4229) [INFO] Running: /scripts/sysup * 2023-12-14 02:12:20 (4230) [INFO] * 2023-12-14 02:12:20 (4243) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-14 02:12:23 (4243) [INFO] All Needed Packages are already installed. * 2023-12-14 02:12:23 (4260) [INFO] * 2023-12-14 02:12:27 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-14 02:12:27 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-14 02:13:20 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-14 02:13:20 (1620) [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-12-14 02:13:20 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-14 02:13:20 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-14 02:13:20 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-14 02:13:21 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-14 02:13:21 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-14 02:13:21 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-14 02:13:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-14 02:13:21 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jIpya_gYxA/ea_profile.json * 2023-12-14 02:17:40 (2294) [INFO] Backed up EA4 profile to /tmp/jIpya_gYxA/ea_profile.json * 2023-12-14 02:17:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-15 02:00:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-15 02:00:30 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-15 02:00:30 (1753) [INFO] Checking if your system is up to date: * 2023-12-15 02:00:30 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-15 02:00:30 (4230) [INFO] * 2023-12-15 02:00:31 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-15 02:00:31 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-15 02:00:31 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-15 02:00:31 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-15 02:00:31 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-15 02:00:31 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-15 02:00:32 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-15 02:00:32 (4260) [INFO] * 2023-12-15 02:00:32 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-15 02:00:32 (4230) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] One of the configured repositories failed (Unknown), * 2023-12-15 02:01:27 (4243) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-15 02:01:27 (4243) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-15 02:01:27 (4243) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-15 02:01:27 (4243) [INFO] distribution release than is supported by the repository (and the * 2023-12-15 02:01:27 (4243) [INFO] packages for the previous distribution release still work). * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-15 02:01:27 (4243) [INFO] yum --disablerepo= ... * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-15 02:01:27 (4243) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-15 02:01:27 (4243) [INFO] again or use --enablerepo for temporary usage: * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] yum-config-manager --disable * 2023-12-15 02:01:27 (4243) [INFO] or * 2023-12-15 02:01:27 (4243) [INFO] subscription-manager repos --disable= * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-15 02:01:27 (4243) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-15 02:01:27 (4243) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-15 02:01:27 (4243) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-15 02:01:27 (4243) [INFO] compromise: * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-15 02:01:27 (4243) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-15 02:01:27 (4260) [INFO] * 2023-12-15 02:01:27 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-15 02:01:27 (1774) [INFO] Checking /scripts/sysup * 2023-12-15 02:01:27 (4229) [INFO] Running: /scripts/sysup * 2023-12-15 02:01:27 (4230) [INFO] * 2023-12-15 02:01:27 (4243) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-15 02:01:30 (4243) [INFO] All Needed Packages are already installed. * 2023-12-15 02:01:30 (4260) [INFO] * 2023-12-15 02:01:34 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-15 02:01:34 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-15 02:02:28 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-15 02:02:28 (1620) [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-12-15 02:02:28 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-15 02:02:28 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-15 02:02:28 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-15 02:02:29 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-15 02:02:29 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-15 02:02:29 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-15 02:02:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-15 02:02:29 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n7PXglPc2r/ea_profile.json * 2023-12-15 02:06:09 (2294) [INFO] Backed up EA4 profile to /tmp/n7PXglPc2r/ea_profile.json * 2023-12-15 02:06:12 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-16 02:03:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-16 02:03:36 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-16 02:03:36 (1753) [INFO] Checking if your system is up to date: * 2023-12-16 02:03:36 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-16 02:03:36 (4230) [INFO] * 2023-12-16 02:03:37 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-16 02:03:37 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-16 02:03:37 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-16 02:03:37 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-16 02:03:37 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-16 02:03:37 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-16 02:03:38 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-16 02:03:38 (4260) [INFO] * 2023-12-16 02:03:38 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-16 02:03:38 (4230) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] One of the configured repositories failed (Unknown), * 2023-12-16 02:04:33 (4243) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-16 02:04:33 (4243) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-16 02:04:33 (4243) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-16 02:04:33 (4243) [INFO] distribution release than is supported by the repository (and the * 2023-12-16 02:04:33 (4243) [INFO] packages for the previous distribution release still work). * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-16 02:04:33 (4243) [INFO] yum --disablerepo= ... * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-16 02:04:33 (4243) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-16 02:04:33 (4243) [INFO] again or use --enablerepo for temporary usage: * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] yum-config-manager --disable * 2023-12-16 02:04:33 (4243) [INFO] or * 2023-12-16 02:04:33 (4243) [INFO] subscription-manager repos --disable= * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-16 02:04:33 (4243) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-16 02:04:33 (4243) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-16 02:04:33 (4243) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-16 02:04:33 (4243) [INFO] compromise: * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-16 02:04:33 (4243) [INFO] * 2023-12-16 02:04:33 (4243) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-16 02:04:33 (4260) [INFO] * 2023-12-16 02:04:33 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-16 02:04:33 (1774) [INFO] Checking /scripts/sysup * 2023-12-16 02:04:33 (4229) [INFO] Running: /scripts/sysup * 2023-12-16 02:04:33 (4230) [INFO] * 2023-12-16 02:04:34 (4243) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-16 02:04:37 (4243) [INFO] All Needed Packages are already installed. * 2023-12-16 02:04:37 (4260) [INFO] * 2023-12-16 02:04:40 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-16 02:04:40 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-16 02:14:07 (1619) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-16 02:14:07 (1620) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.13/wp-toolkit/repodata/69c3d9cd3c88bbf364bb0876a71e7c43c4703f8abb92cb9540240fefe80c6998-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.13/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.osuosl.org/pub/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ohioix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://ftp.usf.edu/pub/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vacares.com/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-12-16 02:14:07 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-16 02:14:07 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-16 02:14:07 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-16 02:14:08 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-16 02:14:08 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-16 02:14:08 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-16 02:14:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-16 02:14:08 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W5amkITn0T/ea_profile.json * 2023-12-16 02:14:11 (2294) [INFO] Backed up EA4 profile to /tmp/W5amkITn0T/ea_profile.json * 2023-12-16 02:14:16 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-17 02:03:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-17 02:03:13 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-17 02:03:13 (1753) [INFO] Checking if your system is up to date: * 2023-12-17 02:03:13 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-17 02:03:13 (4230) [INFO] * 2023-12-17 02:03:13 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-17 02:03:13 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-17 02:03:13 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-17 02:03:13 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-17 02:03:13 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-17 02:03:13 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-17 02:03:13 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-17 02:03:14 (4260) [INFO] * 2023-12-17 02:03:14 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-17 02:03:14 (4230) [INFO] * 2023-12-17 02:07:06 (4243) [INFO] * 2023-12-17 02:07:06 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-17 02:07:06 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-17 02:07:07 (4260) [INFO] * 2023-12-17 02:07:07 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-17 02:07:07 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-17 02:07:10 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-17 02:07:10 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-17 02:10:10 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-17 02:10:10 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-17 02:10:11 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-17 02:10:11 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-17 02:10:11 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-17 02:10:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-17 02:10:11 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Xx2gMOVQLR/ea_profile.json * 2023-12-17 02:10:13 (2294) [INFO] Backed up EA4 profile to /tmp/Xx2gMOVQLR/ea_profile.json * 2023-12-17 02:10:16 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-18 02:01:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-18 02:01:35 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-18 02:01:35 (1753) [INFO] Checking if your system is up to date: * 2023-12-18 02:01:35 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-18 02:01:35 (4230) [INFO] * 2023-12-18 02:01:35 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-18 02:01:35 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-18 02:01:35 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-18 02:01:35 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-18 02:01:35 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-18 02:01:35 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-18 02:01:35 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-18 02:01:35 (4260) [INFO] * 2023-12-18 02:01:35 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-18 02:01:35 (4230) [INFO] * 2023-12-18 02:05:51 (4243) [INFO] * 2023-12-18 02:05:51 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-18 02:05:51 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-18 02:05:51 (4260) [INFO] * 2023-12-18 02:05:51 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-18 02:05:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-18 02:05:54 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-18 02:05:54 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-18 02:09:26 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-18 02:09:26 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-18 02:09:27 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-18 02:09:27 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-18 02:09:27 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-18 02:09:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-18 02:09:27 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1DwO0haPTP/ea_profile.json * 2023-12-18 02:09:29 (2294) [INFO] Backed up EA4 profile to /tmp/1DwO0haPTP/ea_profile.json * 2023-12-18 02:09:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-19 02:01:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-19 02:01:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-19 02:01:04 (1753) [INFO] Checking if your system is up to date: * 2023-12-19 02:01:04 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-19 02:01:04 (4230) [INFO] * 2023-12-19 02:01:04 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-19 02:01:04 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-19 02:01:04 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-19 02:01:04 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-19 02:01:04 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-19 02:01:04 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-19 02:01:05 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-19 02:01:05 (4260) [INFO] * 2023-12-19 02:01:05 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-19 02:01:05 (4230) [INFO] * 2023-12-19 02:05:13 (4243) [INFO] * 2023-12-19 02:05:13 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-19 02:05:13 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-19 02:05:14 (4260) [INFO] * 2023-12-19 02:05:14 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-19 02:05:14 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-19 02:05:16 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-19 02:05:16 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-19 02:08:32 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-19 02:08:32 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-19 02:08:32 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-19 02:08:32 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-19 02:08:32 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-19 02:08:32 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-19 02:08:32 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dlQ2SKHGBz/ea_profile.json * 2023-12-19 02:08:35 (2294) [INFO] Backed up EA4 profile to /tmp/dlQ2SKHGBz/ea_profile.json * 2023-12-19 02:08:38 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-20 01:55:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-20 01:55:07 (155) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-20 01:55:07 (1753) [INFO] Checking if your system is up to date: * 2023-12-20 01:55:07 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-20 01:55:07 (4230) [INFO] * 2023-12-20 01:55:07 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-20 01:55:08 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-20 01:55:08 (4243) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-20 01:55:08 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-20 01:55:08 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-20 01:55:08 (4243) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-20 01:55:08 (4243) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-20 01:55:08 (4260) [INFO] * 2023-12-20 01:55:08 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-20 01:55:08 (4230) [INFO] * 2023-12-20 01:59:26 (4243) [INFO] * 2023-12-20 01:59:26 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-20 01:59:26 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-20 01:59:27 (4260) [INFO] * 2023-12-20 01:59:27 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-20 01:59:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-20 01:59:29 (1678) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-20 01:59:29 (155) [WARN] *** Elevation Blocker detected: *** One or more enabled YUM repo are currently unsupported and have installed packages. You should disable these repositories and remove packages installed from them before continuing the update. * 2023-12-20 02:02:41 (1821) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-20 02:02:41 (155) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-20 02:02:41 (1168) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-20 02:02:41 (155) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-20 02:02:41 (155) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-20 02:02:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-20 02:02:41 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0mmkYKyrUo/ea_profile.json * 2023-12-20 02:02:44 (2294) [INFO] Backed up EA4 profile to /tmp/0mmkYKyrUo/ea_profile.json * 2023-12-20 02:02:47 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-21 01:57:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-21 01:57:57 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-21 01:57:57 (1774) [INFO] Checking if your system is up to date: * 2023-12-21 01:57:57 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-21 01:57:57 (4251) [INFO] * 2023-12-21 01:57:57 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-21 01:57:57 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-21 01:57:57 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-21 01:57:57 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-21 01:57:57 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-21 01:57:57 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-21 01:57:58 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-21 01:57:58 (4281) [INFO] * 2023-12-21 01:57:58 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-21 01:57:58 (4251) [INFO] * 2023-12-21 02:02:05 (4264) [INFO] * 2023-12-21 02:02:05 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-21 02:02:05 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-21 02:02:05 (4281) [INFO] * 2023-12-21 02:02:05 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-21 02:02:05 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-21 02:02:09 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-21 02:05:22 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-21 02:05:22 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-21 02:05:23 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-21 02:05:23 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-21 02:05:23 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-21 02:05:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-21 02:05:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/scZWQmiAGj/ea_profile.json * 2023-12-21 02:05:25 (2315) [INFO] Backed up EA4 profile to /tmp/scZWQmiAGj/ea_profile.json * 2023-12-21 02:05:27 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-22 01:56:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-22 01:56:58 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-22 01:56:58 (1774) [INFO] Checking if your system is up to date: * 2023-12-22 01:56:58 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-22 01:56:58 (4251) [INFO] * 2023-12-22 01:56:59 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-22 01:56:59 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-22 01:56:59 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-22 01:56:59 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-22 01:56:59 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-22 01:56:59 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-22 01:57:00 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-22 01:57:00 (4281) [INFO] * 2023-12-22 01:57:00 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-22 01:57:00 (4251) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] One of the configured repositories failed (Unknown), * 2023-12-22 01:57:56 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-22 01:57:56 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-22 01:57:56 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-22 01:57:56 (4264) [INFO] distribution release than is supported by the repository (and the * 2023-12-22 01:57:56 (4264) [INFO] packages for the previous distribution release still work). * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-22 01:57:56 (4264) [INFO] yum --disablerepo= ... * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-22 01:57:56 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-22 01:57:56 (4264) [INFO] again or use --enablerepo for temporary usage: * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] yum-config-manager --disable * 2023-12-22 01:57:56 (4264) [INFO] or * 2023-12-22 01:57:56 (4264) [INFO] subscription-manager repos --disable= * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-22 01:57:56 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-22 01:57:56 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-22 01:57:56 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-22 01:57:56 (4264) [INFO] compromise: * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-22 01:57:56 (4264) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-22 01:57:56 (4281) [INFO] * 2023-12-22 01:57:56 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-22 01:57:56 (1795) [INFO] Checking /scripts/sysup * 2023-12-22 01:57:56 (4250) [INFO] Running: /scripts/sysup * 2023-12-22 01:57:56 (4251) [INFO] * 2023-12-22 01:57:56 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-22 01:57:59 (4264) [INFO] All Needed Packages are already installed. * 2023-12-22 01:57:59 (4281) [INFO] * 2023-12-22 01:58:03 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-22 02:05:18 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-22 02:05:18 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-22 02:05:19 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-22 02:05:19 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-22 02:05:19 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-22 02:05:19 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-22 02:05:19 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eNstNNEQVJ/ea_profile.json * 2023-12-22 02:05:23 (2315) [INFO] Backed up EA4 profile to /tmp/eNstNNEQVJ/ea_profile.json * 2023-12-22 02:05:27 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-23 02:00:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-23 02:00:47 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-23 02:00:47 (1774) [INFO] Checking if your system is up to date: * 2023-12-23 02:00:47 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-23 02:00:47 (4251) [INFO] * 2023-12-23 02:00:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-23 02:00:48 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-23 02:00:48 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-23 02:00:48 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-23 02:00:48 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-23 02:00:48 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-23 02:00:49 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-23 02:00:49 (4281) [INFO] * 2023-12-23 02:00:49 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-23 02:00:49 (4251) [INFO] * 2023-12-23 02:03:43 (4264) [INFO] https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/8d3a830d1e86270cf55d1eafa421ce8a5d4caf258d748493669bc42fb383d117-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-12-23 02:03:43 (4264) [INFO] Trying other mirror. * 2023-12-23 02:03:43 (4264) [INFO] To address this issue please refer to the below wiki article * 2023-12-23 02:03:43 (4264) [INFO] * 2023-12-23 02:03:43 (4264) [INFO] https://wiki.centos.org/yum-errors * 2023-12-23 02:03:43 (4264) [INFO] * 2023-12-23 02:03:43 (4264) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-12-23 02:03:43 (4264) [INFO] * 2023-12-23 02:05:06 (4264) [INFO] * 2023-12-23 02:05:06 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-23 02:05:06 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-23 02:05:06 (4281) [INFO] * 2023-12-23 02:05:06 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-23 02:05:06 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-23 02:05:10 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-23 02:08:34 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-23 02:08:34 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-23 02:08:35 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-23 02:08:35 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-23 02:08:35 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-23 02:08:35 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-23 02:08:35 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Gh9aGOvcgy/ea_profile.json * 2023-12-23 02:08:38 (2315) [INFO] Backed up EA4 profile to /tmp/Gh9aGOvcgy/ea_profile.json * 2023-12-23 02:08:41 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-24 02:03:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-24 02:03:48 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-24 02:03:48 (1774) [INFO] Checking if your system is up to date: * 2023-12-24 02:03:48 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-24 02:03:48 (4251) [INFO] * 2023-12-24 02:03:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-24 02:03:48 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-24 02:03:48 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-24 02:03:48 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-24 02:03:48 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-24 02:03:48 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-24 02:03:49 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-24 02:03:49 (4281) [INFO] * 2023-12-24 02:03:49 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-24 02:03:49 (4251) [INFO] * 2023-12-24 02:07:46 (4264) [INFO] * 2023-12-24 02:07:46 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-24 02:07:46 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-24 02:07:46 (4281) [INFO] * 2023-12-24 02:07:46 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-24 02:07:46 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-24 02:07:48 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-24 02:11:13 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-24 02:11:13 (1634) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. * 2023-12-24 02:11:13 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-24 02:11:13 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-24 02:11:13 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-24 02:11:13 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-24 02:11:13 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-24 02:11:13 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-24 02:11:14 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-24 02:11:14 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FlLGUA0HTX/ea_profile.json * 2023-12-24 02:11:16 (2315) [INFO] Backed up EA4 profile to /tmp/FlLGUA0HTX/ea_profile.json * 2023-12-24 02:11:20 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-25 02:00:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-25 02:00:37 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-25 02:00:37 (1774) [INFO] Checking if your system is up to date: * 2023-12-25 02:00:37 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-25 02:00:37 (4251) [INFO] * 2023-12-25 02:00:37 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-25 02:00:37 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-25 02:00:37 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-25 02:00:37 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-25 02:00:37 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-25 02:00:37 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-25 02:00:38 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-25 02:00:38 (4281) [INFO] * 2023-12-25 02:00:38 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-25 02:00:38 (4251) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] One of the configured repositories failed (Unknown), * 2023-12-25 02:01:32 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-25 02:01:32 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-25 02:01:32 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-25 02:01:32 (4264) [INFO] distribution release than is supported by the repository (and the * 2023-12-25 02:01:32 (4264) [INFO] packages for the previous distribution release still work). * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-25 02:01:32 (4264) [INFO] yum --disablerepo= ... * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-25 02:01:32 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-25 02:01:32 (4264) [INFO] again or use --enablerepo for temporary usage: * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] yum-config-manager --disable * 2023-12-25 02:01:32 (4264) [INFO] or * 2023-12-25 02:01:32 (4264) [INFO] subscription-manager repos --disable= * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-25 02:01:32 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-25 02:01:32 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-25 02:01:32 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-25 02:01:32 (4264) [INFO] compromise: * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-25 02:01:32 (4264) [INFO] * 2023-12-25 02:01:32 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-25 02:01:32 (4281) [INFO] * 2023-12-25 02:01:32 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-25 02:01:32 (1795) [INFO] Checking /scripts/sysup * 2023-12-25 02:01:32 (4250) [INFO] Running: /scripts/sysup * 2023-12-25 02:01:32 (4251) [INFO] * 2023-12-25 02:01:33 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-25 02:01:35 (4264) [INFO] All Needed Packages are already installed. * 2023-12-25 02:01:35 (4281) [INFO] * 2023-12-25 02:01:38 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-25 02:08:49 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-25 02:08:49 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-25 02:08:49 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-25 02:08:49 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-25 02:08:49 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-25 02:08:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-25 02:08:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_cKzDre_tK/ea_profile.json * 2023-12-25 02:08:51 (2315) [INFO] Backed up EA4 profile to /tmp/_cKzDre_tK/ea_profile.json * 2023-12-25 02:08:55 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-26 02:03:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-26 02:03:08 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-26 02:03:08 (1774) [INFO] Checking if your system is up to date: * 2023-12-26 02:03:08 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-26 02:03:08 (4251) [INFO] * 2023-12-26 02:03:09 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-26 02:03:09 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-26 02:03:09 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-26 02:03:09 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-26 02:03:09 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-26 02:03:09 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-26 02:03:09 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-26 02:03:09 (4281) [INFO] * 2023-12-26 02:03:09 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-26 02:03:09 (4251) [INFO] * 2023-12-26 02:07:32 (4264) [INFO] * 2023-12-26 02:07:32 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-26 02:07:32 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-26 02:07:32 (4281) [INFO] * 2023-12-26 02:07:32 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-26 02:07:32 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-26 02:07:35 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-26 02:11:08 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-26 02:11:08 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-26 02:11:09 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-26 02:11:09 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-26 02:11:09 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-26 02:11:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-26 02:11:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QVvzGcsT1y/ea_profile.json * 2023-12-26 02:11:11 (2315) [INFO] Backed up EA4 profile to /tmp/QVvzGcsT1y/ea_profile.json * 2023-12-26 02:11:14 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-27 01:57:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-27 01:57:12 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-27 01:57:12 (1774) [INFO] Checking if your system is up to date: * 2023-12-27 01:57:12 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-27 01:57:12 (4251) [INFO] * 2023-12-27 01:57:13 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-27 01:57:13 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-27 01:57:13 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-27 01:57:13 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-27 01:57:13 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-27 01:57:13 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-27 01:57:13 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-27 01:57:13 (4281) [INFO] * 2023-12-27 01:57:13 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-27 01:57:13 (4251) [INFO] * 2023-12-27 02:01:45 (4264) [INFO] * 2023-12-27 02:01:45 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-27 02:01:45 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-27 02:01:45 (4281) [INFO] * 2023-12-27 02:01:45 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-27 02:01:45 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-27 02:01:49 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-27 02:05:50 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-27 02:05:50 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30026 milliseconds with 0 out of 0 bytes received') * 2023-12-27 02:05:50 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-27 02:05:50 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-27 02:05:50 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-27 02:05:51 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-27 02:05:51 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-27 02:05:51 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-27 02:05:51 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-27 02:05:51 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cGk6aKaHQ9/ea_profile.json * 2023-12-27 02:05:53 (2315) [INFO] Backed up EA4 profile to /tmp/cGk6aKaHQ9/ea_profile.json * 2023-12-27 02:05:55 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-28 02:00:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-28 02:00:43 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-28 02:00:43 (1774) [INFO] Checking if your system is up to date: * 2023-12-28 02:00:43 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-28 02:00:43 (4251) [INFO] * 2023-12-28 02:00:44 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-28 02:00:44 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-28 02:00:44 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-28 02:00:44 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-28 02:00:44 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-28 02:00:44 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-28 02:00:44 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-28 02:00:44 (4281) [INFO] * 2023-12-28 02:00:44 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-28 02:00:44 (4251) [INFO] * 2023-12-28 02:04:47 (4264) [INFO] * 2023-12-28 02:04:47 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-28 02:04:47 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-28 02:04:48 (4281) [INFO] * 2023-12-28 02:04:48 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-28 02:04:48 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-28 02:04:50 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-28 02:07:18 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-28 02:07:18 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-28 02:07:19 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-28 02:07:19 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-28 02:07:19 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-28 02:07:19 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-28 02:07:19 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/poKjSxXzwW/ea_profile.json * 2023-12-28 02:07:21 (2315) [INFO] Backed up EA4 profile to /tmp/poKjSxXzwW/ea_profile.json * 2023-12-28 02:07:23 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-29 01:54:32 (307) [WARN] Unknown error while checking blockers: Cpanel::Exception::HTTP::Network/(XID 3qhkbf) The system failed to send an HTTP “GET” request to “https://raw.githubusercontent.com/cpanel/elevate/release/version” because of an error: Could not connect to 'raw.githubusercontent.com:443': Network is unreachable at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 137. Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x365dc80), "GET", "https://raw.githubusercontent.com/cpanel/elevate/release/version", HASH(0x36483b0)) called at (eval 6) line 6 HTTP::Tiny::get(Cpanel::HTTP::Client=HASH(0x365dc80), "https://raw.githubusercontent.com/cpanel/elevate/release/version") called at /usr/local/cpanel/scripts/elevate-cpanel line 4323 Elevate::Script::_build_latest_version(Elevate::Script=HASH(0x36685f0)) called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Simple/Accessor.pm line 259 Simple::Accessor::__ANON__(Elevate::Script=HASH(0x36685f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 4333 Elevate::Script::is_out_of_date(Elevate::Script=HASH(0x36685f0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 898 Elevate::Blockers::ElevateScript::_is_up_to_date(Elevate::Blockers::ElevateScript=HASH(0x1f6f0c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 873 Elevate::Blockers::ElevateScript::check(Elevate::Blockers::ElevateScript=HASH(0x1f6f0c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 348 Elevate::Blockers::_check_single_blocker(Elevate::Blockers=HASH(0x36005c0), "ElevateScript") called at /usr/local/cpanel/scripts/elevate-cpanel line 336 Elevate::Blockers::_check_all_blockers(Elevate::Blockers=HASH(0x36005c0)) called at /usr/local/cpanel/scripts/elevate-cpanel line 299 eval {...} called at /usr/local/cpanel/scripts/elevate-cpanel line 299 Elevate::Blockers::_has_blockers(Elevate::Blockers=HASH(0x36005c0), 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 264 Elevate::Blockers::check(Elevate::Blockers=HASH(0x36005c0), "dry_run", 1) called at /usr/local/cpanel/scripts/elevate-cpanel line 5048 cpev::run("cpev", "--check", "/var/cpanel/elevate-blockers.security-advisor") called at /usr/local/cpanel/scripts/elevate-cpanel line 4994 * 2023-12-29 01:54:32 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-30 02:04:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-30 02:04:04 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-30 02:04:04 (1774) [INFO] Checking if your system is up to date: * 2023-12-30 02:04:04 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-30 02:04:04 (4251) [INFO] * 2023-12-30 02:04:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-30 02:04:05 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-30 02:04:05 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-30 02:04:05 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-30 02:04:05 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-30 02:04:05 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-30 02:04:05 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-30 02:04:05 (4281) [INFO] * 2023-12-30 02:04:05 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-30 02:04:05 (4251) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] One of the configured repositories failed (Unknown), * 2023-12-30 02:05:00 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-30 02:05:00 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-30 02:05:00 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-30 02:05:00 (4264) [INFO] distribution release than is supported by the repository (and the * 2023-12-30 02:05:00 (4264) [INFO] packages for the previous distribution release still work). * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-30 02:05:00 (4264) [INFO] yum --disablerepo= ... * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-30 02:05:00 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-30 02:05:00 (4264) [INFO] again or use --enablerepo for temporary usage: * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] yum-config-manager --disable * 2023-12-30 02:05:00 (4264) [INFO] or * 2023-12-30 02:05:00 (4264) [INFO] subscription-manager repos --disable= * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-30 02:05:00 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-30 02:05:00 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-30 02:05:00 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-30 02:05:00 (4264) [INFO] compromise: * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-30 02:05:00 (4264) [INFO] * 2023-12-30 02:05:00 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-30 02:05:00 (4281) [INFO] * 2023-12-30 02:05:00 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-30 02:05:00 (1795) [INFO] Checking /scripts/sysup * 2023-12-30 02:05:00 (4250) [INFO] Running: /scripts/sysup * 2023-12-30 02:05:00 (4251) [INFO] * 2023-12-30 02:05:01 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-30 02:05:04 (4264) [INFO] All Needed Packages are already installed. * 2023-12-30 02:05:04 (4281) [INFO] * 2023-12-30 02:05:07 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-30 02:14:02 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-12-30 02:14:02 (1634) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.us.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/69c3d9cd3c88bbf364bb0876a71e7c43c4703f8abb92cb9540240fefe80c6998-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.steadfastnet.com/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.arizona.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.maine.edu/CentOS/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nnenix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.clarkson.edu/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://paducahix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/a08d753160a0cf6bf11e6fd2c2e78d83ac1d8ab9a1afabaa1ec9caa68cc0b2e6-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2023-12-30 02:14:02 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-12-30 02:14:02 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-30 02:14:02 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-30 02:14:03 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-30 02:14:03 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-30 02:14:03 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-30 02:14:03 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-30 02:14:03 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rO6VsOAhbG/ea_profile.json * 2023-12-30 02:14:06 (2315) [INFO] Backed up EA4 profile to /tmp/rO6VsOAhbG/ea_profile.json * 2023-12-30 02:14:10 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-31 01:56:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2023-12-31 01:56:10 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-31 01:56:10 (1774) [INFO] Checking if your system is up to date: * 2023-12-31 01:56:10 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-31 01:56:10 (4251) [INFO] * 2023-12-31 01:56:11 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-31 01:56:11 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2023-12-31 01:56:11 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-31 01:56:11 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-31 01:56:11 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-31 01:56:11 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2023-12-31 01:56:11 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2023-12-31 01:56:11 (4281) [INFO] * 2023-12-31 01:56:11 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-31 01:56:11 (4251) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] One of the configured repositories failed (Unknown), * 2023-12-31 01:57:08 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-12-31 01:57:08 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-12-31 01:57:08 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2023-12-31 01:57:08 (4264) [INFO] distribution release than is supported by the repository (and the * 2023-12-31 01:57:08 (4264) [INFO] packages for the previous distribution release still work). * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2023-12-31 01:57:08 (4264) [INFO] yum --disablerepo= ... * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-12-31 01:57:08 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2023-12-31 01:57:08 (4264) [INFO] again or use --enablerepo for temporary usage: * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] yum-config-manager --disable * 2023-12-31 01:57:08 (4264) [INFO] or * 2023-12-31 01:57:08 (4264) [INFO] subscription-manager repos --disable= * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-12-31 01:57:08 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-12-31 01:57:08 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-12-31 01:57:08 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-12-31 01:57:08 (4264) [INFO] compromise: * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-12-31 01:57:08 (4264) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-12-31 01:57:08 (4281) [INFO] * 2023-12-31 01:57:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-31 01:57:08 (1795) [INFO] Checking /scripts/sysup * 2023-12-31 01:57:08 (4250) [INFO] Running: /scripts/sysup * 2023-12-31 01:57:08 (4251) [INFO] * 2023-12-31 01:57:08 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-12-31 01:57:10 (4264) [INFO] All Needed Packages are already installed. * 2023-12-31 01:57:10 (4281) [INFO] * 2023-12-31 01:57:14 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2023-12-31 02:04:10 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2023-12-31 02:04:10 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2023-12-31 02:04:11 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2023-12-31 02:04:11 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2023-12-31 02:04:11 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2023-12-31 02:04:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-31 02:04:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ki57HBMGXP/ea_profile.json * 2023-12-31 02:04:13 (2315) [INFO] Backed up EA4 profile to /tmp/ki57HBMGXP/ea_profile.json * 2023-12-31 02:04:16 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-01 02:00:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-01 02:00:14 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-01 02:00:14 (1774) [INFO] Checking if your system is up to date: * 2024-01-01 02:00:14 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-01 02:00:14 (4251) [INFO] * 2024-01-01 02:00:15 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-01 02:00:15 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-01 02:00:15 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-01 02:00:15 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-01 02:00:15 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-01 02:00:15 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-01 02:00:15 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-01 02:00:15 (4281) [INFO] * 2024-01-01 02:00:15 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-01 02:00:15 (4251) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-01 02:01:11 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-01 02:01:11 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-01 02:01:11 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-01 02:01:11 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-01 02:01:11 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-01 02:01:11 (4264) [INFO] yum --disablerepo= ... * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-01 02:01:11 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-01 02:01:11 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] yum-config-manager --disable * 2024-01-01 02:01:11 (4264) [INFO] or * 2024-01-01 02:01:11 (4264) [INFO] subscription-manager repos --disable= * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-01 02:01:11 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-01 02:01:11 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-01 02:01:11 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-01 02:01:11 (4264) [INFO] compromise: * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-01 02:01:11 (4264) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-01 02:01:11 (4281) [INFO] * 2024-01-01 02:01:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-01 02:01:11 (1795) [INFO] Checking /scripts/sysup * 2024-01-01 02:01:11 (4250) [INFO] Running: /scripts/sysup * 2024-01-01 02:01:11 (4251) [INFO] * 2024-01-01 02:01:11 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-01 02:01:12 (4264) [INFO] All Needed Packages are already installed. * 2024-01-01 02:01:12 (4281) [INFO] * 2024-01-01 02:01:15 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-01 02:08:11 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-01 02:08:11 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-01 02:08:11 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-01 02:08:11 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-01 02:08:11 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-01 02:08:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-01 02:08:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YvjTi6TvAr/ea_profile.json * 2024-01-01 02:08:13 (2315) [INFO] Backed up EA4 profile to /tmp/YvjTi6TvAr/ea_profile.json * 2024-01-01 02:08:16 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-02 02:00:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-02 02:00:14 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-02 02:00:14 (1774) [INFO] Checking if your system is up to date: * 2024-01-02 02:00:14 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-02 02:00:14 (4251) [INFO] * 2024-01-02 02:00:14 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-02 02:00:14 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-02 02:00:14 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-02 02:00:14 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-02 02:00:14 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-02 02:00:14 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-02 02:00:15 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-02 02:00:15 (4281) [INFO] * 2024-01-02 02:00:15 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-02 02:00:15 (4251) [INFO] * 2024-01-02 02:04:35 (4264) [INFO] * 2024-01-02 02:04:35 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-02 02:04:35 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-02 02:04:35 (4281) [INFO] * 2024-01-02 02:04:35 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-02 02:04:35 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-02 02:04:37 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-02 02:08:07 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-02 02:08:07 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-02 02:08:07 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-02 02:08:07 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-02 02:08:07 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-02 02:08:07 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-02 02:08:07 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/95EVhIoOaF/ea_profile.json * 2024-01-02 02:08:10 (2315) [INFO] Backed up EA4 profile to /tmp/95EVhIoOaF/ea_profile.json * 2024-01-02 02:08:13 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-03 02:03:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-03 02:03:55 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-03 02:03:55 (1774) [INFO] Checking if your system is up to date: * 2024-01-03 02:03:55 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-03 02:03:55 (4251) [INFO] * 2024-01-03 02:03:56 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-03 02:03:56 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-03 02:03:56 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-03 02:03:56 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-03 02:03:56 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-03 02:03:56 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-03 02:03:57 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-03 02:03:57 (4281) [INFO] * 2024-01-03 02:03:57 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-03 02:03:57 (4251) [INFO] * 2024-01-03 02:07:53 (4264) [INFO] * 2024-01-03 02:07:53 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-03 02:07:53 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-03 02:07:53 (4281) [INFO] * 2024-01-03 02:07:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-03 02:07:53 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-03 02:07:56 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-03 02:11:02 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-03 02:11:02 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30658 milliseconds') * 2024-01-03 02:11:02 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-03 02:11:02 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-03 02:11:02 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-03 02:11:03 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-03 02:11:03 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-03 02:11:03 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-03 02:11:03 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-03 02:11:03 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uw5tQuu6m2/ea_profile.json * 2024-01-03 02:11:04 (2315) [INFO] Backed up EA4 profile to /tmp/uw5tQuu6m2/ea_profile.json * 2024-01-03 02:11:07 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-04 02:00:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-04 02:00:50 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-04 02:00:50 (1774) [INFO] Checking if your system is up to date: * 2024-01-04 02:00:50 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-04 02:00:50 (4251) [INFO] * 2024-01-04 02:00:50 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-04 02:00:50 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-04 02:00:50 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-04 02:00:50 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-04 02:00:50 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-04 02:00:50 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-04 02:00:51 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-04 02:00:51 (4281) [INFO] * 2024-01-04 02:00:51 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-04 02:00:51 (4251) [INFO] * 2024-01-04 02:05:13 (4264) [INFO] * 2024-01-04 02:05:13 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-04 02:05:13 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-04 02:05:14 (4281) [INFO] * 2024-01-04 02:05:14 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-04 02:05:14 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-04 02:05:16 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-04 02:09:00 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-04 02:09:00 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2024-01-04 02:09:00 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-04 02:09:00 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-04 02:09:00 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-04 02:09:01 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-04 02:09:01 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-04 02:09:01 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-04 02:09:01 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-04 02:09:01 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TsYLJUEtxe/ea_profile.json * 2024-01-04 02:09:04 (2315) [INFO] Backed up EA4 profile to /tmp/TsYLJUEtxe/ea_profile.json * 2024-01-04 02:09:07 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-05 02:01:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-05 02:01:58 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-05 02:01:58 (1774) [INFO] Checking if your system is up to date: * 2024-01-05 02:01:58 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-05 02:01:58 (4251) [INFO] * 2024-01-05 02:01:58 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-05 02:01:59 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-05 02:01:59 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-05 02:01:59 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-05 02:01:59 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-05 02:01:59 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-05 02:01:59 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-05 02:01:59 (4281) [INFO] * 2024-01-05 02:01:59 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-05 02:01:59 (4251) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-05 02:02:54 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-05 02:02:54 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-05 02:02:54 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-05 02:02:54 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-05 02:02:54 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-05 02:02:54 (4264) [INFO] yum --disablerepo= ... * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-05 02:02:54 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-05 02:02:54 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] yum-config-manager --disable * 2024-01-05 02:02:54 (4264) [INFO] or * 2024-01-05 02:02:54 (4264) [INFO] subscription-manager repos --disable= * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-05 02:02:54 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-05 02:02:54 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-05 02:02:54 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-05 02:02:54 (4264) [INFO] compromise: * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-05 02:02:54 (4264) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-05 02:02:54 (4281) [INFO] * 2024-01-05 02:02:54 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-05 02:02:54 (1795) [INFO] Checking /scripts/sysup * 2024-01-05 02:02:54 (4250) [INFO] Running: /scripts/sysup * 2024-01-05 02:02:54 (4251) [INFO] * 2024-01-05 02:02:54 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-05 02:02:56 (4264) [INFO] All Needed Packages are already installed. * 2024-01-05 02:02:56 (4281) [INFO] * 2024-01-05 02:02:58 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-05 02:09:40 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-05 02:09:40 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-05 02:09:41 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-05 02:09:41 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-05 02:09:41 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-05 02:09:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-05 02:09:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UY5JhRZuF5/ea_profile.json * 2024-01-05 02:09:43 (2315) [INFO] Backed up EA4 profile to /tmp/UY5JhRZuF5/ea_profile.json * 2024-01-05 02:09:45 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-06 02:01:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-06 02:01:48 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-06 02:01:48 (1774) [INFO] Checking if your system is up to date: * 2024-01-06 02:01:48 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-06 02:01:48 (4251) [INFO] * 2024-01-06 02:01:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-06 02:01:49 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-06 02:01:49 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-06 02:01:49 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-06 02:01:49 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-06 02:01:49 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-06 02:01:49 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-06 02:01:49 (4281) [INFO] * 2024-01-06 02:01:49 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-06 02:01:49 (4251) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-06 02:02:46 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-06 02:02:46 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-06 02:02:46 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-06 02:02:46 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-06 02:02:46 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-06 02:02:46 (4264) [INFO] yum --disablerepo= ... * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-06 02:02:46 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-06 02:02:46 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] yum-config-manager --disable * 2024-01-06 02:02:46 (4264) [INFO] or * 2024-01-06 02:02:46 (4264) [INFO] subscription-manager repos --disable= * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-06 02:02:46 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-06 02:02:46 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-06 02:02:46 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-06 02:02:46 (4264) [INFO] compromise: * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-06 02:02:46 (4264) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-06 02:02:46 (4281) [INFO] * 2024-01-06 02:02:46 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-06 02:02:46 (1795) [INFO] Checking /scripts/sysup * 2024-01-06 02:02:46 (4250) [INFO] Running: /scripts/sysup * 2024-01-06 02:02:46 (4251) [INFO] * 2024-01-06 02:02:46 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-06 02:02:48 (4264) [INFO] All Needed Packages are already installed. * 2024-01-06 02:02:48 (4281) [INFO] * 2024-01-06 02:02:51 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-06 02:03:48 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-06 02:03:48 (1634) [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 * 2024-01-06 02:03:48 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-06 02:03:48 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-06 02:03:48 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-06 02:03:49 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-06 02:03:49 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-06 02:03:49 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-06 02:03:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-06 02:03:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NuCZhBNvqt/ea_profile.json * 2024-01-06 02:08:15 (2315) [INFO] Backed up EA4 profile to /tmp/NuCZhBNvqt/ea_profile.json * 2024-01-06 02:08:18 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-07 01:55:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-07 01:55:48 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-07 01:55:48 (1774) [INFO] Checking if your system is up to date: * 2024-01-07 01:55:48 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-07 01:55:48 (4251) [INFO] * 2024-01-07 01:55:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-07 01:55:48 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-07 01:55:48 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-07 01:55:48 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-07 01:55:48 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-07 01:55:48 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-07 01:55:48 (4264) [INFO] Other repos take up 780 k of disk space (use --verbose for details) * 2024-01-07 01:55:48 (4281) [INFO] * 2024-01-07 01:55:48 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-07 01:55:48 (4251) [INFO] * 2024-01-07 02:00:07 (4264) [INFO] * 2024-01-07 02:00:07 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-07 02:00:07 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-07 02:00:07 (4281) [INFO] * 2024-01-07 02:00:07 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-07 02:00:07 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-07 02:00:09 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-07 02:03:21 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-07 02:03:21 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-07 02:03:22 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-07 02:03:22 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-07 02:03:22 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-07 02:03:22 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-07 02:03:22 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RwZtEYX10m/ea_profile.json * 2024-01-07 02:03:23 (2315) [INFO] Backed up EA4 profile to /tmp/RwZtEYX10m/ea_profile.json * 2024-01-07 02:03:26 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-08 02:00:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-08 02:01:00 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-08 02:01:00 (1774) [INFO] Checking if your system is up to date: * 2024-01-08 02:01:00 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-08 02:01:00 (4251) [INFO] * 2024-01-08 02:01:00 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-08 02:01:00 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-08 02:01:00 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-08 02:01:00 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-08 02:01:00 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-08 02:01:00 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-08 02:01:01 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-08 02:01:01 (4281) [INFO] * 2024-01-08 02:01:01 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-08 02:01:01 (4251) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-08 02:01:56 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-08 02:01:56 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-08 02:01:56 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-08 02:01:56 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-08 02:01:56 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-08 02:01:56 (4264) [INFO] yum --disablerepo= ... * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-08 02:01:56 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-08 02:01:56 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] yum-config-manager --disable * 2024-01-08 02:01:56 (4264) [INFO] or * 2024-01-08 02:01:56 (4264) [INFO] subscription-manager repos --disable= * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-08 02:01:56 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-08 02:01:56 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-08 02:01:56 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-08 02:01:56 (4264) [INFO] compromise: * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-08 02:01:56 (4264) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-08 02:01:56 (4281) [INFO] * 2024-01-08 02:01:56 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-08 02:01:56 (1795) [INFO] Checking /scripts/sysup * 2024-01-08 02:01:56 (4250) [INFO] Running: /scripts/sysup * 2024-01-08 02:01:56 (4251) [INFO] * 2024-01-08 02:01:56 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-08 02:01:58 (4264) [INFO] All Needed Packages are already installed. * 2024-01-08 02:01:58 (4281) [INFO] * 2024-01-08 02:02:00 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-08 02:09:09 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-08 02:09:09 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-08 02:09:09 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-08 02:09:09 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-08 02:09:09 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-08 02:09:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-08 02:09:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Uxpb2YDQZd/ea_profile.json * 2024-01-08 02:09:11 (2315) [INFO] Backed up EA4 profile to /tmp/Uxpb2YDQZd/ea_profile.json * 2024-01-08 02:09:13 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-09 01:56:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-09 01:56:02 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-09 01:56:02 (1774) [INFO] Checking if your system is up to date: * 2024-01-09 01:56:02 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-09 01:56:02 (4251) [INFO] * 2024-01-09 01:56:02 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-09 01:56:02 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-09 01:56:02 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-09 01:56:02 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-09 01:56:02 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-09 01:56:02 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-09 01:56:03 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-09 01:56:03 (4281) [INFO] * 2024-01-09 01:56:03 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-09 01:56:03 (4251) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-09 01:56:57 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-09 01:56:57 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-09 01:56:57 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-09 01:56:57 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-09 01:56:57 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-09 01:56:57 (4264) [INFO] yum --disablerepo= ... * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-09 01:56:57 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-09 01:56:57 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] yum-config-manager --disable * 2024-01-09 01:56:57 (4264) [INFO] or * 2024-01-09 01:56:57 (4264) [INFO] subscription-manager repos --disable= * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-09 01:56:57 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-09 01:56:57 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-09 01:56:57 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-09 01:56:57 (4264) [INFO] compromise: * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-09 01:56:57 (4264) [INFO] * 2024-01-09 01:56:57 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-09 01:56:57 (4281) [INFO] * 2024-01-09 01:56:57 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-09 01:56:57 (1795) [INFO] Checking /scripts/sysup * 2024-01-09 01:56:57 (4250) [INFO] Running: /scripts/sysup * 2024-01-09 01:56:57 (4251) [INFO] * 2024-01-09 01:56:58 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-09 01:56:59 (4264) [INFO] All Needed Packages are already installed. * 2024-01-09 01:56:59 (4281) [INFO] * 2024-01-09 01:57:03 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-09 01:57:57 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-09 01:57:57 (1634) [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 * 2024-01-09 01:57:57 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-09 01:57:57 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-09 01:57:57 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-09 01:57:58 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-09 01:57:58 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-09 01:57:58 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-09 01:57:58 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-09 01:57:58 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j_dozAf9b5/ea_profile.json * 2024-01-09 02:02:26 (2315) [INFO] Backed up EA4 profile to /tmp/j_dozAf9b5/ea_profile.json * 2024-01-09 02:02:28 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-10 01:55:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-10 01:55:19 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-10 01:55:19 (1774) [INFO] Checking if your system is up to date: * 2024-01-10 01:55:19 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-10 01:55:19 (4251) [INFO] * 2024-01-10 01:55:20 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-10 01:55:20 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-10 01:55:20 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-10 01:55:20 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-10 01:55:20 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-10 01:55:20 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-10 01:55:21 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-10 01:55:21 (4281) [INFO] * 2024-01-10 01:55:21 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-10 01:55:21 (4251) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-10 01:56:16 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-10 01:56:16 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-10 01:56:16 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-10 01:56:16 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-10 01:56:16 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-10 01:56:16 (4264) [INFO] yum --disablerepo= ... * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-10 01:56:16 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-10 01:56:16 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] yum-config-manager --disable * 2024-01-10 01:56:16 (4264) [INFO] or * 2024-01-10 01:56:16 (4264) [INFO] subscription-manager repos --disable= * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-10 01:56:16 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-10 01:56:16 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-10 01:56:16 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-10 01:56:16 (4264) [INFO] compromise: * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-10 01:56:16 (4264) [INFO] * 2024-01-10 01:56:16 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-10 01:56:16 (4281) [INFO] * 2024-01-10 01:56:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-10 01:56:16 (1795) [INFO] Checking /scripts/sysup * 2024-01-10 01:56:16 (4250) [INFO] Running: /scripts/sysup * 2024-01-10 01:56:16 (4251) [INFO] * 2024-01-10 01:56:17 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-10 01:56:19 (4264) [INFO] All Needed Packages are already installed. * 2024-01-10 01:56:19 (4281) [INFO] * 2024-01-10 01:56:21 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-10 01:57:16 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-10 01:57:16 (1634) [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 * 2024-01-10 01:57:16 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-10 01:57:16 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-10 01:57:16 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-10 01:57:16 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-10 01:57:16 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-10 01:57:16 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-10 01:57:16 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-10 01:57:16 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OCY7Zz0ENl/ea_profile.json * 2024-01-10 01:58:42 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OCY7Zz0ENl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294. * 2024-01-10 01:58:42 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-11 02:12:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-11 02:12:52 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-11 02:12:52 (1774) [INFO] Checking if your system is up to date: * 2024-01-11 02:12:52 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-11 02:12:52 (4251) [INFO] * 2024-01-11 02:12:52 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-11 02:12:52 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-11 02:12:52 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-11 02:12:52 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-11 02:12:52 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-11 02:12:52 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-11 02:12:53 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-11 02:12:53 (4281) [INFO] * 2024-01-11 02:12:53 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-11 02:12:53 (4251) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-11 02:13:48 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-11 02:13:48 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-11 02:13:48 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-11 02:13:48 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-11 02:13:48 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-11 02:13:48 (4264) [INFO] yum --disablerepo= ... * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-11 02:13:48 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-11 02:13:48 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] yum-config-manager --disable * 2024-01-11 02:13:48 (4264) [INFO] or * 2024-01-11 02:13:48 (4264) [INFO] subscription-manager repos --disable= * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-11 02:13:48 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-11 02:13:48 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-11 02:13:48 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-11 02:13:48 (4264) [INFO] compromise: * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-11 02:13:48 (4264) [INFO] * 2024-01-11 02:13:48 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-11 02:13:48 (4281) [INFO] * 2024-01-11 02:13:48 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-11 02:13:48 (1795) [INFO] Checking /scripts/sysup * 2024-01-11 02:13:48 (4250) [INFO] Running: /scripts/sysup * 2024-01-11 02:13:48 (4251) [INFO] * 2024-01-11 02:13:49 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-11 02:13:51 (4264) [INFO] All Needed Packages are already installed. * 2024-01-11 02:13:51 (4281) [INFO] * 2024-01-11 02:13:53 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-11 02:21:33 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-11 02:21:33 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-11 02:21:34 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-11 02:21:34 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-11 02:21:34 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-11 02:21:34 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-11 02:21:34 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kDE6x7f2Pb/ea_profile.json * 2024-01-11 02:21:36 (2315) [INFO] Backed up EA4 profile to /tmp/kDE6x7f2Pb/ea_profile.json * 2024-01-11 02:21:40 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-12 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-12 02:02:09 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-12 02:02:10 (1774) [INFO] Checking if your system is up to date: * 2024-01-12 02:02:10 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-12 02:02:10 (4251) [INFO] * 2024-01-12 02:02:10 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-12 02:02:10 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-12 02:02:10 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-12 02:02:10 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-12 02:02:10 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-12 02:02:10 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-12 02:02:10 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-12 02:02:10 (4281) [INFO] * 2024-01-12 02:02:10 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-12 02:02:10 (4251) [INFO] * 2024-01-12 02:06:51 (4264) [INFO] * 2024-01-12 02:06:51 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-12 02:06:51 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-12 02:06:52 (4281) [INFO] * 2024-01-12 02:06:52 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-12 02:06:52 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-12 02:06:54 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-12 02:10:40 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-12 02:10:40 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30065 milliseconds') * 2024-01-12 02:10:40 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-12 02:10:40 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-12 02:10:40 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-12 02:10:41 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-12 02:10:41 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-12 02:10:41 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-12 02:10:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-12 02:10:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PNlUYNJO3_/ea_profile.json * 2024-01-12 02:10:44 (2315) [INFO] Backed up EA4 profile to /tmp/PNlUYNJO3_/ea_profile.json * 2024-01-12 02:10:48 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-13 02:03:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-13 02:03:53 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-13 02:03:53 (1774) [INFO] Checking if your system is up to date: * 2024-01-13 02:03:53 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-13 02:03:53 (4251) [INFO] * 2024-01-13 02:03:53 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-13 02:03:53 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-13 02:03:53 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-13 02:03:53 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-13 02:03:53 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-13 02:03:53 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-13 02:03:54 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-13 02:03:54 (4281) [INFO] * 2024-01-13 02:03:54 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-13 02:03:54 (4251) [INFO] * 2024-01-13 02:08:17 (4264) [INFO] * 2024-01-13 02:08:17 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-13 02:08:17 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-13 02:08:17 (4281) [INFO] * 2024-01-13 02:08:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-13 02:08:17 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-13 02:08:21 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-13 02:11:49 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-13 02:11:49 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-13 02:11:50 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-13 02:11:50 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-13 02:11:50 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-13 02:11:50 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-13 02:11:50 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6EKtdlZHCO/ea_profile.json * 2024-01-13 02:11:51 (2315) [INFO] Backed up EA4 profile to /tmp/6EKtdlZHCO/ea_profile.json * 2024-01-13 02:11:55 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-14 01:56:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-14 01:56:09 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-14 01:56:09 (1774) [INFO] Checking if your system is up to date: * 2024-01-14 01:56:09 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-14 01:56:09 (4251) [INFO] * 2024-01-14 01:56:10 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-14 01:56:10 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-14 01:56:10 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-14 01:56:10 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-14 01:56:10 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-14 01:56:10 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-14 01:56:10 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-14 01:56:10 (4281) [INFO] * 2024-01-14 01:56:10 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-14 01:56:10 (4251) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-14 01:57:05 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-14 01:57:05 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-14 01:57:05 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-14 01:57:05 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-14 01:57:05 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-14 01:57:05 (4264) [INFO] yum --disablerepo= ... * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-14 01:57:05 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-14 01:57:05 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] yum-config-manager --disable * 2024-01-14 01:57:05 (4264) [INFO] or * 2024-01-14 01:57:05 (4264) [INFO] subscription-manager repos --disable= * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-14 01:57:05 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-14 01:57:05 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-14 01:57:05 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-14 01:57:05 (4264) [INFO] compromise: * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-14 01:57:05 (4264) [INFO] * 2024-01-14 01:57:05 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-14 01:57:05 (4281) [INFO] * 2024-01-14 01:57:05 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-14 01:57:05 (1795) [INFO] Checking /scripts/sysup * 2024-01-14 01:57:05 (4250) [INFO] Running: /scripts/sysup * 2024-01-14 01:57:05 (4251) [INFO] * 2024-01-14 01:57:06 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-14 01:57:07 (4264) [INFO] All Needed Packages are already installed. * 2024-01-14 01:57:07 (4281) [INFO] * 2024-01-14 01:57:10 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-14 01:58:04 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-14 01:58:04 (1634) [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 * 2024-01-14 01:58:04 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-14 01:58:04 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-14 01:58:04 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-14 01:58:05 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-14 01:58:05 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-14 01:58:05 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-14 01:58:05 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-14 01:58:05 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Tu4MtpR7Z8/ea_profile.json * 2024-01-14 01:59:32 (307) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Tu4MtpR7Z8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2294. * 2024-01-14 01:59:32 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-15 02:01:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-15 02:01:25 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-15 02:01:25 (1774) [INFO] Checking if your system is up to date: * 2024-01-15 02:01:25 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-15 02:01:25 (4251) [INFO] * 2024-01-15 02:01:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-15 02:01:26 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-15 02:01:26 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-15 02:01:26 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-15 02:01:26 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-15 02:01:26 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-15 02:01:26 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-15 02:01:26 (4281) [INFO] * 2024-01-15 02:01:26 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-15 02:01:26 (4251) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-15 02:02:22 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-15 02:02:22 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-15 02:02:22 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-15 02:02:22 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-15 02:02:22 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-15 02:02:22 (4264) [INFO] yum --disablerepo= ... * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-15 02:02:22 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-15 02:02:22 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] yum-config-manager --disable * 2024-01-15 02:02:22 (4264) [INFO] or * 2024-01-15 02:02:22 (4264) [INFO] subscription-manager repos --disable= * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-15 02:02:22 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-15 02:02:22 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-15 02:02:22 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-15 02:02:22 (4264) [INFO] compromise: * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-15 02:02:22 (4264) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-15 02:02:22 (4281) [INFO] * 2024-01-15 02:02:22 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-15 02:02:22 (1795) [INFO] Checking /scripts/sysup * 2024-01-15 02:02:22 (4250) [INFO] Running: /scripts/sysup * 2024-01-15 02:02:22 (4251) [INFO] * 2024-01-15 02:02:22 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-15 02:02:24 (4264) [INFO] All Needed Packages are already installed. * 2024-01-15 02:02:24 (4281) [INFO] * 2024-01-15 02:02:26 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-15 02:09:23 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-15 02:09:23 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-15 02:09:24 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-15 02:09:24 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-15 02:09:24 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-15 02:09:24 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-15 02:09:24 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VUliNi8OvW/ea_profile.json * 2024-01-15 02:09:26 (2315) [INFO] Backed up EA4 profile to /tmp/VUliNi8OvW/ea_profile.json * 2024-01-15 02:09:29 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-16 02:02:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-16 02:02:36 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-16 02:02:36 (1774) [INFO] Checking if your system is up to date: * 2024-01-16 02:02:36 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-16 02:02:36 (4251) [INFO] * 2024-01-16 02:02:37 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-16 02:02:37 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-16 02:02:37 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-16 02:02:37 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-16 02:02:37 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-16 02:02:37 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-16 02:02:38 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-16 02:02:38 (4281) [INFO] * 2024-01-16 02:02:38 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-16 02:02:38 (4251) [INFO] * 2024-01-16 02:06:45 (4264) [INFO] * 2024-01-16 02:06:45 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-16 02:06:45 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-16 02:06:46 (4281) [INFO] * 2024-01-16 02:06:46 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-16 02:06:46 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-16 02:06:48 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-16 02:10:11 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-16 02:10:11 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30658 milliseconds') https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2024-01-16 02:10:11 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-16 02:10:11 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-16 02:10:11 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-16 02:10:11 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-16 02:10:11 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-16 02:10:11 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-16 02:10:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-16 02:10:12 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/w6_xIhwAsJ/ea_profile.json * 2024-01-16 02:10:14 (2315) [INFO] Backed up EA4 profile to /tmp/w6_xIhwAsJ/ea_profile.json * 2024-01-16 02:10:16 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-17 02:00:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-17 02:01:00 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-17 02:01:00 (1774) [INFO] Checking if your system is up to date: * 2024-01-17 02:01:00 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-17 02:01:00 (4251) [INFO] * 2024-01-17 02:01:00 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-17 02:01:00 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-17 02:01:00 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-17 02:01:00 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-17 02:01:00 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-17 02:01:00 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-17 02:01:00 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-17 02:01:00 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-17 02:01:00 (4281) [INFO] * 2024-01-17 02:01:00 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-17 02:01:00 (4251) [INFO] * 2024-01-17 02:05:07 (4264) [INFO] * 2024-01-17 02:05:07 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-17 02:05:07 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-17 02:05:07 (4281) [INFO] * 2024-01-17 02:05:07 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-17 02:05:07 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-17 02:05:10 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-17 02:08:27 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-17 02:08:27 (1634) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30533 milliseconds') * 2024-01-17 02:08:27 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-17 02:08:27 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-17 02:08:27 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-17 02:08:28 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-17 02:08:28 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-17 02:08:28 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-17 02:08:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-17 02:08:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sQ3HYZ3nSo/ea_profile.json * 2024-01-17 02:08:31 (2315) [INFO] Backed up EA4 profile to /tmp/sQ3HYZ3nSo/ea_profile.json * 2024-01-17 02:08:33 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-18 02:02:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-18 02:02:16 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-18 02:02:16 (1774) [INFO] Checking if your system is up to date: * 2024-01-18 02:02:16 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-18 02:02:16 (4251) [INFO] * 2024-01-18 02:02:16 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-18 02:02:17 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-18 02:02:17 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-18 02:02:17 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-18 02:02:17 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-18 02:02:17 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-18 02:02:17 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-18 02:02:17 (4281) [INFO] * 2024-01-18 02:02:17 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-18 02:02:17 (4251) [INFO] * 2024-01-18 02:06:33 (4264) [INFO] * 2024-01-18 02:06:33 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-18 02:06:33 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-18 02:06:34 (4281) [INFO] * 2024-01-18 02:06:34 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-18 02:06:34 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-18 02:06:37 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-18 02:10:07 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-18 02:10:07 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-18 02:10:07 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-18 02:10:07 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-18 02:10:07 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-18 02:10:07 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-18 02:10:07 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XFzWRQnuXG/ea_profile.json * 2024-01-18 02:10:10 (2315) [INFO] Backed up EA4 profile to /tmp/XFzWRQnuXG/ea_profile.json * 2024-01-18 02:10:12 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-19 02:02:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-19 02:02:04 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-19 02:02:04 (1774) [INFO] Checking if your system is up to date: * 2024-01-19 02:02:04 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-19 02:02:04 (4251) [INFO] * 2024-01-19 02:02:04 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-19 02:02:05 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-19 02:02:05 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-19 02:02:05 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-19 02:02:05 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-19 02:02:05 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-19 02:02:05 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-19 02:02:05 (4281) [INFO] * 2024-01-19 02:02:05 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-19 02:02:05 (4251) [INFO] * 2024-01-19 02:05:03 (4264) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/33b2575ebfa315a2ee6a634fe60c6dfd84b886191ccf3a4bebc55cb8b6ab4a44-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 2024-01-19 02:05:03 (4264) [INFO] Trying other mirror. * 2024-01-19 02:05:03 (4264) [INFO] To address this issue please refer to the below wiki article * 2024-01-19 02:05:03 (4264) [INFO] * 2024-01-19 02:05:03 (4264) [INFO] https://wiki.centos.org/yum-errors * 2024-01-19 02:05:03 (4264) [INFO] * 2024-01-19 02:05:03 (4264) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-01-19 02:05:03 (4264) [INFO] * 2024-01-19 02:05:03 (4264) [INFO] http://mirrors.tscak.com/Fedora/epel/7/x86_64/repodata/899e1d6d94a7452c001654385635990526f66e8d89666ab27420bff3f3bbb32a-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 2024-01-19 02:05:03 (4264) [INFO] Trying other mirror. * 2024-01-19 02:06:20 (4264) [INFO] * 2024-01-19 02:06:20 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-19 02:06:20 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-19 02:06:21 (4281) [INFO] * 2024-01-19 02:06:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-19 02:06:21 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-19 02:06:24 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-19 02:10:30 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-19 02:10:30 (1634) [ERROR] http://mirrors.seas.harvard.edu/centos/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds') Trying other mirror. * 2024-01-19 02:10:30 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-19 02:10:30 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-19 02:10:30 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-19 02:10:31 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-19 02:10:31 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-19 02:10:31 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-19 02:10:31 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-19 02:10:31 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JZ2s3qel3_/ea_profile.json * 2024-01-19 02:10:33 (2315) [INFO] Backed up EA4 profile to /tmp/JZ2s3qel3_/ea_profile.json * 2024-01-19 02:10:37 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-20 02:03:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-20 02:03:37 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-20 02:03:37 (1774) [INFO] Checking if your system is up to date: * 2024-01-20 02:03:37 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-20 02:03:37 (4251) [INFO] * 2024-01-20 02:03:38 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-20 02:03:38 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-20 02:03:38 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-20 02:03:38 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-20 02:03:38 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-20 02:03:38 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-20 02:03:38 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-20 02:03:38 (4281) [INFO] * 2024-01-20 02:03:38 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-20 02:03:38 (4251) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] One of the configured repositories failed (Unknown), * 2024-01-20 02:04:33 (4264) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-20 02:04:33 (4264) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-20 02:04:33 (4264) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-20 02:04:33 (4264) [INFO] distribution release than is supported by the repository (and the * 2024-01-20 02:04:33 (4264) [INFO] packages for the previous distribution release still work). * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-20 02:04:33 (4264) [INFO] yum --disablerepo= ... * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-20 02:04:33 (4264) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-20 02:04:33 (4264) [INFO] again or use --enablerepo for temporary usage: * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] yum-config-manager --disable * 2024-01-20 02:04:33 (4264) [INFO] or * 2024-01-20 02:04:33 (4264) [INFO] subscription-manager repos --disable= * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-20 02:04:33 (4264) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-20 02:04:33 (4264) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-20 02:04:33 (4264) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-20 02:04:33 (4264) [INFO] compromise: * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-20 02:04:33 (4264) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-20 02:04:33 (4281) [INFO] * 2024-01-20 02:04:33 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-20 02:04:33 (1795) [INFO] Checking /scripts/sysup * 2024-01-20 02:04:33 (4250) [INFO] Running: /scripts/sysup * 2024-01-20 02:04:33 (4251) [INFO] * 2024-01-20 02:04:33 (4264) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-20 02:04:36 (4264) [INFO] All Needed Packages are already installed. * 2024-01-20 02:04:36 (4281) [INFO] * 2024-01-20 02:04:39 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-20 02:13:49 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-20 02:13:49 (1634) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://centos.mirror.shastacoe.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/69c3d9cd3c88bbf364bb0876a71e7c43c4703f8abb92cb9540240fefe80c6998-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo1.sea.innoscale.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftpmirror.your.org/pub/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.nodesdirect.com/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://mirror.clarkson.edu/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.arizona.edu/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://forksystems.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-01-20 02:13:49 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-20 02:13:49 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-20 02:13:49 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-20 02:13:49 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-20 02:13:49 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-20 02:13:49 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-20 02:13:49 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-20 02:13:49 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RkUSefzg0d/ea_profile.json * 2024-01-20 02:13:52 (2315) [INFO] Backed up EA4 profile to /tmp/RkUSefzg0d/ea_profile.json * 2024-01-20 02:13:56 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-21 01:56:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-21 01:56:55 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-21 01:56:55 (1774) [INFO] Checking if your system is up to date: * 2024-01-21 01:56:55 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-21 01:56:55 (4251) [INFO] * 2024-01-21 01:56:55 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-21 01:56:56 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-21 01:56:56 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-21 01:56:56 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-21 01:56:56 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-21 01:56:56 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-21 01:56:56 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-21 01:56:56 (4281) [INFO] * 2024-01-21 01:56:56 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-21 01:56:56 (4251) [INFO] * 2024-01-21 02:00:59 (4264) [INFO] * 2024-01-21 02:00:59 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-21 02:00:59 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-21 02:00:59 (4281) [INFO] * 2024-01-21 02:00:59 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-21 02:00:59 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-21 02:01:02 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-21 02:04:44 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-21 02:04:44 (1634) [ERROR] http://mirrors.seas.harvard.edu/centos/7.9.2009/updates/x86_64/repodata/d5865f9dfbe94b805f65f53393626ab56460bf97a5b7c650c8882ad6dbb9a0c0-other.sqlite.bz2: [Errno 12] Timeout on http://mirrors.seas.harvard.edu/centos/7.9.2009/updates/x86_64/repodata/d5865f9dfbe94b805f65f53393626ab56460bf97a5b7c650c8882ad6dbb9a0c0-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. * 2024-01-21 02:04:44 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-21 02:04:44 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-21 02:04:44 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-21 02:04:45 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-21 02:04:45 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-21 02:04:45 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-21 02:04:45 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-21 02:04:45 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NN7_VmoK93/ea_profile.json * 2024-01-21 02:04:48 (2315) [INFO] Backed up EA4 profile to /tmp/NN7_VmoK93/ea_profile.json * 2024-01-21 02:04:51 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-22 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-22 02:02:09 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-22 02:02:09 (1774) [INFO] Checking if your system is up to date: * 2024-01-22 02:02:09 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-22 02:02:09 (4251) [INFO] * 2024-01-22 02:02:09 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-22 02:02:09 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-22 02:02:09 (4264) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-22 02:02:09 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-22 02:02:09 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-22 02:02:09 (4264) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-22 02:02:10 (4264) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-22 02:02:10 (4281) [INFO] * 2024-01-22 02:02:10 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-22 02:02:10 (4251) [INFO] * 2024-01-22 02:06:19 (4264) [INFO] * 2024-01-22 02:06:19 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-22 02:06:19 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-22 02:06:19 (4281) [INFO] * 2024-01-22 02:06:19 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-22 02:06:19 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-22 02:06:21 (1693) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-22 02:09:34 (1842) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-22 02:09:34 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-22 02:09:34 (1176) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-22 02:09:34 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-22 02:09:34 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-22 02:09:34 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-22 02:09:34 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dy30baj9QX/ea_profile.json * 2024-01-22 02:09:36 (2315) [INFO] Backed up EA4 profile to /tmp/dy30baj9QX/ea_profile.json * 2024-01-22 02:09:39 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-23 01:59:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-23 01:59:29 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-23 01:59:29 (1842) [INFO] Checking if your system is up to date: * 2024-01-23 01:59:29 (4318) [INFO] Running: /usr/bin/yum clean all * 2024-01-23 01:59:29 (4319) [INFO] * 2024-01-23 01:59:30 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-23 01:59:30 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-23 01:59:30 (4332) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-23 01:59:30 (4332) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-23 01:59:30 (4332) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-23 01:59:30 (4332) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-23 01:59:30 (4332) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-23 01:59:30 (4349) [INFO] * 2024-01-23 01:59:30 (4318) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-23 01:59:30 (4319) [INFO] * 2024-01-23 02:03:58 (4332) [INFO] * 2024-01-23 02:03:58 (4332) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-23 02:03:58 (4332) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-23 02:03:58 (4349) [INFO] * 2024-01-23 02:03:58 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-23 02:03:58 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-23 02:04:01 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-23 02:07:31 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-23 02:07:31 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-23 02:07:32 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-23 02:07:32 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-23 02:07:32 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-23 02:07:32 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-23 02:07:32 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8cjKxhnZoV/ea_profile.json * 2024-01-23 02:07:33 (2383) [INFO] Backed up EA4 profile to /tmp/8cjKxhnZoV/ea_profile.json * 2024-01-23 02:07:34 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-23 02:07:35 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-24 02:04:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-24 02:05:01 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-24 02:05:01 (1842) [INFO] Checking if your system is up to date: * 2024-01-24 02:05:01 (4318) [INFO] Running: /usr/bin/yum clean all * 2024-01-24 02:05:01 (4319) [INFO] * 2024-01-24 02:05:01 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-24 02:05:01 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-24 02:05:01 (4332) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-24 02:05:01 (4332) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-24 02:05:01 (4332) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-24 02:05:01 (4332) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-24 02:05:02 (4332) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-24 02:05:02 (4349) [INFO] * 2024-01-24 02:05:02 (4318) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-24 02:05:02 (4319) [INFO] * 2024-01-24 02:09:24 (4332) [INFO] * 2024-01-24 02:09:24 (4332) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-24 02:09:24 (4332) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-24 02:09:24 (4349) [INFO] * 2024-01-24 02:09:24 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-24 02:09:24 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-24 02:09:26 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-24 02:13:14 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-24 02:13:14 (1702) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-01-24 02:13:14 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-24 02:13:14 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-24 02:13:14 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-24 02:13:15 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-24 02:13:15 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-24 02:13:15 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-24 02:13:15 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-24 02:13:15 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VtpkF6zV9T/ea_profile.json * 2024-01-24 02:13:16 (2383) [INFO] Backed up EA4 profile to /tmp/VtpkF6zV9T/ea_profile.json * 2024-01-24 02:13:17 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-24 02:13:19 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-25 01:58:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-25 01:58:11 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-25 01:58:11 (1842) [INFO] Checking if your system is up to date: * 2024-01-25 01:58:11 (4318) [INFO] Running: /usr/bin/yum clean all * 2024-01-25 01:58:11 (4319) [INFO] * 2024-01-25 01:58:11 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-25 01:58:11 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-25 01:58:11 (4332) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-25 01:58:11 (4332) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-25 01:58:11 (4332) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-25 01:58:11 (4332) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-25 01:58:11 (4332) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-25 01:58:11 (4349) [INFO] * 2024-01-25 01:58:11 (4318) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-25 01:58:11 (4319) [INFO] * 2024-01-25 02:02:27 (4332) [INFO] * 2024-01-25 02:02:27 (4332) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-25 02:02:27 (4332) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-25 02:02:28 (4349) [INFO] * 2024-01-25 02:02:28 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-25 02:02:28 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-25 02:02:30 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-25 02:05:59 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-25 02:05:59 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-25 02:05:59 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-25 02:05:59 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-25 02:05:59 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-25 02:05:59 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-25 02:05:59 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Zg8LU4PBM9/ea_profile.json * 2024-01-25 02:06:01 (2383) [INFO] Backed up EA4 profile to /tmp/Zg8LU4PBM9/ea_profile.json * 2024-01-25 02:06:02 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-25 02:06:05 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-26 02:07:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-26 02:07:09 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-26 02:07:09 (1842) [INFO] Checking if your system is up to date: * 2024-01-26 02:07:09 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-26 02:07:09 (4322) [INFO] * 2024-01-26 02:07:09 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-26 02:07:10 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-26 02:07:10 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-26 02:07:10 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-26 02:07:10 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-26 02:07:10 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-26 02:07:10 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-26 02:07:10 (4352) [INFO] * 2024-01-26 02:07:10 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-26 02:07:10 (4322) [INFO] * 2024-01-26 02:10:35 (4335) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/85a6db063eeb1bd2aa13ebf70e8526ff4eed05d8eb9446d630c957571ed510cf-comps-Everything.x86_64.xml.gz: [Errno -1] Metadata file does not match checksum * 2024-01-26 02:10:35 (4335) [INFO] Trying other mirror. * 2024-01-26 02:10:35 (4335) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:10:35 (4335) [INFO] Trying other mirror. * 2024-01-26 02:10:50 (4335) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:10:50 (4335) [INFO] Trying other mirror. * 2024-01-26 02:10:52 (4335) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:10:52 (4335) [INFO] Trying other mirror. * 2024-01-26 02:10:54 (4335) [INFO] https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:10:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:10:54 (4335) [INFO] https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:10:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:06 (4335) [INFO] http://mirrors.xtom.com/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:06 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:06 (4335) [INFO] http://us.mirrors.virtono.com/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:06 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:07 (4335) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/69c3d9cd3c88bbf364bb0876a71e7c43c4703f8abb92cb9540240fefe80c6998-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:07 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:07 (4335) [INFO] https://epel.mcn.us.ssimn.org/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 403 - Forbidden * 2024-01-26 02:11:07 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:07 (4335) [INFO] To address this issue please refer to the below wiki article * 2024-01-26 02:11:07 (4335) [INFO] * 2024-01-26 02:11:07 (4335) [INFO] https://wiki.centos.org/yum-errors * 2024-01-26 02:11:07 (4335) [INFO] * 2024-01-26 02:11:07 (4335) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-01-26 02:11:07 (4335) [INFO] * 2024-01-26 02:11:08 (4335) [INFO] https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:08 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:09 (4335) [INFO] http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:09 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:09 (4335) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:09 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:10 (4335) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:10 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:22 (4335) [INFO] http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:22 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:24 (4335) [INFO] http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:24 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:25 (4335) [INFO] https://dfw.mirror.rackspace.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:25 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:25 (4335) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:25 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:26 (4335) [INFO] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:26 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:27 (4335) [INFO] https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:27 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:37 (4335) [INFO] http://mirrors.advancedhosters.com/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:37 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:37 (4335) [INFO] http://mirror.chpc.utah.edu/pub/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:37 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:40 (4335) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:40 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:41 (4335) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:41 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:42 (4335) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:42 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:42 (4335) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:42 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:43 (4335) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:43 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:53 (4335) [INFO] http://mirror.vacares.com/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:53 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:58 (4335) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:58 (4335) [INFO] Trying other mirror. * 2024-01-26 02:11:58 (4335) [INFO] https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:11:58 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:09 (4335) [INFO] http://paducahix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:09 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:14 (4335) [INFO] https://mirror.servaxnet.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:14 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:14 (4335) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:14 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:24 (4335) [INFO] http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:24 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:30 (4335) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:30 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:30 (4335) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:30 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:39 (4335) [INFO] http://abqix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:39 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:45 (4335) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:45 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:45 (4335) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:45 (4335) [INFO] Trying other mirror. * 2024-01-26 02:12:54 (4335) [INFO] http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/fd3848a4a6549cc66935b1a10b01492889874c4d3d9ee6d511f56e636ea15df0-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:12:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:01 (4335) [INFO] https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:01 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:01 (4335) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:01 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:02 (4335) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:02 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:03 (4335) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:03 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:17 (4335) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:17 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:18 (4335) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:18 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:18 (4335) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:18 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:33 (4335) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:33 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:34 (4335) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:34 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:49 (4335) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:49 (4335) [INFO] Trying other mirror. * 2024-01-26 02:13:49 (4335) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:13:49 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:05 (4335) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:05 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:19 (4335) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-01-26 02:14:19 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:20 (4335) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:20 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:35 (4335) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:35 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:36 (4335) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:36 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:36 (4335) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:36 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:50 (4335) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:50 (4335) [INFO] Trying other mirror. * 2024-01-26 02:14:52 (4335) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:14:52 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:06 (4335) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:06 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:07 (4335) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:07 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:21 (4335) [INFO] http://mirror.team-cymru.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:21 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:22 (4335) [INFO] https://mirror.lstn.net/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:22 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:22 (4335) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:22 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:23 (4335) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:23 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:38 (4335) [INFO] https://abqix.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:38 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:38 (4335) [INFO] https://mirrors.iu13.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:38 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:38 (4335) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:38 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:38 (4335) [INFO] http://mirrors.mit.edu/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:38 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:39 (4335) [INFO] https://repos.eggycrew.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:39 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:39 (4335) [INFO] https://mirrors.lug.mtu.edu/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:39 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:39 (4335) [INFO] https://mirror.dst.ca/fedora-linux/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:39 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:39 (4335) [INFO] https://mirror.umd.edu/fedora/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:39 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:54 (4335) [INFO] http://mirrors.liquidweb.com/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:54 (4335) [INFO] https://mirrors.wcupa.edu/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:15:54 (4335) [INFO] https://dl.fedoraproject.org/pub/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:15:54 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:10 (4335) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:10 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:24 (4335) [INFO] https://epel.mcn.us.ssimn.org/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 12] Timeout on https://epel.mcn.us.ssimn.org/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: (28, 'Connection timed out after 30000 milliseconds') * 2024-01-26 02:16:24 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:25 (4335) [INFO] https://iad.mirror.rackspace.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:25 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:25 (4335) [INFO] https://mirror.facebook.net/fedora/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:25 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:40 (4335) [INFO] http://mirror.metrocast.net/fedora/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:40 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:40 (4335) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:40 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:55 (4335) [INFO] https://epel.mirror.constant.com/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:55 (4335) [INFO] Trying other mirror. * 2024-01-26 02:16:56 (4335) [INFO] https://mirror.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:16:56 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:10 (4335) [INFO] https://mirror.servaxnet.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:10 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:11 (4335) [INFO] https://ftp-osl.osuosl.org/pub/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:11 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:26 (4335) [INFO] http://mirror.rnet.missouri.edu/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:26 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:26 (4335) [INFO] https://nnenix.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:26 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:41 (4335) [INFO] https://mirrors.upr.edu/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:41 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:41 (4335) [INFO] https://mirror-mci.yuki.net.uk/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:41 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:57 (4335) [INFO] https://ima.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:57 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:57 (4335) [INFO] https://lolhost.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:57 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:57 (4335) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:57 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:57 (4335) [INFO] https://pubmirror2.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:57 (4335) [INFO] Trying other mirror. * 2024-01-26 02:17:57 (4335) [INFO] https://pubmirror3.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:17:57 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:12 (4335) [INFO] https://codingflyboy.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:12 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:12 (4335) [INFO] https://lesnet.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:12 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:27 (4335) [INFO] https://mirror.xenyth.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:27 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:27 (4335) [INFO] http://mirror.tornadovps.com/pub/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:27 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:43 (4335) [INFO] https://mirror.dal.nexril.net/fedora-epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:43 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:58 (4335) [INFO] https://opencolo.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:18:58 (4335) [INFO] Trying other mirror. * 2024-01-26 02:18:58 (4335) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-01-26 02:18:58 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:13 (4335) [INFO] https://ix-denver.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:13 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:13 (4335) [INFO] https://uvermont.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:13 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:28 (4335) [INFO] https://southfront.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:28 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:29 (4335) [INFO] https://forksystems.mm.fcix.net/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:29 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:43 (4335) [INFO] https://mirror.steadfastnet.com/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:43 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:44 (4335) [INFO] https://mirrors.ocf.berkeley.edu/fedora/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:44 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:59 (4335) [INFO] https://ziply.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:59 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:59 (4335) [INFO] http://mirror.cogentco.com/pub/linux/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:59 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:59 (4335) [INFO] http://mirror.team-cymru.com/epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:59 (4335) [INFO] Trying other mirror. * 2024-01-26 02:19:59 (4335) [INFO] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/3f71a303b3c3970c6cf4039de9eeda41c7bd2003646e146e02681104373b7c68-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:19:59 (4335) [INFO] Trying other mirror. * 2024-01-26 02:20:14 (4335) [INFO] https://mirrors.sonic.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:20:14 (4335) [INFO] Trying other mirror. * 2024-01-26 02:20:29 (4335) [INFO] https://paducahix.mm.fcix.net/epel/7/x86_64/repodata/773a5d241ab8bb092c3dc05db6d57a5faf495cecc31419dbe7fbd1b01fcb5b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-26 02:20:29 (4335) [INFO] Trying other mirror. * 2024-01-26 02:20:45 (4335) [INFO] * 2024-01-26 02:20:45 (4335) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-26 02:20:45 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-26 02:20:45 (4352) [INFO] * 2024-01-26 02:20:45 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-26 02:20:45 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-26 02:20:49 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-26 02:24:24 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-26 02:24:24 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-26 02:24:25 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-26 02:24:25 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-26 02:24:25 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-26 02:24:25 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-26 02:24:25 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c4OnR1QVgq/ea_profile.json * 2024-01-26 02:24:28 (2382) [INFO] Backed up EA4 profile to /tmp/c4OnR1QVgq/ea_profile.json * 2024-01-26 02:24:28 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-26 02:24:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-27 02:10:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-27 02:10:59 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-27 02:10:59 (1842) [INFO] Checking if your system is up to date: * 2024-01-27 02:10:59 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-27 02:10:59 (4322) [INFO] * 2024-01-27 02:11:00 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-27 02:11:00 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-27 02:11:00 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-27 02:11:00 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-27 02:11:00 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-27 02:11:00 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-27 02:11:01 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-27 02:11:01 (4352) [INFO] * 2024-01-27 02:11:01 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-27 02:11:01 (4322) [INFO] * 2024-01-27 02:15:54 (4335) [INFO] * 2024-01-27 02:15:54 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-01-27 02:15:54 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-27 02:15:54 (4352) [INFO] * 2024-01-27 02:15:54 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-27 02:15:54 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-27 02:15:58 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-27 02:19:46 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-27 02:19:46 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-27 02:19:47 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-27 02:19:47 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-27 02:19:47 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-27 02:19:47 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-27 02:19:47 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AiUihVNm_v/ea_profile.json * 2024-01-27 02:19:50 (2382) [INFO] Backed up EA4 profile to /tmp/AiUihVNm_v/ea_profile.json * 2024-01-27 02:19:51 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-27 02:19:54 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-28 02:03:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-28 02:03:56 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-28 02:03:56 (1842) [INFO] Checking if your system is up to date: * 2024-01-28 02:03:56 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-28 02:03:56 (4322) [INFO] * 2024-01-28 02:03:56 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-28 02:03:57 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-28 02:03:57 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-28 02:03:57 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-28 02:03:57 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-28 02:03:57 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-28 02:03:57 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-28 02:03:57 (4352) [INFO] * 2024-01-28 02:03:57 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-28 02:03:57 (4322) [INFO] * 2024-01-28 02:08:33 (4335) [INFO] * 2024-01-28 02:08:33 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-01-28 02:08:33 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-28 02:08:34 (4352) [INFO] * 2024-01-28 02:08:34 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-28 02:08:34 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-28 02:08:36 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-28 02:12:05 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-28 02:12:05 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-28 02:12:06 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-28 02:12:06 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-28 02:12:06 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-28 02:12:06 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-28 02:12:06 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CKETYhrf6B/ea_profile.json * 2024-01-28 02:12:08 (2382) [INFO] Backed up EA4 profile to /tmp/CKETYhrf6B/ea_profile.json * 2024-01-28 02:12:09 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-28 02:12:12 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-29 01:55:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-29 01:56:01 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-29 01:56:02 (1842) [INFO] Checking if your system is up to date: * 2024-01-29 01:56:02 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-29 01:56:02 (4322) [INFO] * 2024-01-29 01:56:02 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-29 01:56:03 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-29 01:56:03 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-29 01:56:03 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-29 01:56:03 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-29 01:56:03 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-29 01:56:03 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-29 01:56:03 (4352) [INFO] * 2024-01-29 01:56:03 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-29 01:56:03 (4322) [INFO] * 2024-01-29 02:00:17 (4335) [INFO] * 2024-01-29 02:00:17 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-01-29 02:00:17 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-29 02:00:17 (4352) [INFO] * 2024-01-29 02:00:17 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-29 02:00:17 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-29 02:00:21 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-29 02:03:28 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-29 02:03:28 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-29 02:03:29 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-29 02:03:29 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-29 02:03:29 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-29 02:03:29 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-29 02:03:29 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GT1csFBRlg/ea_profile.json * 2024-01-29 02:03:31 (2382) [INFO] Backed up EA4 profile to /tmp/GT1csFBRlg/ea_profile.json * 2024-01-29 02:03:32 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-29 02:03:35 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-30 02:06:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-30 02:06:11 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-30 02:06:11 (1842) [INFO] Checking if your system is up to date: * 2024-01-30 02:06:11 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-30 02:06:11 (4322) [INFO] * 2024-01-30 02:06:11 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-30 02:06:12 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-30 02:06:12 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-30 02:06:12 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-30 02:06:12 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-30 02:06:12 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-30 02:06:12 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-30 02:06:12 (4352) [INFO] * 2024-01-30 02:06:12 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-30 02:06:12 (4322) [INFO] * 2024-01-30 02:10:08 (4335) [INFO] http://mirrors.xmission.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:10:08 (4335) [INFO] Trying other mirror. * 2024-01-30 02:10:08 (4335) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:10:08 (4335) [INFO] Trying other mirror. * 2024-01-30 02:10:23 (4335) [INFO] http://mirrors.xtom.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:10:23 (4335) [INFO] Trying other mirror. * 2024-01-30 02:10:38 (4335) [INFO] http://mirror.pit.teraswitch.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:10:38 (4335) [INFO] Trying other mirror. * 2024-01-30 02:10:39 (4335) [INFO] http://us.mirrors.virtono.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:10:39 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:06 (4335) [INFO] http://ftp.osuosl.org/pub/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:06 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:06 (4335) [INFO] http://mirror.us-midwest-1.nexcess.net/CentOS/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:06 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:06 (4335) [INFO] http://volico.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:06 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:22 (4335) [INFO] http://paducahix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:22 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:37 (4335) [INFO] http://ix-denver.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:37 (4335) [INFO] Trying other mirror. * 2024-01-30 02:11:53 (4335) [INFO] http://mirror.team-cymru.com/CentOS/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-01-30 02:11:53 (4335) [INFO] Trying other mirror. * 2024-01-30 02:12:03 (4335) [INFO] * 2024-01-30 02:12:03 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-01-30 02:12:03 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-30 02:12:04 (4352) [INFO] * 2024-01-30 02:12:04 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-30 02:12:04 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-30 02:12:07 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-30 02:15:40 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-30 02:15:40 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-30 02:15:40 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-30 02:15:40 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-30 02:15:40 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-30 02:15:40 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-30 02:15:40 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1MPmkidZgu/ea_profile.json * 2024-01-30 02:15:43 (2382) [INFO] Backed up EA4 profile to /tmp/1MPmkidZgu/ea_profile.json * 2024-01-30 02:15:44 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-30 02:15:47 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-31 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-01-31 02:02:11 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-31 02:02:11 (1842) [INFO] Checking if your system is up to date: * 2024-01-31 02:02:11 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-01-31 02:02:11 (4322) [INFO] * 2024-01-31 02:02:11 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-31 02:02:11 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-01-31 02:02:11 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-31 02:02:11 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-31 02:02:11 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-31 02:02:11 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-01-31 02:02:12 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-01-31 02:02:12 (4352) [INFO] * 2024-01-31 02:02:12 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-31 02:02:12 (4322) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] One of the configured repositories failed (Unknown), * 2024-01-31 02:03:07 (4335) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-01-31 02:03:07 (4335) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-01-31 02:03:07 (4335) [INFO] upstream. This is most often useful if you are using a newer * 2024-01-31 02:03:07 (4335) [INFO] distribution release than is supported by the repository (and the * 2024-01-31 02:03:07 (4335) [INFO] packages for the previous distribution release still work). * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] 3. Run the command with the repository temporarily disabled * 2024-01-31 02:03:07 (4335) [INFO] yum --disablerepo= ... * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-01-31 02:03:07 (4335) [INFO] will then just ignore the repository until you permanently enable it * 2024-01-31 02:03:07 (4335) [INFO] again or use --enablerepo for temporary usage: * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] yum-config-manager --disable * 2024-01-31 02:03:07 (4335) [INFO] or * 2024-01-31 02:03:07 (4335) [INFO] subscription-manager repos --disable= * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-01-31 02:03:07 (4335) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-01-31 02:03:07 (4335) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-01-31 02:03:07 (4335) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-01-31 02:03:07 (4335) [INFO] compromise: * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-01-31 02:03:07 (4335) [INFO] * 2024-01-31 02:03:07 (4335) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-01-31 02:03:07 (4352) [INFO] * 2024-01-31 02:03:07 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-31 02:03:07 (1863) [INFO] Checking /scripts/sysup * 2024-01-31 02:03:07 (4321) [INFO] Running: /scripts/sysup * 2024-01-31 02:03:07 (4322) [INFO] * 2024-01-31 02:03:08 (4335) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-01-31 02:03:10 (4335) [INFO] All Needed Packages are already installed. * 2024-01-31 02:03:10 (4352) [INFO] * 2024-01-31 02:03:13 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-01-31 02:11:43 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-01-31 02:11:43 (1702) [ERROR] https://mirror.servaxnet.com/epel/7/x86_64/repodata/0d91251259e7b81051af78db975e76c18d86afdbac321fb59ca5e45b5b42f10b-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. http://mirror.nodesdirect.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.wdc2.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.clarkson.edu/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.unifiedlayer.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.advancedhosters.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.chpc.utah.edu/pub/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nnenix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nocix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ridgewireless.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-01-31 02:11:43 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-01-31 02:11:43 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-01-31 02:11:43 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-01-31 02:11:44 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-01-31 02:11:44 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-01-31 02:11:44 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-01-31 02:11:44 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-31 02:11:44 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/89wpYq3Ew3/ea_profile.json * 2024-01-31 02:11:47 (2382) [INFO] Backed up EA4 profile to /tmp/89wpYq3Ew3/ea_profile.json * 2024-01-31 02:11:48 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-01-31 02:11:51 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-01 02:05:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-01 02:05:51 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-01 02:05:51 (1842) [INFO] Checking if your system is up to date: * 2024-02-01 02:05:51 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-02-01 02:05:51 (4322) [INFO] * 2024-02-01 02:05:51 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-01 02:05:52 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-01 02:05:52 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-01 02:05:52 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-01 02:05:52 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-01 02:05:52 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-01 02:05:52 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-01 02:05:52 (4352) [INFO] * 2024-02-01 02:05:52 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-01 02:05:52 (4322) [INFO] * 2024-02-01 02:10:05 (4335) [INFO] Traceback (most recent call last): * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/bin/yum", line 29, in * 2024-02-01 02:10:05 (4335) [INFO] yummain.user_main(sys.argv[1:], exit_code=True) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/share/yum-cli/yummain.py", line 375, in user_main * 2024-02-01 02:10:05 (4335) [INFO] errcode = main(args) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/share/yum-cli/yummain.py", line 184, in main * 2024-02-01 02:10:05 (4335) [INFO] result, resultmsgs = base.doCommands() * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/share/yum-cli/cli.py", line 585, in doCommands * 2024-02-01 02:10:05 (4335) [INFO] return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand * 2024-02-01 02:10:05 (4335) [INFO] ypl = base.returnPkgLists(extcmds, repoid=repoid) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists * 2024-02-01 02:10:05 (4335) [INFO] ignore_case=True, repoid=repoid) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists * 2024-02-01 02:10:05 (4335) [INFO] for (n,a,e,v,r) in self.up.getUpdatesList(): * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in * 2024-02-01 02:10:05 (4335) [INFO] up = property(fget=lambda self: self._getUpdates(), * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates * 2024-02-01 02:10:05 (4335) [INFO] self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList()) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in * 2024-02-01 02:10:05 (4335) [INFO] pkgSack = property(fget=lambda self: self._getSacks(), * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks * 2024-02-01 02:10:05 (4335) [INFO] self.repos.populateSack(which=repos) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack * 2024-02-01 02:10:05 (4335) [INFO] sack.populate(repo, mdtype, callback, cacheonly) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 242, in populate * 2024-02-01 02:10:05 (4335) [INFO] mydbtype) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen * 2024-02-01 02:10:05 (4335) [INFO] cached=repo.cache) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress * 2024-02-01 02:10:05 (4335) [INFO] return decompress(filename, dest=dest, check_timestamps=True) * 2024-02-01 02:10:05 (4335) [INFO] File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress * 2024-02-01 02:10:05 (4335) [INFO] os.utime(out, (fi.st_mtime, fi.st_mtime)) * 2024-02-01 02:10:05 (4335) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite' * 2024-02-01 02:10:05 (4352) [INFO] * 2024-02-01 02:10:05 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-01 02:10:05 (1863) [INFO] Checking /scripts/sysup * 2024-02-01 02:10:05 (4321) [INFO] Running: /scripts/sysup * 2024-02-01 02:10:05 (4322) [INFO] * 2024-02-01 02:10:06 (4335) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-01 02:10:08 (4335) [INFO] All Needed Packages are already installed. * 2024-02-01 02:10:08 (4352) [INFO] * 2024-02-01 02:10:10 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-01 02:13:39 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-01 02:13:39 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-01 02:13:40 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-01 02:13:40 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-01 02:13:40 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-01 02:13:40 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-01 02:13:40 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DXw5Ddsfmw/ea_profile.json * 2024-02-01 02:13:43 (2382) [INFO] Backed up EA4 profile to /tmp/DXw5Ddsfmw/ea_profile.json * 2024-02-01 02:13:44 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-01 02:13:46 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-02 02:07:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-02 02:07:30 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-02 02:07:30 (1842) [INFO] Checking if your system is up to date: * 2024-02-02 02:07:30 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-02-02 02:07:30 (4322) [INFO] * 2024-02-02 02:07:30 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-02 02:07:30 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-02 02:07:30 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-02 02:07:30 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-02 02:07:30 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-02 02:07:30 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-02 02:07:31 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-02 02:07:31 (4352) [INFO] * 2024-02-02 02:07:31 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-02 02:07:31 (4322) [INFO] * 2024-02-02 02:11:25 (4335) [INFO] * 2024-02-02 02:11:25 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-02 02:11:25 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-02 02:11:25 (4352) [INFO] * 2024-02-02 02:11:25 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-02 02:11:25 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-02 02:11:28 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-02 02:14:19 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-02 02:14:19 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-02 02:14:20 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-02 02:14:20 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-02 02:14:20 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-02 02:14:20 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-02 02:14:20 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E1r3Vhf2m7/ea_profile.json * 2024-02-02 02:14:22 (2382) [INFO] Backed up EA4 profile to /tmp/E1r3Vhf2m7/ea_profile.json * 2024-02-02 02:14:23 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-02 02:14:26 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-03 02:04:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-03 02:04:10 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-03 02:04:10 (1842) [INFO] Checking if your system is up to date: * 2024-02-03 02:04:10 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-02-03 02:04:10 (4322) [INFO] * 2024-02-03 02:04:10 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-03 02:04:11 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-03 02:04:11 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-03 02:04:11 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-03 02:04:11 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-03 02:04:11 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-03 02:04:11 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-03 02:04:12 (4352) [INFO] * 2024-02-03 02:04:12 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-03 02:04:12 (4322) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] One of the configured repositories failed (Unknown), * 2024-02-03 02:05:07 (4335) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-03 02:05:07 (4335) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-03 02:05:07 (4335) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-03 02:05:07 (4335) [INFO] distribution release than is supported by the repository (and the * 2024-02-03 02:05:07 (4335) [INFO] packages for the previous distribution release still work). * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-03 02:05:07 (4335) [INFO] yum --disablerepo= ... * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-03 02:05:07 (4335) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-03 02:05:07 (4335) [INFO] again or use --enablerepo for temporary usage: * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] yum-config-manager --disable * 2024-02-03 02:05:07 (4335) [INFO] or * 2024-02-03 02:05:07 (4335) [INFO] subscription-manager repos --disable= * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-03 02:05:07 (4335) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-03 02:05:07 (4335) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-03 02:05:07 (4335) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-03 02:05:07 (4335) [INFO] compromise: * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-03 02:05:07 (4335) [INFO] * 2024-02-03 02:05:07 (4335) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-03 02:05:08 (4352) [INFO] * 2024-02-03 02:05:08 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-03 02:05:08 (1863) [INFO] Checking /scripts/sysup * 2024-02-03 02:05:08 (4321) [INFO] Running: /scripts/sysup * 2024-02-03 02:05:08 (4322) [INFO] * 2024-02-03 02:05:08 (4335) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-03 02:05:11 (4335) [INFO] All Needed Packages are already installed. * 2024-02-03 02:05:11 (4352) [INFO] * 2024-02-03 02:05:14 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-03 02:14:05 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-03 02:14:05 (1702) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.xmission.com/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.mia11.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.cmich.edu/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://mirror.chpc.utah.edu/pub/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.arizona.edu/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://uvermont.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/47907d37439f9f68dfb0df485e8e21beb0ede3a98159a7e9434bcc97e075e175-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-02-03 02:14:05 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-03 02:14:05 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-03 02:14:05 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-03 02:14:06 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-03 02:14:06 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-03 02:14:06 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-03 02:14:06 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-03 02:14:07 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YyDPNTnhim/ea_profile.json * 2024-02-03 02:14:09 (2382) [INFO] Backed up EA4 profile to /tmp/YyDPNTnhim/ea_profile.json * 2024-02-03 02:14:10 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-03 02:14:13 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-04 02:01:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-04 02:02:01 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-04 02:02:01 (1842) [INFO] Checking if your system is up to date: * 2024-02-04 02:02:01 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-02-04 02:02:01 (4322) [INFO] * 2024-02-04 02:02:02 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-04 02:02:03 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-04 02:02:03 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-04 02:02:03 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-04 02:02:03 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-04 02:02:03 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-04 02:02:03 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-04 02:02:03 (4352) [INFO] * 2024-02-04 02:02:03 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-04 02:02:03 (4322) [INFO] * 2024-02-04 02:06:31 (4335) [INFO] * 2024-02-04 02:06:31 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-04 02:06:31 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-04 02:06:32 (4352) [INFO] * 2024-02-04 02:06:32 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-04 02:06:32 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-04 02:06:35 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-04 02:10:28 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-04 02:10:28 (1702) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30118 milliseconds with 0 out of 0 bytes received') https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2024-02-04 02:10:28 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-04 02:10:28 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-04 02:10:28 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-04 02:10:29 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-04 02:10:29 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-04 02:10:29 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-04 02:10:29 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-04 02:10:29 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QePd844Oq9/ea_profile.json * 2024-02-04 02:10:31 (2382) [INFO] Backed up EA4 profile to /tmp/QePd844Oq9/ea_profile.json * 2024-02-04 02:10:32 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-04 02:10:35 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-05 01:54:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-05 01:54:53 (161) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-05 01:54:53 (1842) [INFO] Checking if your system is up to date: * 2024-02-05 01:54:53 (4321) [INFO] Running: /usr/bin/yum clean all * 2024-02-05 01:54:53 (4322) [INFO] * 2024-02-05 01:54:54 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-05 01:54:54 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-05 01:54:54 (4335) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-05 01:54:54 (4335) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-05 01:54:54 (4335) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-05 01:54:54 (4335) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-05 01:54:54 (4335) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-05 01:54:55 (4352) [INFO] * 2024-02-05 01:54:55 (4321) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-05 01:54:55 (4322) [INFO] * 2024-02-05 01:59:19 (4335) [INFO] * 2024-02-05 01:59:19 (4335) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-05 01:59:19 (4335) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-05 01:59:19 (4352) [INFO] * 2024-02-05 01:59:19 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-05 01:59:19 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-05 01:59:22 (1761) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-05 02:02:57 (1701) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-05 02:02:57 (1702) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-02-05 02:02:57 (161) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-05 02:02:57 (1910) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-05 02:02:57 (161) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-05 02:02:58 (1244) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-05 02:02:58 (161) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-05 02:02:58 (161) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-05 02:02:58 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-05 02:02:58 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CpVySg29p9/ea_profile.json * 2024-02-05 02:03:01 (2382) [INFO] Backed up EA4 profile to /tmp/CpVySg29p9/ea_profile.json * 2024-02-05 02:03:02 (161) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-05 02:03:05 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-06 02:01:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-06 02:01:26 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-06 02:01:26 (1844) [INFO] Checking if your system is up to date: * 2024-02-06 02:01:26 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-06 02:01:26 (4416) [INFO] * 2024-02-06 02:01:27 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-06 02:01:27 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-06 02:01:27 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-06 02:01:27 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-06 02:01:27 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-06 02:01:27 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-06 02:01:28 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-06 02:01:28 (4446) [INFO] * 2024-02-06 02:01:28 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-06 02:01:28 (4416) [INFO] * 2024-02-06 02:04:40 (4429) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/912725255b64e9d74c4137830af85aa3451b3ca327c49b5055995bad3c70d928-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-02-06 02:04:40 (4429) [INFO] Trying other mirror. * 2024-02-06 02:04:40 (4429) [INFO] To address this issue please refer to the below wiki article * 2024-02-06 02:04:40 (4429) [INFO] * 2024-02-06 02:04:40 (4429) [INFO] https://wiki.centos.org/yum-errors * 2024-02-06 02:04:40 (4429) [INFO] * 2024-02-06 02:04:40 (4429) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-02-06 02:04:40 (4429) [INFO] * 2024-02-06 02:05:44 (4429) [INFO] * 2024-02-06 02:05:44 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-06 02:05:44 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-06 02:05:45 (4446) [INFO] * 2024-02-06 02:05:45 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-06 02:05:45 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-06 02:05:48 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-06 02:09:40 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-06 02:09:40 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-06 02:09:40 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-06 02:09:40 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-06 02:09:40 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-06 02:09:40 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-06 02:09:40 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8ZuVr5OUN9/ea_profile.json * 2024-02-06 02:09:43 (2436) [INFO] Backed up EA4 profile to /tmp/8ZuVr5OUN9/ea_profile.json * 2024-02-06 02:09:43 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-06 02:09:47 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-07 02:00:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-07 02:00:27 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-07 02:00:27 (1844) [INFO] Checking if your system is up to date: * 2024-02-07 02:00:27 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-07 02:00:27 (4416) [INFO] * 2024-02-07 02:00:27 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-07 02:00:27 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-07 02:00:27 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-07 02:00:27 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-07 02:00:27 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-07 02:00:27 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-07 02:00:28 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-07 02:00:28 (4446) [INFO] * 2024-02-07 02:00:28 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-07 02:00:28 (4416) [INFO] * 2024-02-07 02:04:40 (4429) [INFO] * 2024-02-07 02:04:40 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-07 02:04:40 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-07 02:04:41 (4446) [INFO] * 2024-02-07 02:04:41 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-07 02:04:41 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-07 02:04:43 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-07 02:08:19 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-07 02:08:19 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-07 02:08:20 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-07 02:08:20 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-07 02:08:20 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-07 02:08:20 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-07 02:08:20 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GC401EOxOD/ea_profile.json * 2024-02-07 02:08:23 (2436) [INFO] Backed up EA4 profile to /tmp/GC401EOxOD/ea_profile.json * 2024-02-07 02:08:24 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-07 02:08:26 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-08 02:03:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-08 02:03:56 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-08 02:03:56 (1844) [INFO] Checking if your system is up to date: * 2024-02-08 02:03:56 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-08 02:03:56 (4416) [INFO] * 2024-02-08 02:03:57 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-08 02:03:57 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-08 02:03:57 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-08 02:03:57 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-08 02:03:57 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-08 02:03:57 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-08 02:03:58 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-08 02:03:58 (4446) [INFO] * 2024-02-08 02:03:58 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-08 02:03:58 (4416) [INFO] * 2024-02-08 02:08:29 (4429) [INFO] * 2024-02-08 02:08:29 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-08 02:08:29 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-08 02:08:29 (4446) [INFO] * 2024-02-08 02:08:29 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-08 02:08:29 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-08 02:08:33 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-08 02:12:14 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-08 02:12:14 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-08 02:12:14 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-08 02:12:14 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-08 02:12:14 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-08 02:12:14 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-08 02:12:14 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T_qr1go0Lq/ea_profile.json * 2024-02-08 02:12:17 (2436) [INFO] Backed up EA4 profile to /tmp/T_qr1go0Lq/ea_profile.json * 2024-02-08 02:12:18 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-08 02:12:21 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-09 01:55:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-09 01:55:35 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-09 01:55:35 (1844) [INFO] Checking if your system is up to date: * 2024-02-09 01:55:35 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-09 01:55:35 (4416) [INFO] * 2024-02-09 01:55:35 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-09 01:55:36 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-09 01:55:36 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-09 01:55:36 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-09 01:55:36 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-09 01:55:36 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-09 01:55:36 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-09 01:55:36 (4446) [INFO] * 2024-02-09 01:55:36 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-09 01:55:36 (4416) [INFO] * 2024-02-09 02:00:01 (4429) [INFO] * 2024-02-09 02:00:01 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-09 02:00:01 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-09 02:00:02 (4446) [INFO] * 2024-02-09 02:00:02 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-09 02:00:02 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-09 02:00:06 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-09 02:03:35 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-09 02:03:35 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-09 02:03:36 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-09 02:03:36 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-09 02:03:36 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-09 02:03:36 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-09 02:03:36 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kwETCOkBcg/ea_profile.json * 2024-02-09 02:03:38 (2436) [INFO] Backed up EA4 profile to /tmp/kwETCOkBcg/ea_profile.json * 2024-02-09 02:03:39 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-09 02:03:42 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-10 02:04:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-10 02:04:31 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-10 02:04:31 (1844) [INFO] Checking if your system is up to date: * 2024-02-10 02:04:31 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-10 02:04:31 (4416) [INFO] * 2024-02-10 02:04:32 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-10 02:04:32 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-10 02:04:32 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-10 02:04:32 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-10 02:04:32 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-10 02:04:32 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-10 02:04:33 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-10 02:04:33 (4446) [INFO] * 2024-02-10 02:04:33 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-10 02:04:33 (4416) [INFO] * 2024-02-10 02:08:48 (4429) [INFO] * 2024-02-10 02:08:48 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-10 02:08:48 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-10 02:08:49 (4446) [INFO] * 2024-02-10 02:08:49 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-10 02:08:49 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-10 02:08:52 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-10 02:12:15 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-10 02:12:15 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-10 02:12:15 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-10 02:12:15 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-10 02:12:15 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-10 02:12:15 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-10 02:12:15 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V0CS_XICyX/ea_profile.json * 2024-02-10 02:12:18 (2436) [INFO] Backed up EA4 profile to /tmp/V0CS_XICyX/ea_profile.json * 2024-02-10 02:12:19 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-10 02:12:22 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-11 02:01:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-11 02:01:49 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-11 02:01:49 (1844) [INFO] Checking if your system is up to date: * 2024-02-11 02:01:49 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-11 02:01:49 (4416) [INFO] * 2024-02-11 02:01:49 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-11 02:01:49 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-11 02:01:49 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-11 02:01:49 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-11 02:01:49 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-11 02:01:49 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-11 02:01:50 (4429) [INFO] Other repos take up 800 k of disk space (use --verbose for details) * 2024-02-11 02:01:50 (4446) [INFO] * 2024-02-11 02:01:50 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-11 02:01:50 (4416) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] One of the configured repositories failed (Unknown), * 2024-02-11 02:02:46 (4429) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-11 02:02:46 (4429) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-11 02:02:46 (4429) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-11 02:02:46 (4429) [INFO] distribution release than is supported by the repository (and the * 2024-02-11 02:02:46 (4429) [INFO] packages for the previous distribution release still work). * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-11 02:02:46 (4429) [INFO] yum --disablerepo= ... * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-11 02:02:46 (4429) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-11 02:02:46 (4429) [INFO] again or use --enablerepo for temporary usage: * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] yum-config-manager --disable * 2024-02-11 02:02:46 (4429) [INFO] or * 2024-02-11 02:02:46 (4429) [INFO] subscription-manager repos --disable= * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-11 02:02:46 (4429) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-11 02:02:46 (4429) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-11 02:02:46 (4429) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-11 02:02:46 (4429) [INFO] compromise: * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-11 02:02:46 (4429) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-11 02:02:46 (4446) [INFO] * 2024-02-11 02:02:46 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-11 02:02:46 (1865) [INFO] Checking /scripts/sysup * 2024-02-11 02:02:46 (4415) [INFO] Running: /scripts/sysup * 2024-02-11 02:02:46 (4416) [INFO] * 2024-02-11 02:02:46 (4429) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-11 02:02:49 (4429) [INFO] All Needed Packages are already installed. * 2024-02-11 02:02:49 (4446) [INFO] * 2024-02-11 02:02:52 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-11 02:10:24 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-11 02:10:24 (1704) [ERROR] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. * 2024-02-11 02:10:24 (162) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-11 02:10:24 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-11 02:10:24 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-11 02:10:25 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-11 02:10:25 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-11 02:10:25 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-11 02:10:25 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-11 02:10:25 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D6DthWVkuX/ea_profile.json * 2024-02-11 02:10:27 (2436) [INFO] Backed up EA4 profile to /tmp/D6DthWVkuX/ea_profile.json * 2024-02-11 02:10:28 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-11 02:10:32 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-12 02:00:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-12 02:00:16 (162) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-12 02:00:16 (1844) [INFO] Checking if your system is up to date: * 2024-02-12 02:00:16 (4415) [INFO] Running: /usr/bin/yum clean all * 2024-02-12 02:00:16 (4416) [INFO] * 2024-02-12 02:00:16 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-12 02:00:17 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-12 02:00:17 (4429) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-12 02:00:17 (4429) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-12 02:00:17 (4429) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-12 02:00:17 (4429) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-12 02:00:17 (4429) [INFO] Other repos take up 832 k of disk space (use --verbose for details) * 2024-02-12 02:00:17 (4446) [INFO] * 2024-02-12 02:00:17 (4415) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-12 02:00:17 (4416) [INFO] * 2024-02-12 02:04:44 (4429) [INFO] * 2024-02-12 02:04:44 (4429) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-12 02:04:44 (4429) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-12 02:04:45 (4446) [INFO] * 2024-02-12 02:04:45 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-12 02:04:45 (162) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-12 02:04:48 (1763) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-12 02:08:22 (1912) [ERROR] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". Please set the 'PermitRootLogin' value in /etc/ssh/sshd_config before upgrading. * 2024-02-12 02:08:22 (162) [WARN] *** Elevation Blocker detected: *** Issue with sshd configuration * 2024-02-12 02:08:23 (1246) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-12 02:08:23 (162) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-12 02:08:23 (162) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-12 02:08:23 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-12 02:08:23 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jNQxb30DG4/ea_profile.json * 2024-02-12 02:08:26 (2436) [INFO] Backed up EA4 profile to /tmp/jNQxb30DG4/ea_profile.json * 2024-02-12 02:08:27 (162) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-12 02:08:29 (270) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-13 02:02:40 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-13 02:02:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-13 02:02:42 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-13 02:02:42 (1845) [INFO] Checking if your system is up to date: * 2024-02-13 02:02:42 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-13 02:02:42 (4463) [INFO] * 2024-02-13 02:02:43 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-13 02:02:43 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-13 02:02:43 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-13 02:02:43 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-13 02:02:43 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-13 02:02:43 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-13 02:02:44 (4476) [INFO] Other repos take up 832 k of disk space (use --verbose for details) * 2024-02-13 02:02:44 (4493) [INFO] * 2024-02-13 02:02:44 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-13 02:02:44 (4463) [INFO] * 2024-02-13 02:07:13 (4476) [INFO] * 2024-02-13 02:07:13 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-13 02:07:13 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-13 02:07:14 (4493) [INFO] * 2024-02-13 02:07:14 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-13 02:07:14 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-13 02:07:17 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-13 02:10:38 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-13 02:10:38 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-13 02:10:38 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-13 02:10:38 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-13 02:10:38 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fxPEnilfp3/ea_profile.json * 2024-02-13 02:10:41 (2437) [INFO] Backed up EA4 profile to /tmp/fxPEnilfp3/ea_profile.json * 2024-02-13 02:10:42 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-13 02:10:45 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-14 02:04:16 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-14 02:04:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-14 02:04:18 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-14 02:04:18 (1845) [INFO] Checking if your system is up to date: * 2024-02-14 02:04:18 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-14 02:04:18 (4463) [INFO] * 2024-02-14 02:04:19 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-14 02:04:19 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-14 02:04:19 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-14 02:04:19 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-14 02:04:19 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-14 02:04:19 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-14 02:04:20 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-14 02:04:20 (4493) [INFO] * 2024-02-14 02:04:20 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-14 02:04:20 (4463) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] One of the configured repositories failed (Unknown), * 2024-02-14 02:05:16 (4476) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-14 02:05:16 (4476) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-14 02:05:16 (4476) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-14 02:05:16 (4476) [INFO] distribution release than is supported by the repository (and the * 2024-02-14 02:05:16 (4476) [INFO] packages for the previous distribution release still work). * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-14 02:05:16 (4476) [INFO] yum --disablerepo= ... * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-14 02:05:16 (4476) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-14 02:05:16 (4476) [INFO] again or use --enablerepo for temporary usage: * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] yum-config-manager --disable * 2024-02-14 02:05:16 (4476) [INFO] or * 2024-02-14 02:05:16 (4476) [INFO] subscription-manager repos --disable= * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-14 02:05:16 (4476) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-14 02:05:16 (4476) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-14 02:05:16 (4476) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-14 02:05:16 (4476) [INFO] compromise: * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-14 02:05:16 (4476) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-14 02:05:16 (4493) [INFO] * 2024-02-14 02:05:16 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-14 02:05:16 (1866) [INFO] Checking /scripts/sysup * 2024-02-14 02:05:16 (4462) [INFO] Running: /scripts/sysup * 2024-02-14 02:05:16 (4463) [INFO] * 2024-02-14 02:05:16 (4476) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-14 02:05:19 (4476) [INFO] All Needed Packages are already installed. * 2024-02-14 02:05:19 (4493) [INFO] * 2024-02-14 02:05:22 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-14 02:14:05 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-14 02:14:05 (1705) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.oit.uci.edu/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo1.sea.innoscale.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rit.edu/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.rackspace.com/CentOS/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://nc-centos-mirror.iwebfusion.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mnvoip.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ix-denver.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.mit.edu/centos/7.9.2009/updates/x86_64/repodata/e51e85f92481d159a62b12c9fd3c54e006e7380e806a6a47d695a61900b9c855-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-02-14 02:14:05 (163) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-14 02:14:06 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-14 02:14:06 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-14 02:14:06 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-14 02:14:06 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-14 02:14:06 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r2ElPrwqaP/ea_profile.json * 2024-02-14 02:14:08 (2437) [INFO] Backed up EA4 profile to /tmp/r2ElPrwqaP/ea_profile.json * 2024-02-14 02:14:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-14 02:14:12 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-15 01:55:19 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-15 01:55:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-15 01:55:21 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-15 01:55:21 (1845) [INFO] Checking if your system is up to date: * 2024-02-15 01:55:21 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-15 01:55:21 (4463) [INFO] * 2024-02-15 01:55:22 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-15 01:55:22 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-15 01:55:22 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-15 01:55:22 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-15 01:55:22 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-15 01:55:22 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-15 01:55:22 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-15 01:55:22 (4493) [INFO] * 2024-02-15 01:55:22 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-15 01:55:22 (4463) [INFO] * 2024-02-15 01:59:45 (4476) [INFO] * 2024-02-15 01:59:45 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-15 01:59:45 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-15 01:59:46 (4493) [INFO] * 2024-02-15 01:59:46 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-15 01:59:46 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-15 01:59:48 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-15 02:03:23 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-15 02:03:23 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-15 02:03:23 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-15 02:03:23 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-15 02:03:23 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VoSzlT5oOe/ea_profile.json * 2024-02-15 02:03:25 (2437) [INFO] Backed up EA4 profile to /tmp/VoSzlT5oOe/ea_profile.json * 2024-02-15 02:03:25 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-15 02:03:29 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-16 02:01:23 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-16 02:01:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-16 02:01:25 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-16 02:01:25 (1845) [INFO] Checking if your system is up to date: * 2024-02-16 02:01:25 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-16 02:01:25 (4463) [INFO] * 2024-02-16 02:01:26 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-16 02:01:26 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-16 02:01:26 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-16 02:01:26 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-16 02:01:26 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-16 02:01:26 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-16 02:01:27 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-16 02:01:27 (4493) [INFO] * 2024-02-16 02:01:27 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-16 02:01:27 (4463) [INFO] * 2024-02-16 02:05:50 (4476) [INFO] * 2024-02-16 02:05:50 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-16 02:05:50 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-16 02:05:50 (4493) [INFO] * 2024-02-16 02:05:50 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-16 02:05:50 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-16 02:05:53 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-16 02:09:28 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-16 02:09:28 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-16 02:09:28 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-16 02:09:28 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-16 02:09:28 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9GWljiYqHi/ea_profile.json * 2024-02-16 02:09:30 (2437) [INFO] Backed up EA4 profile to /tmp/9GWljiYqHi/ea_profile.json * 2024-02-16 02:09:30 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-16 02:09:34 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-17 02:05:42 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-17 02:05:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-17 02:05:44 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-17 02:05:44 (1845) [INFO] Checking if your system is up to date: * 2024-02-17 02:05:44 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-17 02:05:44 (4463) [INFO] * 2024-02-17 02:05:44 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-17 02:05:45 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-17 02:05:45 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-17 02:05:45 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-17 02:05:45 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-17 02:05:45 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-17 02:05:45 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-17 02:05:45 (4493) [INFO] * 2024-02-17 02:05:45 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-17 02:05:45 (4463) [INFO] * 2024-02-17 02:09:37 (4476) [INFO] * 2024-02-17 02:09:37 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-17 02:09:37 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-17 02:09:38 (4493) [INFO] * 2024-02-17 02:09:38 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-17 02:09:38 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-17 02:09:41 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-17 02:12:53 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-17 02:12:53 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-17 02:12:53 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-17 02:12:53 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-17 02:12:53 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gb5OBJ7F7I/ea_profile.json * 2024-02-17 02:12:55 (2437) [INFO] Backed up EA4 profile to /tmp/gb5OBJ7F7I/ea_profile.json * 2024-02-17 02:12:56 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-17 02:12:59 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-18 02:03:07 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-18 02:03:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-18 02:03:10 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-18 02:03:10 (1845) [INFO] Checking if your system is up to date: * 2024-02-18 02:03:10 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-18 02:03:10 (4463) [INFO] * 2024-02-18 02:03:10 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-18 02:03:11 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-18 02:03:11 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-18 02:03:11 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-18 02:03:11 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-18 02:03:11 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-18 02:03:11 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-18 02:03:11 (4493) [INFO] * 2024-02-18 02:03:11 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-18 02:03:11 (4463) [INFO] * 2024-02-18 02:07:39 (4476) [INFO] * 2024-02-18 02:07:39 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-18 02:07:39 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-18 02:07:39 (4493) [INFO] * 2024-02-18 02:07:39 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-18 02:07:39 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-18 02:07:43 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-18 02:11:34 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-18 02:11:34 (1705) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30658 milliseconds') * 2024-02-18 02:11:34 (163) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-18 02:11:35 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-18 02:11:35 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-18 02:11:35 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-18 02:11:35 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-18 02:11:35 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/10E5G3o7MY/ea_profile.json * 2024-02-18 02:11:37 (2437) [INFO] Backed up EA4 profile to /tmp/10E5G3o7MY/ea_profile.json * 2024-02-18 02:11:38 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-18 02:11:41 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-19 01:54:53 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-19 01:54:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-19 01:54:55 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-19 01:54:55 (1845) [INFO] Checking if your system is up to date: * 2024-02-19 01:54:55 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-19 01:54:55 (4463) [INFO] * 2024-02-19 01:54:56 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-19 01:54:56 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-19 01:54:56 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-19 01:54:56 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-19 01:54:56 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-19 01:54:56 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-19 01:54:56 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-19 01:54:56 (4493) [INFO] * 2024-02-19 01:54:56 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-19 01:54:56 (4463) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] One of the configured repositories failed (Unknown), * 2024-02-19 01:55:52 (4476) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-19 01:55:52 (4476) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-19 01:55:52 (4476) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-19 01:55:52 (4476) [INFO] distribution release than is supported by the repository (and the * 2024-02-19 01:55:52 (4476) [INFO] packages for the previous distribution release still work). * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-19 01:55:52 (4476) [INFO] yum --disablerepo= ... * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-19 01:55:52 (4476) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-19 01:55:52 (4476) [INFO] again or use --enablerepo for temporary usage: * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] yum-config-manager --disable * 2024-02-19 01:55:52 (4476) [INFO] or * 2024-02-19 01:55:52 (4476) [INFO] subscription-manager repos --disable= * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-19 01:55:52 (4476) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-19 01:55:52 (4476) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-19 01:55:52 (4476) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-19 01:55:52 (4476) [INFO] compromise: * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-19 01:55:52 (4476) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-19 01:55:52 (4493) [INFO] * 2024-02-19 01:55:52 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-19 01:55:52 (1866) [INFO] Checking /scripts/sysup * 2024-02-19 01:55:52 (4462) [INFO] Running: /scripts/sysup * 2024-02-19 01:55:52 (4463) [INFO] * 2024-02-19 01:55:52 (4476) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-19 01:55:55 (4476) [INFO] All Needed Packages are already installed. * 2024-02-19 01:55:55 (4493) [INFO] * 2024-02-19 01:55:57 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-19 02:02:55 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-19 02:02:55 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-19 02:02:55 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-19 02:02:55 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-19 02:02:55 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PcPlBQphnp/ea_profile.json * 2024-02-19 02:02:58 (2437) [INFO] Backed up EA4 profile to /tmp/PcPlBQphnp/ea_profile.json * 2024-02-19 02:02:59 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-19 02:03:02 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-20 02:05:50 (1912) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-20 02:05:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-20 02:05:53 (163) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-20 02:05:53 (1845) [INFO] Checking if your system is up to date: * 2024-02-20 02:05:53 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-20 02:05:53 (4463) [INFO] * 2024-02-20 02:05:53 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-20 02:05:53 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-20 02:05:53 (4476) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-20 02:05:53 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-20 02:05:53 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-20 02:05:53 (4476) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-20 02:05:54 (4476) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-20 02:05:54 (4493) [INFO] * 2024-02-20 02:05:54 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-20 02:05:54 (4463) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] One of the configured repositories failed (Unknown), * 2024-02-20 02:06:50 (4476) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-20 02:06:50 (4476) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-20 02:06:50 (4476) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-20 02:06:50 (4476) [INFO] distribution release than is supported by the repository (and the * 2024-02-20 02:06:50 (4476) [INFO] packages for the previous distribution release still work). * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-20 02:06:50 (4476) [INFO] yum --disablerepo= ... * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-20 02:06:50 (4476) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-20 02:06:50 (4476) [INFO] again or use --enablerepo for temporary usage: * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] yum-config-manager --disable * 2024-02-20 02:06:50 (4476) [INFO] or * 2024-02-20 02:06:50 (4476) [INFO] subscription-manager repos --disable= * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-20 02:06:50 (4476) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-20 02:06:50 (4476) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-20 02:06:50 (4476) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-20 02:06:50 (4476) [INFO] compromise: * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-20 02:06:50 (4476) [INFO] * 2024-02-20 02:06:50 (4476) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-20 02:06:50 (4493) [INFO] * 2024-02-20 02:06:50 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-20 02:06:50 (1866) [INFO] Checking /scripts/sysup * 2024-02-20 02:06:50 (4462) [INFO] Running: /scripts/sysup * 2024-02-20 02:06:50 (4463) [INFO] * 2024-02-20 02:06:51 (4476) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-20 02:06:52 (4476) [INFO] All Needed Packages are already installed. * 2024-02-20 02:06:52 (4493) [INFO] * 2024-02-20 02:06:55 (1764) [ERROR] 5 package(s) installed from unsupported YUM repo 'MariaDB100' from /etc/yum.repos.d/MariaDB100.repo * 2024-02-20 02:15:50 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-20 02:15:50 (1705) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/4c366cce1d4d7b973f0f1b434c2e8d5e907324154f6eba8d3b72af9030d2df2b-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c17f5a125bc69be7a6a0bb3f9b999929b9298928e634fc1dae1305df5dbb286-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.web-ster.com/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ftp.osuosl.org/pub/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rcs.alaska.edu/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://us.mirrors.virtono.com/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.ash.fastserv.com/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://repo.ialab.dsu.edu/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://opencolo.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://ziply.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/7f8b6abf5de2f50cd8c4d1e3286d3b5b2ff2a4dfbe5522102a070a3710df7672-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/4c366cce1d4d7b973f0f1b434c2e8d5e907324154f6eba8d3b72af9030d2df2b-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c17f5a125bc69be7a6a0bb3f9b999929b9298928e634fc1dae1305df5dbb286-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/4c366cce1d4d7b973f0f1b434c2e8d5e907324154f6eba8d3b72af9030d2df2b-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. One of the configured repositories failed (EL-7 - Imunify360), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360 or subscription-manager repos --disable=imunify360 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360.skip_if_unavailable=true failure: repodata/4c366cce1d4d7b973f0f1b434c2e8d5e907324154f6eba8d3b72af9030d2df2b-filelists.sqlite.bz2 from imunify360: [Errno 256] No more mirrors to try. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/4c366cce1d4d7b973f0f1b434c2e8d5e907324154f6eba8d3b72af9030d2df2b-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-02-20 02:15:50 (163) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-20 02:15:51 (1247) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-20 02:15:51 (163) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-20 02:15:51 (163) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-20 02:15:51 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-20 02:15:51 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0AY_MIIHJu/ea_profile.json * 2024-02-20 02:19:08 (2437) [INFO] Backed up EA4 profile to /tmp/0AY_MIIHJu/ea_profile.json * 2024-02-20 02:19:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-20 02:19:12 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-21 02:02:49 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-21 02:02:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-21 02:02:52 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-21 02:02:53 (1782) [INFO] Checking if your system is up to date: * 2024-02-21 02:02:53 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-21 02:02:53 (4911) [INFO] * 2024-02-21 02:02:53 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-21 02:02:54 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-21 02:02:54 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-21 02:02:54 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-21 02:02:54 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-21 02:02:54 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-21 02:02:54 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-21 02:02:54 (4941) [INFO] * 2024-02-21 02:02:54 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-21 02:02:54 (4911) [INFO] * 2024-02-21 02:07:09 (4924) [INFO] * 2024-02-21 02:07:09 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-21 02:07:09 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-21 02:07:09 (4941) [INFO] * 2024-02-21 02:07:09 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-21 02:07:09 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-21 02:10:35 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-21 02:10:35 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-21 02:10:35 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-21 02:10:35 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-21 02:10:35 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NlAMcX3iGL/ea_profile.json * 2024-02-21 02:10:37 (2386) [INFO] Backed up EA4 profile to /tmp/NlAMcX3iGL/ea_profile.json * 2024-02-21 02:10:38 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-21 02:10:41 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-22 02:05:03 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-22 02:05:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-22 02:05:06 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-22 02:05:07 (1782) [INFO] Checking if your system is up to date: * 2024-02-22 02:05:07 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-22 02:05:07 (4911) [INFO] * 2024-02-22 02:05:07 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-22 02:05:08 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-22 02:05:08 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-22 02:05:08 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-22 02:05:08 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-22 02:05:08 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-22 02:05:08 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-22 02:05:08 (4941) [INFO] * 2024-02-22 02:05:08 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-22 02:05:08 (4911) [INFO] * 2024-02-22 02:08:18 (4924) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/cd16842ac4d0255d18f5811ec29b44794bacd7fdb2f6d47428dcf8e11b0203d8-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-02-22 02:08:18 (4924) [INFO] Trying other mirror. * 2024-02-22 02:08:18 (4924) [INFO] To address this issue please refer to the below wiki article * 2024-02-22 02:08:18 (4924) [INFO] * 2024-02-22 02:08:18 (4924) [INFO] https://wiki.centos.org/yum-errors * 2024-02-22 02:08:18 (4924) [INFO] * 2024-02-22 02:08:18 (4924) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-02-22 02:08:18 (4924) [INFO] * 2024-02-22 02:08:33 (4924) [INFO] https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/304cd8c05567e1542146a361b311437a201635f50b90dfb161334a27fea52f67-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-02-22 02:08:33 (4924) [INFO] Trying other mirror. * 2024-02-22 02:09:28 (4924) [INFO] * 2024-02-22 02:09:28 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-22 02:09:28 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-22 02:09:28 (4941) [INFO] * 2024-02-22 02:09:28 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-22 02:09:28 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-22 02:13:37 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-22 02:13:37 (1642) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30535 milliseconds') https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/933e2194d2ab241aed71127510ccece60d795246fd01d74d88444bfbeb7d2655-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/083dde008aeffcda21a19c4d99df7e20082bec2bf3683d095433a4dfccb88021-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2024-02-22 02:13:37 (170) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-22 02:13:38 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-22 02:13:38 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-22 02:13:38 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-22 02:13:38 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-22 02:13:38 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sF2jcbgBnu/ea_profile.json * 2024-02-22 02:13:40 (2386) [INFO] Backed up EA4 profile to /tmp/sF2jcbgBnu/ea_profile.json * 2024-02-22 02:13:41 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-22 02:13:44 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-23 02:01:59 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-23 02:02:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-23 02:02:03 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-23 02:02:03 (1782) [INFO] Checking if your system is up to date: * 2024-02-23 02:02:03 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-23 02:02:03 (4911) [INFO] * 2024-02-23 02:02:04 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-23 02:02:04 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-23 02:02:04 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-23 02:02:04 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-23 02:02:04 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-23 02:02:04 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-23 02:02:04 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-23 02:02:04 (4941) [INFO] * 2024-02-23 02:02:04 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-23 02:02:04 (4911) [INFO] * 2024-02-23 02:06:28 (4924) [INFO] * 2024-02-23 02:06:28 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-23 02:06:28 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-23 02:06:29 (4941) [INFO] * 2024-02-23 02:06:29 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-23 02:06:29 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-23 02:10:08 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-23 02:10:08 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-23 02:10:08 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-23 02:10:08 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-23 02:10:08 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sJFSI353MI/ea_profile.json * 2024-02-23 02:10:11 (2386) [INFO] Backed up EA4 profile to /tmp/sJFSI353MI/ea_profile.json * 2024-02-23 02:10:11 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-23 02:10:14 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-24 01:56:39 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-24 01:56:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-24 01:56:42 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-24 01:56:42 (1782) [INFO] Checking if your system is up to date: * 2024-02-24 01:56:42 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-24 01:56:42 (4911) [INFO] * 2024-02-24 01:56:43 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-24 01:56:43 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-24 01:56:43 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-24 01:56:43 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-24 01:56:43 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-24 01:56:43 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-24 01:56:44 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-24 01:56:44 (4941) [INFO] * 2024-02-24 01:56:44 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-24 01:56:44 (4911) [INFO] * 2024-02-24 02:00:57 (4924) [INFO] * 2024-02-24 02:00:57 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-24 02:00:57 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-24 02:00:57 (4941) [INFO] * 2024-02-24 02:00:57 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-24 02:00:57 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-24 02:04:25 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-24 02:04:25 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-24 02:04:25 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-24 02:04:25 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-24 02:04:25 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/edMQPSW4c7/ea_profile.json * 2024-02-24 02:04:27 (2386) [INFO] Backed up EA4 profile to /tmp/edMQPSW4c7/ea_profile.json * 2024-02-24 02:04:28 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-24 02:04:30 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-25 02:04:46 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-25 02:04:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-25 02:04:49 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-25 02:04:50 (1782) [INFO] Checking if your system is up to date: * 2024-02-25 02:04:50 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-25 02:04:50 (4911) [INFO] * 2024-02-25 02:04:50 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-25 02:04:51 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-25 02:04:51 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-25 02:04:51 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-25 02:04:51 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-25 02:04:51 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-25 02:04:51 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-25 02:04:51 (4941) [INFO] * 2024-02-25 02:04:51 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-25 02:04:51 (4911) [INFO] * 2024-02-25 02:09:12 (4924) [INFO] * 2024-02-25 02:09:12 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-25 02:09:12 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-25 02:09:12 (4941) [INFO] * 2024-02-25 02:09:12 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-25 02:09:12 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-25 02:13:01 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-25 02:13:01 (1642) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30103 milliseconds with 0 out of 0 bytes received') * 2024-02-25 02:13:01 (170) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-25 02:13:02 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-25 02:13:02 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-25 02:13:02 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-25 02:13:02 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-25 02:13:02 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oZFwI3PPiu/ea_profile.json * 2024-02-25 02:13:05 (2386) [INFO] Backed up EA4 profile to /tmp/oZFwI3PPiu/ea_profile.json * 2024-02-25 02:13:05 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-25 02:13:08 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-26 02:02:11 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-26 02:02:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-26 02:02:13 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-26 02:02:14 (1782) [INFO] Checking if your system is up to date: * 2024-02-26 02:02:14 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-26 02:02:14 (4911) [INFO] * 2024-02-26 02:02:14 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-26 02:02:14 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-26 02:02:14 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-26 02:02:14 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-26 02:02:14 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-26 02:02:14 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-26 02:02:14 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-26 02:02:15 (4941) [INFO] * 2024-02-26 02:02:15 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-26 02:02:15 (4911) [INFO] * 2024-02-26 02:06:49 (4924) [INFO] * 2024-02-26 02:06:49 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-26 02:06:49 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-26 02:06:49 (4941) [INFO] * 2024-02-26 02:06:49 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-26 02:06:49 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-26 02:10:23 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-26 02:10:23 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-26 02:10:23 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-26 02:10:23 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-26 02:10:23 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u0PRgJ7cKc/ea_profile.json * 2024-02-26 02:10:25 (2386) [INFO] Backed up EA4 profile to /tmp/u0PRgJ7cKc/ea_profile.json * 2024-02-26 02:10:26 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-26 02:10:29 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-27 02:01:43 (1849) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-27 02:01:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-27 02:01:45 (170) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-27 02:01:46 (1782) [INFO] Checking if your system is up to date: * 2024-02-27 02:01:46 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-27 02:01:46 (4911) [INFO] * 2024-02-27 02:01:46 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-27 02:01:47 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-27 02:01:47 (4924) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-27 02:01:47 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-27 02:01:47 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-27 02:01:47 (4924) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-27 02:01:47 (4924) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-27 02:01:47 (4941) [INFO] * 2024-02-27 02:01:47 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-27 02:01:47 (4911) [INFO] * 2024-02-27 02:06:17 (4924) [INFO] * 2024-02-27 02:06:17 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-27 02:06:17 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-27 02:06:17 (4941) [INFO] * 2024-02-27 02:06:17 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-27 02:06:17 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-27 02:09:53 (1265) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-27 02:09:53 (170) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-27 02:09:53 (170) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-27 02:09:53 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-27 02:09:53 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QCULAqcZ0n/ea_profile.json * 2024-02-27 02:09:56 (2386) [INFO] Backed up EA4 profile to /tmp/QCULAqcZ0n/ea_profile.json * 2024-02-27 02:09:56 (170) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-27 02:09:59 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-28 02:01:31 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-28 02:01:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-28 02:01:33 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-28 02:01:34 (1828) [INFO] Checking if your system is up to date: * 2024-02-28 02:01:34 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-02-28 02:01:34 (5105) [INFO] * 2024-02-28 02:01:35 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-28 02:01:35 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-28 02:01:35 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-28 02:01:35 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-28 02:01:35 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-28 02:01:35 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-28 02:01:36 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-28 02:01:36 (5135) [INFO] * 2024-02-28 02:01:36 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-28 02:01:36 (5105) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] One of the configured repositories failed (Unknown), * 2024-02-28 02:02:32 (5118) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-02-28 02:02:32 (5118) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-02-28 02:02:32 (5118) [INFO] upstream. This is most often useful if you are using a newer * 2024-02-28 02:02:32 (5118) [INFO] distribution release than is supported by the repository (and the * 2024-02-28 02:02:32 (5118) [INFO] packages for the previous distribution release still work). * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] 3. Run the command with the repository temporarily disabled * 2024-02-28 02:02:32 (5118) [INFO] yum --disablerepo= ... * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-02-28 02:02:32 (5118) [INFO] will then just ignore the repository until you permanently enable it * 2024-02-28 02:02:32 (5118) [INFO] again or use --enablerepo for temporary usage: * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] yum-config-manager --disable * 2024-02-28 02:02:32 (5118) [INFO] or * 2024-02-28 02:02:32 (5118) [INFO] subscription-manager repos --disable= * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-02-28 02:02:32 (5118) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-02-28 02:02:32 (5118) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-02-28 02:02:32 (5118) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-02-28 02:02:32 (5118) [INFO] compromise: * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-02-28 02:02:32 (5118) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-02-28 02:02:32 (5135) [INFO] * 2024-02-28 02:02:32 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-28 02:02:32 (1849) [INFO] Checking /scripts/sysup * 2024-02-28 02:02:32 (5104) [INFO] Running: /scripts/sysup * 2024-02-28 02:02:32 (5105) [INFO] * 2024-02-28 02:02:32 (5118) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-02-28 02:02:35 (5118) [INFO] All Needed Packages are already installed. * 2024-02-28 02:02:35 (5135) [INFO] * 2024-02-28 02:09:56 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-28 02:09:56 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-28 02:09:56 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-28 02:09:56 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-28 02:09:56 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oevE9scfWW/ea_profile.json * 2024-02-28 02:09:59 (2488) [INFO] Backed up EA4 profile to /tmp/oevE9scfWW/ea_profile.json * 2024-02-28 02:09:59 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-28 02:10:03 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-29 01:55:12 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-02-29 01:55:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-29 01:55:15 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-29 01:55:16 (1828) [INFO] Checking if your system is up to date: * 2024-02-29 01:55:16 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-02-29 01:55:16 (5105) [INFO] * 2024-02-29 01:55:16 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-29 01:55:17 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-02-29 01:55:17 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-29 01:55:17 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-29 01:55:17 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-29 01:55:17 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-02-29 01:55:17 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-02-29 01:55:17 (5135) [INFO] * 2024-02-29 01:55:17 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-29 01:55:17 (5105) [INFO] * 2024-02-29 02:00:31 (5118) [INFO] * 2024-02-29 02:00:31 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-29 02:00:31 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-29 02:00:32 (5135) [INFO] * 2024-02-29 02:00:32 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-29 02:00:32 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-29 02:04:25 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-29 02:04:25 (1688) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-02-29 02:04:25 (173) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-29 02:04:26 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-02-29 02:04:26 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-02-29 02:04:26 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-02-29 02:04:26 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-29 02:04:26 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HXQUPfT9Mu/ea_profile.json * 2024-02-29 02:04:28 (2488) [INFO] Backed up EA4 profile to /tmp/HXQUPfT9Mu/ea_profile.json * 2024-02-29 02:04:29 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-02-29 02:04:32 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-01 02:06:27 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-01 02:06:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-01 02:06:29 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-01 02:06:30 (1828) [INFO] Checking if your system is up to date: * 2024-03-01 02:06:30 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-01 02:06:30 (5105) [INFO] * 2024-03-01 02:06:30 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-01 02:06:30 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-01 02:06:30 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-01 02:06:30 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-01 02:06:30 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-01 02:06:30 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-01 02:06:31 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-01 02:06:31 (5135) [INFO] * 2024-03-01 02:06:31 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-01 02:06:31 (5105) [INFO] * 2024-03-01 02:10:15 (5118) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-03-01 02:10:15 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:31 (5118) [INFO] http://mirrors.xtom.com/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:31 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:31 (5118) [INFO] http://mirror.centos.iad1.serverforge.org/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:31 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:31 (5118) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:31 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:46 (5118) [INFO] http://tx-mirror.tier.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:46 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:46 (5118) [INFO] http://mirrors.mit.edu/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:46 (5118) [INFO] Trying other mirror. * 2024-03-01 02:10:47 (5118) [INFO] http://volico.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:10:47 (5118) [INFO] Trying other mirror. * 2024-03-01 02:11:02 (5118) [INFO] http://nnenix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:11:02 (5118) [INFO] Trying other mirror. * 2024-03-01 02:11:17 (5118) [INFO] http://ohioix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:11:17 (5118) [INFO] Trying other mirror. * 2024-03-01 02:11:18 (5118) [INFO] http://mirrors.lug.mtu.edu/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:11:18 (5118) [INFO] Trying other mirror. * 2024-03-01 02:11:33 (5118) [INFO] http://mirror.clarkson.edu/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:11:33 (5118) [INFO] Trying other mirror. * 2024-03-01 02:11:33 (5118) [INFO] http://mirror.cogentco.com/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-03-01 02:11:33 (5118) [INFO] Trying other mirror. * 2024-03-01 02:12:04 (5118) [INFO] * 2024-03-01 02:12:04 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-01 02:12:04 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-01 02:12:05 (5135) [INFO] * 2024-03-01 02:12:05 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-01 02:12:05 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-01 02:15:49 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-01 02:15:49 (1688) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 7196. Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 61 M RSS (388 MB VSZ) Started: Fri Mar 1 02:07:06 2024 - 04:59 ago State : Running, pid: 7196 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 72 M RSS (399 MB VSZ) Started: Fri Mar 1 02:07:06 2024 - 05:02 ago State : Running, pid: 7196 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 76 M RSS (403 MB VSZ) Started: Fri Mar 1 02:07:06 2024 - 05:04 ago State : Running, pid: 7196 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 80 M RSS (407 MB VSZ) Started: Fri Mar 1 02:07:06 2024 - 05:06 ago State : Running, pid: 7196 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 85 M RSS (413 MB VSZ) Started: Fri Mar 1 02:07:06 2024 - 05:08 ago State : Running, pid: 7196 * 2024-03-01 02:15:49 (173) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-03-01 02:15:50 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-01 02:15:50 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-01 02:15:50 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-01 02:15:50 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-01 02:15:50 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R4bP7DHP8N/ea_profile.json * 2024-03-01 02:15:52 (2488) [INFO] Backed up EA4 profile to /tmp/R4bP7DHP8N/ea_profile.json * 2024-03-01 02:15:53 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-01 02:15:56 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-02 02:03:59 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-02 02:04:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-02 02:04:03 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-02 02:04:04 (1828) [INFO] Checking if your system is up to date: * 2024-03-02 02:04:04 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-02 02:04:04 (5105) [INFO] * 2024-03-02 02:04:04 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-02 02:04:04 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-02 02:04:04 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-02 02:04:04 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-02 02:04:04 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-02 02:04:04 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-02 02:04:05 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-02 02:04:05 (5135) [INFO] * 2024-03-02 02:04:05 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-02 02:04:05 (5105) [INFO] * 2024-03-02 02:08:37 (5118) [INFO] * 2024-03-02 02:08:37 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-02 02:08:37 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-02 02:08:37 (5135) [INFO] * 2024-03-02 02:08:37 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-02 02:08:37 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-02 02:12:21 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-02 02:12:21 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-02 02:12:21 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-02 02:12:21 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-02 02:12:21 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vMGZkcpvpw/ea_profile.json * 2024-03-02 02:12:24 (2488) [INFO] Backed up EA4 profile to /tmp/vMGZkcpvpw/ea_profile.json * 2024-03-02 02:12:25 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-02 02:12:28 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-03 02:02:17 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-03 02:02:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-03 02:02:20 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-03 02:02:21 (1828) [INFO] Checking if your system is up to date: * 2024-03-03 02:02:21 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-03 02:02:21 (5105) [INFO] * 2024-03-03 02:02:21 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-03 02:02:21 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-03 02:02:21 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-03 02:02:21 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-03 02:02:21 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-03 02:02:21 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-03 02:02:22 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-03 02:02:22 (5135) [INFO] * 2024-03-03 02:02:22 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-03 02:02:22 (5105) [INFO] * 2024-03-03 02:06:46 (5118) [INFO] * 2024-03-03 02:06:46 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-03 02:06:46 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-03 02:06:46 (5135) [INFO] * 2024-03-03 02:06:46 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-03 02:06:46 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-03 02:10:10 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-03 02:10:10 (1688) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. * 2024-03-03 02:10:10 (173) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-03-03 02:10:11 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-03 02:10:11 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-03 02:10:11 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-03 02:10:11 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-03 02:10:11 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gxc6f4O9xh/ea_profile.json * 2024-03-03 02:10:13 (2488) [INFO] Backed up EA4 profile to /tmp/gxc6f4O9xh/ea_profile.json * 2024-03-03 02:10:14 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-03 02:10:16 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-04 01:56:10 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-04 01:56:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-04 01:56:13 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-04 01:56:14 (1828) [INFO] Checking if your system is up to date: * 2024-03-04 01:56:14 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-04 01:56:14 (5105) [INFO] * 2024-03-04 01:56:14 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-04 01:56:14 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-04 01:56:14 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-04 01:56:14 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-04 01:56:14 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-04 01:56:14 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-04 01:56:15 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-04 01:56:15 (5135) [INFO] * 2024-03-04 01:56:15 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-04 01:56:15 (5105) [INFO] * 2024-03-04 02:00:40 (5118) [INFO] * 2024-03-04 02:00:40 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-04 02:00:40 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-04 02:00:41 (5135) [INFO] * 2024-03-04 02:00:41 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-04 02:00:41 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-04 02:04:34 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-04 02:04:34 (1688) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2024-03-04 02:04:34 (173) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-03-04 02:04:35 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-04 02:04:35 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-04 02:04:35 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-04 02:04:35 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-04 02:04:35 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K9_dZkKVKF/ea_profile.json * 2024-03-04 02:04:37 (2488) [INFO] Backed up EA4 profile to /tmp/K9_dZkKVKF/ea_profile.json * 2024-03-04 02:04:38 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-04 02:04:40 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-05 01:54:59 (1895) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-05 01:55:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-05 01:55:03 (173) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-05 01:55:03 (1828) [INFO] Checking if your system is up to date: * 2024-03-05 01:55:03 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-05 01:55:03 (5105) [INFO] * 2024-03-05 01:55:04 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-05 01:55:04 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-05 01:55:04 (5118) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-05 01:55:04 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-05 01:55:04 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-05 01:55:04 (5118) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-05 01:55:04 (5118) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-05 01:55:04 (5135) [INFO] * 2024-03-05 01:55:04 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-05 01:55:04 (5105) [INFO] * 2024-03-05 01:59:19 (5118) [INFO] * 2024-03-05 01:59:19 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-05 01:59:19 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-05 01:59:19 (5135) [INFO] * 2024-03-05 01:59:19 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-05 01:59:19 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-05 02:02:43 (1311) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-05 02:02:43 (173) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-05 02:02:43 (173) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-05 02:02:43 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-05 02:02:43 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_3FEuIO3gM/ea_profile.json * 2024-03-05 02:02:46 (2488) [INFO] Backed up EA4 profile to /tmp/_3FEuIO3gM/ea_profile.json * 2024-03-05 02:02:47 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-05 02:02:50 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-06 02:00:40 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-06 02:00:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-06 02:00:42 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-06 02:00:43 (1896) [INFO] Checking if your system is up to date: * 2024-03-06 02:00:43 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-06 02:00:43 (5196) [INFO] * 2024-03-06 02:00:44 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-06 02:00:44 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-06 02:00:44 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-06 02:00:44 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-06 02:00:44 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-06 02:00:44 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-06 02:00:44 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-06 02:00:44 (5226) [INFO] * 2024-03-06 02:00:44 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-06 02:00:44 (5196) [INFO] * 2024-03-06 02:05:15 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-06 02:05:15 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-06 02:05:16 (5226) [INFO] * 2024-03-06 02:05:16 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-06 02:08:50 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-06 02:08:50 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-06 02:08:50 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-06 02:08:50 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-06 02:08:50 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zFsO553GdE/ea_profile.json * 2024-03-06 02:08:53 (2579) [INFO] Backed up EA4 profile to /tmp/zFsO553GdE/ea_profile.json * 2024-03-06 02:08:54 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-06 02:08:57 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-07 01:56:42 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-07 01:56:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-07 01:56:45 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-07 01:56:46 (1896) [INFO] Checking if your system is up to date: * 2024-03-07 01:56:46 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-07 01:56:46 (5196) [INFO] * 2024-03-07 01:56:46 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-07 01:56:46 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-07 01:56:46 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-07 01:56:46 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-07 01:56:46 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-07 01:56:46 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-07 01:56:47 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-07 01:56:47 (5226) [INFO] * 2024-03-07 01:56:47 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-07 01:56:47 (5196) [INFO] * 2024-03-07 02:01:51 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-07 02:01:51 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-07 02:01:51 (5226) [INFO] * 2024-03-07 02:01:51 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-07 02:05:41 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-07 02:05:41 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-07 02:05:41 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-07 02:05:41 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-07 02:05:41 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6JhrWsD6XD/ea_profile.json * 2024-03-07 02:05:44 (2579) [INFO] Backed up EA4 profile to /tmp/6JhrWsD6XD/ea_profile.json * 2024-03-07 02:05:45 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-07 02:05:48 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-08 02:14:39 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-08 02:14:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-08 02:14:42 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-08 02:14:43 (1896) [INFO] Checking if your system is up to date: * 2024-03-08 02:14:43 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-08 02:14:43 (5196) [INFO] * 2024-03-08 02:14:43 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-08 02:14:43 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-08 02:14:43 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-08 02:14:43 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-08 02:14:43 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-08 02:14:43 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-08 02:14:44 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-08 02:14:44 (5226) [INFO] * 2024-03-08 02:14:44 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-08 02:14:44 (5196) [INFO] * 2024-03-08 02:20:02 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-08 02:20:02 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-08 02:20:03 (5226) [INFO] * 2024-03-08 02:20:03 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-08 02:23:59 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-08 02:23:59 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-08 02:23:59 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-08 02:23:59 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-08 02:23:59 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5N8VWqOpKM/ea_profile.json * 2024-03-08 02:24:02 (2579) [INFO] Backed up EA4 profile to /tmp/5N8VWqOpKM/ea_profile.json * 2024-03-08 02:24:03 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-08 02:24:06 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-09 02:04:47 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-09 02:04:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-09 02:04:50 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-09 02:04:51 (1896) [INFO] Checking if your system is up to date: * 2024-03-09 02:04:51 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-09 02:04:51 (5196) [INFO] * 2024-03-09 02:04:52 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-09 02:04:52 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-09 02:04:52 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-09 02:04:52 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-09 02:04:52 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-09 02:04:52 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-09 02:04:53 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-09 02:04:53 (5226) [INFO] * 2024-03-09 02:04:53 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-09 02:04:53 (5196) [INFO] * 2024-03-09 02:09:09 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-09 02:09:09 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-09 02:09:09 (5226) [INFO] * 2024-03-09 02:09:09 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-09 02:12:25 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-09 02:12:25 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-09 02:12:25 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-09 02:12:25 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-09 02:12:25 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2TkO7juJnp/ea_profile.json * 2024-03-09 02:12:27 (2579) [INFO] Backed up EA4 profile to /tmp/2TkO7juJnp/ea_profile.json * 2024-03-09 02:12:28 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-09 02:12:32 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-10 01:58:11 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-10 01:58:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-10 01:58:14 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-10 01:58:15 (1896) [INFO] Checking if your system is up to date: * 2024-03-10 01:58:15 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-10 01:58:15 (5196) [INFO] * 2024-03-10 01:58:15 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-10 01:58:15 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-10 01:58:15 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-10 01:58:15 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-10 01:58:15 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-10 01:58:15 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-10 01:58:16 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-10 01:58:16 (5226) [INFO] * 2024-03-10 01:58:16 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-10 01:58:16 (5196) [INFO] * 2024-03-10 03:02:37 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-10 03:02:37 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-10 03:02:37 (5226) [INFO] * 2024-03-10 03:02:37 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-10 03:06:15 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-10 03:06:15 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-10 03:06:15 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-10 03:06:15 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-10 03:06:15 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ObPvJPk5ZH/ea_profile.json * 2024-03-10 03:06:17 (2579) [INFO] Backed up EA4 profile to /tmp/ObPvJPk5ZH/ea_profile.json * 2024-03-10 03:06:18 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-10 03:06:21 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-11 02:01:14 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-11 02:01:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-11 02:01:17 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-11 02:01:17 (1896) [INFO] Checking if your system is up to date: * 2024-03-11 02:01:17 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-11 02:01:17 (5196) [INFO] * 2024-03-11 02:01:18 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-11 02:01:18 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-11 02:01:18 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-11 02:01:18 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-11 02:01:18 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-11 02:01:18 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-11 02:01:19 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-11 02:01:19 (5226) [INFO] * 2024-03-11 02:01:19 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-11 02:01:19 (5196) [INFO] * 2024-03-11 02:05:45 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-11 02:05:45 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-11 02:05:45 (5226) [INFO] * 2024-03-11 02:05:45 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-11 02:09:21 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-11 02:09:21 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-11 02:09:22 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-11 02:09:22 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-11 02:09:22 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/18p8UHu3Ip/ea_profile.json * 2024-03-11 02:09:24 (2579) [INFO] Backed up EA4 profile to /tmp/18p8UHu3Ip/ea_profile.json * 2024-03-11 02:09:25 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-11 02:09:28 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-12 02:02:48 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-12 02:02:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-12 02:02:50 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-12 02:02:51 (1896) [INFO] Checking if your system is up to date: * 2024-03-12 02:02:51 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-12 02:02:51 (5196) [INFO] * 2024-03-12 02:02:52 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-12 02:02:52 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-12 02:02:52 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-12 02:02:52 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-12 02:02:52 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-12 02:02:52 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-12 02:02:53 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-12 02:02:53 (5226) [INFO] * 2024-03-12 02:02:53 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-12 02:02:53 (5196) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] One of the configured repositories failed (Unknown), * 2024-03-12 02:03:48 (5209) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-03-12 02:03:48 (5209) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-03-12 02:03:48 (5209) [INFO] upstream. This is most often useful if you are using a newer * 2024-03-12 02:03:48 (5209) [INFO] distribution release than is supported by the repository (and the * 2024-03-12 02:03:48 (5209) [INFO] packages for the previous distribution release still work). * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] 3. Run the command with the repository temporarily disabled * 2024-03-12 02:03:48 (5209) [INFO] yum --disablerepo= ... * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-03-12 02:03:48 (5209) [INFO] will then just ignore the repository until you permanently enable it * 2024-03-12 02:03:48 (5209) [INFO] again or use --enablerepo for temporary usage: * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] yum-config-manager --disable * 2024-03-12 02:03:48 (5209) [INFO] or * 2024-03-12 02:03:48 (5209) [INFO] subscription-manager repos --disable= * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-03-12 02:03:48 (5209) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-03-12 02:03:48 (5209) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-03-12 02:03:48 (5209) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-03-12 02:03:48 (5209) [INFO] compromise: * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5209) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-03-12 02:03:48 (5209) [INFO] * 2024-03-12 02:03:48 (5226) [INFO] * 2024-03-12 02:03:48 (1940) [INFO] Checking /scripts/sysup * 2024-03-12 02:03:48 (5195) [INFO] Running: /scripts/sysup * 2024-03-12 02:03:48 (5196) [INFO] * 2024-03-12 02:03:49 (5209) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-03-12 02:03:51 (5209) [INFO] All Needed Packages are already installed. * 2024-03-12 02:03:51 (5226) [INFO] * 2024-03-12 02:04:46 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-12 02:04:46 (1701) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-03-12 02:04:47 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-12 02:04:47 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-12 02:04:47 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-12 02:04:47 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-12 02:04:47 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/laNaOYct6m/ea_profile.json * 2024-03-13 02:02:44 (1986) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-13 02:02:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-13 02:02:47 (190) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-13 02:02:48 (1896) [INFO] Checking if your system is up to date: * 2024-03-13 02:02:48 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-13 02:02:48 (5196) [INFO] * 2024-03-13 02:02:48 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-13 02:02:49 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-03-13 02:02:49 (5209) [INFO] : epel extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-13 02:02:49 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-13 02:02:49 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-13 02:02:49 (5209) [INFO] : updates wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-03-13 02:02:49 (5209) [INFO] Other repos take up 848 k of disk space (use --verbose for details) * 2024-03-13 02:02:49 (5226) [INFO] * 2024-03-13 02:02:49 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-13 02:02:49 (5196) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] One of the configured repositories failed (Unknown), * 2024-03-13 02:03:45 (5209) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-03-13 02:03:45 (5209) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-03-13 02:03:45 (5209) [INFO] upstream. This is most often useful if you are using a newer * 2024-03-13 02:03:45 (5209) [INFO] distribution release than is supported by the repository (and the * 2024-03-13 02:03:45 (5209) [INFO] packages for the previous distribution release still work). * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] 3. Run the command with the repository temporarily disabled * 2024-03-13 02:03:45 (5209) [INFO] yum --disablerepo= ... * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-03-13 02:03:45 (5209) [INFO] will then just ignore the repository until you permanently enable it * 2024-03-13 02:03:45 (5209) [INFO] again or use --enablerepo for temporary usage: * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] yum-config-manager --disable * 2024-03-13 02:03:45 (5209) [INFO] or * 2024-03-13 02:03:45 (5209) [INFO] subscription-manager repos --disable= * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-03-13 02:03:45 (5209) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-03-13 02:03:45 (5209) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-03-13 02:03:45 (5209) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-03-13 02:03:45 (5209) [INFO] compromise: * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-03-13 02:03:45 (5209) [INFO] * 2024-03-13 02:03:45 (5226) [INFO] * 2024-03-13 02:03:45 (1940) [INFO] Checking /scripts/sysup * 2024-03-13 02:03:45 (5195) [INFO] Running: /scripts/sysup * 2024-03-13 02:03:45 (5196) [INFO] * 2024-03-13 02:03:45 (5209) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2024-03-13 02:03:48 (5209) [INFO] All Needed Packages are already installed. * 2024-03-13 02:03:48 (5226) [INFO] * 2024-03-13 02:12:31 (1700) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-13 02:12:31 (1701) [ERROR] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. http://mirror.keystealth.org/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/wp-toolkit/repodata/0b55209265624ad2c3a0d4a86611623a767eb91e5054e38a9a28c6a01e555558-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux.cc.lehigh.edu/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.grid.uchicago.edu/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.vcu.edu/pub/gnu_linux/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.wdc2.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://la.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.sonic.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://abqix.mm.fcix.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.metrocast.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.vcea.wsu.edu/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-03-13 02:12:32 (1328) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-13 02:12:32 (190) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-13 02:12:32 (190) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-13 02:12:32 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-13 02:12:32 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ajvdlZTwBn/ea_profile.json * 2024-03-13 02:12:35 (2579) [INFO] Backed up EA4 profile to /tmp/ajvdlZTwBn/ea_profile.json * 2024-03-13 02:12:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-13 02:12:38 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-14 02:08:07 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-14 02:08:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-14 02:08:10 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-14 02:11:52 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-14 02:11:52 (1717) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30315 milliseconds') https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/78781cae5ecc8d955caf557d81d60b67b100d47b3ffb250cfef1036ab51a4786-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/. * 2024-03-14 02:11:53 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-14 02:11:53 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-14 02:11:53 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-14 02:11:53 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-14 02:11:53 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EjFpJyLrvC/ea_profile.json * 2024-03-14 02:11:55 (2541) [INFO] Backed up EA4 profile to /tmp/EjFpJyLrvC/ea_profile.json * 2024-03-14 02:11:56 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-14 02:11:59 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-15 02:02:00 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-15 02:02:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-15 02:02:03 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-15 02:05:20 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-15 02:05:20 (1717) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2024-03-15 02:05:21 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-15 02:05:21 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-15 02:05:21 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-15 02:05:21 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-15 02:05:21 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MYGa_dTMHN/ea_profile.json * 2024-03-15 02:05:24 (2541) [INFO] Backed up EA4 profile to /tmp/MYGa_dTMHN/ea_profile.json * 2024-03-15 02:05:24 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-15 02:05:28 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-16 02:04:21 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-16 02:04:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-16 02:04:24 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-16 02:07:24 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-16 02:07:24 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-16 02:07:24 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-16 02:07:24 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-16 02:07:24 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TwipMFaCHP/ea_profile.json * 2024-03-16 02:07:27 (2541) [INFO] Backed up EA4 profile to /tmp/TwipMFaCHP/ea_profile.json * 2024-03-16 02:07:27 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-16 02:07:31 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-17 02:14:04 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-17 02:14:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-17 02:14:07 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-17 02:17:05 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-17 02:17:05 (1717) [ERROR] https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/1f7f05402060bfecbfaa9917ba81b35318fac37bf97cec64d8d8330ebca3609d-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/. * 2024-03-17 02:17:06 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-17 02:17:06 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-17 02:17:06 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-17 02:17:06 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-17 02:17:06 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wwl3gF9Ycx/ea_profile.json * 2024-03-17 02:17:09 (2541) [INFO] Backed up EA4 profile to /tmp/wwl3gF9Ycx/ea_profile.json * 2024-03-17 02:17:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-17 02:17:13 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-18 02:02:32 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-18 02:02:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-18 02:02:35 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-18 02:06:46 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-18 02:06:46 (1717) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30332 milliseconds') https://mirrors.xmission.com/fedora-epel/7/x86_64/repodata/9cef350d2b0cdb00c294ed85cf32299abc569413ca028e0f24bd0e94d459dc39-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/. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/9cef350d2b0cdb00c294ed85cf32299abc569413ca028e0f24bd0e94d459dc39-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://mirror.servaxnet.com/epel/7/x86_64/repodata/9cef350d2b0cdb00c294ed85cf32299abc569413ca028e0f24bd0e94d459dc39-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2024-03-18 02:06:47 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-18 02:06:47 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-18 02:06:47 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-18 02:06:47 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-18 02:06:47 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/k_5DwfvuW7/ea_profile.json * 2024-03-18 02:06:50 (2541) [INFO] Backed up EA4 profile to /tmp/k_5DwfvuW7/ea_profile.json * 2024-03-18 02:06: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-18 02:06:54 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-19 01:55:39 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-19 01:55:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-19 01:55:42 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-19 02:00:26 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-19 02:00:26 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-19 02:00:26 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-19 02:00:26 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-19 02:00:26 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qgT30CTxII/ea_profile.json * 2024-03-19 02:00:29 (2541) [INFO] Backed up EA4 profile to /tmp/qgT30CTxII/ea_profile.json * 2024-03-19 02:00:30 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-19 02:00:33 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-20 02:08:12 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-20 02:08:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-20 02:08:14 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-20 02:16:38 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-20 02:16:38 (1717) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to download.imunify360.com:443; Operation now in progress" Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/367a0cdcec3c855c52b5d6f843d3e32aefcd4787a70839e7b6bb210aeb193cc4-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://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/a971ab8e8efc251a4e86a5fed4f808e899d1860531b9c5a44e3ff87918683816-filelists.sqlite.bz2: [Errno 14] curl#56 - "TCP connection reset by peer" Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/313cf71ca54993a1a792299f97e8239b3b1443cf04f35d5613823d54807988de-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/313cf71ca54993a1a792299f97e8239b3b1443cf04f35d5613823d54807988de-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/313cf71ca54993a1a792299f97e8239b3b1443cf04f35d5613823d54807988de-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/313cf71ca54993a1a792299f97e8239b3b1443cf04f35d5613823d54807988de-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/a971ab8e8efc251a4e86a5fed4f808e899d1860531b9c5a44e3ff87918683816-filelists.sqlite.bz2: [Errno 14] curl#56 - "TCP connection reset by peer" Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/a971ab8e8efc251a4e86a5fed4f808e899d1860531b9c5a44e3ff87918683816-filelists.sqlite.bz2: [Errno 14] curl#56 - "TCP connection reset by peer" Trying other mirror. One of the configured repositories failed (EL-7 - Imunify360), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360 or subscription-manager repos --disable=imunify360 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360.skip_if_unavailable=true failure: repodata/a971ab8e8efc251a4e86a5fed4f808e899d1860531b9c5a44e3ff87918683816-filelists.sqlite.bz2 from imunify360: [Errno 256] No more mirrors to try. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/a971ab8e8efc251a4e86a5fed4f808e899d1860531b9c5a44e3ff87918683816-filelists.sqlite.bz2: [Errno 14] curl#56 - "TCP connection reset by peer" * 2024-03-20 02:16:39 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-20 02:16:39 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-20 02:16:39 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-20 02:16:39 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-20 02:16:39 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aHAIXSnH86/ea_profile.json * 2024-03-20 02:19:32 (2541) [INFO] Backed up EA4 profile to /tmp/aHAIXSnH86/ea_profile.json * 2024-03-20 02:19:33 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-20 02:19:36 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-21 02:04:54 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-21 02:04:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-21 02:04:57 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-21 02:07:31 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-21 02:07:31 (1717) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30538 milliseconds') * 2024-03-21 02:07:32 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-21 02:07:32 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-21 02:07:32 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-21 02:07:32 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-21 02:07:32 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uDjD0g3JYn/ea_profile.json * 2024-03-21 02:07:34 (2541) [INFO] Backed up EA4 profile to /tmp/uDjD0g3JYn/ea_profile.json * 2024-03-21 02:07:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-21 02:07:38 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-22 02:02:22 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-22 02:02:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-22 02:02:25 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-22 02:04:41 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-22 02:04:41 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-22 02:04:41 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-22 02:04:41 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-22 02:04:41 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eXYS27AGzi/ea_profile.json * 2024-03-22 02:04:44 (2541) [INFO] Backed up EA4 profile to /tmp/eXYS27AGzi/ea_profile.json * 2024-03-22 02:04: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-22 02:04:48 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-23 02:04:43 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-23 02:04:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-23 02:04:46 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-23 02:08:03 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-23 02:08:03 (1717) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30541 milliseconds') * 2024-03-23 02:08:04 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-23 02:08:04 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-23 02:08:04 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-23 02:08:04 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-23 02:08:04 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PspHvBIT8H/ea_profile.json * 2024-03-23 02:08:06 (2541) [INFO] Backed up EA4 profile to /tmp/PspHvBIT8H/ea_profile.json * 2024-03-23 02:08:07 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-23 02:08:10 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-24 02:56:10 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-24 02:56:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-24 02:56:13 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-24 03:10:45 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-24 03:10:45 (1717) [ERROR] http://linux-mirrors.fnal.gov/linux/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. * 2024-03-24 03:10:46 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-24 03:10:46 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-24 03:10:46 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-24 03:10:46 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-24 03:10:46 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wBIcAnNYrP/ea_profile.json * 2024-03-24 03:10:48 (2541) [INFO] Backed up EA4 profile to /tmp/wBIcAnNYrP/ea_profile.json * 2024-03-24 03:10:49 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-24 03:10:52 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-25 02:02:51 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-25 02:02:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-25 02:02:53 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-25 02:05:40 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-25 02:05:40 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-25 02:05:40 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-25 02:05:40 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-25 02:05:40 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MzW20MV_kR/ea_profile.json * 2024-03-25 02:05:42 (2541) [INFO] Backed up EA4 profile to /tmp/MzW20MV_kR/ea_profile.json * 2024-03-25 02:05: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-25 02:05:47 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-26 01:56:36 (1947) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-26 01:56:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-26 01:56:38 (191) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-26 01:59:59 (1345) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-26 01:59:59 (191) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-26 01:59:59 (191) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-26 01:59:59 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-26 01:59:59 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NNcYiwfkDp/ea_profile.json * 2024-03-26 02:00:01 (2541) [INFO] Backed up EA4 profile to /tmp/NNcYiwfkDp/ea_profile.json * 2024-03-26 02:00:03 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-26 02:00:06 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-27 02:39:44 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-27 02:39:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-27 02:39:47 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-27 02:42:46 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-27 02:42:46 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-27 02:42:46 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-27 02:42:46 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-27 02:42:46 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1GwUpSMrS6/ea_profile.json * 2024-03-27 02:42:48 (2641) [INFO] Backed up EA4 profile to /tmp/1GwUpSMrS6/ea_profile.json * 2024-03-27 02:42:49 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-27 02:43:24 (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 02:43:24 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-28 02:01:35 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-28 02:01:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-28 02:01:37 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-28 02:05:36 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-28 02:05:36 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-28 02:05:36 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-28 02:05:36 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-28 02:05:37 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B6cDPvTEuq/ea_profile.json * 2024-03-28 02:05:39 (2641) [INFO] Backed up EA4 profile to /tmp/B6cDPvTEuq/ea_profile.json * 2024-03-28 02:05:40 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-28 02:06:13 (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 02:06:13 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-29 02:01:24 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-29 02:01:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-29 02:01:27 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-29 02:01:58 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-29 02:01:58 (1755) [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 * 2024-03-29 02:01:59 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-29 02:01:59 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-29 02:01:59 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-29 02:01:59 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-29 02:01:59 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/h463sSQXDT/ea_profile.json * 2024-03-29 02:03:26 (344) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/h463sSQXDT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2620. * 2024-03-29 02:03:26 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-30 01:59:52 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-30 01:59:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-30 01:59:55 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-30 02:03:41 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-30 02:03:41 (1755) [ERROR] https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/cd00e9ebc502010b989fcfc3be3fd1baee70fa79eb7c05639c58b3a8155aa37c-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/. * 2024-03-30 02:03:42 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-30 02:03:42 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-30 02:03:42 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-30 02:03:42 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-30 02:03:42 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/idhYPR0MMK/ea_profile.json * 2024-03-30 02:03:44 (2641) [INFO] Backed up EA4 profile to /tmp/idhYPR0MMK/ea_profile.json * 2024-03-30 02:03: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-30 02:04:20 (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 02:04:20 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-31 02:02:09 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-03-31 02:02:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-03-31 02:02:11 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-31 02:04:58 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-31 02:04:58 (1755) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30538 milliseconds') * 2024-03-31 02:04:59 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-03-31 02:04:59 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-03-31 02:04:59 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-03-31 02:04:59 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-31 02:04:59 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IH0wxWF5U5/ea_profile.json * 2024-03-31 02:05:01 (2641) [INFO] Backed up EA4 profile to /tmp/IH0wxWF5U5/ea_profile.json * 2024-03-31 02:05:03 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-03-31 02:05:37 (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 02:05:37 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-01 02:02:59 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-01 02:02:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-01 02:03:02 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-01 02:05:46 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-01 02:05:46 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-01 02:05:46 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-01 02:05:46 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-01 02:05:46 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JiKN9tEifh/ea_profile.json * 2024-04-01 02:05:48 (2641) [INFO] Backed up EA4 profile to /tmp/JiKN9tEifh/ea_profile.json * 2024-04-01 02:05:49 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-01 02:06:23 (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 02:06:23 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-02 02:04:08 (1985) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-02 02:04:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-02 02:04:11 (194) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-02 02:07:24 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-04-02 02:07:24 (1755) [ERROR] https://mirror.arizona.edu/fedora-epel/7/x86_64/repodata/2e940657548e67b01dbcf2375c6564f5321e7e9b07246cbfa0fc891398646491-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/. * 2024-04-02 02:07:25 (1383) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-02 02:07:25 (194) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-02 02:07:25 (194) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-02 02:07:25 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-02 02:07:25 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IZmOxgSWEq/ea_profile.json * 2024-04-02 02:07:28 (2641) [INFO] Backed up EA4 profile to /tmp/IZmOxgSWEq/ea_profile.json * 2024-04-02 02:07:29 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-02 02:08:03 (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 02:08:03 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-03 02:03:29 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-03 02:03:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-03 02:03:32 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-03 02:06:18 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-03 02:06:18 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-03 02:06:18 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-03 02:06:18 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-03 02:06:18 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YRCMIvPV7m/ea_profile.json * 2024-04-03 02:06:20 (2647) [INFO] Backed up EA4 profile to /tmp/YRCMIvPV7m/ea_profile.json * 2024-04-03 02:06:21 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-03 02:06:56 (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 02:06:56 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-04 02:06:05 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-04 02:06:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-04 02:06:07 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-04 02:09:08 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-04 02:09:08 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-04 02:09:08 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-04 02:09:08 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-04 02:09:08 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x5VrNYVwTF/ea_profile.json * 2024-04-04 02:09:11 (2647) [INFO] Backed up EA4 profile to /tmp/x5VrNYVwTF/ea_profile.json * 2024-04-04 02:09:12 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-04 02:09:46 (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 02:09:46 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-05 02:03:40 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-05 02:03:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-05 02:03:42 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-05 02:06:29 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-05 02:06:29 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-05 02:06:29 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-05 02:06:29 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-05 02:06:29 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ru9KQHPpCS/ea_profile.json * 2024-04-05 02:06:32 (2647) [INFO] Backed up EA4 profile to /tmp/ru9KQHPpCS/ea_profile.json * 2024-04-05 02:06: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-05 02:07:08 (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 02:07:08 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-06 02:04:47 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-06 02:04:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-06 02:04:50 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-06 02:07:23 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-06 02:07:23 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-06 02:07:23 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-06 02:07:23 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-06 02:07:23 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/z6jsyx_b3m/ea_profile.json * 2024-04-06 02:07:26 (2647) [INFO] Backed up EA4 profile to /tmp/z6jsyx_b3m/ea_profile.json * 2024-04-06 02:07:27 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-06 02:08:02 (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 02:08:02 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-07 02:02:29 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-07 02:02:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-07 02:02:32 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-07 02:05:32 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-04-07 02:05:32 (1760) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30604 milliseconds') * 2024-04-07 02:05:33 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-07 02:05:33 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-07 02:05:33 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-07 02:05:33 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-07 02:05:33 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/icC65kqv8o/ea_profile.json * 2024-04-07 02:05:34 (2647) [INFO] Backed up EA4 profile to /tmp/icC65kqv8o/ea_profile.json * 2024-04-07 02:05:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-07 02:06:09 (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 02:06:09 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-08 02:02:37 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-08 02:02:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-08 02:02:39 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-08 02:05:26 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-08 02:05:26 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-08 02:05:26 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-08 02:05:26 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-08 02:05:26 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/H42G7EVjEw/ea_profile.json * 2024-04-08 02:05:29 (2647) [INFO] Backed up EA4 profile to /tmp/H42G7EVjEw/ea_profile.json * 2024-04-08 02:05:30 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-08 02:06:03 (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 02:06:03 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-09 02:20:38 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-09 02:20:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-09 02:20:41 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-09 02:23:31 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-09 02:23:31 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-09 02:23:31 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-09 02:23:31 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-09 02:23:31 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wzuZoMDKEf/ea_profile.json * 2024-04-09 02:23:33 (2647) [INFO] Backed up EA4 profile to /tmp/wzuZoMDKEf/ea_profile.json * 2024-04-09 02:23: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-09 02:24:09 (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 02:24:09 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-10 02:03:01 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-10 02:03:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-10 02:03:04 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-10 02:05:55 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-10 02:05:55 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-10 02:05:55 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-10 02:05:55 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-10 02:05:55 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ua3sBCd9rR/ea_profile.json * 2024-04-10 02:05:58 (2647) [INFO] Backed up EA4 profile to /tmp/ua3sBCd9rR/ea_profile.json * 2024-04-10 02:05:59 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-10 02:06:34 (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 02:06:34 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-11 02:03:03 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-11 02:03:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-11 02:03:07 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-11 02:05:53 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-11 02:05:53 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-11 02:05:53 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-11 02:05:53 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-11 02:05:53 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4DTmauV4xb/ea_profile.json * 2024-04-11 02:05:56 (2647) [INFO] Backed up EA4 profile to /tmp/4DTmauV4xb/ea_profile.json * 2024-04-11 02:05:57 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-11 02:06: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-11 02:06:33 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-12 02:04:07 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-12 02:04:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-12 02:04:10 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-12 02:07:12 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-12 02:07:12 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-12 02:07:12 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-12 02:07:12 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-12 02:07:12 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2UFCl1zspO/ea_profile.json * 2024-04-12 02:07:15 (2647) [INFO] Backed up EA4 profile to /tmp/2UFCl1zspO/ea_profile.json * 2024-04-12 02:07:16 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-12 02:07: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-12 02:07:51 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-13 01:06:24 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-13 01:06:27 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-13 01:09:29 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-13 01:09:29 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-13 01:09:29 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-13 01:09:29 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-13 01:09:29 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qjIrgF9tU0/ea_profile.json * 2024-04-13 01:09:32 (2647) [INFO] Backed up EA4 profile to /tmp/qjIrgF9tU0/ea_profile.json * 2024-04-13 01:09: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-13 01:10:08 (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 01:10:08 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-14 02:04:13 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-14 02:04:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-14 02:04:16 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-14 02:06:59 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-04-14 02:06:59 (1760) [ERROR] http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/329ff173d7b1f48f1b3bb2f1577da47aec6827c955662b745aa1dbb401e3cfc6-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-04-14 02:07:00 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-14 02:07:00 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-14 02:07:00 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-14 02:07:00 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-14 02:07:00 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4dkCZS5Ucj/ea_profile.json * 2024-04-14 02:07:03 (2647) [INFO] Backed up EA4 profile to /tmp/4dkCZS5Ucj/ea_profile.json * 2024-04-14 02:07:03 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-14 02:07: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-14 02:07:37 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-15 02:03:59 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-15 02:04:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-15 02:04:02 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-15 02:06:58 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-15 02:06:58 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-15 02:06:58 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-15 02:06:58 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-15 02:06:58 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1p9KqSH_1U/ea_profile.json * 2024-04-15 02:07:00 (2647) [INFO] Backed up EA4 profile to /tmp/1p9KqSH_1U/ea_profile.json * 2024-04-15 02:07:01 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-15 02:07: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-15 02:07:35 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-16 01:57:52 (6907) [INFO] Self-update of script version 33 requested. * 2024-04-16 02:01:52 (6929) [INFO] Script is up to date. * 2024-04-16 02:05:55 (1990) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-16 02:05:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-16 02:05:58 (196) [WARN] *** Elevation Blocker detected: *** You are using MariaDB server 10.0, this version is not available for AlmaLinux 8. You first need to update MariaDB server to 10.5 or later. You can update to version 10.5 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.5 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-16 02:08:42 (1388) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-16 02:08:42 (196) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-16 02:08:42 (196) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-16 02:08:42 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-16 02:08:42 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ebgb974DXq/ea_profile.json * 2024-04-16 02:08:45 (2647) [INFO] Backed up EA4 profile to /tmp/ebgb974DXq/ea_profile.json * 2024-04-16 02:08: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-16 02:09:19 (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 02:09:19 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-17 01:52:01 (6907) [INFO] Self-update of script version 33 requested. * 2024-04-17 01:56:02 (6912) [INFO] Newer version of script found. Downloading. * 2024-04-17 02:00:05 (6921) [INFO] Script update to version 34 successful. * 2024-04-17 02:04:07 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-17 02:04:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-17 02:04:10 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-17 02:04:10 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:06 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-17 02:07:06 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-17 02:07:06 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-17 02:07:06 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-17 02:07:06 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9Ucz0i7DoU/ea_profile.json * 2024-04-17 02:07:09 (2664) [INFO] Backed up EA4 profile to /tmp/9Ucz0i7DoU/ea_profile.json * 2024-04-17 02:07:09 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-17 02:07: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-17 02:07:44 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-18 01:58:45 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-18 02:02:45 (7128) [INFO] Script is up to date. * 2024-04-18 02:06:48 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-18 02:06:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-18 02:06:51 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-18 02:06:51 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:25 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-18 02:09:25 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-18 02:09:25 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-18 02:09:25 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-18 02:09:25 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/reUsfsoU5E/ea_profile.json * 2024-04-18 02:09:27 (2664) [INFO] Backed up EA4 profile to /tmp/reUsfsoU5E/ea_profile.json * 2024-04-18 02:09:28 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-18 02:10:03 (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 02:10:03 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-19 02:03:24 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-19 02:07:24 (7128) [INFO] Script is up to date. * 2024-04-19 02:11:27 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-19 02:11:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-19 02:11:31 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-19 02:11:31 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:15:12 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-19 02:15:12 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-19 02:15:12 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-19 02:15:12 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-19 02:15:12 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jX2_9bvSTo/ea_profile.json * 2024-04-19 02:15:15 (2664) [INFO] Backed up EA4 profile to /tmp/jX2_9bvSTo/ea_profile.json * 2024-04-19 02:15:16 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-19 02:15:51 (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 02:15:51 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-20 02:00:44 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-20 02:04:45 (7128) [INFO] Script is up to date. * 2024-04-20 02:08:48 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-20 02:08:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-20 02:08:51 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-20 02:08:51 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:11:53 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-20 02:11:53 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-20 02:11:53 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-20 02:11:53 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-20 02:11:53 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JI__Ox9pmt/ea_profile.json * 2024-04-20 02:11:56 (2664) [INFO] Backed up EA4 profile to /tmp/JI__Ox9pmt/ea_profile.json * 2024-04-20 02:11:57 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-20 02:12:31 (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 02:12:31 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-21 01:53:54 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-21 01:57:55 (7128) [INFO] Script is up to date. * 2024-04-21 02:01:58 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-21 02:01:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-21 02:02:01 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-21 02:02:01 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:05 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-21 02:05:05 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-21 02:05:05 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-21 02:05:05 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-21 02:05:05 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2lORSvQz0L/ea_profile.json * 2024-04-21 02:05:07 (2664) [INFO] Backed up EA4 profile to /tmp/2lORSvQz0L/ea_profile.json * 2024-04-21 02:05:08 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-21 02:05: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-21 02:05:42 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-22 01:49:31 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-22 01:53:31 (7128) [INFO] Script is up to date. * 2024-04-22 01:57:34 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-22 01:57:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-22 01:57:38 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-22 01:57:38 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:00:11 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-22 02:00:11 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-22 02:00:11 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-22 02:00:11 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-22 02:00:11 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CoDu_eA6kI/ea_profile.json * 2024-04-22 02:00:13 (2664) [INFO] Backed up EA4 profile to /tmp/CoDu_eA6kI/ea_profile.json * 2024-04-22 02:00:14 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-22 02:00:48 (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 02:00:48 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-23 02:23:18 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-23 02:27:19 (7128) [INFO] Script is up to date. * 2024-04-23 02:31:22 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-23 02:31:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-23 02:31:25 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-23 02:31:25 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:33:55 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-23 02:33:55 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-23 02:33:55 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-23 02:33:55 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-23 02:33:55 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B5PWjxkiDJ/ea_profile.json * 2024-04-23 02:33:58 (2664) [INFO] Backed up EA4 profile to /tmp/B5PWjxkiDJ/ea_profile.json * 2024-04-23 02:33:58 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-23 02:34:34 (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 02:34:34 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-24 01:56:37 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-24 02:00:37 (7128) [INFO] Script is up to date. * 2024-04-24 02:04:40 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-24 02:04:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-24 02:04:43 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-24 02:04:43 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:29 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-24 02:07:29 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-24 02:07:29 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-24 02:07:29 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-24 02:07:29 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nAbD9daQ1c/ea_profile.json * 2024-04-24 02:07:32 (2664) [INFO] Backed up EA4 profile to /tmp/nAbD9daQ1c/ea_profile.json * 2024-04-24 02:07:33 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-24 02:08:08 (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 02:08:08 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-25 01:49:26 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-25 01:53:27 (7128) [INFO] Script is up to date. * 2024-04-25 01:57:30 (2007) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-25 01:57:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-25 01:57:32 (712) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-25 01:57:32 (719) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:00:00 (1405) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-25 02:00:00 (192) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-25 02:00:00 (192) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-25 02:00:00 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-25 02:00:00 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L7UeXVfY6z/ea_profile.json * 2024-04-25 02:00:04 (2664) [INFO] Backed up EA4 profile to /tmp/L7UeXVfY6z/ea_profile.json * 2024-04-25 02:00:05 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-25 02:00:39 (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-25 02:00:39 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-26 01:57:05 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-26 02:01:06 (7111) [INFO] Newer version of script found. Downloading. * 2024-04-26 02:05:08 (7120) [INFO] Script update to version 35 successful. * 2024-04-26 02:09:11 (2016) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-26 02:09:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-26 02:09:14 (715) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-26 02:09:14 (722) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:12:15 (1414) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-26 02:12:15 (198) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-26 02:12:15 (198) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-26 02:12:15 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-26 02:12:15 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y9ZWZ7m55F/ea_profile.json * 2024-04-26 02:12:18 (2782) [INFO] Backed up EA4 profile to /tmp/Y9ZWZ7m55F/ea_profile.json * 2024-04-26 02:12:19 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-26 02:12:53 (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 02:12:53 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-27 01:54:26 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-27 01:58:26 (7138) [INFO] Script is up to date. * 2024-04-27 02:02:29 (2016) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-27 02:02:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-27 02:02:33 (715) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-27 02:02:33 (722) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:34 (1414) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-27 02:05:34 (198) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-27 02:05:34 (198) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-27 02:05:34 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-27 02:05:34 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7qIpVoAfMZ/ea_profile.json * 2024-04-27 02:05:37 (2782) [INFO] Backed up EA4 profile to /tmp/7qIpVoAfMZ/ea_profile.json * 2024-04-27 02:05: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-27 02:06:12 (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 02:06:12 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-28 01:53:23 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-28 01:57:24 (7138) [INFO] Script is up to date. * 2024-04-28 02:01:27 (2016) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-28 02:01:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-28 02:01:30 (715) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-28 02:01:30 (722) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:31 (1414) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-28 02:04:32 (198) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-28 02:04:32 (198) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-28 02:04:32 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-28 02:04:32 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4oyLIhLEGN/ea_profile.json * 2024-04-28 02:04:34 (2782) [INFO] Backed up EA4 profile to /tmp/4oyLIhLEGN/ea_profile.json * 2024-04-28 02:04:35 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-28 02:05:10 (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 02:05:10 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-29 01:50:56 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-29 01:54:56 (7138) [INFO] Script is up to date. * 2024-04-29 01:59:00 (2016) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-29 01:59:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-29 01:59:03 (715) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-29 01:59:03 (722) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:47 (1414) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-29 02:01:47 (198) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-29 02:01:47 (198) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-29 02:01:47 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-29 02:01:47 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6LXOkar0Qv/ea_profile.json * 2024-04-29 02:01:50 (2782) [INFO] Backed up EA4 profile to /tmp/6LXOkar0Qv/ea_profile.json * 2024-04-29 02:01:50 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-29 02:02:25 (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 02:02:25 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-30 01:44:47 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-30 01:48:48 (7138) [INFO] Script is up to date. * 2024-04-30 01:52:51 (2016) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-04-30 01:52:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-04-30 01:52:54 (715) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-04-30 01:52:54 (722) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-30 01:56:46 (1414) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-04-30 01:56:46 (198) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-04-30 01:56:46 (198) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-04-30 01:56:46 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-30 01:56:46 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uGfDdDED98/ea_profile.json * 2024-04-30 01:56:49 (2782) [INFO] Backed up EA4 profile to /tmp/uGfDdDED98/ea_profile.json * 2024-04-30 01:56:50 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-04-30 01:57:24 (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-30 01:57:24 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-01 01:50:49 (7116) [INFO] Self-update of script version 35 requested. * 2024-05-01 01:54:50 (7121) [INFO] Newer version of script found. Downloading. * 2024-05-01 01:58:51 (7130) [INFO] Script update to version 36 successful. * 2024-05-01 02:02:53 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-01 02:02:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-01 02:02:56 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-01 02:02:56 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:06:36 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-01 02:06:36 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-01 02:06:36 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-01 02:06:36 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-01 02:06:36 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S5E8WhKJN7/ea_profile.json * 2024-05-01 02:06:39 (3173) [INFO] Backed up EA4 profile to /tmp/S5E8WhKJN7/ea_profile.json * 2024-05-01 02:06:40 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-01 02:07:15 (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 02:07:15 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-02 01:51:33 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-02 01:55:34 (7530) [INFO] Script is up to date. * 2024-05-02 01:59:37 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-02 01:59:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-02 01:59:39 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-02 01:59:39 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:02:40 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-02 02:02:40 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-02 02:02:40 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-02 02:02:40 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-02 02:02:40 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LsNIrHjMgk/ea_profile.json * 2024-05-02 02:02:43 (3173) [INFO] Backed up EA4 profile to /tmp/LsNIrHjMgk/ea_profile.json * 2024-05-02 02:02:44 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-02 02:03:18 (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 02:03:18 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-03 01:53:07 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-03 01:57:07 (7530) [INFO] Script is up to date. * 2024-05-03 02:01:11 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-03 02:01:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-03 02:01:13 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-03 02:01:13 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:14 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-03 02:04:14 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-03 02:04:15 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-03 02:04:15 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-03 02:04:15 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7bVoa0B1Fc/ea_profile.json * 2024-05-03 02:04:17 (3173) [INFO] Backed up EA4 profile to /tmp/7bVoa0B1Fc/ea_profile.json * 2024-05-03 02:04:18 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-03 02:04:53 (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 02:04:53 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-04 01:46:11 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-04 01:50:11 (7530) [INFO] Script is up to date. * 2024-05-04 01:54:14 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-04 01:54:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-04 01:54:16 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-04 01:54:16 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-04 01:57:49 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-04 01:57:49 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-04 01:57:49 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-04 01:57:49 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-04 01:57:49 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hkS5tCKKE5/ea_profile.json * 2024-05-04 01:57:52 (3173) [INFO] Backed up EA4 profile to /tmp/hkS5tCKKE5/ea_profile.json * 2024-05-04 01:57:53 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-04 01:58:28 (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 01:58:28 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-05 01:53:40 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-05 01:57:41 (7530) [INFO] Script is up to date. * 2024-05-05 02:01:44 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-05 02:01:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-05 02:01:46 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-05 02:01:46 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:16 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-05 02:04:16 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-05 02:04:16 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-05 02:04:16 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-05 02:04:16 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0nBczZZzqr/ea_profile.json * 2024-05-05 02:04:18 (3173) [INFO] Backed up EA4 profile to /tmp/0nBczZZzqr/ea_profile.json * 2024-05-05 02:04:19 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-05 02:04:53 (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 02:04:53 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-06 01:44:51 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-06 01:48:52 (7530) [INFO] Script is up to date. * 2024-05-06 01:52:55 (2017) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-06 01:52:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-06 01:52:57 (716) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-06 01:52:57 (723) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:50 (1415) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-06 02:01:50 (199) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-06 02:01:50 (199) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-06 02:01:50 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-06 02:01:50 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/G8bhMLqtT1/ea_profile.json * 2024-05-06 02:01:53 (3173) [INFO] Backed up EA4 profile to /tmp/G8bhMLqtT1/ea_profile.json * 2024-05-06 02:01:54 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-06 02:02:29 (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-06 02:02:29 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-07 01:54:27 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-07 01:58:27 (7513) [INFO] Newer version of script found. Downloading. * 2024-05-07 02:02:29 (7522) [INFO] Script update to version 37 successful. * 2024-05-07 02:06:32 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-07 02:06:32 (6322) [INFO] * 2024-05-07 02:06:32 (6352) [INFO] * 2024-05-07 02:06:32 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-07 02:06:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-07 02:06:34 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-07 02:06:34 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:10:26 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-07 02:10:26 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-07 02:10:27 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-07 02:10:27 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-07 02:10:27 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/puYv65Qyi3/ea_profile.json * 2024-05-07 02:10:29 (3212) [INFO] Backed up EA4 profile to /tmp/puYv65Qyi3/ea_profile.json * 2024-05-07 02:10: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-07 02:11:05 (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 02:11:05 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-08 01:51:43 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-08 01:55:44 (7570) [INFO] Script is up to date. * 2024-05-08 01:59:47 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-08 01:59:47 (6322) [INFO] * 2024-05-08 01:59:47 (6352) [INFO] * 2024-05-08 01:59:47 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-08 01:59:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-08 01:59:49 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-08 01:59:49 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:55 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-08 02:03:55 (1826) [ERROR] http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/9f5dcb7a76f7c9e3430ffcab3cde3215d4050b01405bd25c8f7a31c612dbe8e3-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-05-08 02:03:56 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-08 02:03:56 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-08 02:03:56 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-08 02:03:56 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-08 02:03:56 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FWHmWC0hTW/ea_profile.json * 2024-05-08 02:03:59 (3212) [INFO] Backed up EA4 profile to /tmp/FWHmWC0hTW/ea_profile.json * 2024-05-08 02:04:00 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-08 02:04:34 (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 02:04:34 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-09 01:54:24 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-09 01:58:24 (7570) [INFO] Script is up to date. * 2024-05-09 02:02:27 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-09 02:02:27 (6322) [INFO] * 2024-05-09 02:02:27 (6352) [INFO] * 2024-05-09 02:02:27 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-09 02:02:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-09 02:02:30 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-09 02:02:30 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:06:29 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-09 02:06:29 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-09 02:06:29 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-09 02:06:29 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-09 02:06:29 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hjQsosMkVR/ea_profile.json * 2024-05-09 02:06:31 (3212) [INFO] Backed up EA4 profile to /tmp/hjQsosMkVR/ea_profile.json * 2024-05-09 02:06:32 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-09 02:07:05 (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 02:07:05 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-10 01:58:10 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-10 02:02:11 (7570) [INFO] Script is up to date. * 2024-05-10 02:06:14 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-10 02:06:14 (6322) [INFO] * 2024-05-10 02:06:14 (6352) [INFO] * 2024-05-10 02:06:14 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-10 02:06:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-10 02:06:16 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-10 02:06:16 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:10:20 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-10 02:10:20 (1826) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') * 2024-05-10 02:10:21 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-10 02:10:21 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-10 02:10:21 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-10 02:10:21 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-10 02:10:21 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nZPFCVhCn8/ea_profile.json * 2024-05-10 02:10:23 (3212) [INFO] Backed up EA4 profile to /tmp/nZPFCVhCn8/ea_profile.json * 2024-05-10 02:10:24 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-10 02:10:58 (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 02:10:58 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-11 02:01:04 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-11 02:05:04 (7570) [INFO] Script is up to date. * 2024-05-11 02:09:08 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-11 02:09:08 (6322) [INFO] * 2024-05-11 02:09:08 (6352) [INFO] * 2024-05-11 02:09:08 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-11 02:09:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-11 02:09:10 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-11 02:09:10 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:13:16 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-11 02:13:16 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-11 02:13:16 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-11 02:13:16 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-11 02:13:16 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bcgenELXVs/ea_profile.json * 2024-05-11 02:13:19 (3212) [INFO] Backed up EA4 profile to /tmp/bcgenELXVs/ea_profile.json * 2024-05-11 02:13:20 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-11 02:13:55 (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 02:13:55 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-12 01:54:59 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-12 01:58:59 (7570) [INFO] Script is up to date. * 2024-05-12 02:03:03 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-12 02:03:03 (6322) [INFO] * 2024-05-12 02:03:03 (6352) [INFO] * 2024-05-12 02:03:03 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-12 02:03:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-12 02:03:05 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-12 02:03:05 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:04 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-12 02:07:04 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-12 02:07:04 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-12 02:07:04 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-12 02:07:04 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/233G7UZ0L0/ea_profile.json * 2024-05-12 02:07:07 (3212) [INFO] Backed up EA4 profile to /tmp/233G7UZ0L0/ea_profile.json * 2024-05-12 02:07:07 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-12 02:07:41 (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 02:07:41 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-13 01:52:34 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-13 01:56:34 (7570) [INFO] Script is up to date. * 2024-05-13 02:00:37 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-13 02:00:37 (6322) [INFO] * 2024-05-13 02:00:37 (6352) [INFO] * 2024-05-13 02:00:37 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-13 02:00:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-13 02:00:39 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-13 02:00:39 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:26 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-13 02:04:26 (1826) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-05-13 02:04:27 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-13 02:04:27 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-13 02:04:27 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-13 02:04:27 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-13 02:04:27 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bYwQhWCcZP/ea_profile.json * 2024-05-13 02:04:30 (3212) [INFO] Backed up EA4 profile to /tmp/bYwQhWCcZP/ea_profile.json * 2024-05-13 02:04: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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-13 02:05:05 (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 02:05:05 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-14 01:52:13 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-14 01:56:13 (7570) [INFO] Script is up to date. * 2024-05-14 02:00:17 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-14 02:00:17 (6322) [INFO] * 2024-05-14 02:00:17 (6352) [INFO] * 2024-05-14 02:00:17 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-14 02:00:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-14 02:00:19 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-14 02:00:19 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:17 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-14 02:03:17 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-14 02:03:17 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-14 02:03:17 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-14 02:03:17 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3LDiHUOqwF/ea_profile.json * 2024-05-14 02:03:20 (3212) [INFO] Backed up EA4 profile to /tmp/3LDiHUOqwF/ea_profile.json * 2024-05-14 02:03:20 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-14 02:03:55 (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 02:03:55 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-15 01:44:38 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-15 01:48:38 (7570) [INFO] Script is up to date. * 2024-05-15 01:52:41 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-15 01:52:41 (6322) [INFO] * 2024-05-15 01:52:41 (6352) [INFO] * 2024-05-15 01:52:41 (2056) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-15 01:52:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-15 01:52:43 (719) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-15 01:52:43 (726) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-15 01:53:14 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-15 01:53:14 (1826) [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 * 2024-05-15 01:53:15 (1418) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-15 01:53:15 (200) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-15 01:53:15 (200) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-15 01:53:15 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-15 01:53:15 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YdQoFVAcIF/ea_profile.json * 2024-05-15 01:57:32 (3212) [INFO] Backed up EA4 profile to /tmp/YdQoFVAcIF/ea_profile.json * 2024-05-15 01:57:33 (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-php55 - ea-php55-libc-client - ea-php55-pear - ea-php55-php-bcmath - ea-php55-php-calendar - ea-php55-php-cli - ea-php55-php-common - ea-php55-php-curl - ea-php55-php-devel - ea-php55-php-exif - ea-php55-php-fileinfo - ea-php55-php-fpm - ea-php55-php-ftp - ea-php55-php-gd - ea-php55-php-gettext - ea-php55-php-iconv - ea-php55-php-imap - ea-php55-php-intl - ea-php55-php-litespeed - ea-php55-php-mbstring - ea-php55-php-mcrypt - ea-php55-php-mssql - ea-php55-php-mysqlnd - ea-php55-php-pdo - ea-php55-php-posix - ea-php55-php-snmp - ea-php55-php-soap - ea-php55-php-sockets - ea-php55-php-sourceguardian - ea-php55-php-xml - ea-php55-php-xmlrpc - ea-php55-php-zip - ea-php55-runtime - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php70 - ea-php70-libc-client - ea-php70-pear - ea-php70-php-bcmath - ea-php70-php-calendar - ea-php70-php-cli - ea-php70-php-common - ea-php70-php-curl - ea-php70-php-devel - ea-php70-php-fileinfo - ea-php70-php-fpm - ea-php70-php-ftp - ea-php70-php-gd - ea-php70-php-gettext - ea-php70-php-iconv - ea-php70-php-imap - ea-php70-php-intl - ea-php70-php-litespeed - ea-php70-php-mbstring - ea-php70-php-mcrypt - ea-php70-php-mysqlnd - ea-php70-php-pdo - ea-php70-php-posix - ea-php70-php-snmp - ea-php70-php-soap - ea-php70-php-sockets - ea-php70-php-sourceguardian - ea-php70-php-xml - ea-php70-php-xmlrpc - ea-php70-php-zip - ea-php70-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-15 01:58:07 (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 01:58:07 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-16 01:54:13 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-16 01:58:14 (7553) [INFO] Newer version of script found. Downloading. * 2024-05-16 02:02:15 (7562) [INFO] Script update to version 38 successful. * 2024-05-16 02:06:18 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-16 02:06:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-16 02:06:20 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-16 02:06:20 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:49 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-16 02:09:49 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-16 02:09:49 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-16 02:09:49 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-16 02:09:49 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4eAUQg5HT8/ea_profile.json * 2024-05-16 02:09:51 (5705) [INFO] Backed up EA4 profile to /tmp/4eAUQg5HT8/ea_profile.json * 2024-05-16 02:10:01 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-16 02:10:35 (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 02:10:35 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-17 01:56:30 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-17 02:00:31 (7748) [INFO] Script is up to date. * 2024-05-17 02:04:34 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-17 02:04:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-17 02:04:36 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-17 02:04:36 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:48 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-17 02:07:48 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30066 milliseconds with 0 out of 0 bytes received') * 2024-05-17 02:07:49 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-17 02:07:49 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-17 02:07:49 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-17 02:07:49 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-17 02:07:49 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UvMVWMhVGH/ea_profile.json * 2024-05-17 02:07:51 (5705) [INFO] Backed up EA4 profile to /tmp/UvMVWMhVGH/ea_profile.json * 2024-05-17 02:08:01 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-17 02:08:36 (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 02:08:36 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-18 01:54:38 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-18 01:58:38 (7748) [INFO] Script is up to date. * 2024-05-18 02:02:41 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-18 02:02:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-18 02:02:43 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-18 02:02:43 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:55 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-18 02:05:55 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-18 02:05:55 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-18 02:05:55 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-18 02:05:55 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y58Ael79de/ea_profile.json * 2024-05-18 02:05:58 (5705) [INFO] Backed up EA4 profile to /tmp/y58Ael79de/ea_profile.json * 2024-05-18 02:06:08 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-18 02:06:42 (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 02:06:42 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-19 01:53:35 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-19 01:57:36 (7748) [INFO] Script is up to date. * 2024-05-19 02:01:38 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-19 02:01:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-19 02:01:40 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-19 02:01:40 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:54 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-19 02:04:54 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-19 02:04:54 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-19 02:04:54 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-19 02:04:54 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qnfD4OUAPE/ea_profile.json * 2024-05-19 02:04:57 (5705) [INFO] Backed up EA4 profile to /tmp/qnfD4OUAPE/ea_profile.json * 2024-05-19 02:05:08 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-19 02:05:42 (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 02:05:42 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-20 01:53:35 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-20 01:57:35 (7748) [INFO] Script is up to date. * 2024-05-20 02:01:38 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-20 02:01:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-20 02:01:40 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-20 02:01:40 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:22 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-20 02:05:22 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30314 milliseconds') * 2024-05-20 02:05:22 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-20 02:05:22 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-20 02:05:22 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-20 02:05:22 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-20 02:05:22 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PhSRVRQ18m/ea_profile.json * 2024-05-20 02:05:25 (5705) [INFO] Backed up EA4 profile to /tmp/PhSRVRQ18m/ea_profile.json * 2024-05-20 02:05:35 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-20 02:06:09 (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 02:06:09 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-20 17:34:45 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-20 17:38:45 (7748) [INFO] Script is up to date. * 2024-05-20 17:42:48 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-20 17:42:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-20 17:42:49 (201) [WARN] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.31) does not appear to be up to date. Please upgrade cPanel to 11.110.0.33. * 2024-05-20 17:42:51 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-20 17:42:51 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 17:45:48 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-20 17:45:48 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-20 17:45:48 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-20 17:45:48 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-20 17:45:48 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A1DNPpzKgh/ea_profile.json * 2024-05-20 17:45:53 (5705) [INFO] Backed up EA4 profile to /tmp/A1DNPpzKgh/ea_profile.json * 2024-05-20 17:46:03 (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-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-20 17:46:38 (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 17:46:38 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-21 02:03:51 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-21 02:07:52 (7748) [INFO] Script is up to date. * 2024-05-21 02:11:55 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-21 02:11:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-21 02:11:57 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-21 02:11:57 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-21 02:15:08 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-21 02:15:08 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-21 02:15:08 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-21 02:15:08 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-21 02:15:08 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dndKW_BtCE/ea_profile.json * 2024-05-21 02:15:11 (5705) [INFO] Backed up EA4 profile to /tmp/dndKW_BtCE/ea_profile.json * 2024-05-21 02:15:21 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-21 02:15:55 (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-21 02:15:55 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-22 02:06:26 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-22 02:10:26 (7748) [INFO] Script is up to date. * 2024-05-22 02:14:29 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-22 02:14:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-22 02:14:31 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-22 02:14:31 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-22 02:17:53 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-22 02:17:53 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30089 milliseconds with 0 out of 0 bytes received') * 2024-05-22 02:17:54 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-22 02:17:54 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-22 02:17:54 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-22 02:17:54 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-22 02:17:54 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RojjL08ivQ/ea_profile.json * 2024-05-22 02:17:57 (5705) [INFO] Backed up EA4 profile to /tmp/RojjL08ivQ/ea_profile.json * 2024-05-22 02:18: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-22 02:18:42 (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-22 02:18:42 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-23 01:57:28 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-23 02:01:28 (7748) [INFO] Script is up to date. * 2024-05-23 02:05:31 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-23 02:05:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-23 02:05:33 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-23 02:05:33 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-23 02:09:05 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-23 02:09:05 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-23 02:09:05 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-23 02:09:05 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-23 02:09:05 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oSwAAwOPSs/ea_profile.json * 2024-05-23 02:09:07 (5705) [INFO] Backed up EA4 profile to /tmp/oSwAAwOPSs/ea_profile.json * 2024-05-23 02:09:18 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-23 02:09: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-23 02:09:53 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-24 01:56:56 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-24 02:00:56 (7748) [INFO] Script is up to date. * 2024-05-24 02:04:59 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-24 02:05:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-24 02:05:02 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-24 02:05:02 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-24 02:08:04 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-24 02:08:04 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-24 02:08:04 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-24 02:08:04 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-24 02:08:04 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PLLrMrzu2_/ea_profile.json * 2024-05-24 02:08:06 (5705) [INFO] Backed up EA4 profile to /tmp/PLLrMrzu2_/ea_profile.json * 2024-05-24 02:08:17 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-24 02:08:52 (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-24 02:08:52 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-25 01:59:49 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-25 02:03:49 (7748) [INFO] Script is up to date. * 2024-05-25 02:07:52 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-25 02:07:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-25 02:07:55 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-25 02:07:55 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-25 02:11:10 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-25 02:11:10 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-25 02:11:10 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-25 02:11:10 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-25 02:11:10 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C7lDyZYCWf/ea_profile.json * 2024-05-25 02:11:13 (5705) [INFO] Backed up EA4 profile to /tmp/C7lDyZYCWf/ea_profile.json * 2024-05-25 02:11:23 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-25 02:11:58 (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-25 02:11:58 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-26 01:54:24 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-26 01:58:25 (7748) [INFO] Script is up to date. * 2024-05-26 02:02:28 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-26 02:02:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-26 02:02:30 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-26 02:02:30 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-26 02:05:56 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-26 02:05:56 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') * 2024-05-26 02:05:57 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-26 02:05:57 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-26 02:05:57 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-26 02:05:57 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-26 02:05:57 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Bq0cdA3eDl/ea_profile.json * 2024-05-26 02:05:59 (5705) [INFO] Backed up EA4 profile to /tmp/Bq0cdA3eDl/ea_profile.json * 2024-05-26 02:06:10 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-26 02:06:45 (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-26 02:06:45 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-27 01:53:37 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-27 01:57:37 (7748) [INFO] Script is up to date. * 2024-05-27 02:01:40 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-27 02:01:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-27 02:01:42 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-27 02:01:42 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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-27 02:05:26 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-27 02:05:26 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2024-05-27 02:05:27 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-27 02:05:27 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-27 02:05:27 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-27 02:05:27 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-27 02:05:27 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tCegScuIHu/ea_profile.json * 2024-05-27 02:05:30 (5705) [INFO] Backed up EA4 profile to /tmp/tCegScuIHu/ea_profile.json * 2024-05-27 02:05:40 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-27 02:06:15 (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-27 02:06:15 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-28 01:54:17 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-28 01:58:18 (7748) [INFO] Script is up to date. * 2024-05-28 02:02:21 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-28 02:02:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-28 02:02:23 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-28 02:02:23 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-28 02:05:54 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-28 02:05:54 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-28 02:05:54 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-28 02:05:54 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-28 02:05:54 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ktJXpBT4t0/ea_profile.json * 2024-05-28 02:05:56 (5705) [INFO] Backed up EA4 profile to /tmp/ktJXpBT4t0/ea_profile.json * 2024-05-28 02:06: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-28 02:06:41 (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-28 02:06:41 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-28 08:51:20 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-28 08:55:20 (7748) [INFO] Script is up to date. * 2024-05-28 08:59:23 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-28 08:59:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-28 08:59:25 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-28 08:59:25 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-28 09:02:15 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-28 09:02:15 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-28 09:02:15 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-28 09:02:15 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-28 09:02:15 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QstnNdWTAy/ea_profile.json * 2024-05-28 09:02:18 (5705) [INFO] Backed up EA4 profile to /tmp/QstnNdWTAy/ea_profile.json * 2024-05-28 09:02:29 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-28 09:03:04 (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-28 09:03:04 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-29 01:52:19 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-29 01:56:19 (7748) [INFO] Script is up to date. * 2024-05-29 02:00:21 (2163) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-29 02:00:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-29 02:00:24 (720) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-29 02:00:24 (727) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-29 02:05:26 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-29 02:05:26 (1933) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/6de075d5241d04134c50f4ecf6506ffb213df39ebbb7d5bf333ecac88d3950fe-other.sqlite.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/. * 2024-05-29 02:05:27 (1502) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-29 02:05:27 (201) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-29 02:05:27 (201) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-29 02:05:27 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-29 02:05:27 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/V4YVp7sr7q/ea_profile.json * 2024-05-29 02:05:29 (5705) [INFO] Backed up EA4 profile to /tmp/V4YVp7sr7q/ea_profile.json * 2024-05-29 02:05:39 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-29 02:06: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-29 02:06:14 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-30 02:26:11 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-30 02:30:12 (7731) [INFO] Newer version of script found. Downloading. * 2024-05-30 02:34:13 (7740) [INFO] Script update to version 39 successful. * 2024-05-30 02:38:16 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-30 02:38:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-30 02:38:17 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-05-30 02:38:17 (6568) [INFO] * 2024-05-30 02:38:27 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-05-30 02:38:27 (6598) [INFO] * 2024-05-30 02:38:29 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-30 02:38:29 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-30 02:41:57 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-30 02:41:57 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-30 02:41:57 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-30 02:41:57 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-30 02:41:57 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KkcOSFAqtY/ea_profile.json * 2024-05-30 02:42:00 (5773) [INFO] Backed up EA4 profile to /tmp/KkcOSFAqtY/ea_profile.json * 2024-05-30 02:42:10 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-30 02:42:44 (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-05-30 02:42:44 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-31 02:04:48 (7795) [INFO] Self-update of script version 39 requested. * 2024-05-31 02:08:48 (7817) [INFO] Script is up to date. * 2024-05-31 02:12:51 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-05-31 02:12:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-05-31 02:12:52 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-05-31 02:12:52 (6568) [INFO] * 2024-05-31 02:13:05 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-05-31 02:13:05 (6598) [INFO] * 2024-05-31 02:13:07 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-05-31 02:13:07 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-31 02:16:34 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-05-31 02:16:34 (1982) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') * 2024-05-31 02:16:34 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-05-31 02:16:34 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-05-31 02:16:34 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-05-31 02:16:34 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-31 02:16:35 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KoHT5J19Jl/ea_profile.json * 2024-05-31 02:16:37 (5773) [INFO] Backed up EA4 profile to /tmp/KoHT5J19Jl/ea_profile.json * 2024-05-31 02:16:47 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-05-31 02:17:21 (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-05-31 02:17:21 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-01 01:55:06 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-01 01:59:07 (7817) [INFO] Script is up to date. * 2024-06-01 02:03:10 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-01 02:03:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-01 02:03:10 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-01 02:03:10 (6568) [INFO] * 2024-06-01 02:03:24 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-01 02:03:24 (6598) [INFO] * 2024-06-01 02:03:26 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-01 02:03:26 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-01 02:06:56 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-01 02:06:56 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-01 02:06:56 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-01 02:06:56 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-01 02:06:56 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eLDduZE9vW/ea_profile.json * 2024-06-01 02:06:59 (5773) [INFO] Backed up EA4 profile to /tmp/eLDduZE9vW/ea_profile.json * 2024-06-01 02:07:10 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-01 02:07:45 (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-01 02:07:45 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-02 01:54:04 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-02 01:58:04 (7817) [INFO] Script is up to date. * 2024-06-02 02:02:07 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-02 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-02 02:02:08 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-02 02:02:08 (6568) [INFO] * 2024-06-02 02:02:19 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-02 02:02:20 (6598) [INFO] * 2024-06-02 02:02:22 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-02 02:02:22 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:49 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-02 02:05:49 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-02 02:05:49 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-02 02:05:49 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-02 02:05:49 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LsJY3vMgoD/ea_profile.json * 2024-06-02 02:05:52 (5773) [INFO] Backed up EA4 profile to /tmp/LsJY3vMgoD/ea_profile.json * 2024-06-02 02:06:03 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-02 02:06:38 (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 02:06:38 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-03 01:45:29 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-03 01:49:29 (7817) [INFO] Script is up to date. * 2024-06-03 01:53:32 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-03 01:53:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-03 01:53:32 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-03 01:53:32 (6568) [INFO] * 2024-06-03 01:53:44 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-03 01:53:45 (6598) [INFO] * 2024-06-03 01:53:47 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-03 01:53:47 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-03 01:58:01 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-03 01:58:01 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-03 01:58:01 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-03 01:58:01 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-03 01:58:01 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WPrv1fnQCv/ea_profile.json * 2024-06-03 01:58:04 (5773) [INFO] Backed up EA4 profile to /tmp/WPrv1fnQCv/ea_profile.json * 2024-06-03 01:58:14 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-03 01:58:48 (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 01:58:48 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-04 01:51:14 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-04 01:55:14 (7817) [INFO] Script is up to date. * 2024-06-04 01:59:17 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-04 01:59:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-04 01:59:17 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-04 01:59:17 (6568) [INFO] * 2024-06-04 01:59:29 (6581) [INFO] {"items": "7.12.4", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-04 01:59:29 (6598) [INFO] * 2024-06-04 01:59:31 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-04 01:59:31 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:02:17 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-04 02:02:17 (1982) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30192 milliseconds with 0 out of 0 bytes received') * 2024-06-04 02:02:18 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-04 02:02:18 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-04 02:02:18 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-04 02:02:18 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-04 02:02:18 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fFqi8nCfpw/ea_profile.json * 2024-06-04 02:02:21 (5773) [INFO] Backed up EA4 profile to /tmp/fFqi8nCfpw/ea_profile.json * 2024-06-04 02:02:31 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-04 02:03:06 (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 02:03:06 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-05 02:00:05 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-05 02:04:06 (7817) [INFO] Script is up to date. * 2024-06-05 02:08:09 (2212) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-05 02:08:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-05 02:08:09 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-05 02:08:09 (6568) [INFO] * 2024-06-05 02:08:13 (6581) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-05 02:08:13 (6598) [INFO] * 2024-06-05 02:08:15 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-05 02:08:15 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:11:43 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-05 02:11:43 (1982) [ERROR] https://mirror.servaxnet.com/epel/7/x86_64/repodata/7f3262f88f89b5d6073aebbb424f56fd2e659948eced4954e4439d3c901c1e1a-other.sqlite.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/. * 2024-06-05 02:11:44 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-05 02:11:44 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-05 02:11:44 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-05 02:11:44 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-05 02:11:44 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lG17W4uTcR/ea_profile.json * 2024-06-05 02:11:47 (5773) [INFO] Backed up EA4 profile to /tmp/lG17W4uTcR/ea_profile.json * 2024-06-05 02:11: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-05 02:12:32 (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 02:12:32 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-06 01:57:18 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-06 02:01:18 (7800) [INFO] Newer version of script found. Downloading. * 2024-06-06 02:05:20 (7809) [INFO] Script update to version 40 successful. * 2024-06-06 02:09:23 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-06 02:09:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-06 02:09:23 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-06 02:09:23 (6580) [INFO] * 2024-06-07 01:53:31 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-07 01:57:31 (7829) [INFO] Script is up to date. * 2024-06-07 02:01:34 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-07 02:01:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-07 02:01:34 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-07 02:01:34 (6580) [INFO] * 2024-06-07 02:01:37 (6593) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-07 02:01:37 (6610) [INFO] * 2024-06-07 02:01:39 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-07 02:01:39 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:23 (1982) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30724 milliseconds') * 2024-06-07 02:05:23 (1983) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-07 02:05:23 (6579) [INFO] Running: /usr/bin/yum clean all * 2024-06-07 02:05:23 (6580) [INFO] * 2024-06-07 02:05:23 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-07 02:05:24 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-07 02:05:24 (6593) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-07 02:05:24 (6593) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-07 02:05:24 (6593) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-07 02:05:24 (6593) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-07 02:05:24 (6593) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-07 02:05:24 (6593) [INFO] Cleaning up list of fastest mirrors * 2024-06-07 02:05:24 (6593) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-07 02:05:25 (6610) [INFO] * 2024-06-07 02:06:19 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-07 02:06:19 (1993) [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 * 2024-06-07 02:06:20 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-07 02:06:20 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-07 02:06:20 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-07 02:06:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-07 02:06:20 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/af5_sqjB4c/ea_profile.json * 2024-06-07 02:12:52 (5785) [INFO] Backed up EA4 profile to /tmp/af5_sqjB4c/ea_profile.json * 2024-06-07 02:13:03 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-07 02:13: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 02:13:38 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-08 01:53:46 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-08 01:57:46 (7829) [INFO] Script is up to date. * 2024-06-08 02:01:49 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-08 02:01:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-08 02:01:50 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-08 02:01:50 (6580) [INFO] * 2024-06-08 02:02:04 (6593) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-08 02:02:05 (6610) [INFO] * 2024-06-08 02:02:07 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-08 02:02:07 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:06:07 (1982) [WARN] Initial run of "yum makecache" failed: https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/af7d65257a8666d7726a8fc24b5db50138ad6634bf3386d81af153d00495b57b-other.sqlite.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/. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/af7d65257a8666d7726a8fc24b5db50138ad6634bf3386d81af153d00495b57b-other.sqlite.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://linux.mirrors.es.net/fedora-epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://www.gtlib.gatech.edu/pub/fedora-epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. http://mirror.compevo.com/epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://mirrors.wcupa.edu/epel/7/x86_64/repodata/3ff739acc53134c7fc8586b00efb21b8db6395bfda3a452ded5c7a51baa19207-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2024-06-08 02:06:07 (1983) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-08 02:06:07 (6579) [INFO] Running: /usr/bin/yum clean all * 2024-06-08 02:06:07 (6580) [INFO] * 2024-06-08 02:06:07 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-08 02:06:07 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-08 02:06:07 (6593) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-08 02:06:07 (6593) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-08 02:06:07 (6593) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-08 02:06:07 (6593) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-08 02:06:07 (6593) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-08 02:06:08 (6593) [INFO] Cleaning up list of fastest mirrors * 2024-06-08 02:06:08 (6593) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-08 02:06:08 (6610) [INFO] * 2024-06-08 02:16:14 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-08 02:16:14 (1993) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/002b81c9c93242d32766c4f8496aea981ac7df990c5b652cfc917b2cef7c6364-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE3ODMzNzIyOjE3MTgwOTI5MjI6LBmW36eiuS5sqzytlUdABc0oHQhsUqPgJYeHHMBkyc868Mw4J6wZjhGMOL_3dKXs88WJuZb3eejhmuwlALI0zQJ9EAlm7qyns749N8L7gllCNLY2A-4-FhstDPa4okdQBCvRsXAVKGYupUj4ez2-U4UvSLqzi0WG0Hqtq3cr78jRZIoS5H0FRi6vKXSwFpZ1qnONLj07I38oKO2XALQtU7zIRO9HWhOF6hjHFyhxpzHSJ94TBIn2QVWgX8AZARxRNOM3PzX-USpcGIgzpPcYp4S1hQ6R656M_J4IsyF7KJyjkxnqqkZMZEkRlzoKtuODlpOgAuWEfraDF1fz0ptf4p4_VZ6L9RwyI4v-vwrWlhW_yeX22TiiNQmepfuIYYv7RzI9QrJQEgmUrl7PpEMsDdkVuj0k0i58SeaZYtRyzfBxsdu_nG3Js3I3VaDdTMZn8UD3_OCM4ArmpCYPN92Y17U9d-6JMx_lGI3sRQGBEwyUPVMVLulixlRC5wxoO7swxeadOsyANweqlBCfOQc378LbGf1pRw-yg8dHqA1Qow6P3KvHfKDhiTSBY5gfxjPE2TuEqEojgTBssrX77cEAefM45lGtqd5-_kR1W6mS3XlfAr7KSmDvNcyMaedcU_Luwo12Q_9dgeh3Ouf83XNfLAmeudKrig7FAp9deZZyXc8%3D/ea-php/7/updates/x86_64/repodata/9a8fd6ee864ffcde316d7770302273afe8dcbbef4df3745946cd6c6cfa146fb5-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.sfo12.us.leaseweb.net/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.rit.edu/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://www.gtlib.gatech.edu/pub/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.centos.iad1.serverforge.org/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirrors.maine.edu/CentOS/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://linux-mirrors.fnal.gov/linux/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.facebook.net/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.team-cymru.com/CentOS/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.cogentco.com/pub/linux/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-06-08 02:16:15 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-08 02:16:15 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-08 02:16:15 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-08 02:16:15 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-08 02:16:15 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/whF7tfiX6T/ea_profile.json * 2024-06-08 02:16:18 (5785) [INFO] Backed up EA4 profile to /tmp/whF7tfiX6T/ea_profile.json * 2024-06-08 02:16:29 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-08 02:17:03 (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 02:17:03 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-09 01:54:17 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-09 01:58:17 (7829) [INFO] Script is up to date. * 2024-06-09 02:02:20 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-09 02:02:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-09 02:02:20 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-09 02:02:20 (6580) [INFO] * 2024-06-10 01:50:30 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-10 01:54:30 (7829) [INFO] Script is up to date. * 2024-06-10 01:58:33 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-10 01:58:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-10 01:58:34 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-10 01:58:34 (6580) [INFO] * 2024-06-10 01:58:45 (6593) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-10 01:58:46 (6610) [INFO] * 2024-06-10 01:58:48 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-10 01:58:48 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:44 (1982) [WARN] Initial run of "yum makecache" failed: https://sjc.mirror.rackspace.com/epel/7/x86_64/repodata/d18597546d793126bca85e7d17cc6417d7448423af682487d2b4cb952ec3a27c-other.sqlite.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/. * 2024-06-10 02:01:44 (1983) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-10 02:01:44 (6579) [INFO] Running: /usr/bin/yum clean all * 2024-06-10 02:01:44 (6580) [INFO] * 2024-06-10 02:01:45 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-10 02:01:45 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-10 02:01:45 (6593) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-10 02:01:45 (6593) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-10 02:01:45 (6593) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-10 02:01:45 (6593) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-10 02:01:45 (6593) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-10 02:01:46 (6593) [INFO] Cleaning up list of fastest mirrors * 2024-06-10 02:01:46 (6593) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-10 02:01:46 (6610) [INFO] * 2024-06-10 02:02:41 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-10 02:02:41 (1993) [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 * 2024-06-10 02:02:42 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-10 02:02:42 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-10 02:02:42 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-10 02:02:42 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-10 02:02:42 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UjEbqwSXwN/ea_profile.json * 2024-06-10 02:07:27 (5785) [INFO] Backed up EA4 profile to /tmp/UjEbqwSXwN/ea_profile.json * 2024-06-10 02:07: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-10 02:08:12 (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 02:08:12 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-11 02:02:28 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-11 02:06:28 (7829) [INFO] Script is up to date. * 2024-06-11 02:10:31 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-11 02:10:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-11 02:10:32 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-11 02:10:32 (6580) [INFO] * 2024-06-11 02:14:50 (6593) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-11 02:14:51 (6610) [INFO] * 2024-06-11 02:14:53 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-11 02:14:53 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:18:25 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-11 02:18:25 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-11 02:18:25 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-11 02:18:25 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-11 02:18:25 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WLi78w1rTm/ea_profile.json * 2024-06-11 02:18:28 (5785) [INFO] Backed up EA4 profile to /tmp/WLi78w1rTm/ea_profile.json * 2024-06-11 02:18:39 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-11 02:19:14 (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 02:19:14 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-12 01:53:49 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-12 01:57:49 (7829) [INFO] Script is up to date. * 2024-06-12 02:01:52 (2224) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-12 02:01:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-12 02:01:52 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-12 02:01:52 (6580) [INFO] * 2024-06-12 02:02:05 (6593) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-12 02:02:06 (6610) [INFO] * 2024-06-12 02:02:08 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-12 02:02:08 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:06 (1982) [WARN] Initial run of "yum makecache" failed: http://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/e810119a8fd6e42559b1413753d8c0fca3984524d4d0217c9e2fbec4e5fca802-filelists.sqlite.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/. * 2024-06-12 02:09:06 (1983) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-12 02:09:06 (6579) [INFO] Running: /usr/bin/yum clean all * 2024-06-12 02:09:06 (6580) [INFO] * 2024-06-12 02:09:07 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-12 02:09:07 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-12 02:09:07 (6593) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-12 02:09:07 (6593) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-12 02:09:07 (6593) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-12 02:09:07 (6593) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-12 02:09:07 (6593) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-12 02:09:08 (6593) [INFO] Cleaning up list of fastest mirrors * 2024-06-12 02:09:08 (6593) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-12 02:09:08 (6610) [INFO] * 2024-06-12 02:10:03 (1992) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-12 02:10:03 (1993) [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 * 2024-06-12 02:10:04 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-12 02:10:04 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-12 02:10:04 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-12 02:10:04 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-12 02:10:04 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cooVWNz3WB/ea_profile.json * 2024-06-12 02:15:14 (5785) [INFO] Backed up EA4 profile to /tmp/cooVWNz3WB/ea_profile.json * 2024-06-12 02: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-12 02:16:00 (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 02:16:00 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-13 01:48:22 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-13 01:52:23 (7812) [INFO] Newer version of script found. Downloading. * 2024-06-13 01:56:24 (7821) [INFO] Script update to version 41 successful. * 2024-06-13 02:00:27 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-13 02:00:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-13 02:00:28 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-13 02:00:28 (6591) [INFO] * 2024-06-13 02:00:39 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-13 02:00:40 (6621) [INFO] * 2024-06-13 02:00:42 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-13 02:00:42 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:13 (1985) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-06-13 02:01:13 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-13 02:01:13 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-13 02:01:13 (6591) [INFO] * 2024-06-13 02:01:13 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-13 02:01:13 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-13 02:01:13 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-13 02:01:13 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-13 02:01:13 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-13 02:01:13 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-13 02:01:13 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-13 02:01:14 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-13 02:01:14 (6604) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-13 02:01:14 (6621) [INFO] * 2024-06-13 02:07:18 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-13 02:07:18 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-13 02:07:18 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-13 02:07:18 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-13 02:07:18 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/us5oqRVg9C/ea_profile.json * 2024-06-13 02:07:21 (5796) [INFO] Backed up EA4 profile to /tmp/us5oqRVg9C/ea_profile.json * 2024-06-13 02:07: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-13 02:08: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-13 02:08:06 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-14 02:24:45 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-14 02:28:45 (7840) [INFO] Script is up to date. * 2024-06-14 02:32:48 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-14 02:32:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-14 02:32:48 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-14 02:32:48 (6591) [INFO] * 2024-06-14 02:32:52 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-14 02:32:52 (6621) [INFO] * 2024-06-14 02:32:54 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-14 02:32:54 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:36:23 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-14 02:36:23 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-14 02:36:23 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-14 02:36:23 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-14 02:36:23 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1spcsDLxoJ/ea_profile.json * 2024-06-14 02:36:26 (5796) [INFO] Backed up EA4 profile to /tmp/1spcsDLxoJ/ea_profile.json * 2024-06-14 02:36: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-14 02:37:11 (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 02:37:11 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-15 01:57:16 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-15 02:01:16 (7840) [INFO] Script is up to date. * 2024-06-15 02:05:19 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-15 02:05:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-15 02:05:19 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-15 02:05:19 (6591) [INFO] * 2024-06-15 02:05:30 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-15 02:05:30 (6621) [INFO] * 2024-06-15 02:05:32 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-15 02:05:32 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:08:50 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-15 02:08:50 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-15 02:08:50 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-15 02:08:50 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-15 02:08:50 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q7ocJmg9F5/ea_profile.json * 2024-06-15 02:08:53 (5796) [INFO] Backed up EA4 profile to /tmp/q7ocJmg9F5/ea_profile.json * 2024-06-15 02:09:04 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-15 02:09: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 02:09:38 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-16 02:11:28 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-16 02:15:28 (7840) [INFO] Script is up to date. * 2024-06-16 02:19:31 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-16 02:19:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-16 02:19:32 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-16 02:19:32 (6591) [INFO] * 2024-06-16 02:19:35 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-16 02:19:35 (6621) [INFO] * 2024-06-16 02:19:37 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-16 02:19:37 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:23:10 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-16 02:23:10 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-16 02:23:10 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-16 02:23:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-16 02:23:10 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3zDA4blmNj/ea_profile.json * 2024-06-16 02:23:13 (5796) [INFO] Backed up EA4 profile to /tmp/3zDA4blmNj/ea_profile.json * 2024-06-16 02:23:23 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-16 02:23:57 (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 02:23:57 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-17 01:55:30 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-17 01:59:30 (7840) [INFO] Script is up to date. * 2024-06-17 02:03:33 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-17 02:03:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-17 02:03:34 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-17 02:03:34 (6591) [INFO] * 2024-06-17 02:03:45 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-17 02:03:45 (6621) [INFO] * 2024-06-17 02:03:47 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-17 02:03:47 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:20 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-17 02:07:20 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-17 02:07:20 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-17 02:07:20 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-17 02:07:20 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/onaq9bnkxf/ea_profile.json * 2024-06-17 02:07:23 (5796) [INFO] Backed up EA4 profile to /tmp/onaq9bnkxf/ea_profile.json * 2024-06-17 02:07: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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-17 02:08:07 (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 02:08:07 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-18 02:14:47 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-18 02:18:48 (7840) [INFO] Script is up to date. * 2024-06-18 02:22:51 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-18 02:22:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-18 02:22:51 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-18 02:22:51 (6591) [INFO] * 2024-06-18 02:29:53 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-18 02:29:53 (6621) [INFO] * 2024-06-18 02:29:55 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-18 02:29:55 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:33:10 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-18 02:33:10 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-18 02:33:10 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-18 02:33:10 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-18 02:33:10 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lxd3VSXL_a/ea_profile.json * 2024-06-18 02:33:12 (5796) [INFO] Backed up EA4 profile to /tmp/lxd3VSXL_a/ea_profile.json * 2024-06-18 02:33:22 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-18 02:33:57 (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 02:33:57 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-19 01:55:09 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-19 01:59:09 (7840) [INFO] Script is up to date. * 2024-06-19 02:03:11 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-19 02:03:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-19 02:03:12 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-19 02:03:12 (6591) [INFO] * 2024-06-19 02:03:22 (6604) [INFO] {"items": "7.12.6", "strategy": "CSF_COOP", "warnings": [], "version": "7.12.6", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 122, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-19 02:03:22 (6621) [INFO] * 2024-06-19 02:03:24 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-19 02:03:24 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:11 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-19 02:07:11 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-19 02:07:11 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-19 02:07:11 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-19 02:07:11 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3tgOhGykfc/ea_profile.json * 2024-06-19 02:07:13 (5796) [INFO] Backed up EA4 profile to /tmp/3tgOhGykfc/ea_profile.json * 2024-06-19 02:07:24 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-19 02:07:58 (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 02:07:58 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-20 01:58:57 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-20 02:02:57 (7840) [INFO] Script is up to date. * 2024-06-20 02:07:00 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-20 02:07:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-20 02:07:00 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-20 02:07:00 (6591) [INFO] * 2024-06-20 02:07:10 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-20 02:07:10 (6621) [INFO] * 2024-06-20 02:07:12 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-20 02:07:12 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:10:44 (1985) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2024-06-20 02:10:44 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-20 02:10:44 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-20 02:10:44 (6591) [INFO] * 2024-06-20 02:10:44 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-20 02:10:44 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-20 02:10:44 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-20 02:10:44 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-20 02:10:44 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-20 02:10:44 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-20 02:10:44 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-20 02:10:45 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-20 02:10:45 (6604) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-20 02:10:45 (6621) [INFO] * 2024-06-20 02:19:00 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-20 02:19:00 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-20 02:19:00 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-20 02:19:00 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-20 02:19:00 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y3SwUVkJ0E/ea_profile.json * 2024-06-20 02:19:03 (5796) [INFO] Backed up EA4 profile to /tmp/y3SwUVkJ0E/ea_profile.json * 2024-06-20 02:19:13 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-20 02:19:48 (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 02:19:48 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-21 02:15:21 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-21 02:19:22 (7840) [INFO] Script is up to date. * 2024-06-21 02:23:24 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-21 02:23:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-21 02:23:25 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-21 02:23:25 (6591) [INFO] * 2024-06-21 02:23:37 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-21 02:23:37 (6621) [INFO] * 2024-06-21 02:23:39 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-21 02:23:39 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:27:11 (1985) [WARN] Initial run of "yum makecache" failed: https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/9f81317f8511f3c549a00e624f3b13265f4858c4f6a339eb49689b616fceff2f-other.sqlite.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/. * 2024-06-21 02:27:11 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-21 02:27:11 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-21 02:27:11 (6591) [INFO] * 2024-06-21 02:27:11 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-21 02:27:12 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-21 02:27:12 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-21 02:27:12 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-21 02:27:12 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-21 02:27:12 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-21 02:27:12 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-21 02:27:12 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-21 02:27:12 (6604) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-21 02:27:12 (6621) [INFO] * 2024-06-21 02:36:21 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-21 02:36:21 (1996) [ERROR] https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/c0b5a9a02c323c10a21a578ab5ce3fdce9e4783bd0658f51990e9a67c7a651dd-filelists.sqlite.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://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/3f3cbcdead721e21aaad88e3078f6e174717febe7f77c1774b54062c1ee1f1c3-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2024-06-21 02:36:22 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-21 02:36:22 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-21 02:36:22 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-21 02:36:22 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-21 02:36:22 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P180EcOWeF/ea_profile.json * 2024-06-21 02:36:25 (5796) [INFO] Backed up EA4 profile to /tmp/P180EcOWeF/ea_profile.json * 2024-06-21 02:36:35 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-21 02:37:10 (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 02:37:10 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-22 01:57:36 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-22 02:01:37 (7840) [INFO] Script is up to date. * 2024-06-22 02:05:39 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-22 02:05:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-22 02:05:40 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-22 02:05:40 (6591) [INFO] * 2024-06-22 02:05:52 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-22 02:05:53 (6621) [INFO] * 2024-06-22 02:05:55 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-22 02:05:55 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:37 (1985) [WARN] Initial run of "yum makecache" failed: https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/d0b763e2d537579e3b527e04bea1227a42552b08ab21d078db1f9722accff1a9-other.sqlite.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/. * 2024-06-22 02:09:37 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-22 02:09:37 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-22 02:09:37 (6591) [INFO] * 2024-06-22 02:09:37 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-22 02:09:38 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-22 02:09:38 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-22 02:09:38 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-22 02:09:38 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-22 02:09:38 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-22 02:09:38 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-22 02:09:39 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-22 02:09:39 (6604) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-06-22 02:09:39 (6621) [INFO] * 2024-06-22 02:18:04 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-22 02:18:04 (1996) [ERROR] https://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/80c022262d02f9b84b175930b25822fee5cd8dc964297c4087ed73ef742857bd-filelists.sqlite.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://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/e0e45df60bbb20381c6ae2add2354b115977142b2a0848073b15c6bdb73ddd27-prestodelta.xml.gz: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2024-06-22 02:18:05 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-22 02:18:05 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-22 02:18:05 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-22 02:18:05 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-22 02:18:05 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zJjniPJdKh/ea_profile.json * 2024-06-22 02:18:08 (5796) [INFO] Backed up EA4 profile to /tmp/zJjniPJdKh/ea_profile.json * 2024-06-22 02:18:18 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-22 02:18: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-22 02:18:53 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-23 01:50:49 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-23 01:54:50 (7840) [INFO] Script is up to date. * 2024-06-23 01:58:53 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-23 01:58:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-23 01:58:53 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-23 01:58:53 (6591) [INFO] * 2024-06-23 01:59:05 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-23 01:59:05 (6621) [INFO] * 2024-06-23 01:59:07 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-23 01:59:07 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:59 (1985) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-23 02:01:59 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-23 02:01:59 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-23 02:01:59 (6591) [INFO] * 2024-06-23 02:02:00 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-23 02:02:00 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-23 02:02:00 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-23 02:02:00 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-23 02:02:00 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-23 02:02:00 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-23 02:02:00 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-23 02:02:00 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-23 02:02:00 (6604) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2024-06-23 02:02:00 (6621) [INFO] * 2024-06-23 02:04:52 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-23 02:04:52 (1996) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-23 02:04:52 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-23 02:04:52 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-23 02:04:52 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-23 02:04:52 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-23 02:04:52 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BftEf8g_mB/ea_profile.json * 2024-06-23 02:07:32 (353) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BftEf8g_mB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775. * 2024-06-23 02:07:32 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-24 01:44:31 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-24 01:48:31 (7840) [INFO] Script is up to date. * 2024-06-24 01:52:34 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-24 01:52:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-24 01:52:34 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-24 01:52:34 (6591) [INFO] * 2024-06-24 01:52:43 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-24 01:52:44 (6621) [INFO] * 2024-06-24 01:52:45 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-24 01:52:45 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-24 01:53:17 (1985) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-06-24 01:53:17 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-24 01:53:17 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-24 01:53:17 (6591) [INFO] * 2024-06-24 01:53:17 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-24 01:53:17 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-24 01:53:17 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-24 01:53:17 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-24 01:53:17 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-24 01:53:17 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-24 01:53:17 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-24 01:53:17 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-24 01:53:17 (6604) [INFO] Other repos take up 912 k of disk space (use --verbose for details) * 2024-06-24 01:53:17 (6621) [INFO] * 2024-06-24 01:56:06 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-24 01:56:06 (1996) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-24 01:56:07 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-24 01:56:07 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-24 01:56:07 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-24 01:56:07 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-24 01:56:07 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PqCCXdkSyi/ea_profile.json * 2024-06-24 01:58:39 (353) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PqCCXdkSyi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775. * 2024-06-24 01:58:39 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-25 01:44:22 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-25 01:48:22 (7840) [INFO] Script is up to date. * 2024-06-25 01:52:25 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-25 01:52:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-25 01:52:26 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-25 01:52:26 (6591) [INFO] * 2024-06-25 01:52:35 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-25 01:52:36 (6621) [INFO] * 2024-06-25 01:52:37 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-25 01:52:37 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-25 01:55:19 (1985) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-25 01:55:19 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-25 01:55:19 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-25 01:55:19 (6591) [INFO] * 2024-06-25 01:55:19 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-25 01:55:20 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-25 01:55:20 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-25 01:55:20 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-25 01:55:20 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-25 01:55:20 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-25 01:55:20 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-25 01:55:20 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-25 01:55:20 (6604) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2024-06-25 01:55:20 (6621) [INFO] * 2024-06-25 01:58:24 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-25 01:58:24 (1996) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-25 01:58:25 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-25 01:58:25 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-25 01:58:25 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-25 01:58:25 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-25 01:58:25 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hYagbOXZkl/ea_profile.json * 2024-06-25 02:00:47 (353) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hYagbOXZkl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775. * 2024-06-25 02:00:47 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-26 01:53:54 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-26 01:57:54 (7840) [INFO] Script is up to date. * 2024-06-26 02:01:57 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-26 02:01:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-26 02:01:57 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-26 02:01:57 (6591) [INFO] * 2024-06-26 02:02:10 (6604) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-26 02:02:11 (6621) [INFO] * 2024-06-26 02:02:13 (723) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-26 02:02:13 (730) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:24 (1985) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-26 02:04:24 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-26 02:04:24 (6590) [INFO] Running: /usr/bin/yum clean all * 2024-06-26 02:04:24 (6591) [INFO] * 2024-06-26 02:04:24 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-26 02:04:25 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-26 02:04:25 (6604) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-26 02:04:25 (6604) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-26 02:04:25 (6604) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-26 02:04:25 (6604) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-26 02:04:25 (6604) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-26 02:04:25 (6604) [INFO] Cleaning up list of fastest mirrors * 2024-06-26 02:04:25 (6604) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2024-06-26 02:04:25 (6621) [INFO] * 2024-06-26 02:07:14 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-26 02:07:14 (1996) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-26 02:07:15 (1551) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-26 02:07:15 (202) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-26 02:07:15 (202) [WARN] *** Elevation Blocker detected: *** Your machine has multiple network interface cards (NICs) using kernel-names (ethX). Since the upgrade process cannot guarantee their stability after upgrade, you cannot upgrade. Please provide those interfaces new names before continuing the update. * 2024-06-26 02:07:15 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-26 02:07:15 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HWDIILcPRw/ea_profile.json * 2024-06-26 02:09:46 (353) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HWDIILcPRw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5775. * 2024-06-26 02:09:46 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-27 01:45:43 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-27 01:49:43 (7823) [INFO] Newer version of script found. Downloading. * 2024-06-27 01:53:45 (7832) [INFO] Script update to version 43 successful. * 2024-06-27 01:57:47 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-27 01:57:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-27 01:57:48 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-27 01:57:48 (6738) [INFO] * 2024-06-27 01:57:58 (6751) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-27 01:57:59 (6768) [INFO] * 2024-06-27 01:58:00 (726) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-27 01:58:00 (733) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:00:10 (1985) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-27 02:00:10 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-27 02:00:10 (6737) [INFO] Running: /usr/bin/yum clean all * 2024-06-27 02:00:10 (6738) [INFO] * 2024-06-27 02:00:11 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-27 02:00:11 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-27 02:00:11 (6751) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-27 02:00:11 (6751) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-27 02:00:11 (6751) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-27 02:00:11 (6751) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-27 02:00:11 (6751) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-27 02:00:11 (6751) [INFO] Cleaning up list of fastest mirrors * 2024-06-27 02:00:11 (6751) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2024-06-27 02:00:11 (6768) [INFO] * 2024-06-27 02:01:06 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-27 02:01:06 (1996) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-06-27 02:01:07 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-27 02:01:07 (207) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-27 02:01:07 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-06-27 02:01:07 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-06-27 02:01:07 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-27 02:01:14 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YYAT9f_nHs/ea_profile.json * 2024-06-27 02:04:01 (356) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YYAT9f_nHs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883. * 2024-06-27 02:04:01 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-28 01:52:03 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-28 01:56:04 (7994) [INFO] Script is up to date. * 2024-06-28 02:00:07 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-28 02:00:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-28 02:00:07 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-28 02:00:07 (6738) [INFO] * 2024-06-28 02:00:18 (6751) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-28 02:00:18 (6768) [INFO] * 2024-06-28 02:00:19 (726) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-28 02:00:19 (733) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:02:30 (1985) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE4ODAyODA1OjE3MTkwNjIwMDU6kPACTrR4_N9LTRR_b8EH2JISBjRSJ43_7Yk9jGRfIZsv_O2BC5XIt51V8kzbH9NCcejwBl0UmP5zTG_7waKxSztHEKBPKbEXTaG1atefQ8XNZPXAIg7pQ2LOsi22OmGgVgMxF_rEAVmN8xOn1-ifICVOLiQA6bYRd2fkcp78bUYx2jBMolxRV4QzhhjQM0ruUq2Y5p9LV6_8nFhm5zkNmy7XnJQ_gWAeK2ZUqq8upoQsy7M8AX7gpcZ3mRNboE2w57dcHqHF5T-Vkyg38x1u24lYLTFygvf-zxtEQC31cc-ZN6h9ZTeivvAM1Wy0PITnjByt7LrVqmnjFzCdpbLxxE8fG12AlyPEVYHDTwIzmMGJu3qyp_geKCLCA_6xU6H3BACFMmIlnHt7dJWmpVjaGnQJPyBnpAGVI1LY8VvJghK2kanNU0KGYhJybaaK5uB1unimwoCl09zXPldDL_4aiqH4GuRc7Q35XLRsY9VFwJx2RaLbVkfP7blPNmH2vPAFsv3qUDLTPsR0hvXG5sf5apkCNW5PJIarZMzEvkcs7p3L8taClVBfQrjrHL2RCo6WWe9kaPBqGNryEf1wI5TZRMNPNPimP6IGkuCBCqG7nN9gyDvmDsMbphfBdg88H_Xx8lBdkBnB6XCls955I7T7f3Gq4hzh4hwJtfu3b6OcQTM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-06-28 02:02:30 (1986) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-06-28 02:02:30 (6737) [INFO] Running: /usr/bin/yum clean all * 2024-06-28 02:02:30 (6738) [INFO] * 2024-06-28 02:02:30 (6751) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-06-28 02:02:30 (6751) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-06-28 02:02:30 (6751) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-06-28 02:02:30 (6751) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-06-28 02:02:30 (6751) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-06-28 02:02:30 (6751) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-06-28 02:02:30 (6751) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-06-28 02:02:30 (6751) [INFO] Cleaning up list of fastest mirrors * 2024-06-28 02:02:30 (6751) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2024-06-28 02:02:31 (6768) [INFO] * 2024-06-28 02:03:25 (1995) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-06-28 02:03:25 (1996) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-06-28 02:03:26 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-28 02:03:26 (207) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-28 02:03:26 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-06-28 02:03:26 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-06-28 02:03:26 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-28 02:03:33 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MiDXXZVHqP/ea_profile.json * 2024-06-28 02:06:20 (356) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MiDXXZVHqP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5883. * 2024-06-28 02:06:20 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-29 01:51:59 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-29 01:55:59 (7994) [INFO] Script is up to date. * 2024-06-29 02:00:02 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-29 02:00:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-29 02:00:03 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-29 02:00:03 (6738) [INFO] * 2024-06-29 02:00:14 (6751) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-29 02:00:14 (6768) [INFO] * 2024-06-29 02:00:16 (726) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-29 02:00:16 (733) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:43 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-29 02:04:43 (207) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-29 02:04:43 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-06-29 02:04:43 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-06-29 02:04:43 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-29 02:04:51 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1EmdEHCFAG/ea_profile.json * 2024-06-29 02:04:54 (5904) [INFO] Backed up EA4 profile to /tmp/1EmdEHCFAG/ea_profile.json * 2024-06-29 02:04:54 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-29 02:05:28 (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 02:05:28 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-30 01:55:56 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-30 01:59:56 (7994) [INFO] Script is up to date. * 2024-06-30 02:03:59 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-06-30 02:03:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-06-30 02:03:59 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-30 02:03:59 (6738) [INFO] * 2024-06-30 02:04:09 (6751) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-06-30 02:04:10 (6768) [INFO] * 2024-06-30 02:04:12 (726) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-06-30 02:04:12 (733) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:07:32 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-06-30 02:07:32 (207) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-06-30 02:07:32 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-06-30 02:07:32 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-06-30 02:07:32 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-30 02:07:39 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/D4_plhf18K/ea_profile.json * 2024-06-30 02:07:41 (5904) [INFO] Backed up EA4 profile to /tmp/D4_plhf18K/ea_profile.json * 2024-06-30 02:07:42 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-06-30 02:08:16 (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 02:08:16 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-01 01:53:57 (7972) [INFO] Self-update of script version 43 requested. * 2024-07-01 01:57:57 (7994) [INFO] Script is up to date. * 2024-07-01 02:02:00 (2235) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-01 02:02:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-01 02:02:00 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-01 02:02:00 (6738) [INFO] * 2024-07-01 02:02:10 (6751) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-01 02:02:11 (6768) [INFO] * 2024-07-01 02:02:13 (726) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-01 02:02:13 (733) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:27 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-01 02:05:27 (207) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-01 02:05:27 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-01 02:05:27 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-01 02:05:27 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-01 02:05:35 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eCd_42HMoZ/ea_profile.json * 2024-07-01 02:05:38 (5904) [INFO] Backed up EA4 profile to /tmp/eCd_42HMoZ/ea_profile.json * 2024-07-01 02:05:39 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-01 02:06:13 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported. If you proceed with this upgrade, we will switch your system to use the Let's Encrypt™ provider. * 2024-07-01 02:06:13 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-02 01:46:04 (7972) [INFO] Self-update of script version 43 requested. * 2024-07-02 01:50:04 (7977) [INFO] Newer version of script found. Downloading. * 2024-07-02 01:54:06 (7986) [INFO] Script update to version 44 successful. * 2024-07-02 01:58:09 (2236) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-02 01:58:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-02 01:58:09 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-02 01:58:09 (6800) [INFO] * 2024-07-02 01:58:20 (6813) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-02 01:58:20 (6830) [INFO] * 2024-07-02 01:58:22 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-02 01:58:22 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:15:28 (1986) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30801 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30846 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30901 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-07-02 02:15:28 (1987) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-02 02:15:28 (6799) [INFO] Running: /usr/bin/yum clean all * 2024-07-02 02:15:28 (6800) [INFO] * 2024-07-02 02:15:29 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-02 02:15:29 (6813) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 10224. * 2024-07-02 02:15:29 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:29 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:29 (6813) [INFO] Memory : 58 M RSS (385 MB VSZ) * 2024-07-02 02:15:29 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:23 ago * 2024-07-02 02:15:29 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:31 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:31 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:31 (6813) [INFO] Memory : 77 M RSS (405 MB VSZ) * 2024-07-02 02:15:31 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:25 ago * 2024-07-02 02:15:31 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:33 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:33 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:33 (6813) [INFO] Memory : 82 M RSS (409 MB VSZ) * 2024-07-02 02:15:33 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:27 ago * 2024-07-02 02:15:33 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:35 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:35 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:35 (6813) [INFO] Memory : 85 M RSS (412 MB VSZ) * 2024-07-02 02:15:35 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:29 ago * 2024-07-02 02:15:35 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:37 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:37 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:37 (6813) [INFO] Memory : 89 M RSS (417 MB VSZ) * 2024-07-02 02:15:37 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:31 ago * 2024-07-02 02:15:37 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:39 (6813) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-07-02 02:15:39 (6813) [INFO] The other application is: yum * 2024-07-02 02:15:39 (6813) [INFO] Memory : 97 M RSS (424 MB VSZ) * 2024-07-02 02:15:39 (6813) [INFO] Started: Tue Jul 2 02:11:06 2024 - 04:33 ago * 2024-07-02 02:15:39 (6813) [INFO] State : Running, pid: 10224 * 2024-07-02 02:15:41 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-02 02:15:41 (6813) [INFO] : epel extras imunify360 imunify360-ea-php-hardened * 2024-07-02 02:15:41 (6813) [INFO] : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3 * 2024-07-02 02:15:41 (6813) [INFO] : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6 * 2024-07-02 02:15:41 (6813) [INFO] : imunify360-rollout-7 imunify360-rollout-8 updates * 2024-07-02 02:15:41 (6813) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-02 02:15:42 (6813) [INFO] Cleaning up list of fastest mirrors * 2024-07-02 02:15:42 (6813) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-02 02:15:42 (6830) [INFO] * 2024-07-03 02:08:15 (8035) [INFO] Self-update of script version 44 requested. * 2024-07-03 02:12:16 (8057) [INFO] Script is up to date. * 2024-07-03 02:16:19 (2236) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-03 02:16:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-03 02:16:19 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-03 02:16:19 (6800) [INFO] * 2024-07-03 02:16:22 (6813) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-03 02:16:22 (6830) [INFO] * 2024-07-03 02:16:24 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-03 02:16:24 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:16:28 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-03 02:23:47 (1986) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate." Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-03 02:23:47 (1987) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-03 02:23:47 (6799) [INFO] Running: /usr/bin/yum clean all * 2024-07-03 02:23:47 (6800) [INFO] * 2024-07-03 02:23:48 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-03 02:23:48 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-03 02:23:48 (6813) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-03 02:23:48 (6813) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-03 02:23:48 (6813) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-03 02:23:48 (6813) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-03 02:23:48 (6813) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-03 02:23:48 (6813) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-03 02:23:48 (6813) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-03 02:23:48 (6813) [INFO] : wp-toolkit-thirdparties * 2024-07-03 02:23:49 (6813) [INFO] Cleaning up list of fastest mirrors * 2024-07-03 02:23:49 (6813) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-07-03 02:23:49 (6830) [INFO] * 2024-07-04 01:45:32 (8035) [INFO] Self-update of script version 44 requested. * 2024-07-04 01:49:32 (8040) [INFO] Newer version of script found. Downloading. * 2024-07-04 01:53:34 (8049) [INFO] Script update to version 45 successful. * 2024-07-04 01:57:37 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-04 01:57:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-04 01:57:37 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-04 01:57:37 (6814) [INFO] * 2024-07-04 01:57:48 (6827) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-04 01:57:49 (6844) [INFO] * 2024-07-04 01:57:50 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-04 01:57:50 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-04 01:57:55 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-04 01:57:55 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-04 01:57:55 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-04 01:57:55 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-04 01:57:55 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-04 01:57:55 (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 02:00:00 (1999) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-07-04 02:00:00 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-04 02:00:00 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-04 02:00:00 (6814) [INFO] * 2024-07-04 02:00:01 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-04 02:00:01 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-04 02:00:01 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-04 02:00:01 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-04 02:00:01 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-04 02:00:01 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-04 02:00:01 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-04 02:00:01 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-04 02:00:01 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-04 02:00:01 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-04 02:00:01 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-04 02:00:01 (6827) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2024-07-04 02:00:01 (6844) [INFO] * 2024-07-04 02:02:52 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-04 02:02:52 (2010) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-07-04 02:02:53 (1544) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-04 02:02:53 (208) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-04 02:02:53 (1642) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-04 02:02:53 (1648) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-04 02:02:53 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-04 02:03:00 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/vYrOGcU6ti/ea_profile.json * 2024-07-04 02:06:03 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/vYrOGcU6ti/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-04 02:06:03 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-05 01:44:37 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-05 01:48:38 (8071) [INFO] Script is up to date. * 2024-07-05 01:52:41 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-05 01:52:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-05 01:52:41 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-05 01:52:41 (6814) [INFO] * 2024-07-05 02:03:35 (6827) [INFO] {"items": "7.13.7", "strategy": "CSF_COOP", "warnings": [], "version": "7.13.7", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-05 02:03:35 (6844) [INFO] * 2024-07-05 02:03:37 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-05 02:03:37 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:03:42 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-05 02:05:45 (1999) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzE5NzYyNjIxOjE3MjAwMjE4MjE6TTbrPVHggruUJW35SH-UWUApc4xMXvc25G7BOlnHI0ywSZUdkfl6tdHe9fZsQmvjMsAmYtgoOaTnH8LT0sCsI4mbiXcKx4y21IeMctIWQluWUOvjA27NB0eoVvmYhE6Rrg1jjPt7vVUiBcZQmQgIGZDRUOF_qraI88wJSKGdJuiStW-HgCBL93PFtcrTTiCFFcrPn3XcuwSzISqN7oMqxSBvj8dgekyVm8lffRtRjXNC2dJ_CTv7lYzefROZjhq6dv02w7qJkqijvnTgFyUDPpt8koPBxonAV1yHnv_l66bY7TfdxAkmH3CfhXAhm8KYEmk_Rp_9mgBY3TYD6LB0vrJNfdk4C8kxCbWMg4Tqt6NryyaJ2Up9kPyGXIxyGJJ4OBDU2FQaGxTq1K3uDGwiCnh-hEArOwhblWaXtEc7G6tKGgjLLqo4dtqYFdyNnNWq1iqschw_dpbeauNswwBxE_9DjG4JbVQy1rtGO0cA3mdatfN4F3PTQ0WY3KSQs0rAgfB_8PXqNl9N8g-Qi5GA9LBfeT9ZyBaHRDqsY4f-fXrt85vmRcAoQGKaW7z7PdQKJrt-vpx93bayG2LOixwt5Kw6i4IBeng454_PXXlc6h2V3G4lGM3sW1y1PfI-VSCzBGhbDWY_BEt96kGyuuLompSJjwLPLTtyX1jOUV3VMz4=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-07-05 02:05:45 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-05 02:05:45 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-05 02:05:45 (6814) [INFO] * 2024-07-05 02:05:46 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-05 02:05:46 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-05 02:05:46 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-05 02:05:46 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-05 02:05:46 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-05 02:05:46 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-05 02:05:46 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-05 02:05:46 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-05 02:05:46 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-05 02:05:46 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-05 02:05:46 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-05 02:05:46 (6827) [INFO] Other repos take up 968 k of disk space (use --verbose for details) * 2024-07-05 02:05:46 (6844) [INFO] * 2024-07-05 02:06:18 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-05 02:06:18 (2010) [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 * 2024-07-05 02:06:19 (1544) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-05 02:06:19 (208) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-05 02:06:19 (1642) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-05 02:06:19 (1648) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-05 02:06:19 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-05 02:06:27 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NP7m6_m1CO/ea_profile.json * 2024-07-05 02:09:45 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NP7m6_m1CO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-05 02:09:45 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-06 02:01:42 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-06 02:05:43 (8071) [INFO] Script is up to date. * 2024-07-06 02:09:46 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-06 02:09:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-06 02:09:46 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-06 02:09:46 (6814) [INFO] * 2024-07-07 01:57:25 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-07 02:01:25 (8071) [INFO] Script is up to date. * 2024-07-07 02:05:28 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-07 02:05:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-07 02:05:29 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-07 02:05:29 (6814) [INFO] * 2024-07-07 02:05:40 (6827) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-07 02:05:40 (6844) [INFO] * 2024-07-07 02:05:42 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-07 02:05:42 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05: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-07 02:05: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-07 02:05: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-07 02:05: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-07 02:05: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-07 02:05: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-07 02:12:35 (1999) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-07 02:12:35 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-07 02:12:35 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-07 02:12:35 (6814) [INFO] * 2024-07-07 02:12:36 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-07 02:12:36 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-07 02:12:36 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-07 02:12:36 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-07 02:12:36 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-07 02:12:36 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-07 02:12:36 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-07 02:12:36 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-07 02:12:36 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-07 02:12:36 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-07 02:12:37 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-07 02:12:37 (6827) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-07 02:12:37 (6844) [INFO] * 2024-07-08 02:10:00 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-08 02:14:01 (8071) [INFO] Script is up to date. * 2024-07-08 02:18:04 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-08 02:18:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-08 02:18:04 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-08 02:18:04 (6814) [INFO] * 2024-07-08 02:18:14 (6827) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-08 02:18:14 (6844) [INFO] * 2024-07-08 02:18:16 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-08 02:18:16 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:18:21 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation * 2024-07-08 02:23:49 (1999) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-08 02:23:49 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-08 02:23:49 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-08 02:23:49 (6814) [INFO] * 2024-07-08 02:23:50 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-08 02:23:50 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-08 02:23:50 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-08 02:23:50 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-08 02:23:50 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-08 02:23:50 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-08 02:23:50 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-08 02:23:50 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-08 02:23:50 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-08 02:23:50 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-08 02:23:51 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-08 02:23:51 (6827) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-08 02:23:51 (6844) [INFO] * 2024-07-09 01:54:11 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-09 01:58:11 (8071) [INFO] Script is up to date. * 2024-07-09 02:02:14 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-09 02:02:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-09 02:02:14 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-09 02:02:14 (6814) [INFO] * 2024-07-09 02:02:25 (6827) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-09 02:02:25 (6844) [INFO] * 2024-07-09 02:02:27 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-09 02:02:27 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:02:31 (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 02:02:31 (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 02:02:31 (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 02:02:31 (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 02:02:31 (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 02:02:31 (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 02:08:35 (1999) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-09 02:08:35 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-09 02:08:35 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-09 02:08:35 (6814) [INFO] * 2024-07-09 02:08:36 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-09 02:08:36 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-09 02:08:36 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-09 02:08:36 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-09 02:08:36 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-09 02:08:36 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-09 02:08:36 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-09 02:08:36 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-09 02:08:36 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-09 02:08:36 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-09 02:08:37 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-09 02:08:37 (6827) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-09 02:08:37 (6844) [INFO] * 2024-07-10 02:08:51 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-10 02:12:52 (8071) [INFO] Script is up to date. * 2024-07-10 02:16:55 (2249) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-10 02:16:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-10 02:16:55 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-10 02:16:55 (6814) [INFO] * 2024-07-10 02:17:06 (6827) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-10 02:17:06 (6844) [INFO] * 2024-07-10 02:17:08 (727) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-10 02:17:08 (734) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:17:11 (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 02:17:11 (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 02:17:11 (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 02:17:11 (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 02:17:11 (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 02:17:11 (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 02:23:47 (1999) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-10 02:23:47 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-10 02:23:47 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-10 02:23:47 (6814) [INFO] * 2024-07-10 02:23:48 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-10 02:23:48 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-10 02:23:48 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-10 02:23:48 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-10 02:23:48 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-10 02:23:48 (6827) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-10 02:23:48 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-10 02:23:48 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-10 02:23:48 (6827) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-10 02:23:48 (6827) [INFO] : wp-toolkit-thirdparties * 2024-07-10 02:23:49 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-10 02:23:49 (6827) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-10 02:23:49 (6844) [INFO] * 2024-07-10 02:37:43 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-10 02:37:43 (2010) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-10 02:37:44 (1544) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-10 02:37:44 (208) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-10 02:37:44 (1642) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-10 02:37:44 (1648) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-10 02:37:44 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-10 02:37:58 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/RhEFJp5heX/ea_profile.json * 2024-07-10 02:38:00 (5980) [INFO] Backed up EA4 profile to /tmp/RhEFJp5heX/ea_profile.json * 2024-07-10 02:38:01 (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-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-10 02:38:35 (2546) [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-10 02:38:35 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-11 02:09:39 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-11 02:13:39 (8054) [INFO] Newer version of script found. Downloading. * 2024-07-11 02:17:41 (8063) [INFO] Script update to version 46 successful. * 2024-07-11 02:21:44 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-11 02:21:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-11 02:21:44 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-11 02:21:44 (6847) [INFO] * 2024-07-11 02:21:53 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-11 02:21:54 (6877) [INFO] * 2024-07-11 02:21:56 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-11 02:21:56 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:21:56 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-11 02:21:56 (6847) [INFO] * 2024-07-11 02:22:11 (6877) [INFO] * 2024-07-11 02:22:11 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-11 02:22:15 (2139) [ERROR] 75 package(s) installed from unsupported YUM repo 'jetapps' from /etc/yum.repos.d/jetapps.repo * 2024-07-11 02:22:15 (2139) [ERROR] 2 package(s) installed from unsupported YUM repo 'jetapps-stable' from /etc/yum.repos.d/jetapps.repo * 2024-07-11 02:28:17 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-11 02:28:17 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-11 02:28:17 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-11 02:28:17 (6847) [INFO] * 2024-07-11 02:28:17 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-11 02:28:17 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-11 02:28:17 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-11 02:28:17 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-11 02:28:17 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-11 02:28:17 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-11 02:28:17 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-11 02:28:17 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-11 02:28:17 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-11 02:28:17 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-11 02:28:18 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-11 02:28:18 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-11 02:28:18 (6877) [INFO] * 2024-07-12 02:13:49 (8126) [INFO] Self-update of script version 46 requested. * 2024-07-12 02:17:50 (8131) [INFO] Newer version of script found. Downloading. * 2024-07-12 02:21:51 (8140) [INFO] Script update to version 47 successful. * 2024-07-12 02:25:54 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-12 02:25:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-12 02:25:55 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-12 02:25:55 (6849) [INFO] * 2024-07-12 02:26:05 (6862) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-12 02:26:05 (6879) [INFO] * 2024-07-12 02:26:07 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-12 02:26:07 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:26:07 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-12 02:26:07 (6849) [INFO] * 2024-07-12 02:26:21 (6879) [INFO] * 2024-07-12 02:26:21 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-12 02:32:26 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2024-07-12 02:32:26 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-12 02:32:26 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-12 02:32:26 (6849) [INFO] * 2024-07-12 02:32:27 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-12 02:32:27 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-12 02:32:27 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-12 02:32:27 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-12 02:32:27 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-12 02:32:27 (6862) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-12 02:32:27 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-12 02:32:27 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-12 02:32:27 (6862) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-12 02:32:27 (6862) [INFO] : wp-toolkit-thirdparties * 2024-07-12 02:32:28 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-12 02:32:28 (6862) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-12 02:32:28 (6879) [INFO] * 2024-07-13 02:03:05 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-13 02:07:06 (8150) [INFO] Script is up to date. * 2024-07-13 02:11:09 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-13 02:11:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-13 02:11:09 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-13 02:11:09 (6849) [INFO] * 2024-07-13 02:11:20 (6862) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-13 02:11:21 (6879) [INFO] * 2024-07-13 02:11:22 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-13 02:11:22 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:11:22 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-13 02:11:22 (6849) [INFO] * 2024-07-13 02:11:36 (6879) [INFO] * 2024-07-13 02:11:36 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-13 02:17:52 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2024-07-13 02:17:52 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-13 02:17:52 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-13 02:17:52 (6849) [INFO] * 2024-07-13 02:17:53 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-13 02:17:53 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-13 02:17:53 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-13 02:17:53 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-13 02:17:53 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-13 02:17:53 (6862) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-13 02:17:53 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-13 02:17:53 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-13 02:17:53 (6862) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-13 02:17:53 (6862) [INFO] : wp-toolkit-thirdparties * 2024-07-13 02:17:54 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-13 02:17:54 (6862) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-13 02:17:54 (6879) [INFO] * 2024-07-13 02:18:26 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-07-13 02:18:26 (2036) [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 * 2024-07-13 02:18:27 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-13 02:18:27 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-13 02:18:27 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-13 02:18:27 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-13 02:18:27 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-13 02:24:13 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/T_SFjU8cUn/ea_profile.json * 2024-07-13 02:29:50 (6013) [INFO] Backed up EA4 profile to /tmp/T_SFjU8cUn/ea_profile.json * 2024-07-13 02:29:51 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-13 02:30:24 (2575) [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-13 02:30:24 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-14 01:56:37 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-14 02:00:37 (8150) [INFO] Script is up to date. * 2024-07-14 02:04:40 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-14 02:04:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-14 02:04:40 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-14 02:04:40 (6849) [INFO] * 2024-07-14 02:04:51 (6862) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-14 02:04:52 (6879) [INFO] * 2024-07-14 02:04:54 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-14 02:04:54 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:04:54 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-14 02:04:54 (6849) [INFO] * 2024-07-14 02:05:09 (6879) [INFO] * 2024-07-14 02:05:09 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-14 02:11:25 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-14 02:11:25 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-14 02:11:25 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-14 02:11:25 (6849) [INFO] * 2024-07-14 02:11:26 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-14 02:11:26 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-14 02:11:26 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-14 02:11:26 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-14 02:11:26 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-14 02:11:26 (6862) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-14 02:11:26 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-14 02:11:26 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-14 02:11:26 (6862) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-14 02:11:26 (6862) [INFO] : wp-toolkit-thirdparties * 2024-07-14 02:11:26 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-14 02:11:26 (6862) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-14 02:11:26 (6879) [INFO] * 2024-07-14 02:25:23 (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 02:25:23 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-07-14 02:25:24 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-14 02:25:24 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-14 02:25:24 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-14 02:25:24 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-14 02:25:24 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-14 02:25:38 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/73y6Cwb31Q/ea_profile.json * 2024-07-14 02:25:41 (6013) [INFO] Backed up EA4 profile to /tmp/73y6Cwb31Q/ea_profile.json * 2024-07-14 02:25:41 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-14 02:26:16 (2575) [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-14 02:26:16 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-15 02:11:29 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-15 02:15:29 (8150) [INFO] Script is up to date. * 2024-07-15 02:19:32 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-15 02:19:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-15 02:19:32 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-15 02:19:32 (6849) [INFO] * 2024-07-15 02:19:43 (6862) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-15 02:19:43 (6879) [INFO] * 2024-07-15 02:19:45 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-15 02:19:45 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:19:45 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-15 02:19:45 (6849) [INFO] * 2024-07-15 02:19:55 (6879) [INFO] * 2024-07-15 02:19:55 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-15 02:25:11 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30833 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-15 02:25:11 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-15 02:25:11 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-15 02:25:11 (6849) [INFO] * 2024-07-15 02:25:12 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-15 02:25:12 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-15 02:25:12 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-15 02:25:12 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-15 02:25:12 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-15 02:25:12 (6862) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-15 02:25:12 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-15 02:25:12 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-15 02:25:12 (6862) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-15 02:25:12 (6862) [INFO] : wp-toolkit-thirdparties * 2024-07-15 02:25:13 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-15 02:25:13 (6862) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-15 02:25:13 (6879) [INFO] * 2024-07-15 02:40:08 (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 02:40:08 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-15 02:40:09 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-15 02:40:09 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-15 02:40:09 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-15 02:40:09 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-15 02:40:09 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-15 02:40:22 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mgYUUQ60Og/ea_profile.json * 2024-07-15 02:40:25 (6013) [INFO] Backed up EA4 profile to /tmp/mgYUUQ60Og/ea_profile.json * 2024-07-15 02:40:26 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-15 02:41:00 (2575) [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-15 02:41:00 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-16 02:01:11 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-16 02:05:11 (8150) [INFO] Script is up to date. * 2024-07-16 02:09:15 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-16 02:09:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-16 02:09:15 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-16 02:09:15 (6849) [INFO] * 2024-07-16 02:09:25 (6862) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-16 02:09:26 (6879) [INFO] * 2024-07-16 02:09:28 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-16 02:09:28 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:28 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-16 02:09:28 (6849) [INFO] * 2024-07-16 02:09:44 (6879) [INFO] * 2024-07-16 02:09:44 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-16 02:14:46 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. * 2024-07-16 02:14:46 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-16 02:14:46 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-16 02:14:46 (6849) [INFO] * 2024-07-16 02:14:46 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-16 02:14:46 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-16 02:14:46 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-16 02:14:46 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-16 02:14:46 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-16 02:14:46 (6862) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-16 02:14:46 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-16 02:14:46 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-16 02:14:46 (6862) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-16 02:14:46 (6862) [INFO] : wp-toolkit-thirdparties * 2024-07-16 02:14:47 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-16 02:14:47 (6862) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-16 02:14:47 (6879) [INFO] * 2024-07-16 02:29:45 (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 02:29:45 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-16 02:29:46 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-16 02:29:46 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-16 02:29:46 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-16 02:29:46 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-16 02:29:46 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-16 02:29:59 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/PW8IkBbZxG/ea_profile.json * 2024-07-16 02:30:02 (6013) [INFO] Backed up EA4 profile to /tmp/PW8IkBbZxG/ea_profile.json * 2024-07-16 02:30:03 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-16 02:30:38 (2575) [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-16 02:30:38 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-17 02:12:02 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-17 02:16:03 (8133) [INFO] Newer version of script found. Downloading. * 2024-07-17 02:20:04 (8142) [INFO] Script update to version 48 successful. * 2024-07-17 02:24:07 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-17 02:24:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-17 02:24:07 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-17 02:24:07 (6847) [INFO] * 2024-07-17 02:24:18 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-17 02:24:18 (6877) [INFO] * 2024-07-17 02:24:20 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-17 02:24:20 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:24:20 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-17 02:24:20 (6847) [INFO] * 2024-07-17 02:24:52 (6877) [INFO] * 2024-07-17 02:24:52 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-17 02:30:41 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30532 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2024-07-17 02:30:41 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-17 02:30:41 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-17 02:30:41 (6847) [INFO] * 2024-07-17 02:30:42 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-17 02:30:42 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-17 02:30:42 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-17 02:30:42 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-17 02:30:42 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-17 02:30:42 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-17 02:30:42 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-17 02:30:42 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-17 02:30:42 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-17 02:30:42 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-17 02:30:43 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-17 02:30:43 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-17 02:30:43 (6877) [INFO] * 2024-07-18 02:11:48 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-18 02:15:48 (8148) [INFO] Script is up to date. * 2024-07-18 02:19:51 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-18 02:19:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-18 02:19:51 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-18 02:19:51 (6847) [INFO] * 2024-07-18 02:20:00 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-18 02:20:01 (6877) [INFO] * 2024-07-18 02:20:03 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-18 02:20:03 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:20:03 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-18 02:20:03 (6847) [INFO] * 2024-07-18 02:20:22 (6877) [INFO] * 2024-07-18 02:20:22 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-18 02:25:39 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-07-18 02:25:39 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-18 02:25:39 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-18 02:25:39 (6847) [INFO] * 2024-07-18 02:25:39 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-18 02:25:40 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-18 02:25:40 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-18 02:25:40 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-18 02:25:40 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-18 02:25:40 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-18 02:25:40 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-18 02:25:40 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-18 02:25:40 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-18 02:25:40 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-18 02:25:40 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-18 02:25:40 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-18 02:25:40 (6877) [INFO] * 2024-07-18 02:39:31 (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 02:39:31 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-18 02:39:32 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-18 02:39:32 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-18 02:39:32 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-18 02:39:32 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-18 02:39:32 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-18 02:39:46 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XQp98dR9cd/ea_profile.json * 2024-07-18 02:39:49 (6011) [INFO] Backed up EA4 profile to /tmp/XQp98dR9cd/ea_profile.json * 2024-07-18 02:39:50 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-18 02:40:24 (2575) [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-18 02:40:24 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-19 02:07:25 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-19 02:11:26 (8148) [INFO] Script is up to date. * 2024-07-19 02:15:29 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-19 02:15:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-19 02:15:29 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-19 02:15:29 (6847) [INFO] * 2024-07-19 02:15:41 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-19 02:15:41 (6877) [INFO] * 2024-07-19 02:15:43 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-19 02:15:43 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:15:43 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-19 02:15:43 (6847) [INFO] * 2024-07-19 02:15:49 (6877) [INFO] * 2024-07-19 02:24:54 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-19 02:24:54 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-19 02:24:54 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-19 02:24:54 (6847) [INFO] * 2024-07-19 02:24:54 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-19 02:24:55 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-19 02:24:55 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-19 02:24:55 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-19 02:24:55 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-19 02:24:55 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-19 02:24:55 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-19 02:24:55 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-19 02:24:55 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-19 02:24:55 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-19 02:24:55 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-19 02:24:55 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-19 02:24:55 (6877) [INFO] * 2024-07-19 02:36:26 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-07-19 02:36:26 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-19 02:36:27 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-19 02:36:27 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-19 02:36:27 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-19 02:36:27 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-19 02:36:27 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-19 02:36:41 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eEuFL659aZ/ea_profile.json * 2024-07-19 02:36:44 (6011) [INFO] Backed up EA4 profile to /tmp/eEuFL659aZ/ea_profile.json * 2024-07-19 02:36:44 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-20 02:04:51 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-20 02:08:52 (8148) [INFO] Script is up to date. * 2024-07-20 02:12:55 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-20 02:12:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-20 02:12:55 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-20 02:12:55 (6847) [INFO] * 2024-07-20 02:13:06 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-20 02:13:06 (6877) [INFO] * 2024-07-20 02:13:08 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-20 02:13:08 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:13:08 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-20 02:13:08 (6847) [INFO] * 2024-07-20 02:13:23 (6877) [INFO] * 2024-07-20 02:13:23 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-20 02:18:56 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30723 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-20 02:18:56 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-20 02:18:56 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-20 02:18:56 (6847) [INFO] * 2024-07-20 02:18:57 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-20 02:18:57 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-20 02:18:57 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-20 02:18:57 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-20 02:18:57 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-20 02:18:57 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-20 02:18:57 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-20 02:18:57 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-20 02:18:57 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-20 02:18:57 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-20 02:18:58 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-20 02:18:58 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-20 02:18:58 (6877) [INFO] * 2024-07-20 02:33: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-20 02:33:01 (2036) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30723 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-07-20 02:33:01 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-20 02:33:01 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-20 02:33:01 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-20 02:33:01 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-20 02:33:01 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-20 02:33:15 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8EVP04OBph/ea_profile.json * 2024-07-20 02:33:18 (6011) [INFO] Backed up EA4 profile to /tmp/8EVP04OBph/ea_profile.json * 2024-07-20 02:33:18 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-20 02:33:52 (2575) [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-20 02:33:52 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-21 01:46:44 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-21 01:50:44 (8148) [INFO] Script is up to date. * 2024-07-21 01:54:47 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-21 01:54:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-21 01:54:48 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-21 01:54:48 (6847) [INFO] * 2024-07-21 01:54:59 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-21 01:54:59 (6877) [INFO] * 2024-07-21 01:55:01 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-21 01:55:01 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-21 01:55:01 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-21 01:55:01 (6847) [INFO] * 2024-07-21 01:55:15 (6877) [INFO] * 2024-07-21 01:55:15 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-21 02:04:18 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-21 02:04:18 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-21 02:04:18 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-21 02:04:18 (6847) [INFO] * 2024-07-21 02:04:19 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-21 02:04:19 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-21 02:04:19 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-21 02:04:19 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-21 02:04:19 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-21 02:04:19 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-21 02:04:19 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-21 02:04:19 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-21 02:04:19 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-21 02:04:19 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-21 02:04:20 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-21 02:04:20 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-21 02:04:20 (6877) [INFO] * 2024-07-22 01:50:05 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-22 01:54:06 (8148) [INFO] Script is up to date. * 2024-07-22 01:58:09 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-22 01:58:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-22 01:58:09 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-22 01:58:09 (6847) [INFO] * 2024-07-22 01:58:20 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-22 01:58:20 (6877) [INFO] * 2024-07-22 01:58:22 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-22 01:58:22 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-22 01:58:22 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-22 01:58:22 (6847) [INFO] * 2024-07-22 01:58:35 (6877) [INFO] * 2024-07-22 01:58:35 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-22 02:14:34 (2025) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.2/wp-toolkit/repodata/repomd.xml: [Errno 12] Timeout on https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.2/wp-toolkit/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.2/wp-toolkit/repodata/repomd.xml: [Errno 12] Timeout on https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.2/wp-toolkit/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30933 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') 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 extras: Check uncompressed DB failed * 2024-07-22 02:14:34 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-22 02:14:34 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-22 02:14:34 (6847) [INFO] * 2024-07-22 02:14:34 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-22 02:14:35 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-22 02:14:35 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-22 02:14:35 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-22 02:14:35 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-22 02:14:35 (6860) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-22 02:14:35 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-22 02:14:35 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-22 02:14:35 (6860) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-22 02:14:35 (6860) [INFO] : wp-toolkit-thirdparties * 2024-07-22 02:14:36 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-22 02:14:36 (6860) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-22 02:14:36 (6877) [INFO] * 2024-07-23 01:47:42 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-23 01:51:43 (8148) [INFO] Script is up to date. * 2024-07-23 01:55:45 (2278) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-23 01:55:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-23 01:55:45 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-23 01:55:45 (6847) [INFO] * 2024-07-23 01:55:56 (6860) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-23 01:55:57 (6877) [INFO] * 2024-07-23 01:55:59 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-23 01:55:59 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-23 01:55:59 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-23 01:55:59 (6847) [INFO] * 2024-07-23 02:08:57 (6877) [INFO] * 2024-07-23 02:08:57 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-24 02:05:41 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-24 02:09:42 (8131) [INFO] Newer version of script found. Downloading. * 2024-07-24 02:13:43 (8140) [INFO] Script update to version 49 successful. * 2024-07-24 02:17:46 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-24 02:17:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-24 02:17:46 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-24 02:17:46 (6908) [INFO] * 2024-07-24 02:17:58 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-24 02:17:59 (6938) [INFO] * 2024-07-24 02:18:01 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-24 02:18:01 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:18:01 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-24 02:18:01 (6908) [INFO] * 2024-07-24 02:18:10 (6938) [INFO] * 2024-07-24 02:18:10 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-24 02:21:20 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-24 02:21:20 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-24 02:21:20 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-24 02:21:20 (6908) [INFO] * 2024-07-24 02:21:20 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-24 02:21:21 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-24 02:21:21 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-24 02:21:21 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-24 02:21:21 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-24 02:21:21 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-24 02:21:21 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-24 02:21:21 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-24 02:21:21 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-24 02:21:21 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-24 02:21:21 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-24 02:21:22 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-24 02:21:22 (6938) [INFO] * 2024-07-24 02:34: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-24 02:34:53 (2058) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30724 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-07-24 02:34:54 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-24 02:34:54 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-24 02:34:54 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-24 02:34:54 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-24 02:34:54 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-24 02:35:08 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/36g5sytWOL/ea_profile.json * 2024-07-24 02:35:10 (6072) [INFO] Backed up EA4 profile to /tmp/36g5sytWOL/ea_profile.json * 2024-07-24 02:35:11 (214) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-07-25 01:45:43 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-25 01:49:44 (8209) [INFO] Script is up to date. * 2024-07-25 01:53:47 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-25 01:53:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-25 01:53:47 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-25 01:53:47 (6908) [INFO] * 2024-07-25 01:53:59 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-25 01:53:59 (6938) [INFO] * 2024-07-25 01:54:01 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-25 01:54:01 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-25 01:54:01 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-25 01:54:01 (6908) [INFO] * 2024-07-25 01:54:15 (6938) [INFO] * 2024-07-25 01:54:15 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-25 02:09:22 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30798 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30832 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') 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 updates: Check uncompressed DB failed * 2024-07-25 02:09:22 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-25 02:09:22 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-25 02:09:22 (6908) [INFO] * 2024-07-25 02:09:23 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-25 02:09:23 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-25 02:09:23 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-25 02:09:23 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-25 02:09:23 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-25 02:09:23 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-25 02:09:23 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-25 02:09:23 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-25 02:09:23 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-25 02:09:23 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-25 02:09:24 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-25 02:09:24 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-25 02:09:24 (6938) [INFO] * 2024-07-26 02:48:45 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-26 02:52:46 (8209) [INFO] Script is up to date. * 2024-07-26 02:56:49 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-26 02:56:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-26 02:56:49 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-26 02:56:49 (6908) [INFO] * 2024-07-26 02:57:00 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-26 02:57:00 (6938) [INFO] * 2024-07-26 02:57:02 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-26 02:57:02 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:57:02 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-26 02:57:02 (6908) [INFO] * 2024-07-26 02:57:10 (6938) [INFO] * 2024-07-26 02:59:16 (2047) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzIxNjM3MzQxOjE3MjE4OTY1NDE6pKJOiof27iCg47j50ZcdYRCRFI6NIfa2e2iClIA3usI5HSBAE_E3jcSVACGVxv4ZzDvYCMAlpEA4f8XiRWK2U6McMflzA2eYrlwy7Schc3OUfepCY0WMUWDbjdXcL6Dm_sywNGf15qlTGwrSI7x-6_oySswEy5uyTONccxWWeB8RM2hV05m3CRmBI-7lv1wHpZqlG2QJL5zoZUjsJKTxuySDPeE8ApuKrppszf_3pGj7h4YuJp0w6agWVR4eXmsSFbOrxoUrUuq4LV5VAK5GdcMPRSFS6qgTBA_3TUA_qjHEH7bH2TiBTB7OV4JusBexsAH2nOaYcF0UE05YHlNRQfwKolM26GXERq89Eby3DZT0tpoP9d2wxMGB0R06X-ofj_iZY2ECYX-H3p0cTtU1_FD0PCNwrPPsLtg1NidLXjZ0sPliiuM9fSIikymy2SLum4EntDAio6KaAfc51nZFZTCEHPtzPI9zbLK85ZM69S-47cXGJGC2liaUeg5BCrNoAiublklVAOnNujpjytodluJwSYVjBdBPIsptG-v1km8y59B4hrtTLBXp9k5-jus_8Knsb9uizU5vCU-eLitbwrkyAwpnvSHH3IXJuomIlDoPNT7o0gZRAcsFt4DhVwRiNfKgoIyAAMOc-JGxOISuMV4A2Fb6SZg0_Uq-qaMqK5A%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzIxNjM3MzQxOjE3MjE4OTY1NDE6pKJOiof27iCg47j50ZcdYRCRFI6NIfa2e2iClIA3usI5HSBAE_E3jcSVACGVxv4ZzDvYCMAlpEA4f8XiRWK2U6McMflzA2eYrlwy7Schc3OUfepCY0WMUWDbjdXcL6Dm_sywNGf15qlTGwrSI7x-6_oySswEy5uyTONccxWWeB8RM2hV05m3CRmBI-7lv1wHpZqlG2QJL5zoZUjsJKTxuySDPeE8ApuKrppszf_3pGj7h4YuJp0w6agWVR4eXmsSFbOrxoUrUuq4LV5VAK5GdcMPRSFS6qgTBA_3TUA_qjHEH7bH2TiBTB7OV4JusBexsAH2nOaYcF0UE05YHlNRQfwKolM26GXERq89Eby3DZT0tpoP9d2wxMGB0R06X-ofj_iZY2ECYX-H3p0cTtU1_FD0PCNwrPPsLtg1NidLXjZ0sPliiuM9fSIikymy2SLum4EntDAio6KaAfc51nZFZTCEHPtzPI9zbLK85ZM69S-47cXGJGC2liaUeg5BCrNoAiublklVAOnNujpjytodluJwSYVjBdBPIsptG-v1km8y59B4hrtTLBXp9k5-jus_8Knsb9uizU5vCU-eLitbwrkyAwpnvSHH3IXJuomIlDoPNT7o0gZRAcsFt4DhVwRiNfKgoIyAAMOc-JGxOISuMV4A2Fb6SZg0_Uq-qaMqK5A=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-07-26 02:59:16 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-26 02:59:16 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-26 02:59:16 (6908) [INFO] * 2024-07-26 02:59:17 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-26 02:59:17 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-26 02:59:17 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-26 02:59:17 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-26 02:59:17 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-26 02:59:17 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-26 02:59:17 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-26 02:59:17 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-26 02:59:17 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-26 02:59:17 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-26 02:59:17 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-26 02:59:17 (6921) [INFO] Other repos take up 968 k of disk space (use --verbose for details) * 2024-07-26 02:59:17 (6938) [INFO] * 2024-07-26 03:02: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-26 03:02:42 (2058) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzIxNjM3MzQxOjE3MjE4OTY1NDE6pKJOiof27iCg47j50ZcdYRCRFI6NIfa2e2iClIA3usI5HSBAE_E3jcSVACGVxv4ZzDvYCMAlpEA4f8XiRWK2U6McMflzA2eYrlwy7Schc3OUfepCY0WMUWDbjdXcL6Dm_sywNGf15qlTGwrSI7x-6_oySswEy5uyTONccxWWeB8RM2hV05m3CRmBI-7lv1wHpZqlG2QJL5zoZUjsJKTxuySDPeE8ApuKrppszf_3pGj7h4YuJp0w6agWVR4eXmsSFbOrxoUrUuq4LV5VAK5GdcMPRSFS6qgTBA_3TUA_qjHEH7bH2TiBTB7OV4JusBexsAH2nOaYcF0UE05YHlNRQfwKolM26GXERq89Eby3DZT0tpoP9d2wxMGB0R06X-ofj_iZY2ECYX-H3p0cTtU1_FD0PCNwrPPsLtg1NidLXjZ0sPliiuM9fSIikymy2SLum4EntDAio6KaAfc51nZFZTCEHPtzPI9zbLK85ZM69S-47cXGJGC2liaUeg5BCrNoAiublklVAOnNujpjytodluJwSYVjBdBPIsptG-v1km8y59B4hrtTLBXp9k5-jus_8Knsb9uizU5vCU-eLitbwrkyAwpnvSHH3IXJuomIlDoPNT7o0gZRAcsFt4DhVwRiNfKgoIyAAMOc-JGxOISuMV4A2Fb6SZg0_Uq-qaMqK5A%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzIxNjM3MzQxOjE3MjE4OTY1NDE6pKJOiof27iCg47j50ZcdYRCRFI6NIfa2e2iClIA3usI5HSBAE_E3jcSVACGVxv4ZzDvYCMAlpEA4f8XiRWK2U6McMflzA2eYrlwy7Schc3OUfepCY0WMUWDbjdXcL6Dm_sywNGf15qlTGwrSI7x-6_oySswEy5uyTONccxWWeB8RM2hV05m3CRmBI-7lv1wHpZqlG2QJL5zoZUjsJKTxuySDPeE8ApuKrppszf_3pGj7h4YuJp0w6agWVR4eXmsSFbOrxoUrUuq4LV5VAK5GdcMPRSFS6qgTBA_3TUA_qjHEH7bH2TiBTB7OV4JusBexsAH2nOaYcF0UE05YHlNRQfwKolM26GXERq89Eby3DZT0tpoP9d2wxMGB0R06X-ofj_iZY2ECYX-H3p0cTtU1_FD0PCNwrPPsLtg1NidLXjZ0sPliiuM9fSIikymy2SLum4EntDAio6KaAfc51nZFZTCEHPtzPI9zbLK85ZM69S-47cXGJGC2liaUeg5BCrNoAiublklVAOnNujpjytodluJwSYVjBdBPIsptG-v1km8y59B4hrtTLBXp9k5-jus_8Knsb9uizU5vCU-eLitbwrkyAwpnvSHH3IXJuomIlDoPNT7o0gZRAcsFt4DhVwRiNfKgoIyAAMOc-JGxOISuMV4A2Fb6SZg0_Uq-qaMqK5A=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-07-26 03:02:43 (1548) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-07-26 03:02:43 (214) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-07-26 03:02:43 (1646) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-07-26 03:02:43 (1652) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-07-26 03:02:43 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-26 03:02:50 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ZNQ9qRMbWG/ea_profile.json * 2024-07-26 03:05:28 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ZNQ9qRMbWG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-26 03:05:28 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-27 02:24:25 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-27 02:28:26 (8209) [INFO] Script is up to date. * 2024-07-27 02:32:28 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-27 02:32:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-27 02:32:29 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-27 02:32:29 (6908) [INFO] * 2024-07-27 02:32:39 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-27 02:32:39 (6938) [INFO] * 2024-07-27 02:32:41 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-27 02:32:41 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:32:41 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-27 02:32:41 (6908) [INFO] * 2024-07-27 02:41:59 (6938) [INFO] * 2024-07-27 02:41:59 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-27 02:51:57 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. * 2024-07-27 02:51:57 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-27 02:51:57 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-27 02:51:57 (6908) [INFO] * 2024-07-27 02:51:57 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-27 02:51:58 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-27 02:51:58 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-27 02:51:58 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-27 02:51:58 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-27 02:51:58 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-27 02:51:58 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-27 02:51:58 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-27 02:51:58 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-27 02:51:58 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-27 02:51:58 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-27 02:51:58 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-27 02:51:58 (6938) [INFO] * 2024-07-28 01:46:49 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-28 01:50:49 (8209) [INFO] Script is up to date. * 2024-07-28 01:54:52 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-28 01:54:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-28 01:54:53 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-28 01:54:53 (6908) [INFO] * 2024-07-28 01:55:04 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-28 01:55:04 (6938) [INFO] * 2024-07-28 01:55:06 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-28 01:55:06 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 01:55:06 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-28 01:55:06 (6908) [INFO] * 2024-07-28 01:55:20 (6938) [INFO] * 2024-07-28 01:55:20 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-28 02:07:52 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30916 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') 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 updates: Check uncompressed DB failed * 2024-07-28 02:07:52 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-28 02:07:52 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-28 02:07:52 (6908) [INFO] * 2024-07-28 02:07:53 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-28 02:07:53 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-28 02:07:53 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-28 02:07:53 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-28 02:07:53 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-28 02:07:53 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-28 02:07:53 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-28 02:07:53 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-28 02:07:53 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-28 02:07:53 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-28 02:07:54 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-28 02:07:54 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-28 02:07:54 (6938) [INFO] * 2024-07-29 01:46:43 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-29 01:50:44 (8209) [INFO] Script is up to date. * 2024-07-29 01:54:47 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-29 01:54:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-29 01:54:47 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-29 01:54:47 (6908) [INFO] * 2024-07-29 01:54:57 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-29 01:54:57 (6938) [INFO] * 2024-07-29 01:54:59 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-29 01:54:59 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 01:54:59 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-29 01:54:59 (6908) [INFO] * 2024-07-29 01:55:13 (6938) [INFO] * 2024-07-29 01:55:13 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-29 02:03:39 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-07-29 02:03:39 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-29 02:03:39 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-29 02:03:39 (6908) [INFO] * 2024-07-29 02:03:39 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-29 02:03:40 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-29 02:03:40 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-29 02:03:40 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-29 02:03:40 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-29 02:03:40 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-29 02:03:40 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-29 02:03:40 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-29 02:03:40 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-29 02:03:40 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-29 02:03:41 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-29 02:03:41 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-29 02:03:41 (6938) [INFO] * 2024-07-30 01:46:02 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-30 01:50:02 (8209) [INFO] Script is up to date. * 2024-07-30 01:54:05 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-30 01:54:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-30 01:54:05 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-30 01:54:05 (6908) [INFO] * 2024-07-30 01:54:16 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-30 01:54:16 (6938) [INFO] * 2024-07-30 01:54:18 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-30 01:54:18 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-30 01:54:18 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-30 01:54:18 (6908) [INFO] * 2024-07-30 01:54:29 (6938) [INFO] * 2024-07-30 01:54:29 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-30 02:04:30 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-30 02:04:30 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-30 02:04:30 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-30 02:04:30 (6908) [INFO] * 2024-07-30 02:04:30 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-30 02:04:31 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-30 02:04:31 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-30 02:04:31 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-30 02:04:31 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-30 02:04:31 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-30 02:04:31 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-30 02:04:31 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-30 02:04:31 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-30 02:04:31 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-30 02:04:31 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-30 02:04:31 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-30 02:04:31 (6938) [INFO] * 2024-07-31 01:50:33 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-31 01:54:34 (8209) [INFO] Script is up to date. * 2024-07-31 01:58:37 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-07-31 01:58:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-07-31 01:58:37 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-31 01:58:37 (6908) [INFO] * 2024-07-31 02:09:30 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-07-31 02:09:31 (6938) [INFO] * 2024-07-31 02:09:32 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-07-31 02:09:32 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:09:32 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-31 02:09:32 (6908) [INFO] * 2024-07-31 02:09:44 (6938) [INFO] * 2024-07-31 02:09:44 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-07-31 02:18:18 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-07-31 02:18:18 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-31 02:18:18 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-31 02:18:18 (6908) [INFO] * 2024-07-31 02:18:18 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-31 02:18:18 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-07-31 02:18:18 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-31 02:18:18 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-31 02:18:18 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-07-31 02:18:18 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-07-31 02:18:18 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-31 02:18:18 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-31 02:18:18 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-07-31 02:18:18 (6921) [INFO] : wp-toolkit-thirdparties * 2024-07-31 02:18:19 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-31 02:18:19 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-07-31 02:18:19 (6938) [INFO] * 2024-08-01 01:46:27 (8187) [INFO] Self-update of script version 49 requested. * 2024-08-01 01:50:27 (8209) [INFO] Script is up to date. * 2024-08-01 01:54:30 (2326) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-01 01:54:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-01 01:54:30 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-01 01:54:30 (6908) [INFO] * 2024-08-01 01:54:42 (6921) [INFO] {"items": "7.14.1", "strategy": "CSF_COOP", "warnings": [], "version": "7.14.1", "eula": null, "license": {"status": true, "expiration": null, "user_limit": 2147483647, "id": "SSJevQFXu43C0gUJ", "user_count": 123, "message": "", "license_type": "imunify360", "redirect_url": "https://cln.cloudlinux.com/console/imunify360/servers/SSJevQFXu43C0gUJ/products/IM_UN/convert"}} * 2024-08-01 01:54:42 (6938) [INFO] * 2024-08-01 01:54:44 (744) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-01 01:54:44 (751) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-01 01:54:44 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-08-01 01:54:44 (6908) [INFO] * 2024-08-01 01:54:57 (6938) [INFO] * 2024-08-01 01:54:57 (214) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-01 02:02:54 (2047) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2024-08-01 02:02:54 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-01 02:02:54 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-08-01 02:02:54 (6908) [INFO] * 2024-08-01 02:02:54 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-01 02:02:55 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-01 02:02:55 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-01 02:02:55 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-01 02:02:55 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-01 02:02:55 (6921) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-01 02:02:55 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-01 02:02:55 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-01 02:02:55 (6921) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-01 02:02:55 (6921) [INFO] : wp-toolkit-thirdparties * 2024-08-01 02:02:55 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-08-01 02:02:55 (6921) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-01 02:02:55 (6938) [INFO] * 2024-08-02 01:51:14 (8187) [INFO] Self-update of script version 49 requested. * 2024-08-02 01:55:15 (8192) [INFO] Newer version of script found. Downloading. * 2024-08-02 01:59:16 (8201) [INFO] Script update to version 50 successful. * 2024-08-02 02:03:19 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-02 02:03:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-02 02:03:20 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-02 02:03:20 (7164) [INFO] * 2024-08-02 02:03:32 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-02 02:03:32 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:32 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-02 02:03:32 (7164) [INFO] * 2024-08-02 02:03:45 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-02 02:12:46 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-08-02 02:12:46 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-02 02:12:46 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-02 02:12:46 (7164) [INFO] * 2024-08-02 02:12:46 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-02 02:12:47 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-02 02:12:47 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-02 02:12:47 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-02 02:12:47 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-02 02:12:47 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-02 02:12:47 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-02 02:12:47 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-02 02:12:47 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-02 02:12:47 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-02 02:12:47 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-02 02:12:47 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-02 02:12:47 (7194) [INFO] * 2024-08-03 01:46:58 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-03 01:50:58 (8496) [INFO] Script is up to date. * 2024-08-03 01:55:02 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-03 01:55:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-03 01:55:02 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-03 01:55:02 (7164) [INFO] * 2024-08-03 01:55:16 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-03 01:55:16 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-03 01:55:16 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-03 01:55:16 (7164) [INFO] * 2024-08-03 01:55:29 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-03 02:05:38 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30847 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. * 2024-08-03 02:05:38 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-03 02:05:38 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-03 02:05:38 (7164) [INFO] * 2024-08-03 02:05:39 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-03 02:05:39 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-03 02:05:39 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-03 02:05:39 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-03 02:05:39 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-03 02:05:39 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-03 02:05:39 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-03 02:05:39 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-03 02:05:39 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-03 02:05:39 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-03 02:05:40 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-03 02:05:40 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-03 02:05:40 (7194) [INFO] * 2024-08-04 01:47:44 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-04 01:51:45 (8496) [INFO] Script is up to date. * 2024-08-04 01:55:47 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-04 01:55:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-04 01:55:48 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-04 01:55:48 (7164) [INFO] * 2024-08-04 01:56:00 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-04 01:56:00 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-04 01:56:00 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-04 01:56:00 (7164) [INFO] * 2024-08-04 01:56:13 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-04 02:11:21 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') 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 * 2024-08-04 02:11:21 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-04 02:11:21 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-04 02:11:21 (7164) [INFO] * 2024-08-04 02:11:21 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-04 02:11:21 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-04 02:11:21 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-04 02:11:21 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-04 02:11:21 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-04 02:11:21 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-04 02:11:21 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-04 02:11:21 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-04 02:11:21 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-04 02:11:21 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-04 02:11:22 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-04 02:11:22 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-04 02:11:22 (7194) [INFO] * 2024-08-05 01:46:11 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-05 01:50:12 (8496) [INFO] Script is up to date. * 2024-08-05 01:54:15 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-05 01:54:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-05 01:54:15 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-05 01:54:15 (7164) [INFO] * 2024-08-05 01:54:26 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-05 01:54:26 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-05 01:54:26 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-05 01:54:26 (7164) [INFO] * 2024-08-05 01:54:38 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-05 02:09:43 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30657 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') 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 * 2024-08-05 02:09:43 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-05 02:09:43 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-05 02:09:43 (7164) [INFO] * 2024-08-05 02:09:43 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-05 02:09:44 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-05 02:09:44 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-05 02:09:44 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-05 02:09:44 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-05 02:09:44 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-05 02:09:44 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-05 02:09:44 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-05 02:09:44 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-05 02:09:44 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-05 02:09:44 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-05 02:09:44 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-05 02:09:44 (7194) [INFO] * 2024-08-06 01:45:36 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-06 01:49:36 (8496) [INFO] Script is up to date. * 2024-08-06 01:53:39 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-06 01:53:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-06 01:53:39 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-06 01:53:39 (7164) [INFO] * 2024-08-06 01:53:51 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-06 01:53:51 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-06 01:53:51 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-06 01:53:51 (7164) [INFO] * 2024-08-06 01:54:03 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-06 02:03:07 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-08-06 02:03:07 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-06 02:03:07 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-06 02:03:07 (7164) [INFO] * 2024-08-06 02:03:08 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-06 02:03:08 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-06 02:03:08 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-06 02:03:08 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-06 02:03:08 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-06 02:03:08 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-06 02:03:08 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-06 02:03:08 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-06 02:03:08 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-06 02:03:08 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-06 02:03:09 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-06 02:03:09 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-06 02:03:09 (7194) [INFO] * 2024-08-07 02:01:47 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-07 02:05:47 (8496) [INFO] Script is up to date. * 2024-08-07 02:09:50 (2338) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-07 02:09:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-07 02:09:50 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-07 02:09:50 (7164) [INFO] * 2024-08-07 02:10:03 (756) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-07 02:10:03 (763) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:10:03 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-07 02:10:03 (7164) [INFO] * 2024-08-07 02:17:14 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-07 02:25:19 (2059) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30888 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30891 milliseconds') Trying other mirror. * 2024-08-07 02:25:19 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-07 02:25:19 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-07 02:25:19 (7164) [INFO] * 2024-08-07 02:25:19 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-07 02:25:19 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-07 02:25:19 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-07 02:25:19 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-07 02:25:19 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-07 02:25:19 (7177) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-07 02:25:19 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-07 02:25:20 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-07 02:25:20 (7177) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-07 02:25:20 (7177) [INFO] : wp-toolkit-thirdparties * 2024-08-07 02:25:20 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-07 02:25:20 (7177) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-07 02:25:20 (7194) [INFO] * 2024-08-08 01:47:51 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-08 01:51:51 (8479) [INFO] Newer version of script found. Downloading. * 2024-08-08 01:55:53 (8488) [INFO] Script update to version 51 successful. * 2024-08-08 01:59:56 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-08 01:59:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-08 01:59:56 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-08 01:59:56 (7324) [INFO] * 2024-08-08 02:00:09 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-08 02:00:09 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:00:09 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-08 02:00:09 (7324) [INFO] * 2024-08-08 02:00:21 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-08 02:13:59 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') 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 extras: Check uncompressed DB failed * 2024-08-08 02:13:59 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-08 02:13:59 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-08 02:13:59 (7324) [INFO] * 2024-08-08 02:13:59 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-08 02:14:00 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-08 02:14:00 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-08 02:14:00 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-08 02:14:00 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-08 02:14:00 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-08 02:14:00 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-08 02:14:00 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-08 02:14:00 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-08 02:14:00 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-08 02:14:00 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-08 02:14:00 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-08 02:14:01 (7354) [INFO] * 2024-08-09 01:50:05 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-09 01:54:05 (8664) [INFO] Script is up to date. * 2024-08-09 01:58:09 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-09 01:58:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-09 01:58:09 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-09 01:58:09 (7324) [INFO] * 2024-08-09 01:58:21 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-09 01:58:21 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-09 01:58:21 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-09 01:58:21 (7324) [INFO] * 2024-08-09 01:58:33 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-09 02:05:32 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-09 02:05:32 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-09 02:05:32 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-09 02:05:32 (7324) [INFO] * 2024-08-09 02:05:32 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-09 02:05:32 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-09 02:05:32 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-09 02:05:32 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-09 02:05:32 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-09 02:05:32 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-09 02:05:32 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-09 02:05:32 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-09 02:05:32 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-09 02:05:32 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-09 02:05:33 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-09 02:05:33 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-09 02:05:33 (7354) [INFO] * 2024-08-10 01:48:56 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-10 01:52:56 (8664) [INFO] Script is up to date. * 2024-08-10 01:56:59 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-10 01:57:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-10 01:57:00 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-10 01:57:00 (7324) [INFO] * 2024-08-10 01:57:13 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-10 01:57:13 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-10 01:57:13 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-10 01:57:13 (7324) [INFO] * 2024-08-10 01:57:24 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-10 02:15:55 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30439 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') 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 * 2024-08-10 02:15:55 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-10 02:15:55 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-10 02:15:55 (7324) [INFO] * 2024-08-10 02:15:56 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-10 02:15:56 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-10 02:15:56 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-10 02:15:56 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-10 02:15:56 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-10 02:15:56 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-10 02:15:56 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-10 02:15:56 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-10 02:15:56 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-10 02:15:56 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-10 02:15:57 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-10 02:15:57 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-10 02:15:57 (7354) [INFO] * 2024-08-11 01:47:15 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-11 01:51:15 (8664) [INFO] Script is up to date. * 2024-08-11 01:55:18 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-11 01:55:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-11 01:55:18 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-11 01:55:18 (7324) [INFO] * 2024-08-11 01:55:31 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-11 01:55:31 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-11 01:55:31 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-11 01:55:31 (7324) [INFO] * 2024-08-11 01:55:44 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-11 02:03:57 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-08-11 02:03:57 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-11 02:03:57 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-11 02:03:57 (7324) [INFO] * 2024-08-11 02:03:57 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-11 02:03:58 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-11 02:03:58 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-11 02:03:58 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-11 02:03:58 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-11 02:03:58 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-11 02:03:58 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-11 02:03:58 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-11 02:03:58 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-11 02:03:58 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-11 02:03:58 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-11 02:03:58 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-11 02:03:59 (7354) [INFO] * 2024-08-12 01:46:06 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-12 01:50:06 (8664) [INFO] Script is up to date. * 2024-08-12 01:54:09 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-12 01:54:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-12 01:54:09 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-12 01:54:09 (7324) [INFO] * 2024-08-12 01:54:22 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-12 01:54:22 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-12 01:54:23 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-12 01:54:23 (7324) [INFO] * 2024-08-12 01:54:35 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-12 02:04:06 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f1df499708969a49e78baacbd4952820b644cd86a6a5ec930ebc888e4d3bc6c8-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/cef72d11411c1ab38307c0ab7ea627fe06ca7da9642316debb97ac85101ddac1-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f1df499708969a49e78baacbd4952820b644cd86a6a5ec930ebc888e4d3bc6c8-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/cef72d11411c1ab38307c0ab7ea627fe06ca7da9642316debb97ac85101ddac1-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f1df499708969a49e78baacbd4952820b644cd86a6a5ec930ebc888e4d3bc6c8-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. One of the configured repositories failed (EL-7 - Imunify360), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360 or subscription-manager repos --disable=imunify360 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360.skip_if_unavailable=true failure: repodata/f1df499708969a49e78baacbd4952820b644cd86a6a5ec930ebc888e4d3bc6c8-filelists.sqlite.bz2 from imunify360: [Errno 256] No more mirrors to try. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f1df499708969a49e78baacbd4952820b644cd86a6a5ec930ebc888e4d3bc6c8-filelists.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-08-12 02:04:06 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-12 02:04:06 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-12 02:04:06 (7324) [INFO] * 2024-08-12 02:04:06 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-12 02:04:06 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-12 02:04:06 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-12 02:04:06 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-12 02:04:06 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-12 02:04:06 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-12 02:04:06 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-12 02:04:06 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-12 02:04:06 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-12 02:04:06 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-12 02:04:07 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-12 02:04:07 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-12 02:04:07 (7354) [INFO] * 2024-08-13 01:46:29 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-13 01:50:30 (8664) [INFO] Script is up to date. * 2024-08-13 01:54:33 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-13 01:54:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-13 01:54:33 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-13 01:54:33 (7324) [INFO] * 2024-08-13 01:54:46 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-13 01:54:46 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-13 01:54:46 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-13 01:54:46 (7324) [INFO] * 2024-08-13 01:54:57 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-13 02:04:15 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-08-13 02:04:15 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-13 02:04:15 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-13 02:04:15 (7324) [INFO] * 2024-08-13 02:04:15 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-13 02:04:16 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-13 02:04:16 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-13 02:04:16 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-13 02:04:16 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-13 02:04:16 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-13 02:04:16 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-13 02:04:16 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-13 02:04:16 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-13 02:04:16 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-13 02:04:16 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-13 02:04:16 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-13 02:04:16 (7354) [INFO] * 2024-08-14 01:53:27 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-14 01:57:27 (8664) [INFO] Script is up to date. * 2024-08-14 02:01:30 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-14 02:01:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-14 02:01:30 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-14 02:01:30 (7324) [INFO] * 2024-08-14 02:01:42 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-14 02:01:42 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:01:42 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-14 02:01:42 (7324) [INFO] * 2024-08-14 02:14:59 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-15 02:15:24 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-15 02:19:25 (8664) [INFO] Script is up to date. * 2024-08-15 02:23:28 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-15 02:23:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-15 02:23:28 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-15 02:23:28 (7324) [INFO] * 2024-08-15 02:23:41 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-15 02:23:41 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:23:41 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-15 02:23:41 (7324) [INFO] * 2024-08-15 02:23:53 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-15 02:34:41 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30005 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Operation timed out after 30003 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30045 milliseconds with 0 out of 0 bytes received') Trying other mirror. * 2024-08-15 02:34:41 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-15 02:34:41 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-15 02:34:41 (7324) [INFO] * 2024-08-15 02:34:41 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-15 02:34:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-15 02:34:42 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-15 02:34:42 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-15 02:34:42 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-15 02:34:42 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-15 02:34:42 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-15 02:34:42 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-15 02:34:42 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-15 02:34:42 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-15 02:34:42 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-15 02:34:42 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-15 02:34:42 (7354) [INFO] * 2024-08-16 01:50:35 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-16 01:54:35 (8664) [INFO] Script is up to date. * 2024-08-16 01:58:38 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-16 01:58:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-16 01:58:38 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-16 01:58:38 (7324) [INFO] * 2024-08-16 01:58:50 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-16 01:58:50 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-16 01:58:50 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-16 01:58:50 (7324) [INFO] * 2024-08-16 02:08:43 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-16 02:19:01 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30883 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-16 02:19:01 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-16 02:19:01 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-16 02:19:01 (7324) [INFO] * 2024-08-16 02:19:01 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-16 02:19:02 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-16 02:19:02 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-16 02:19:02 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-16 02:19:02 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-16 02:19:02 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-16 02:19:02 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-16 02:19:02 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-16 02:19:02 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-16 02:19:02 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-16 02:19:03 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-16 02:19:03 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-16 02:19:03 (7354) [INFO] * 2024-08-17 01:50:14 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-17 01:54:14 (8664) [INFO] Script is up to date. * 2024-08-17 01:58:17 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-17 01:58:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-17 01:58:17 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-17 01:58:17 (7324) [INFO] * 2024-08-17 01:58:32 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-17 01:58:32 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-17 01:58:32 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-17 01:58:32 (7324) [INFO] * 2024-08-17 02:10:37 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-18 01:46:56 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-18 01:50:57 (8664) [INFO] Script is up to date. * 2024-08-18 01:54:59 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-18 01:55:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-18 01:55:00 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-18 01:55:00 (7324) [INFO] * 2024-08-18 01:55:14 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-18 01:55:14 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-18 01:55:14 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-18 01:55:14 (7324) [INFO] * 2024-08-18 01:55:25 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-18 02:08:45 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30027 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') 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 extras: Check uncompressed DB failed * 2024-08-18 02:08:45 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-18 02:08:45 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-18 02:08:45 (7324) [INFO] * 2024-08-18 02:08:46 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-18 02:08:46 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-18 02:08:46 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-18 02:08:46 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-18 02:08:46 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-18 02:08:46 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-18 02:08:46 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-18 02:08:46 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-18 02:08:46 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-18 02:08:46 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-18 02:08:47 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-18 02:08:47 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-18 02:08:47 (7354) [INFO] * 2024-08-19 01:45:37 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-19 01:49:37 (8664) [INFO] Script is up to date. * 2024-08-19 01:53:40 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-19 01:53:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-19 01:53:40 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-19 01:53:40 (7324) [INFO] * 2024-08-19 01:53:54 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-19 01:53:54 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-19 01:53:54 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-19 01:53:54 (7324) [INFO] * 2024-08-19 01:54:09 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-19 02:03:59 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2024-08-19 02:03:59 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-19 02:03:59 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-19 02:03:59 (7324) [INFO] * 2024-08-19 02:03:59 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-19 02:04:00 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-19 02:04:00 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-19 02:04:00 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-19 02:04:00 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-19 02:04:00 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-19 02:04:00 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-19 02:04:00 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-19 02:04:00 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-19 02:04:00 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-19 02:04:01 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-19 02:04:01 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-19 02:04:01 (7354) [INFO] * 2024-08-20 01:48:22 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-20 01:52:22 (8664) [INFO] Script is up to date. * 2024-08-20 01:56:25 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-20 01:56:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-20 01:56:25 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-20 01:56:25 (7324) [INFO] * 2024-08-20 01:56:36 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-20 01:56:36 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-20 01:56:36 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-20 01:56:36 (7324) [INFO] * 2024-08-20 01:56:49 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-20 02:06:15 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-20 02:06:15 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-20 02:06:15 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-20 02:06:15 (7324) [INFO] * 2024-08-20 02:06:15 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-20 02:06:16 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-20 02:06:16 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-20 02:06:16 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-20 02:06:16 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-20 02:06:16 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-20 02:06:16 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-20 02:06:16 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-20 02:06:16 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-20 02:06:16 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-20 02:06:17 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-20 02:06:17 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-20 02:06:17 (7354) [INFO] * 2024-08-21 01:47:29 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-21 01:51:29 (8664) [INFO] Script is up to date. * 2024-08-21 01:55:32 (2308) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-21 01:55:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-21 01:55:32 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-21 01:55:32 (7324) [INFO] * 2024-08-21 01:55:46 (739) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-21 01:55:46 (746) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-21 01:55:46 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-21 01:55:46 (7324) [INFO] * 2024-08-21 01:55:58 (226) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-21 02:02:52 (2029) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-21 02:02:52 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-21 02:02:52 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-21 02:02:52 (7324) [INFO] * 2024-08-21 02:02:53 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-21 02:02:53 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-21 02:02:53 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-21 02:02:53 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-21 02:02:53 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-21 02:02:53 (7337) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-21 02:02:53 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-21 02:02:53 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-21 02:02:53 (7337) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-21 02:02:53 (7337) [INFO] : wp-toolkit-thirdparties * 2024-08-21 02:02:54 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-21 02:02:54 (7337) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-21 02:02:54 (7354) [INFO] * 2024-08-21 02:17:14 (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 02:17:14 (2040) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MDYzMDE2OjE3MjQzMjIyMTY6Wiid2eP1i_2lnf40fyEQZnWhf8C8mGBxSOTEYjmc7BwiIW5oBj8wq2Akxr8IK48vd4janRCzsosImxDG0UukR0pxAs_LbL53aobBqrhuFsKOfGdEbeowWBr9GSeI6Mc_PlAYVQbL00EsY4xOuGTww9csHrhpuDXVYPQgxV4dH082ytXqKL9L6Jstmrl3jjS7WFWksnfOpaQApMqQ6qNrgRuo4JXjFkIz91C5d4VTVL_Xiws0jIe8A7TVBpSSTvk67WL17MhTaSIXv-Qw4kHoup2VVyAybbzkP1QRk25j_MC4nOq9hNOBaJWv9DObBb3cfN_b5907KQ6DmkU3O2qwdESOaH0hJWHevrUArJIB1YNpw6RyAwXBwZG4tfnvkqQAeTFJDFMpv4NYwR23KOIaViPGM9LdjlDpjH6rVt-zbsp4j-sJFuYki5st-Uhej__1ojbazpJ782zb9R7oLZ3xUFq8w77aWf4RfOUd2gZAljDQPY0RVPzVToBDikSKenIh0Rnu5ECY24lv3FKeBw6FOs23Vf5h3JnYY8fwymfoB2bq1rnaNlySDEV_NMwvR0LMOV32fzrycl0o7PZo9AUy3JI9CmB4PD8nniNHy88FKnOk1yyjrSHV61MF8W9ZE_uLzwdZTth-qncgkbvoNhRsWE0NXKvcDZWEuaYnbUvoznA%3D/ea-php/7/updates/x86_64/repodata/00a228cf1d146aeb97829a95411885c2442b39e590784218d12535ef58cc4d94-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.2/wp-toolkit/repodata/44876075891ccf9bb030bf17a3da0cf35ea9d65949281eb6aba27b644e16d377-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-08-21 02:17:15 (1530) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-08-21 02:17:15 (226) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-08-21 02:17:15 (1628) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-08-21 02:17:15 (1634) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-08-21 02:17:15 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-22 01:51:09 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-22 01:55:10 (8647) [INFO] Newer version of script found. Downloading. * 2024-08-22 01:59:12 (8656) [INFO] Script update to version 52 successful. * 2024-08-22 02:03:15 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-22 02:03:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-22 02:03:15 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-22 02:03:15 (7574) [INFO] * 2024-08-22 02:03:27 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-22 02:03:27 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:27 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-22 02:03:27 (7574) [INFO] * 2024-08-22 02:03:38 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-22 02:13:04 (1963) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30663 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-22 02:13:04 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-22 02:13:04 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-22 02:13:04 (7574) [INFO] * 2024-08-22 02:13:05 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-22 02:13:05 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-22 02:13:05 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-22 02:13:05 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-22 02:13:05 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-22 02:13:05 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-22 02:13:05 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-22 02:13:05 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-22 02:13:05 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-22 02:13:05 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-22 02:13:06 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-22 02:13:06 (7587) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-22 02:13:06 (7604) [INFO] * 2024-08-23 01:55:38 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-23 01:59:38 (8939) [INFO] Script is up to date. * 2024-08-23 02:03:41 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-23 02:03:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-23 02:03:42 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-23 02:03:42 (7574) [INFO] * 2024-08-23 02:03:45 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-23 02:03:45 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:03:45 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-23 02:03:45 (7574) [INFO] * 2024-08-23 02:11:31 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-23 02:21:58 (1963) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-08-23 02:21:58 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-23 02:21:58 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-23 02:21:58 (7574) [INFO] * 2024-08-23 02:21:59 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-23 02:21:59 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-23 02:21:59 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-23 02:21:59 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-23 02:21:59 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-23 02:21:59 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-23 02:21:59 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-23 02:21:59 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-23 02:21:59 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-23 02:21:59 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-23 02:22:00 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-23 02:22:00 (7587) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-23 02:22:00 (7604) [INFO] * 2024-08-24 01:48:29 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-24 01:52:30 (8939) [INFO] Script is up to date. * 2024-08-24 01:56:33 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-24 01:56:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-24 01:56:33 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-24 01:56:33 (7574) [INFO] * 2024-08-24 01:56:38 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-24 01:56:38 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-24 01:56:38 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-24 01:56:38 (7574) [INFO] * 2024-08-24 01:56:49 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-24 02:04:48 (1963) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-24 02:04:48 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-24 02:04:48 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-24 02:04:48 (7574) [INFO] * 2024-08-24 02:04:48 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-24 02:04:49 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-24 02:04:49 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-24 02:04:49 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-24 02:04:49 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-24 02:04:49 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-24 02:04:49 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-24 02:04:49 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-24 02:04:49 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-24 02:04:49 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-24 02:04:49 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-24 02:04:49 (7587) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-24 02:04:49 (7604) [INFO] * 2024-08-25 01:47:18 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-25 01:51:19 (8939) [INFO] Script is up to date. * 2024-08-25 01:55:22 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-25 01:55:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-25 01:55:22 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-25 01:55:22 (7574) [INFO] * 2024-08-25 01:55:34 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-25 01:55:34 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-25 01:55:34 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-25 01:55:34 (7574) [INFO] * 2024-08-25 01:58:15 (1963) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-25 01:58:15 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-25 01:58:15 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-25 01:58:15 (7574) [INFO] * 2024-08-25 01:58:15 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-25 01:58:16 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-25 01:58:16 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-25 01:58:16 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-25 01:58:16 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-25 01:58:16 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-25 01:58:16 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-25 01:58:16 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-25 01:58:16 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-25 01:58:16 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-25 01:58:16 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-25 01:58:16 (7587) [INFO] Other repos take up 968 k of disk space (use --verbose for details) * 2024-08-25 01:58:16 (7604) [INFO] * 2024-08-25 02:00:49 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-08-25 02:00:49 (1974) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-25 02:00:50 (1464) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-08-25 02:00:50 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-08-25 02:00:50 (1562) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-08-25 02:00:50 (1568) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-08-25 02:00:50 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-25 02:00:56 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zxhFCpymUh/ea_profile.json * 2024-08-25 02:04:00 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zxhFCpymUh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-25 02:04:00 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-26 01:44:23 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-26 01:48:24 (8939) [INFO] Script is up to date. * 2024-08-26 01:52:27 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-26 01:52:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-26 01:52:27 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-26 01:52:27 (7574) [INFO] * 2024-08-26 01:52:38 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-26 01:52:38 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-26 01:52:38 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-26 01:52:38 (7574) [INFO] * 2024-08-26 01:54:50 (1963) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-26 01:54:50 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-26 01:54:50 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-26 01:54:50 (7574) [INFO] * 2024-08-26 01:54:51 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-26 01:54:51 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-26 01:54:51 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-26 01:54:51 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-26 01:54:51 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-26 01:54:51 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-26 01:54:51 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-26 01:54:51 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-26 01:54:51 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-26 01:54:51 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-26 01:54:51 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-26 01:54:51 (7587) [INFO] Other repos take up 968 k of disk space (use --verbose for details) * 2024-08-26 01:54:51 (7604) [INFO] * 2024-08-26 01:56:55 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-08-26 01:56:55 (1974) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-26 01:56:56 (1464) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-08-26 01:56:56 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-08-26 01:56:56 (1562) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-08-26 01:56:56 (1568) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-08-26 01:56:56 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-26 01:57:02 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ydsBf8OjmR/ea_profile.json * 2024-08-26 01:59:37 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ydsBf8OjmR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-26 01:59:37 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-27 01:45:24 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-27 01:49:25 (8939) [INFO] Script is up to date. * 2024-08-27 01:53:28 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-27 01:53:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-27 01:53:29 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-27 01:53:29 (7574) [INFO] * 2024-08-27 01:53:39 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-27 01:53:39 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-27 01:53:39 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-27 01:53:39 (7574) [INFO] * 2024-08-27 01:55:51 (1963) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-27 01:55:51 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-27 01:55:51 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-27 01:55:51 (7574) [INFO] * 2024-08-27 01:55:51 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-27 01:55:51 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-27 01:55:51 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-27 01:55:51 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-27 01:55:51 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-27 01:55:51 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-27 01:55:51 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-27 01:55:51 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-27 01:55:51 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-27 01:55:51 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-27 01:55:52 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-27 01:55:52 (7587) [INFO] Other repos take up 968 k of disk space (use --verbose for details) * 2024-08-27 01:55:52 (7604) [INFO] * 2024-08-27 01:57: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-27 01:57:56 (1974) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI0MjM2ODc2OjE3MjQ0OTYwNzY6kcK3DMU7YFz22r8GFUAWRDLfxHXF8cR_6bQzcHje8gf-ZpuXsc-7Hgvxe7_IqAeWDgX7FQ8_H0fVQHalwribcfKu-RQB3WRZUHAh5sTCNCD_Gq5RkR_SF2XU_Ic482Qlighr0TGdyqH7SmUw_7HqjCBnrrU4kH-7RTk4XAY4M6YEr8v9hhiA8eDNq0jRTOryhO4CG-dF_LswD8P81W6oXRWVzAa1g6EY8OAVM467moltOKndZZRUCv2HCHvFdD0w15eAzwR0xEsLfEYDCIfyzHsjpaAvhRpN0CRzBvE-UckPw43JTSgYny1BlHfNCnkyAHLeZGrOqkQB9c4OquHyFhYXaXs-456vU2NIBLmSr9Xjpj5Lvfd5HlDbr6PKD61XtkDn1xK3ABg8L715vvSVdciUMgYOunBQmhHL5fBQeFtIXciAtryvWUALTknFur0lxKoMDmu4YpU3GR1hNkpIGVpA9CBDEuUdZA86B5Aj2D3f_KsODZSRCLGqFOHUDfqmODuHZGQFmsSFK4nUpLz8A4UwQRm3z0oqhvPFSAf2YDxAgdmdf4URCJz9y1_ryj6d5h-BtiVLnRPMfBrPDWpXYZZf1v6uDRPCPU8o4h1PxO51ILuUenLxmHpYM8616ojgKc-lsjYlr5dXzWC0LPHhyA6UZ7jdfWcR1vQAnpSZDwI=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-08-27 01:57:57 (1464) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-08-27 01:57:57 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-08-27 01:57:57 (1562) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-08-27 01:57:57 (1568) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-08-27 01:57:57 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-27 01:58:04 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nWcVHjt8Gi/ea_profile.json * 2024-08-27 02:01:08 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nWcVHjt8Gi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-27 02:01:08 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-28 02:05:17 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-28 02:09:17 (8939) [INFO] Script is up to date. * 2024-08-28 02:13:21 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-28 02:13:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-28 02:13:21 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-28 02:13:21 (7574) [INFO] * 2024-08-28 02:13:30 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-28 02:13:30 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:13:30 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-28 02:13:30 (7574) [INFO] * 2024-08-28 02:15:32 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-28 02:21:37 (1963) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-08-28 02:21:37 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-28 02:21:37 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-28 02:21:37 (7574) [INFO] * 2024-08-28 02:21:37 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-28 02:21:38 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-28 02:21:38 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-28 02:21:38 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-28 02:21:38 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-28 02:21:38 (7587) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-28 02:21:38 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-28 02:21:38 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-28 02:21:38 (7587) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-28 02:21:38 (7587) [INFO] : wp-toolkit-thirdparties * 2024-08-28 02:21:38 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-28 02:21:38 (7587) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-28 02:21:38 (7604) [INFO] * 2024-08-29 01:46:17 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-29 01:50:17 (8939) [INFO] Script is up to date. * 2024-08-29 01:54:20 (2242) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-29 01:54:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-29 01:54:21 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-29 01:54:21 (7574) [INFO] * 2024-08-29 02:05:16 (673) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-29 02:05:16 (680) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/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 02:05:16 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-29 02:05:16 (7574) [INFO] * 2024-08-29 02:05:27 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-30 01:48:34 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-30 01:52:34 (8922) [INFO] Newer version of script found. Downloading. * 2024-08-30 01:56:36 (8931) [INFO] Script update to version 53 successful. * 2024-08-30 02:00:39 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-30 02:00:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-30 02:00:39 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-30 02:00:39 (7647) [INFO] * 2024-08-30 02:00:49 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-30 02:00:49 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-30 02:00:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-08-30 02:00:49 (7647) [INFO] * 2024-08-30 02:08:16 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-31 01:47:08 (8992) [INFO] Self-update of script version 53 requested. * 2024-08-31 01:51:08 (9014) [INFO] Script is up to date. * 2024-08-31 01:55:11 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-08-31 01:55:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-08-31 01:55:12 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-31 01:55:12 (7647) [INFO] * 2024-08-31 01:55:23 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-08-31 01:55:23 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-31 01:55:24 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-08-31 01:55:24 (7647) [INFO] * 2024-08-31 01:55:38 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-08-31 02:03:56 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30722 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-08-31 02:03:56 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-31 02:03:56 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-08-31 02:03:56 (7647) [INFO] * 2024-08-31 02:03:56 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-31 02:03:57 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-08-31 02:03:57 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-31 02:03:57 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-31 02:03:57 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-08-31 02:03:57 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-08-31 02:03:57 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-31 02:03:57 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-31 02:03:57 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-08-31 02:03:57 (7660) [INFO] : wp-toolkit-thirdparties * 2024-08-31 02:03:58 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-08-31 02:03:58 (7660) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-08-31 02:03:58 (7677) [INFO] * 2024-09-01 01:46:44 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-01 01:50:45 (9014) [INFO] Script is up to date. * 2024-09-01 01:54:48 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-01 01:54:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-01 01:54:48 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-01 01:54:48 (7647) [INFO] * 2024-09-01 01:55:00 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-01 01:55:00 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-01 01:55:00 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-01 01:55:00 (7647) [INFO] * 2024-09-01 01:55:14 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-01 02:05:18 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2024-09-01 02:05:18 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-01 02:05:18 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-01 02:05:18 (7647) [INFO] * 2024-09-01 02:05:18 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-01 02:05:19 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-01 02:05:19 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-01 02:05:19 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-01 02:05:19 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-01 02:05:19 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-01 02:05:19 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-01 02:05:19 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-01 02:05:19 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-01 02:05:19 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-01 02:05:19 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-01 02:05:19 (7660) [INFO] Other repos take up 904 k of disk space (use --verbose for details) * 2024-09-01 02:05:19 (7677) [INFO] * 2024-09-02 01:45:11 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-02 01:49:12 (9014) [INFO] Script is up to date. * 2024-09-02 01:53:15 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-02 01:53:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-02 01:53:15 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-02 01:53:15 (7647) [INFO] * 2024-09-02 01:53:26 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-02 01:53:26 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-02 01:53:26 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-02 01:53:26 (7647) [INFO] * 2024-09-02 01:53:41 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-02 02:02:24 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30725 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2024-09-02 02:02:24 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-02 02:02:24 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-02 02:02:24 (7647) [INFO] * 2024-09-02 02:02:24 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-02 02:02:24 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-02 02:02:24 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-02 02:02:24 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-02 02:02:24 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-02 02:02:24 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-02 02:02:24 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-02 02:02:24 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-02 02:02:24 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-02 02:02:24 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-02 02:02:25 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-02 02:02:25 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-02 02:02:25 (7677) [INFO] * 2024-09-03 01:45:11 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-03 01:49:12 (9014) [INFO] Script is up to date. * 2024-09-03 01:53:15 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-03 01:53:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-03 01:53:15 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-03 01:53:15 (7647) [INFO] * 2024-09-03 01:53:26 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-03 01:53:26 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-03 01:53:26 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-03 01:53:26 (7647) [INFO] * 2024-09-03 01:53:37 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-03 02:03:11 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-03 02:03:11 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-03 02:03:11 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-03 02:03:11 (7647) [INFO] * 2024-09-03 02:03:12 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-03 02:03:12 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-03 02:03:12 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-03 02:03:12 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-03 02:03:12 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-03 02:03:12 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-03 02:03:12 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-03 02:03:12 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-03 02:03:12 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-03 02:03:12 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-03 02:03:13 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-03 02:03:13 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-03 02:03:13 (7677) [INFO] * 2024-09-03 02:03:45 (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 02:03:45 (1977) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-09-03 02:03:46 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-03 02:03:46 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-03 02:03:46 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-03 02:03:46 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-03 02:03:46 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-03 02:06:19 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ZOP5JzJ9oe/ea_profile.json * 2024-09-03 02:13:19 (6788) [INFO] Backed up EA4 profile to /tmp/ZOP5JzJ9oe/ea_profile.json * 2024-09-03 02:13:20 (231) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-09-03 02:13:54 (2543) [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-09-03 02:13:54 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-04 01:54:41 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-04 01:58:42 (9014) [INFO] Script is up to date. * 2024-09-04 02:02:45 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-04 02:02:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-04 02:02:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-04 02:02:46 (7647) [INFO] * 2024-09-04 02:02:57 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-04 02:02:57 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-04 02:02:57 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-04 02:02:57 (7647) [INFO] * 2024-09-04 02:03:11 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-04 02:08:47 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. * 2024-09-04 02:08:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-04 02:08:47 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-04 02:08:47 (7647) [INFO] * 2024-09-04 02:08:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-04 02:08:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-04 02:08:47 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-04 02:08:47 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-04 02:08:47 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-04 02:08:47 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-04 02:08:47 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-04 02:08:47 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-04 02:08:47 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-04 02:08:47 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-04 02:08:48 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-04 02:08:48 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-04 02:08:48 (7677) [INFO] * 2024-09-04 02:21:10 (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 02:21:10 (1977) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/7d327e355567a4d82646ff97a4aa5c4ce00ac46d46ee2bbca38331d65f20b546-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/wp-toolkit/repodata/42ad3a6d00363e5a4575f63d414ee5c4968714e58a3799cff08325db47fdfb66-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') 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 extras: Check uncompressed DB failed * 2024-09-04 02:21:11 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-04 02:21:11 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-04 02:21:11 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-04 02:21:11 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-04 02:21:11 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-04 02:21:24 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9od_jVv5Jq/ea_profile.json * 2024-09-04 02:24:01 (6788) [INFO] Backed up EA4 profile to /tmp/9od_jVv5Jq/ea_profile.json * 2024-09-04 02:24:02 (231) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-09-05 01:57:33 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-05 02:01:33 (9014) [INFO] Script is up to date. * 2024-09-05 02:05:36 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-05 02:05:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-05 02:05:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-05 02:05:36 (7647) [INFO] * 2024-09-05 02:05:48 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-05 02:05:48 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-05 02:05:48 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-05 02:05:48 (7647) [INFO] * 2024-09-05 02:06:02 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-05 02:11:24 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI1MzUxMTU2OjE3MjU2MTAzNTY6e3qxSuWkS-HRcpLI5Lq_bLFmALXyl2e1z0wQZqccuA40UMAUZdCxJN481z32GKXzpojMm2QtuDZ22d3IWnEMC_BG75bGhkzdUPUUih1b6A7kVOV6OZkgb98QzenErz9AuhvEy7YOv7LTRbPSQx1l-Ap8k3D43uMOQ94MjNapKE5SS0RfgULD5cIztwsz4wGwQ-qVfZrHemV-UlVZcIo-N920AR_shLQVmFhuCZ5xdzKTClNumrkEygDEvYyHNH_keeKKw3IvboeNphgFET_R-XXVZ-kLiy6lPafHpM7HWvE0UMhlnYZBOICiWtlyPTKGpgFHv0VpABEiuqDRAWwEbnYJDHRbPJrGvD36GAGKOOnkrtFpBbJgO6iYLPrGe61E1xitxFytXTY0oLad1x5bihtY1Q1UbU-9DXGsO7v30IY1sFW7GFqzZ7uxraX2JvEUnPhZtX0xXuX-Zu5thyruUxi3UtenKdD1uPP2P2-0Jn24FyzMEvxcR4Q4o8dRSJbuOsRgF1lYKxtiuA8np1AMyCllrAJtGPep-Ky6HeR85GhyKBg6Wdaymbelv6I1vx5TyZBWMWQrQ5Oe-_QmfTApm9dbseN5wJmA-UPUPErQYZkY7lAjbkTQTYlgtLTwCqJH0-voBZTAa8bJVthjLqcAdmFlSA1qmRnOfjXMV_h7-oY%3D/ea-php/7/updates/x86_64/repodata/c3952d44fc771adbea5763f2394d8da5070df25e9ff3cb9d0a409a83b3399cfe-other.sqlite.bz2: [Errno 12] Timeout on https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI1MzUxMTU2OjE3MjU2MTAzNTY6e3qxSuWkS-HRcpLI5Lq_bLFmALXyl2e1z0wQZqccuA40UMAUZdCxJN481z32GKXzpojMm2QtuDZ22d3IWnEMC_BG75bGhkzdUPUUih1b6A7kVOV6OZkgb98QzenErz9AuhvEy7YOv7LTRbPSQx1l-Ap8k3D43uMOQ94MjNapKE5SS0RfgULD5cIztwsz4wGwQ-qVfZrHemV-UlVZcIo-N920AR_shLQVmFhuCZ5xdzKTClNumrkEygDEvYyHNH_keeKKw3IvboeNphgFET_R-XXVZ-kLiy6lPafHpM7HWvE0UMhlnYZBOICiWtlyPTKGpgFHv0VpABEiuqDRAWwEbnYJDHRbPJrGvD36GAGKOOnkrtFpBbJgO6iYLPrGe61E1xitxFytXTY0oLad1x5bihtY1Q1UbU-9DXGsO7v30IY1sFW7GFqzZ7uxraX2JvEUnPhZtX0xXuX-Zu5thyruUxi3UtenKdD1uPP2P2-0Jn24FyzMEvxcR4Q4o8dRSJbuOsRgF1lYKxtiuA8np1AMyCllrAJtGPep-Ky6HeR85GhyKBg6Wdaymbelv6I1vx5TyZBWMWQrQ5Oe-_QmfTApm9dbseN5wJmA-UPUPErQYZkY7lAjbkTQTYlgtLTwCqJH0-voBZTAa8bJVthjLqcAdmFlSA1qmRnOfjXMV_h7-oY=/ea-php/7/updates/x86_64/repodata/c3952d44fc771adbea5763f2394d8da5070df25e9ff3cb9d0a409a83b3399cfe-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-05 02:11:24 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-05 02:11:24 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-05 02:11:24 (7647) [INFO] * 2024-09-05 02:11:24 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-05 02:11:25 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-05 02:11:25 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-05 02:11:25 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-05 02:11:25 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-05 02:11:25 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-05 02:11:25 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-05 02:11:25 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-05 02:11:25 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-05 02:11:25 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-05 02:11:25 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-05 02:11:25 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-05 02:11:25 (7677) [INFO] * 2024-09-05 02:25:37 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-05 02:25:37 (1977) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. * 2024-09-05 02:25:38 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-05 02:25:38 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-05 02:25:38 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-05 02:25:38 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-05 02:25:38 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-05 02:25:53 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5rKdu28omx/ea_profile.json * 2024-09-05 02:25:56 (6788) [INFO] Backed up EA4 profile to /tmp/5rKdu28omx/ea_profile.json * 2024-09-05 02:25:57 (231) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-09-05 02:26:31 (2543) [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-09-05 02:26:31 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-06 01:55:17 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-06 01:59:17 (9014) [INFO] Script is up to date. * 2024-09-06 02:03:21 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-06 02:03:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-06 02:03:21 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-06 02:03:21 (7647) [INFO] * 2024-09-06 02:03:31 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-06 02:03:31 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-06 02:03:31 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-06 02:03:31 (7647) [INFO] * 2024-09-06 02:12:44 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-06 02:23:45 (1966) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30690 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30798 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-06 02:23:45 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-06 02:23:45 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-06 02:23:45 (7647) [INFO] * 2024-09-06 02:23:45 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-06 02:23:45 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-06 02:23:45 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-06 02:23:45 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-06 02:23:45 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-06 02:23:45 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-06 02:23:45 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-06 02:23:45 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-06 02:23:45 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-06 02:23:45 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-06 02:23:46 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-06 02:23:46 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-06 02:23:46 (7677) [INFO] * 2024-09-07 01:48:06 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-07 01:52:06 (9014) [INFO] Script is up to date. * 2024-09-07 01:56:10 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-07 01:56:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-07 01:56:10 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-07 01:56:10 (7647) [INFO] * 2024-09-07 01:56:21 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-07 01:56:21 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-07 01:56:21 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-07 01:56:21 (7647) [INFO] * 2024-09-07 01:56:36 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-07 02:05:08 (1966) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30102 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-07 02:05:08 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-07 02:05:08 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-07 02:05:08 (7647) [INFO] * 2024-09-07 02:05:09 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-07 02:05:09 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-07 02:05:09 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-07 02:05:09 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-07 02:05:09 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-07 02:05:09 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-07 02:05:09 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-07 02:05:09 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-07 02:05:09 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-07 02:05:09 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-07 02:05:10 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-07 02:05:10 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-07 02:05:10 (7677) [INFO] * 2024-09-08 01:47:08 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-08 01:51:09 (9014) [INFO] Script is up to date. * 2024-09-08 01:55:12 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-08 01:55:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-08 01:55:12 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-08 01:55:12 (7647) [INFO] * 2024-09-08 01:55:24 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-08 01:55:24 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-08 01:55:24 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-08 01:55:24 (7647) [INFO] * 2024-09-08 02:15:49 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30658 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30691 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-08 02:15:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-08 02:15:49 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-08 02:15:49 (7647) [INFO] * 2024-09-08 02:15:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-08 02:15:50 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-08 02:15:50 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-08 02:15:50 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-08 02:15:50 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-08 02:15:50 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-08 02:15:50 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-08 02:15:50 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-08 02:15:50 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-08 02:15:50 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-08 02:15:51 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-08 02:15:51 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-08 02:15:51 (7677) [INFO] * 2024-09-09 01:45:41 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-09 01:49:41 (9014) [INFO] Script is up to date. * 2024-09-09 01:53:45 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-09 01:53:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-09 01:53:45 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-09 01:53:45 (7647) [INFO] * 2024-09-09 01:53:56 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-09 01:53:56 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-09 01:53:56 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-09 01:53:56 (7647) [INFO] * 2024-09-09 01:54:08 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-09 02:02:33 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-09-09 02:02:33 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-09 02:02:33 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-09 02:02:33 (7647) [INFO] * 2024-09-09 02:02:33 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-09 02:02:33 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-09 02:02:33 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-09 02:02:33 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-09 02:02:33 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-09 02:02:33 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-09 02:02:33 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-09 02:02:33 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-09 02:02:33 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-09 02:02:33 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-09 02:02:34 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-09 02:02:34 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-09 02:02:34 (7677) [INFO] * 2024-09-10 01:48:08 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-10 01:52:08 (9014) [INFO] Script is up to date. * 2024-09-10 01:56:12 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-10 01:56:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-10 01:56:12 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-10 01:56:12 (7647) [INFO] * 2024-09-10 01:56:25 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-10 01:56:25 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-10 01:56:25 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-10 01:56:25 (7647) [INFO] * 2024-09-10 02:07:55 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-11 01:53:15 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-11 01:57:15 (9014) [INFO] Script is up to date. * 2024-09-11 02:01:18 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-11 02:01:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-11 02:01:19 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-11 02:01:19 (7647) [INFO] * 2024-09-11 02:01:30 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-11 02:01:30 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-11 02:01:30 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-11 02:01:30 (7647) [INFO] * 2024-09-11 02:11:45 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-11 02:22:44 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-11 02:22:44 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-11 02:22:44 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-11 02:22:44 (7647) [INFO] * 2024-09-11 02:22:45 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-11 02:22:45 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-11 02:22:45 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-11 02:22:45 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-11 02:22:45 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-11 02:22:45 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-11 02:22:45 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-11 02:22:45 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-11 02:22:45 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-11 02:22:45 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-11 02:22:46 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-11 02:22:46 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-11 02:22:46 (7677) [INFO] * 2024-09-12 01:45:59 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-12 01:50:00 (9014) [INFO] Script is up to date. * 2024-09-12 01:54:03 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-12 01:54:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-12 01:54:04 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-12 01:54:04 (7647) [INFO] * 2024-09-12 01:54:17 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-12 01:54:17 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-12 01:54:17 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-12 01:54:17 (7647) [INFO] * 2024-09-12 01:54:31 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-12 02:02:03 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2024-09-12 02:02:03 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-12 02:02:03 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-12 02:02:03 (7647) [INFO] * 2024-09-12 02:02:03 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-12 02:02:03 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-12 02:02:03 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-12 02:02:03 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-12 02:02:03 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-12 02:02:03 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-12 02:02:03 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-12 02:02:03 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-12 02:02:03 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-12 02:02:03 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-12 02:02:04 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-12 02:02:04 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-12 02:02:04 (7677) [INFO] * 2024-09-13 01:46:33 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-13 01:50:33 (9014) [INFO] Script is up to date. * 2024-09-13 01:54:37 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-13 01:54:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-13 01:54:37 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-13 01:54:37 (7647) [INFO] * 2024-09-13 01:54:49 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-13 01:54:49 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-13 01:54:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-13 01:54:49 (7647) [INFO] * 2024-09-13 01:55:02 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-13 02:02:31 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-13 02:02:31 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-13 02:02:31 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-13 02:02:31 (7647) [INFO] * 2024-09-13 02:02:32 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-13 02:02:32 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-13 02:02:32 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-13 02:02:32 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-13 02:02:32 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-13 02:02:32 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-13 02:02:32 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-13 02:02:32 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-13 02:02:32 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-13 02:02:32 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-13 02:02:33 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-13 02:02:33 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-13 02:02:33 (7677) [INFO] * 2024-09-14 01:48:29 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-14 01:52:29 (9014) [INFO] Script is up to date. * 2024-09-14 01:56:33 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-14 01:56:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-14 01:56:33 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-14 01:56:33 (7647) [INFO] * 2024-09-14 01:56:45 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-14 01:56:45 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-14 01:56:45 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-14 01:56:45 (7647) [INFO] * 2024-09-14 01:56:59 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-14 02:10:13 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30803 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30798 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30773 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-09-14 02:10:13 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-14 02:10:13 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-14 02:10:13 (7647) [INFO] * 2024-09-14 02:10:14 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-14 02:10:14 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-14 02:10:14 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-14 02:10:14 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-14 02:10:14 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-14 02:10:14 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-14 02:10:14 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-14 02:10:14 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-14 02:10:14 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-14 02:10:14 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-14 02:10:15 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-14 02:10:15 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-14 02:10:15 (7677) [INFO] * 2024-09-15 01:48:17 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-15 01:52:17 (9014) [INFO] Script is up to date. * 2024-09-15 01:56:20 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-15 01:56:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-15 01:56:21 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-15 01:56:21 (7647) [INFO] * 2024-09-15 02:07:16 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-15 02:07:16 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-15 02:07:16 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-15 02:07:16 (7647) [INFO] * 2024-09-15 02:07:28 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-15 02:16:57 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-15 02:16:57 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-15 02:16:57 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-15 02:16:57 (7647) [INFO] * 2024-09-15 02:16:57 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-15 02:16:57 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-15 02:16:57 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-15 02:16:57 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-15 02:16:57 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-15 02:16:57 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-15 02:16:57 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-15 02:16:57 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-15 02:16:57 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-15 02:16:57 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-15 02:16:58 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-15 02:16:58 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-15 02:16:58 (7677) [INFO] * 2024-09-15 02:17:30 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-15 02:17:30 (1977) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-09-15 02:17:31 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-15 02:17:31 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-15 02:17:31 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-15 02:17:31 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-15 02:17:31 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-16 01:45:20 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-16 01:49:21 (9014) [INFO] Script is up to date. * 2024-09-16 01:53:24 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-16 01:53:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-16 01:53:24 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-16 01:53:24 (7647) [INFO] * 2024-09-16 01:53:35 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-16 01:53:35 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-16 01:53:35 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-16 01:53:35 (7647) [INFO] * 2024-09-16 02:00:00 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-16 02:11:37 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-09-16 02:11:37 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-16 02:11:37 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-16 02:11:37 (7647) [INFO] * 2024-09-16 02:11:38 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-16 02:11:38 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-16 02:11:38 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-16 02:11:38 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-16 02:11:38 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-16 02:11:38 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-16 02:11:38 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-16 02:11:38 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-16 02:11:38 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-16 02:11:38 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-16 02:11:39 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-16 02:11:39 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-16 02:11:39 (7677) [INFO] * 2024-09-17 02:16:34 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-17 02:20:35 (9014) [INFO] Script is up to date. * 2024-09-17 02:24:38 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-17 02:24:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-17 02:24:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-17 02:24:38 (7647) [INFO] * 2024-09-17 02:35:32 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-17 02:35:32 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-17 02:35:32 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-17 02:35:32 (7647) [INFO] * 2024-09-17 02:35:43 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-17 02:41:50 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-17 02:41:50 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-17 02:41:50 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-17 02:41:50 (7647) [INFO] * 2024-09-17 02:41:51 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-17 02:41:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-17 02:41:51 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-17 02:41:51 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-17 02:41:51 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-17 02:41:51 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-17 02:41:51 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-17 02:41:51 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-17 02:41:51 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-17 02:41:51 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-17 02:41:52 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-17 02:41:52 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-17 02:41:52 (7677) [INFO] * 2024-09-17 02:42:24 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-17 02:42:24 (1977) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-09-17 02:42:25 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-17 02:42:25 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-17 02:42:25 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-17 02:42:25 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-17 02:42:25 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-18 02:21:55 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-18 02:25:55 (9014) [INFO] Script is up to date. * 2024-09-18 02:29:59 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-18 02:29:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-18 02:29:59 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-18 02:29:59 (7647) [INFO] * 2024-09-18 02:30:03 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-18 02:30:03 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-18 02:30:03 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-18 02:30:03 (7647) [INFO] * 2024-09-18 02:31:10 (1966) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-09-18 02:31:10 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-18 02:31:10 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-18 02:31:10 (7647) [INFO] * 2024-09-18 02:31:11 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-18 02:31:11 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-18 02:31:11 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-18 02:31:11 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-18 02:31:11 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-18 02:31:11 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-18 02:31:11 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-18 02:31:11 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-18 02:31:11 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-18 02:31:11 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-18 02:31:11 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-18 02:31:11 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-18 02:31:11 (7677) [INFO] * 2024-09-18 02:37: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-18 02:37:05 (1977) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30009 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to vault.centos.org:443; Operation now in progress" Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30047 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30004 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') 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. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30009 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to vault.centos.org:443; Operation now in progress" https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30047 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30004 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2024-09-18 02:37:06 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-18 02:37:06 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-18 02:37:06 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-18 02:37:06 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-18 02:37:06 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-19 01:59:41 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-19 02:03:42 (9014) [INFO] Script is up to date. * 2024-09-19 02:07:45 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-19 02:07:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-19 02:07:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-19 02:07:46 (7647) [INFO] * 2024-09-19 02:08:28 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-19 02:08:28 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-19 02:08:28 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-19 02:08:28 (7647) [INFO] * 2024-09-19 02:17:28 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-19 02:25:50 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-09-19 02:25:50 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-19 02:25:50 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-19 02:25:50 (7647) [INFO] * 2024-09-19 02:25:51 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-19 02:25:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-19 02:25:51 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-19 02:25:51 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-19 02:25:51 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-19 02:25:51 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-19 02:25:51 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-19 02:25:51 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-19 02:25:51 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-19 02:25:51 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-19 02:25:52 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-19 02:25:52 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-19 02:25:52 (7677) [INFO] * 2024-09-19 02:26:24 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-19 02:26:24 (1977) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-09-19 02:26:25 (1467) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-09-19 02:26:25 (231) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-09-19 02:26:25 (1565) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-09-19 02:26:25 (1571) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-09-19 02:26:25 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-19 02:26:40 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Sjjh9l1lA_/ea_profile.json * 2024-09-20 01:48:57 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-20 01:52:58 (9014) [INFO] Script is up to date. * 2024-09-20 01:57:01 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-20 01:57:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-20 01:57:02 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-20 01:57:02 (7647) [INFO] * 2024-09-20 01:57:12 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-20 01:57:12 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-20 01:57:12 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-20 01:57:12 (7647) [INFO] * 2024-09-20 02:05:45 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-20 02:17:17 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. * 2024-09-20 02:17:17 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-20 02:17:17 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-20 02:17:17 (7647) [INFO] * 2024-09-20 02:17:17 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-20 02:17:18 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-20 02:17:18 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-20 02:17:18 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-20 02:17:18 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-20 02:17:18 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-20 02:17:18 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-20 02:17:18 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-20 02:17:18 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-20 02:17:18 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-20 02:17:19 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-20 02:17:19 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-20 02:17:19 (7677) [INFO] * 2024-09-21 01:59:21 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-21 02:03:21 (9014) [INFO] Script is up to date. * 2024-09-21 02:07:25 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-21 02:07:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-21 02:07:25 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-21 02:07:25 (7647) [INFO] * 2024-09-21 02:07:36 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-21 02:07:36 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-21 02:07:36 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-21 02:07:36 (7647) [INFO] * 2024-09-21 02:26:06 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/44abd0f9f867b1349a5925276b44cd0d2976dc691dc52fdfad14a0834dfcd670-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/19699a08b0728d8fcb697ee242e809d5531825194b41494bb28b60e8d04187e3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/22593f84dc8dfb57c9596eeee161e8ceeb5fe44d4823aaf55d19c25f374d6d31-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI2NzUyNjkzOjE3MjcwMTE4OTM6D-WzZcypo72fk1T8TkgZIjdh98Sk3BUuspkpkvP0rx-59VR0L0Wlmf7tb2p0xDM5ze968FeSWsuGci0E-txXlgGLCK4yKLSnTVWf5SOsMRAO8GrVlA9zFesekLgKWBDE6YnvXJ4_ZJUgel1borig36l6T9ZsIEQg0B8k4NuNHASqHgciGHdHw0ZncgzoRPjfUc6TbleOg2QRcG60Bj1i5O5tT_XP3aHYa3T6Fm-Oxr2tqHs4b0Y1ulALSxemTqZNuAkK1XSF02jy6th5NHmhdL56kPRCxog-hqaaDHVKWtXZF-NFMtf8jHuUFHG55a2dgp-_HFwbwtRuMvDnXVFCc0y271MIUpULVisPhI7GqvP_YJTK5mUCg4bTo1Lnoee8HhlWRND3DJzOyJcYbkstpkcNtRQsndczSgfyG4YC-0uOoYH8PIybaCepj3ihXY-cL51B2q16rKwRbUHhpqBC6KGbFAuAjJQM9Nu05HBOPwafWva1Iv9VvuyShTn0pY1S25ffnVxGwbE9qTxr8jiXJMn_mpij5HOhjDgsMpNY5at_oNaYMXZwlza0kG3-nK8BmMxH8k9QXWrZimnlif9DOqb3GDwULLURxNtj5ZlAwklJ61YWBdqNnxuK_NU3wxiuCIRwi4H0yX878SVYK2QZWWxXWv1d-XUNeCScVlS34lU%3D/ea-php/7/updates/x86_64/repodata/2ba859a740e8ebb4fa138003fa3aeeb8b92602e6463bdd9b0b64fefe21668feb-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/wp-toolkit/repodata/42ad3a6d00363e5a4575f63d414ee5c4968714e58a3799cff08325db47fdfb66-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30916 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-09-21 02:26:06 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-21 02:26:06 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-21 02:26:06 (7647) [INFO] * 2024-09-21 02:26:06 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-21 02:26:06 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-21 02:26:06 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-21 02:26:06 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-21 02:26:06 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-21 02:26:06 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-21 02:26:06 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-21 02:26:06 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-21 02:26:06 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-21 02:26:06 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-21 02:26:08 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-21 02:26:08 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-21 02:26:08 (7677) [INFO] * 2024-09-22 01:46:56 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-22 01:50:56 (9014) [INFO] Script is up to date. * 2024-09-22 01:55:00 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-22 01:55:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-22 01:55:00 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-22 01:55:00 (7647) [INFO] * 2024-09-22 01:55:11 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-22 01:55:11 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-22 01:55:11 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-22 01:55:11 (7647) [INFO] * 2024-09-22 01:55:24 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-22 02:11:22 (1966) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') 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 extras: Check uncompressed DB failed * 2024-09-22 02:11:22 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-22 02:11:22 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-22 02:11:22 (7647) [INFO] * 2024-09-22 02:11:22 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-22 02:11:23 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-22 02:11:23 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-22 02:11:23 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-22 02:11:23 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-22 02:11:23 (7660) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-22 02:11:23 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-22 02:11:23 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-22 02:11:23 (7660) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-22 02:11:23 (7660) [INFO] : wp-toolkit-thirdparties * 2024-09-22 02:11:23 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-22 02:11:23 (7660) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-22 02:11:23 (7677) [INFO] * 2024-09-23 01:45:07 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-23 01:49:08 (9014) [INFO] Script is up to date. * 2024-09-23 01:53:11 (2245) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-23 01:53:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-23 01:53:11 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-23 01:53:11 (7647) [INFO] * 2024-09-23 01:53:22 (676) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-23 01:53:22 (683) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-23 01:53:22 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-23 01:53:22 (7647) [INFO] * 2024-09-23 02:00:49 (231) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-24 01:47:14 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-24 01:51:15 (8997) [INFO] Newer version of script found. Downloading. * 2024-09-24 01:55:16 (9006) [INFO] Script update to version 54 successful. * 2024-09-24 01:59:19 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-24 01:59:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-24 01:59:19 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-24 01:59:19 (7667) [INFO] * 2024-09-24 01:59:30 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-24 01:59:30 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-24 01:59:30 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-24 01:59:30 (7667) [INFO] * 2024-09-24 01:59:40 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-24 02:06:33 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2024-09-24 02:06:33 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-24 02:06:33 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-24 02:06:33 (7667) [INFO] * 2024-09-24 02:06:33 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-24 02:06:34 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-24 02:06:34 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-24 02:06:34 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-24 02:06:34 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-24 02:06:34 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-24 02:06:34 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-24 02:06:34 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-24 02:06:34 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-24 02:06:34 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-24 02:06:35 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-24 02:06:35 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-24 02:06:35 (7697) [INFO] * 2024-09-25 01:54:09 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-25 01:58:10 (9030) [INFO] Script is up to date. * 2024-09-25 02:02:12 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-25 02:02:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-25 02:02:13 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-25 02:02:13 (7667) [INFO] * 2024-09-25 02:02:23 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-25 02:02:23 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-25 02:02:23 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-25 02:02:23 (7667) [INFO] * 2024-09-25 02:09:40 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-25 02:16:24 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30658 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-25 02:16:24 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-25 02:16:24 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-25 02:16:24 (7667) [INFO] * 2024-09-25 02:16:25 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-25 02:16:25 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-25 02:16:25 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-25 02:16:25 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-25 02:16:25 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-25 02:16:25 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-25 02:16:25 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-25 02:16:25 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-25 02:16:25 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-25 02:16:25 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-25 02:16:26 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-25 02:16:26 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-25 02:16:26 (7697) [INFO] * 2024-09-26 01:47:47 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-26 01:51:48 (9030) [INFO] Script is up to date. * 2024-09-26 01:55:51 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-26 01:55:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-26 01:55:52 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-26 01:55:52 (7667) [INFO] * 2024-09-26 01:56:02 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-26 01:56:02 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-26 01:56:02 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-26 01:56:02 (7667) [INFO] * 2024-09-26 02:03:29 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-26 02:12:20 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-26 02:12:20 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-26 02:12:20 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-26 02:12:20 (7667) [INFO] * 2024-09-26 02:12:20 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-26 02:12:20 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-26 02:12:20 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-26 02:12:20 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-26 02:12:20 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-26 02:12:20 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-26 02:12:20 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-26 02:12:20 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-26 02:12:20 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-26 02:12:20 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-26 02:12:21 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-26 02:12:21 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-26 02:12:21 (7697) [INFO] * 2024-09-27 01:51:24 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-27 01:55:24 (9030) [INFO] Script is up to date. * 2024-09-27 01:59:28 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-27 01:59:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-27 01:59:28 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-27 01:59:28 (7667) [INFO] * 2024-09-27 01:59:39 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-27 01:59:39 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-27 01:59:39 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-27 01:59:39 (7667) [INFO] * 2024-09-27 02:06:04 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-27 02:15:03 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30322 milliseconds') Trying other mirror. * 2024-09-27 02:15:03 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-27 02:15:03 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-27 02:15:03 (7667) [INFO] * 2024-09-27 02:15:03 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-27 02:15:04 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-27 02:15:04 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-27 02:15:04 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-27 02:15:04 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-27 02:15:04 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-27 02:15:04 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-27 02:15:04 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-27 02:15:04 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-27 02:15:04 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-27 02:15:05 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-27 02:15:05 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-27 02:15:05 (7697) [INFO] * 2024-09-28 01:52:30 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-28 01:56:30 (9030) [INFO] Script is up to date. * 2024-09-28 02:00:33 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-28 02:00:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-28 02:00:33 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-28 02:00:33 (7667) [INFO] * 2024-09-28 02:03:28 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-28 02:03:28 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-28 02:03:28 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-28 02:03:28 (7667) [INFO] * 2024-09-28 02:10:50 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-29 01:47:09 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-29 01:51:10 (9030) [INFO] Script is up to date. * 2024-09-29 01:55:13 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-29 01:55:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-29 01:55:13 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-29 01:55:13 (7667) [INFO] * 2024-09-29 01:55:23 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-29 01:55:23 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-29 01:55:23 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-29 01:55:23 (7667) [INFO] * 2024-09-29 01:55:36 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-29 02:03:55 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-09-29 02:03:55 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-29 02:03:55 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-29 02:03:55 (7667) [INFO] * 2024-09-29 02:03:55 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-29 02:03:55 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-29 02:03:55 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-29 02:03:55 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-29 02:03:55 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-29 02:03:55 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-29 02:03:55 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-29 02:03:55 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-29 02:03:55 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-29 02:03:55 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-29 02:03:56 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-29 02:03:56 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-29 02:03:56 (7697) [INFO] * 2024-09-30 01:47:11 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-30 01:51:12 (9030) [INFO] Script is up to date. * 2024-09-30 01:55:15 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-09-30 01:55:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-09-30 01:55:15 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-30 01:55:15 (7667) [INFO] * 2024-09-30 01:55:27 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-09-30 01:55:27 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-30 01:55:27 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-30 01:55:27 (7667) [INFO] * 2024-09-30 01:55:38 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-09-30 02:04:12 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. * 2024-09-30 02:04:12 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-30 02:04:12 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-30 02:04:12 (7667) [INFO] * 2024-09-30 02:04:13 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-30 02:04:13 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-09-30 02:04:13 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-30 02:04:13 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-30 02:04:13 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-09-30 02:04:13 (7680) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-09-30 02:04:13 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-30 02:04:13 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-30 02:04:13 (7680) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-09-30 02:04:13 (7680) [INFO] : wp-toolkit-thirdparties * 2024-09-30 02:04:14 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-30 02:04:14 (7680) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-09-30 02:04:14 (7697) [INFO] * 2024-10-01 01:49:15 (9008) [INFO] Self-update of script version 54 requested. * 2024-10-01 01:53:16 (9013) [INFO] Newer version of script found. Downloading. * 2024-10-01 01:57:17 (9022) [INFO] Script update to version 55 successful. * 2024-10-01 02:01:20 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-01 02:01:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-01 02:01:21 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-01 02:01:21 (7668) [INFO] * 2024-10-01 02:01:25 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-01 02:01:25 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-01 02:01:25 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-01 02:01:25 (7668) [INFO] * 2024-10-01 02:08:00 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-01 02:17:35 (1995) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30597 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-01 02:17:35 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-01 02:17:35 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-01 02:17:35 (7668) [INFO] * 2024-10-01 02:17:35 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-01 02:17:35 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-01 02:17:35 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-01 02:17:35 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-01 02:17:35 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-01 02:17:35 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-01 02:17:35 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-01 02:17:35 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-01 02:17:35 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-01 02:17:35 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-01 02:17:36 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-01 02:17:36 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-01 02:17:36 (7698) [INFO] * 2024-10-02 01:48:40 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-02 01:52:41 (9031) [INFO] Script is up to date. * 2024-10-02 01:56:44 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-02 01:56:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-02 01:56:44 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-02 01:56:44 (7668) [INFO] * 2024-10-02 01:56:55 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-02 01:56:55 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-02 01:56:55 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-02 01:56:55 (7668) [INFO] * 2024-10-02 02:02:51 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-02 02:12:56 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-02 02:12:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-02 02:12:56 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-02 02:12:56 (7668) [INFO] * 2024-10-02 02:12:56 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-02 02:12:56 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-02 02:12:56 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-02 02:12:56 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-02 02:12:56 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-02 02:12:56 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-02 02:12:56 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-02 02:12:56 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-02 02:12:56 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-02 02:12:56 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-02 02:12:57 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-02 02:12:57 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-02 02:12:57 (7698) [INFO] * 2024-10-03 01:55:02 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-03 01:59:03 (9031) [INFO] Script is up to date. * 2024-10-03 02:03:06 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-03 02:03:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-03 02:03:06 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-03 02:03:06 (7668) [INFO] * 2024-10-03 02:03:17 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-03 02:03:17 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-03 02:03:17 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-03 02:03:17 (7668) [INFO] * 2024-10-03 02:09:12 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-03 02:16:41 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30029 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-03 02:16:41 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-03 02:16:41 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-03 02:16:41 (7668) [INFO] * 2024-10-03 02:16:41 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-03 02:16:41 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-03 02:16:41 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-03 02:16:41 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-03 02:16:41 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-03 02:16:41 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-03 02:16:41 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-03 02:16:41 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-03 02:16:41 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-03 02:16:41 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-03 02:16:42 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-03 02:16:42 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-03 02:16:42 (7698) [INFO] * 2024-10-03 02:17:14 (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 02:17:14 (2006) [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 * 2024-10-03 02:17:15 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-03 02:17:15 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-03 02:17:15 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-03 02:17:15 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-03 02:17:15 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-03 02:17:27 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mTyh7YlNPA/ea_profile.json * 2024-10-03 02:24:12 (6826) [INFO] Backed up EA4 profile to /tmp/mTyh7YlNPA/ea_profile.json * 2024-10-03 02:24:12 (230) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-10-03 02:24:46 (2573) [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-10-03 02:24:46 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-04 01:45:47 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-04 01:49:47 (9031) [INFO] Script is up to date. * 2024-10-04 01:53:50 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-04 01:53:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-04 01:53:51 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-04 01:53:51 (7668) [INFO] * 2024-10-04 01:54:01 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-04 01:54:01 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-04 01:54:01 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-04 01:54:01 (7668) [INFO] * 2024-10-04 01:54:12 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-04 02:06:20 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-04 02:06:20 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-04 02:06:20 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-04 02:06:20 (7668) [INFO] * 2024-10-04 02:06:21 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-04 02:06:21 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-04 02:06:21 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-04 02:06:21 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-04 02:06:21 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-04 02:06:21 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-04 02:06:21 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-04 02:06:21 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-04 02:06:21 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-04 02:06:21 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-04 02:06:22 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-04 02:06:22 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-04 02:06:22 (7698) [INFO] * 2024-10-05 01:48:39 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-05 01:52:40 (9031) [INFO] Script is up to date. * 2024-10-05 01:56:43 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-05 01:56:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-05 01:56:43 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-05 01:56:43 (7668) [INFO] * 2024-10-05 01:56:55 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-05 01:56:55 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-05 01:56:55 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-05 01:56:55 (7668) [INFO] * 2024-10-05 01:57:08 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-05 02:06:57 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-05 02:06:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-05 02:06:57 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-05 02:06:57 (7668) [INFO] * 2024-10-05 02:06:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-05 02:06:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-05 02:06:57 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-05 02:06:57 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-05 02:06:57 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-05 02:06:57 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-05 02:06:57 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-05 02:06:57 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-05 02:06:57 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-05 02:06:57 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-05 02:06:58 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-05 02:06:58 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-05 02:06:58 (7698) [INFO] * 2024-10-05 02:07: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-05 02:07:30 (2006) [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 * 2024-10-05 02:07:31 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-05 02:07:31 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-05 02:07:31 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-05 02:07:31 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-05 02:07:31 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-05 02:09:47 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YjME0spnyT/ea_profile.json * 2024-10-06 01:47:08 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-06 01:51:08 (9031) [INFO] Script is up to date. * 2024-10-06 01:55:11 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-06 01:55:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-06 01:55:11 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-06 01:55:11 (7668) [INFO] * 2024-10-06 01:55:15 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-06 01:55:15 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-06 01:55:15 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-06 01:55:15 (7668) [INFO] * 2024-10-06 01:55:26 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-06 02:01:37 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30004 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-06 02:01:37 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-06 02:01:37 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-06 02:01:37 (7668) [INFO] * 2024-10-06 02:01:38 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-06 02:01:38 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-06 02:01:38 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-06 02:01:38 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-06 02:01:38 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-06 02:01:38 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-06 02:01:38 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-06 02:01:38 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-06 02:01:38 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-06 02:01:38 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-06 02:01:39 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-06 02:01:39 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-06 02:01:39 (7698) [INFO] * 2024-10-06 02:16:24 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-06 02:16:24 (2006) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/wp-toolkit/repodata/42ad3a6d00363e5a4575f63d414ee5c4968714e58a3799cff08325db47fdfb66-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.3/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-10-06 02:16:25 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-06 02:16:25 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-06 02:16:25 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-06 02:16:25 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-06 02:16:25 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-06 02:16:33 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/klJcQOPLbp/ea_profile.json * 2024-10-06 02:16:35 (6826) [INFO] Backed up EA4 profile to /tmp/klJcQOPLbp/ea_profile.json * 2024-10-06 02:16:36 (230) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-10-07 01:45:58 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-07 01:49:58 (9031) [INFO] Script is up to date. * 2024-10-07 01:54:01 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-07 01:54:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-07 01:54:02 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-07 01:54:02 (7668) [INFO] * 2024-10-07 01:54:05 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-07 01:54:05 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-07 01:54:05 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-07 01:54:05 (7668) [INFO] * 2024-10-07 01:54:14 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-07 02:00:00 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. * 2024-10-07 02:00:00 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-07 02:00:00 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-07 02:00:00 (7668) [INFO] * 2024-10-07 02:00:00 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-07 02:00:01 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-07 02:00:01 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-07 02:00:01 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-07 02:00:01 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-07 02:00:01 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-07 02:00:01 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-07 02:00:01 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-07 02:00:01 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-07 02:00:01 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-07 02:00:02 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-07 02:00:02 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-07 02:00:02 (7698) [INFO] * 2024-10-08 01:55:00 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-08 01:59:01 (9031) [INFO] Script is up to date. * 2024-10-08 02:03:04 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-08 02:03:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-08 02:03:04 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-08 02:03:04 (7668) [INFO] * 2024-10-08 02:03:08 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-08 02:03:08 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-08 02:03:08 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-08 02:03:08 (7668) [INFO] * 2024-10-08 02:08:59 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-08 02:18:01 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-08 02:18:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-08 02:18:01 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-08 02:18:01 (7668) [INFO] * 2024-10-08 02:18:02 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-08 02:18:02 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-08 02:18:02 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-08 02:18:02 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-08 02:18:02 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-08 02:18:02 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-08 02:18:02 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-08 02:18:02 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-08 02:18:02 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-08 02:18:02 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-08 02:18:03 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-08 02:18:03 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-08 02:18:03 (7698) [INFO] * 2024-10-08 02:18:36 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-08 02:18:36 (2006) [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 * 2024-10-08 02:18:37 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-08 02:18:37 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-08 02:18:37 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-08 02:18:37 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-08 02:18:37 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-08 02:18:42 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IZhcgs6vkt/ea_profile.json * 2024-10-09 02:16:11 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-09 02:20:12 (9031) [INFO] Script is up to date. * 2024-10-09 02:24:15 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-09 02:24:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-09 02:24:15 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-09 02:24:15 (7668) [INFO] * 2024-10-09 02:24:18 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-09 02:24:18 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-09 02:24:18 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-09 02:24:18 (7668) [INFO] * 2024-10-09 02:24:32 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-09 02:31:34 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2024-10-09 02:31:34 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-09 02:31:34 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-09 02:31:34 (7668) [INFO] * 2024-10-09 02:31:34 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-09 02:31:35 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-09 02:31:35 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-09 02:31:35 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-09 02:31:35 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-09 02:31:35 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-09 02:31:35 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-09 02:31:35 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-09 02:31:35 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-09 02:31:35 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-09 02:31:35 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-09 02:31:35 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-09 02:31:35 (7698) [INFO] * 2024-10-10 01:46:43 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-10 01:50:44 (9031) [INFO] Script is up to date. * 2024-10-10 01:54:47 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-10 01:54:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-10 01:54:48 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-10 01:54:48 (7668) [INFO] * 2024-10-10 01:54:58 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-10 01:54:58 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-10 01:54:58 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-10 01:54:58 (7668) [INFO] * 2024-10-10 01:55:10 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-10 02:04:17 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-10 02:04:17 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-10 02:04:17 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-10 02:04:17 (7668) [INFO] * 2024-10-10 02:04:18 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-10 02:04:18 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-10 02:04:18 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-10 02:04:18 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-10 02:04:18 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-10 02:04:18 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-10 02:04:18 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-10 02:04:18 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-10 02:04:18 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-10 02:04:18 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-10 02:04:19 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-10 02:04:19 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-10 02:04:19 (7698) [INFO] * 2024-10-11 01:46:04 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-11 01:50:05 (9031) [INFO] Script is up to date. * 2024-10-11 01:54:08 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-11 01:54:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-11 01:54:08 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-11 01:54:08 (7668) [INFO] * 2024-10-11 01:54:17 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-11 01:54:17 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-11 01:54:17 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-11 01:54:17 (7668) [INFO] * 2024-10-11 01:59:43 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-11 01:59:43 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-11 01:59:43 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-11 01:59:43 (7668) [INFO] * 2024-10-11 01:59:43 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-11 01:59:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-11 01:59:43 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-11 01:59:43 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-11 01:59:43 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-11 01:59:43 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-11 01:59:43 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-11 01:59:43 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-11 01:59:43 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-11 01:59:43 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-11 01:59:43 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-11 01:59:43 (7681) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-10-11 01:59:44 (7698) [INFO] * 2024-10-11 02:03: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-11 02:03:04 (2006) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-11 02:03:05 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-11 02:03:05 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-11 02:03:05 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-11 02:03:05 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-11 02:03:05 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-11 02:07:11 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lqU5EoTaGl/ea_profile.json * 2024-10-11 02:10:00 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lqU5EoTaGl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-11 02:10:01 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-12 01:51:09 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-12 01:55:10 (9031) [INFO] Script is up to date. * 2024-10-12 01:59:13 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-12 01:59:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-12 01:59:13 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-12 01:59:13 (7668) [INFO] * 2024-10-12 01:59:24 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-12 01:59:24 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-12 01:59:24 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-12 01:59:24 (7668) [INFO] * 2024-10-12 02:02:49 (1995) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30093 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-12 02:02:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-12 02:02:49 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-12 02:02:49 (7668) [INFO] * 2024-10-12 02:02:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-12 02:02:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-12 02:02:50 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-12 02:02:50 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-12 02:02:50 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-12 02:02:50 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-12 02:02:50 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-12 02:02:50 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-12 02:02:50 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-12 02:02:50 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-12 02:02:50 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-12 02:02:50 (7681) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2024-10-12 02:02:50 (7698) [INFO] * 2024-10-12 02:07:43 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-12 02:07:43 (2006) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-12 02:07:44 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-12 02:07:44 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-12 02:07:44 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-12 02:07:44 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-12 02:07:44 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-12 02:12:17 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iUFFSRELC0/ea_profile.json * 2024-10-12 02:12:20 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iUFFSRELC0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-12 02:12:20 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-13 01:47:13 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-13 01:51:13 (9031) [INFO] Script is up to date. * 2024-10-13 01:55:17 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-13 01:55:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-13 01:55:17 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-13 01:55:17 (7668) [INFO] * 2024-10-13 01:55:28 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-13 01:55:28 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-13 01:55:28 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-13 01:55:28 (7668) [INFO] * 2024-10-13 01:58:23 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-13 01:58:23 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-13 01:58:23 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-13 01:58:23 (7668) [INFO] * 2024-10-13 01:58:24 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-13 01:58:24 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-13 01:58:24 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-13 01:58:24 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-13 01:58:24 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-13 01:58:24 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-13 01:58:24 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-13 01:58:24 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-13 01:58:24 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-13 01:58:24 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-13 01:58:24 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-13 01:58:24 (7681) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-10-13 01:58:24 (7698) [INFO] * 2024-10-13 02:01:13 (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 02:01:13 (2006) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-13 02:01:14 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-13 02:01:14 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-13 02:01:14 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-13 02:01:14 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-13 02:01:14 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-13 02:01:20 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/diaTXzEDic/ea_profile.json * 2024-10-13 02:03:38 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/diaTXzEDic/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-13 02:03:38 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-14 01:45:02 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-14 01:49:02 (9031) [INFO] Script is up to date. * 2024-10-14 01:53:06 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-14 01:53:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-14 01:53:06 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-14 01:53:06 (7668) [INFO] * 2024-10-14 01:53:09 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-14 01:53:09 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-14 01:53:09 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-14 01:53:09 (7668) [INFO] * 2024-10-14 01:56:06 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-14 01:56:06 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-14 01:56:06 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-14 01:56:06 (7668) [INFO] * 2024-10-14 01:56:07 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-14 01:56:07 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-14 01:56:07 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-14 01:56:07 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-14 01:56:07 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-14 01:56:07 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-14 01:56:07 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-14 01:56:07 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-14 01:56:07 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-14 01:56:07 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-14 01:56:07 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-14 01:56:07 (7681) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-10-14 01:56:07 (7698) [INFO] * 2024-10-14 01:58:24 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-14 01:58:24 (2006) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzI4MzczNjcyOjE3Mjg2MzI4NzI6qbW5_Sz8FswlgimfSBv9_VnRYZv6Q1RRc-s6vlbmwK7hvU65lSqAl3fJrayVUZG8NWoq3Ovk4d5cS-HRtwqfrniFnhYDT6Kqq2YA3m5s5s_VZ5EWRSJAP_u_X79AR7uShYHUQdSM03mzQaN0sXSj11sXCbEh8Pv2ks2XQmL6iSoHyAJZhNRIdW1nlCUJ38tJJedqyxaQ7uulFnAdzOsf2F-rWq5l_-hhbJ4rBbFL89xGWgsQbJ7mKZ9KyRUj418Ci4UTjdPFJ44OZaFJz7IBWmjAraqOilqCbRPqPYEIjmT_Y-JGWRGNzpWI4PzzIxybybPHqZORG6Hr_Nnc5oXSWi8nNLRWHK4ghIU2ndzztbZzdWPchKxyoIOOWNXw37dMy5kRi3Pzcdr9nIXF3eellfQEDpBbCPGQb_z6yU5_fXudmrJGseIrZEl-oMPiQQR9UnHCtceqBaWLvNCI09jDAKHf8o01EyXCl6YJ1EhHv2y5tlob3h-3EZmRBszeOY0CLeSwbpD3F6UsXN_gkmx8l6uB-nP5A_ZG0ABMgpXuy1MXpZoco5sbOyg_OmxyJ0wUSW_4o93UzTxv-YvhBZblDIVJOQ-HsCtPyRugTDsCBCEmUbCSJ5Wu9oHIzeIxEXS5rPGRh2Xd0Z4Dm0DcyAhNrmLyveQdgddHJmFQohV2n3g=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-10-14 01:58:25 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-14 01:58:25 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-14 01:58:25 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-14 01:58:25 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-14 01:58:25 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-14 01:58:33 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/grWLTYS9Ib/ea_profile.json * 2024-10-14 02:01:53 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/grWLTYS9Ib/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-14 02:01:53 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-15 01:44:44 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-15 01:48:44 (9031) [INFO] Script is up to date. * 2024-10-15 01:52:48 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-15 01:52:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-15 01:52:48 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-15 01:52:48 (7668) [INFO] * 2024-10-15 01:52:51 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-15 01:52:51 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-15 01:52:51 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-15 01:52:51 (7668) [INFO] * 2024-10-15 01:58:02 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-15 02:06:38 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-15 02:06:38 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-15 02:06:38 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-15 02:06:38 (7668) [INFO] * 2024-10-15 02:06:38 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-15 02:06:39 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-15 02:06:39 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-15 02:06:39 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-15 02:06:39 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-15 02:06:39 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-15 02:06:39 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-15 02:06:39 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-15 02:06:39 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-15 02:06:39 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-15 02:06:40 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-15 02:06:40 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-15 02:06:40 (7698) [INFO] * 2024-10-16 01:57:18 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-16 02:01:19 (9031) [INFO] Script is up to date. * 2024-10-16 02:05:22 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-16 02:05:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-16 02:05:23 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-16 02:05:23 (7668) [INFO] * 2024-10-16 02:05:27 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-16 02:05:27 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-16 02:05:27 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-16 02:05:27 (7668) [INFO] * 2024-10-16 02:12:33 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-16 02:21:01 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-16 02:21:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-16 02:21:01 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-16 02:21:01 (7668) [INFO] * 2024-10-16 02:21:01 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-16 02:21:02 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-16 02:21:02 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-16 02:21:02 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-16 02:21:02 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-16 02:21:02 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-16 02:21:02 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-16 02:21:02 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-16 02:21:02 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-16 02:21:02 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-16 02:21:03 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-16 02:21:03 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-16 02:21:03 (7698) [INFO] * 2024-10-16 02:21:34 (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 02:21:34 (2006) [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 * 2024-10-16 02:21:35 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-16 02:21:35 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-16 02:21:35 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-16 02:21:35 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-16 02:21:35 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-16 02:21:41 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UNqIO6XpUO/ea_profile.json * 2024-10-17 01:46:28 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-17 01:50:28 (9031) [INFO] Script is up to date. * 2024-10-17 01:54:32 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-17 01:54:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-17 01:54:32 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-17 01:54:32 (7668) [INFO] * 2024-10-17 01:54:36 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-17 01:54:36 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-17 01:54:36 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-17 01:54:36 (7668) [INFO] * 2024-10-17 01:54:48 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-17 02:04:56 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30537 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-17 02:04:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-17 02:04:56 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-17 02:04:56 (7668) [INFO] * 2024-10-17 02:04:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-17 02:04:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-17 02:04:57 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-17 02:04:57 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-17 02:04:57 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-17 02:04:57 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-17 02:04:57 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-17 02:04:57 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-17 02:04:57 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-17 02:04:57 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-17 02:04:58 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-17 02:04:58 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-17 02:04:58 (7698) [INFO] * 2024-10-18 01:54:14 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-18 01:58:14 (9031) [INFO] Script is up to date. * 2024-10-18 02:02:18 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-18 02:02:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-18 02:02:18 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-18 02:02:18 (7668) [INFO] * 2024-10-18 02:02:22 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-18 02:02:22 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-18 02:02:22 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-18 02:02:22 (7668) [INFO] * 2024-10-18 02:11:10 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-18 02:20:11 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-18 02:20:11 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-18 02:20:11 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-18 02:20:11 (7668) [INFO] * 2024-10-18 02:20:11 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-18 02:20:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-18 02:20:12 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-18 02:20:12 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-18 02:20:12 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-18 02:20:12 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-18 02:20:12 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-18 02:20:12 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-18 02:20:12 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-18 02:20:12 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-18 02:20:13 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-18 02:20:13 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-18 02:20:13 (7698) [INFO] * 2024-10-19 01:46:58 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-19 01:50:58 (9031) [INFO] Script is up to date. * 2024-10-19 01:55:02 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-19 01:55:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-19 01:55:02 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-19 01:55:02 (7668) [INFO] * 2024-10-19 01:55:06 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-19 01:55:06 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-19 01:55:06 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-19 01:55:06 (7668) [INFO] * 2024-10-19 01:55:18 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-19 02:04:26 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30916 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-10-19 02:04:26 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-19 02:04:26 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-19 02:04:26 (7668) [INFO] * 2024-10-19 02:04:26 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-19 02:04:26 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-19 02:04:26 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-19 02:04:26 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-19 02:04:26 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-19 02:04:26 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-19 02:04:26 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-19 02:04:26 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-19 02:04:26 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-19 02:04:26 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-19 02:04:27 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-19 02:04:27 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-19 02:04:27 (7698) [INFO] * 2024-10-20 01:47:11 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-20 01:51:12 (9031) [INFO] Script is up to date. * 2024-10-20 01:55:15 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-20 01:55:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-20 01:55:15 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-20 01:55:15 (7668) [INFO] * 2024-10-20 01:55:20 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-20 01:55:20 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-20 01:55:20 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-20 01:55:20 (7668) [INFO] * 2024-10-20 01:55:31 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-20 02:05:38 (1995) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30544 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-20 02:05:38 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-20 02:05:38 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-20 02:05:38 (7668) [INFO] * 2024-10-20 02:05:39 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-20 02:05:39 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-20 02:05:39 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-20 02:05:39 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-20 02:05:39 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-20 02:05:39 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-20 02:05:39 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-20 02:05:39 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-20 02:05:39 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-20 02:05:39 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-20 02:05:40 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-20 02:05:40 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-20 02:05:40 (7698) [INFO] * 2024-10-21 01:46:21 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-21 01:50:22 (9031) [INFO] Script is up to date. * 2024-10-21 01:54:25 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-21 01:54:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-21 01:54:25 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-21 01:54:25 (7668) [INFO] * 2024-10-21 01:54:29 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-21 01:54:29 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-21 01:54:29 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-21 01:54:29 (7668) [INFO] * 2024-10-21 01:54:40 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-21 02:05:42 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-10-21 02:05:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-21 02:05:42 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-21 02:05:42 (7668) [INFO] * 2024-10-21 02:05:42 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-21 02:05:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-21 02:05:43 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-21 02:05:43 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-21 02:05:43 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-21 02:05:43 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-21 02:05:43 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-21 02:05:43 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-21 02:05:43 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-21 02:05:43 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-21 02:05:44 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-21 02:05:44 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-21 02:05:44 (7698) [INFO] * 2024-10-21 02:06:17 (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 02:06:17 (2006) [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 * 2024-10-21 02:06:18 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-21 02:06:18 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-21 02:06:18 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-21 02:06:18 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-21 02:06:18 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-21 02:06:26 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/M5jioD_vZr/ea_profile.json * 2024-10-21 02:13:25 (6826) [INFO] Backed up EA4 profile to /tmp/M5jioD_vZr/ea_profile.json * 2024-10-21 02:13:26 (230) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-10-21 02:14:00 (2573) [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-10-21 02:14:00 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-22 01:45:24 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-22 01:49:24 (9031) [INFO] Script is up to date. * 2024-10-22 01:53:27 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-22 01:53:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-22 01:53:28 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-22 01:53:28 (7668) [INFO] * 2024-10-22 01:53:32 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-22 01:53:32 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-22 01:53:32 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-22 01:53:32 (7668) [INFO] * 2024-10-22 01:55:30 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-22 02:07:11 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30883 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-10-22 02:07:11 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-22 02:07:11 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-22 02:07:11 (7668) [INFO] * 2024-10-22 02:07:12 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-22 02:07:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-22 02:07:12 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-22 02:07:12 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-22 02:07:12 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-22 02:07:12 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-22 02:07:12 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-22 02:07:12 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-22 02:07:12 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-22 02:07:12 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-22 02:07:13 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-22 02:07:13 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-22 02:07:13 (7698) [INFO] * 2024-10-23 01:47:26 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-23 01:51:26 (9031) [INFO] Script is up to date. * 2024-10-23 01:55:29 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-23 01:55:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-23 01:55:30 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-23 01:55:30 (7668) [INFO] * 2024-10-23 01:55:34 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-23 01:55:34 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-23 01:55:34 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-23 01:55:34 (7668) [INFO] * 2024-10-23 02:08:24 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-23 02:08:24 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-23 02:08:24 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-23 02:08:24 (7668) [INFO] * 2024-10-23 02:08:24 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-23 02:08:25 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-23 02:08:25 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-23 02:08:25 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-23 02:08:25 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-23 02:08:25 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-23 02:08:25 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-23 02:08:25 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-23 02:08:25 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-23 02:08:25 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-23 02:08:26 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-23 02:08:26 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-23 02:08:26 (7698) [INFO] * 2024-10-24 01:46:08 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-24 01:50:08 (9031) [INFO] Script is up to date. * 2024-10-24 01:54:12 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-24 01:54:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-24 01:54:12 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-24 01:54:12 (7668) [INFO] * 2024-10-24 01:54:16 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-24 01:54:16 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-24 01:54:16 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-24 01:54:16 (7668) [INFO] * 2024-10-24 02:09:48 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30693 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-24 02:09:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-24 02:09:48 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-24 02:09:48 (7668) [INFO] * 2024-10-24 02:09:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-24 02:09:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-24 02:09:49 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-24 02:09:49 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-24 02:09:49 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-24 02:09:49 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-24 02:09:49 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-24 02:09:49 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-24 02:09:49 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-24 02:09:49 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-24 02:09:50 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-24 02:09:50 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-24 02:09:50 (7698) [INFO] * 2024-10-25 01:57:56 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-25 02:01:56 (9031) [INFO] Script is up to date. * 2024-10-25 02:06:00 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-25 02:06:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-25 02:06:00 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-25 02:06:00 (7668) [INFO] * 2024-10-25 02:06:04 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-25 02:06:04 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-25 02:06:04 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-25 02:06:04 (7668) [INFO] * 2024-10-25 02:17:42 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-26 02:06:21 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-26 02:10:22 (9031) [INFO] Script is up to date. * 2024-10-26 02:14:25 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-26 02:14:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-26 02:14:26 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-26 02:14:26 (7668) [INFO] * 2024-10-26 02:14:39 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-26 02:14:39 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-26 02:14:39 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-26 02:14:39 (7668) [INFO] * 2024-10-26 02:26:13 (1995) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30798 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30002 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30004 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') 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. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30798 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30002 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30004 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-10-26 02:26:13 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-26 02:26:13 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-26 02:26:13 (7668) [INFO] * 2024-10-26 02:26:13 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-26 02:26:14 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-26 02:26:14 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-26 02:26:14 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-26 02:26:14 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-26 02:26:14 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-26 02:26:14 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-26 02:26:14 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-26 02:26:14 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-26 02:26:14 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-26 02:26:14 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-26 02:26:14 (7681) [INFO] Other repos take up 944 k of disk space (use --verbose for details) * 2024-10-26 02:26:14 (7698) [INFO] * 2024-10-26 02:26:45 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-26 02:26:45 (2006) [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 * 2024-10-26 02:26:46 (1472) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-26 02:26:46 (230) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-26 02:26:46 (1571) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-26 02:26:46 (1577) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-26 02:26:46 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-26 02:27:35 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g3uJ_dOf8P/ea_profile.json * 2024-10-26 02:32:56 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g3uJ_dOf8P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-26 02:32:56 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-27 01:47:29 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-27 01:51:30 (9031) [INFO] Script is up to date. * 2024-10-27 01:55:32 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-27 01:55:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-27 01:55:33 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-27 01:55:33 (7668) [INFO] * 2024-10-27 01:55:37 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-27 01:55:37 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-27 01:55:37 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-27 01:55:37 (7668) [INFO] * 2024-10-27 02:00:58 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-27 02:08:34 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-10-27 02:08:34 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-27 02:08:34 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-27 02:08:34 (7668) [INFO] * 2024-10-27 02:08:34 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-27 02:08:35 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-27 02:08:35 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-27 02:08:35 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-27 02:08:35 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-27 02:08:35 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-27 02:08:35 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-27 02:08:35 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-27 02:08:35 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-27 02:08:35 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-27 02:08:36 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-27 02:08:36 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-27 02:08:36 (7698) [INFO] * 2024-10-28 01:48:38 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-28 01:52:38 (9031) [INFO] Script is up to date. * 2024-10-28 01:56:41 (2274) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-28 01:56:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-28 01:56:41 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-28 01:56:41 (7668) [INFO] * 2024-10-28 01:56:46 (675) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-28 01:56:46 (682) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-28 01:56:46 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-28 01:56:46 (7668) [INFO] * 2024-10-28 01:56:59 (230) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-28 02:06:33 (1995) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-28 02:06:33 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-28 02:06:33 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-28 02:06:33 (7668) [INFO] * 2024-10-28 02:06:34 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-28 02:06:34 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-28 02:06:34 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-28 02:06:34 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-28 02:06:34 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-28 02:06:34 (7681) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-28 02:06:34 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-28 02:06:34 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-28 02:06:34 (7681) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-28 02:06:34 (7681) [INFO] : wp-toolkit-thirdparties * 2024-10-28 02:06:35 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-28 02:06:35 (7681) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-28 02:06:35 (7698) [INFO] * 2024-10-29 01:49:39 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-29 01:53:40 (9014) [INFO] Newer version of script found. Downloading. * 2024-10-29 01:57:42 (9023) [INFO] Script update to version 56 successful. * 2024-10-29 02:01:45 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-29 02:01:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-29 02:01:45 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-29 02:01:45 (7662) [INFO] * 2024-10-29 02:01:49 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-29 02:01:49 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-29 02:01:49 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-29 02:01:49 (7662) [INFO] * 2024-10-29 02:02:55 (5456) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-10-29 02:02:55 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-29 02:02:55 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-29 02:02:55 (7662) [INFO] * 2024-10-29 02:02:56 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-29 02:02:56 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-29 02:02:56 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-29 02:02:56 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-29 02:02:56 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-29 02:02:56 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-29 02:02:56 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-29 02:02:56 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-29 02:02:56 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-29 02:02:56 (7675) [INFO] : wp-toolkit-thirdparties * 2024-10-29 02:02:56 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-29 02:02:56 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-29 02:02:56 (7692) [INFO] * 2024-10-29 02:15:50 (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 02:15:50 (5467) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMwMTAxODk0OjE3MzAzNjEwOTQ6FEMsHNqB7iMxeNoREua4auaXoS1OlmKWgwPtSet_8Em09lQkBTozKPZwPhwDkIbJNiMvqhNzQXRB9-afib1M0gwFu8OfVyTH61zWWSACBw_qtPeGlo6uQRezdv_GZMMTa7Shy85BQ6CoqzEeiL0pMrDDQdhXGXygzZPKtmRfZijCqpT8D42-spVqDRSQG7I6yMSa65v7Ut3MZ_YiZH_L-tJthy8t4gT9sJjbHQa1ldRcSaL7P8IIAT16VnYvHcLYL5-tfiUHIFJ49BzDuuyn2n7TuLlPL0KdFgKu6-jvrUAUMwJJ351iL3Z_4GRW1r81QTNs_zPMmWBEOr3pkuHAEhC_VPwJ8MIPGP09TiFAXQg4TGC_wY8rIl-E5ByCss6DaFeBrAYpwCdSNgzrIpDUfkamt27L0wAsF5kgRVNcknIRV1SZJnP9BEaY4fQNxNKtoKrpZmjAuoUcVr1Tv8UzAnAsyZAXc9XmxcK8U-SZfixEEkdtFR6zcF5By-xDzUmGBIjcriZ0ixjaN14MRnDUfXl_07a6yHvWagJc2gNqn7YX7GlTJJfVdm871NWGQ0IPj_reuk4-z6RKUBITW1Suq-SkJ-bI3PuJGx5GIKWBo3sBGpUyzXRX5_5KoMZnBOyU8c86tzXLIOm-0WOm2Xfu-rvwVknq3ol9XbCgxK5aUT0%3D/ea-php/7/updates/x86_64/repodata/e82e68de0ff5fa39d04a6abc702c06985c12800b48697cd60721f52d46047640-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.4/wp-toolkit/repodata/a1eb3f8abc61d982b63c7cdcd40d494105fa9f65bf0346a2f5ac764227ac2abd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-10-29 02:15:51 (3100) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-29 02:15:51 (264) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-29 02:15:51 (3880) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-29 02:15:51 (3886) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-29 02:15:51 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-30 01:47:09 (8998) [INFO] Self-update of script version 56 requested. * 2024-10-30 01:51:10 (9020) [INFO] Script is up to date. * 2024-10-30 01:55:13 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-30 01:55:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-30 01:55:13 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-30 01:55:13 (7662) [INFO] * 2024-10-30 01:55:17 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-30 01:55:17 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-30 01:55:17 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-30 01:55:17 (7662) [INFO] * 2024-10-30 01:55:29 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-30 02:05:58 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-10-30 02:05:58 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-30 02:05:58 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-30 02:05:58 (7662) [INFO] * 2024-10-30 02:05:59 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-30 02:05:59 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-30 02:05:59 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-30 02:05:59 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-30 02:05:59 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-30 02:05:59 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-30 02:05:59 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-30 02:05:59 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-30 02:05:59 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-30 02:05:59 (7675) [INFO] : wp-toolkit-thirdparties * 2024-10-30 02:06:00 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-30 02:06:00 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-30 02:06:00 (7692) [INFO] * 2024-10-31 01:50:47 (8998) [INFO] Self-update of script version 56 requested. * 2024-10-31 01:54:48 (9020) [INFO] Script is up to date. * 2024-10-31 01:58:51 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-10-31 01:58:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-10-31 01:58:52 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-31 01:58:52 (7662) [INFO] * 2024-10-31 02:02:51 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-10-31 02:02:51 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-31 02:02:51 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-31 02:02:51 (7662) [INFO] * 2024-10-31 02:03:04 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-10-31 02:12:18 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-10-31 02:12:18 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-31 02:12:18 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-31 02:12:18 (7662) [INFO] * 2024-10-31 02:12:19 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-31 02:12:19 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-10-31 02:12:19 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-31 02:12:19 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-31 02:12:19 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-10-31 02:12:19 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-10-31 02:12:19 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-31 02:12:19 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-31 02:12:19 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-10-31 02:12:19 (7675) [INFO] : wp-toolkit-thirdparties * 2024-10-31 02:12:20 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-31 02:12:20 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-10-31 02:12:20 (7692) [INFO] * 2024-10-31 02:12:52 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-31 02:12:52 (5467) [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 * 2024-10-31 02:12:53 (3100) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-10-31 02:12:53 (264) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-10-31 02:12:53 (3880) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-10-31 02:12:53 (3886) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-10-31 02:12:53 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-31 02:13:09 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nmSZedm9le/ea_profile.json * 2024-11-01 01:59:22 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-01 02:03:23 (9020) [INFO] Script is up to date. * 2024-11-01 02:07:26 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-01 02:07:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-01 02:07:26 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-01 02:07:26 (7662) [INFO] * 2024-11-01 02:08:58 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-01 02:08:58 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-01 02:08:58 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-01 02:08:58 (7662) [INFO] * 2024-11-01 02:17:26 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-01 02:26:31 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-01 02:26:31 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-01 02:26:31 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-01 02:26:31 (7662) [INFO] * 2024-11-01 02:26:31 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-01 02:26:31 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-01 02:26:31 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-01 02:26:31 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-01 02:26:31 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-01 02:26:31 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-01 02:26:31 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-01 02:26:31 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-01 02:26:31 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-01 02:26:31 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-01 02:26:32 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-01 02:26:32 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-01 02:26:32 (7692) [INFO] * 2024-11-02 01:52:29 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-02 01:56:30 (9020) [INFO] Script is up to date. * 2024-11-02 02:00:33 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-02 02:00:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-02 02:00:34 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-02 02:00:34 (7662) [INFO] * 2024-11-02 02:00:48 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-02 02:00:48 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-02 02:00:48 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-02 02:00:48 (7662) [INFO] * 2024-11-02 02:00:59 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-02 02:13:10 (5456) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30599 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-02 02:13:10 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-02 02:13:10 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-02 02:13:10 (7662) [INFO] * 2024-11-02 02:13:11 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-02 02:13:11 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-02 02:13:11 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-02 02:13:11 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-02 02:13:11 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-02 02:13:11 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-02 02:13:11 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-02 02:13:11 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-02 02:13:11 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-02 02:13:11 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-02 02:13:12 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-02 02:13:12 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-02 02:13:12 (7692) [INFO] * 2024-11-02 02:13:43 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-02 02:13:43 (5467) [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 * 2024-11-02 02:13:44 (3100) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-02 02:13:44 (264) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-02 02:13:44 (3880) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-02 02:13:44 (3886) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-02 02:13:44 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-02 02:17:44 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4DcFRuA4_X/ea_profile.json * 2024-11-03 01:47:40 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-03 01:51:41 (9020) [INFO] Script is up to date. * 2024-11-03 01:55:44 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-03 01:55:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-03 01:55:45 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-03 01:55:45 (7662) [INFO] * 2024-11-03 01:55:58 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-03 01:55:58 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-03 01:55:58 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-03 01:55:58 (7662) [INFO] * 2024-11-03 01:56:12 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-03 01:06:51 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30802 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2024-11-03 01:06:51 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-03 01:06:51 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-03 01:06:51 (7662) [INFO] * 2024-11-03 01:06:51 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-03 01:06:52 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-03 01:06:52 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-03 01:06:52 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-03 01:06:52 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-03 01:06:52 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-03 01:06:52 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-03 01:06:52 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-03 01:06:52 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-03 01:06:52 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-03 01:06:53 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-03 01:06:53 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-03 01:06:53 (7692) [INFO] * 2024-11-04 01:46:21 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-04 01:50:22 (9020) [INFO] Script is up to date. * 2024-11-04 01:54:24 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-04 01:54:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-04 01:54:25 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-04 01:54:25 (7662) [INFO] * 2024-11-04 01:54:36 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-04 01:54:36 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-04 01:54:37 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-04 01:54:37 (7662) [INFO] * 2024-11-04 01:54:48 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-04 02:04:19 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-04 02:04:19 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-04 02:04:19 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-04 02:04:19 (7662) [INFO] * 2024-11-04 02:04:19 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-04 02:04:20 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-04 02:04:20 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-04 02:04:20 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-04 02:04:20 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-04 02:04:20 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-04 02:04:20 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-04 02:04:20 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-04 02:04:20 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-04 02:04:20 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-04 02:04:21 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-04 02:04:21 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-04 02:04:21 (7692) [INFO] * 2024-11-04 02:04: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-11-04 02:04:53 (5467) [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 * 2024-11-04 02:04:54 (3100) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-04 02:04:54 (264) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-04 02:04:54 (3880) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-04 02:04:54 (3886) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-04 02:04:54 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-04 02:07:33 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/W_Vvv7JSIw/ea_profile.json * 2024-11-04 02:15:36 (6820) [INFO] Backed up EA4 profile to /tmp/W_Vvv7JSIw/ea_profile.json * 2024-11-04 02:15:37 (264) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-11-04 02:16:11 (631) [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-11-04 02:16:11 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-05 02:02:05 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-05 02:06:05 (9020) [INFO] Script is up to date. * 2024-11-05 02:10:08 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-05 02:10:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-05 02:10:08 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-05 02:10:08 (7662) [INFO] * 2024-11-05 02:10:20 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-05 02:10:20 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-05 02:10:20 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-05 02:10:20 (7662) [INFO] * 2024-11-05 02:10:31 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-05 02:17:37 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-05 02:17:37 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-05 02:17:37 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-05 02:17:37 (7662) [INFO] * 2024-11-05 02:17:38 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-05 02:17:38 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-05 02:17:38 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-05 02:17:38 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-05 02:17:38 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-05 02:17:38 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-05 02:17:38 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-05 02:17:38 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-05 02:17:38 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-05 02:17:38 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-05 02:17:39 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-05 02:17:39 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-05 02:17:39 (7692) [INFO] * 2024-11-05 02:18:28 (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 02:18:28 (5467) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/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/. One of the configured repositories failed (MariaDB100), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=MariaDB100 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable MariaDB100 or subscription-manager repos --disable=MariaDB100 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 2024-11-05 02:18:28 (3100) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-05 02:18:28 (264) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-05 02:18:28 (3880) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-05 02:18:28 (3886) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-05 02:18:28 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-05 02:23:34 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/FKaYf6vYUB/ea_profile.json * 2024-11-05 02:30:50 (6820) [INFO] Backed up EA4 profile to /tmp/FKaYf6vYUB/ea_profile.json * 2024-11-05 02:30:51 (264) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-11-05 02:31:25 (631) [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-11-05 02:31:25 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-06 01:50:51 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-06 01:54:51 (9020) [INFO] Script is up to date. * 2024-11-06 01:58:55 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-06 01:58:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-06 01:58:55 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-06 01:58:55 (7662) [INFO] * 2024-11-06 01:58:59 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-06 01:58:59 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-06 01:58:59 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-06 01:58:59 (7662) [INFO] * 2024-11-06 01:59:09 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-06 02:07:44 (5456) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-06 02:07:44 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-06 02:07:44 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-06 02:07:44 (7662) [INFO] * 2024-11-06 02:07:44 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-06 02:07:45 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-06 02:07:45 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-06 02:07:45 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-06 02:07:45 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-06 02:07:45 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-06 02:07:45 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-06 02:07:45 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-06 02:07:45 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-06 02:07:45 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-06 02:07:46 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-06 02:07:46 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-06 02:07:46 (7692) [INFO] * 2024-11-07 02:16:21 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-07 02:20:21 (9020) [INFO] Script is up to date. * 2024-11-07 02:24:24 (5878) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-07 02:24:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-07 02:24:25 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-07 02:24:25 (7662) [INFO] * 2024-11-07 02:28:24 (3708) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-07 02:28:24 (3715) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-07 02:28:24 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-07 02:28:24 (7662) [INFO] * 2024-11-07 02:28:35 (264) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-07 02:41:17 (5456) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30025 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30539 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-07 02:41:17 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-07 02:41:17 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-07 02:41:17 (7662) [INFO] * 2024-11-07 02:41:17 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-07 02:41:17 (7675) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 4344. * 2024-11-07 02:41:17 (7675) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-11-07 02:41:17 (7675) [INFO] The other application is: yum * 2024-11-07 02:41:17 (7675) [INFO] Memory : 33 M RSS (360 MB VSZ) * 2024-11-07 02:41:17 (7675) [INFO] Started: Thu Nov 7 02:29:05 2024 - 12:12 ago * 2024-11-07 02:41:17 (7675) [INFO] State : Running, pid: 4344 * 2024-11-07 02:41:19 (7675) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-11-07 02:41:19 (7675) [INFO] The other application is: yum * 2024-11-07 02:41:19 (7675) [INFO] Memory : 79 M RSS (407 MB VSZ) * 2024-11-07 02:41:19 (7675) [INFO] Started: Thu Nov 7 02:29:05 2024 - 12:14 ago * 2024-11-07 02:41:19 (7675) [INFO] State : Running, pid: 4344 * 2024-11-07 02:41:21 (7675) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-11-07 02:41:21 (7675) [INFO] The other application is: yum * 2024-11-07 02:41:21 (7675) [INFO] Memory : 83 M RSS (411 MB VSZ) * 2024-11-07 02:41:21 (7675) [INFO] Started: Thu Nov 7 02:29:05 2024 - 12:16 ago * 2024-11-07 02:41:21 (7675) [INFO] State : Running, pid: 4344 * 2024-11-07 02:41:23 (7675) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-11-07 02:41:23 (7675) [INFO] The other application is: yum * 2024-11-07 02:41:23 (7675) [INFO] Memory : 88 M RSS (415 MB VSZ) * 2024-11-07 02:41:23 (7675) [INFO] Started: Thu Nov 7 02:29:05 2024 - 12:18 ago * 2024-11-07 02:41:23 (7675) [INFO] State : Running, pid: 4344 * 2024-11-07 02:41:25 (7675) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-11-07 02:41:25 (7675) [INFO] The other application is: yum * 2024-11-07 02:41:25 (7675) [INFO] Memory : 98 M RSS (425 MB VSZ) * 2024-11-07 02:41:25 (7675) [INFO] Started: Thu Nov 7 02:29:05 2024 - 12:20 ago * 2024-11-07 02:41:25 (7675) [INFO] State : Running, pid: 4344 * 2024-11-07 02:41:27 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-07 02:41:27 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-07 02:41:27 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-07 02:41:27 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-07 02:41:27 (7675) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-07 02:41:27 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-07 02:41:27 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-07 02:41:27 (7675) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-07 02:41:27 (7675) [INFO] : wp-toolkit-thirdparties * 2024-11-07 02:41:28 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-07 02:41:28 (7675) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-07 02:41:28 (7692) [INFO] * 2024-11-08 01:45:37 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-08 01:49:38 (9003) [INFO] Newer version of script found. Downloading. * 2024-11-08 01:53:39 (9012) [INFO] Script update to version 57 successful. * 2024-11-08 01:57:43 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-08 01:57:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-08 01:57:43 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-08 01:57:43 (8441) [INFO] * 2024-11-08 01:58:13 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-08 01:58:13 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-08 01:58:13 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-08 01:58:13 (8441) [INFO] * 2024-11-08 02:02:10 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-08 02:02:10 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-08 02:02:10 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-08 02:02:10 (8471) [INFO] * 2024-11-08 02:02:10 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-08 02:02:10 (8441) [INFO] * 2024-11-08 02:02:21 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-08 02:02:24 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-08 02:02:24 (8441) [INFO] * 2024-11-08 02:02:24 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 02:02:24 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-08 02:02:54 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-08 02:02:54 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-08 02:02:54 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-08 02:02:54 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-08 02:05:43 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:05:43 (8454) [INFO] Trying other mirror. * 2024-11-08 02:05:43 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-08 02:05:43 (8454) [INFO] Trying other mirror. * 2024-11-08 02:06:20 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') * 2024-11-08 02:06:20 (8454) [INFO] Trying other mirror. * 2024-11-08 02:06:30 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:06:30 (8454) [INFO] Trying other mirror. * 2024-11-08 02:06:55 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-08 02:06:55 (8454) [INFO] Trying other mirror. * 2024-11-08 02:07:00 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-08 02:07:00 (8454) [INFO] Trying other mirror. * 2024-11-08 02:07:16 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-08 02:07:16 (8454) [INFO] Trying other mirror. * 2024-11-08 02:07:46 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-08 02:07:46 (8454) [INFO] Trying other mirror. * 2024-11-08 02:08:17 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:08:17 (8454) [INFO] Trying other mirror. * 2024-11-08 02:08:47 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-08 02:08:47 (8454) [INFO] Trying other mirror. * 2024-11-08 02:08:48 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:08:48 (8454) [INFO] Trying other mirror. * 2024-11-08 02:08:48 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:08:48 (8454) [INFO] Trying other mirror. * 2024-11-08 02:09:18 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:09:18 (8454) [INFO] Trying other mirror. * 2024-11-08 02:09:49 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:09:49 (8454) [INFO] Trying other mirror. * 2024-11-08 02:09:49 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:09:49 (8454) [INFO] Trying other mirror. * 2024-11-08 02:09:49 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-08 02:09:49 (8454) [INFO] Trying other mirror. * 2024-11-08 02:10:50 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-08 02:10:50 (8454) [INFO] Trying other mirror. * 2024-11-08 02:10:50 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30598 milliseconds') * 2024-11-08 02:10:50 (8454) [INFO] Trying other mirror. * 2024-11-08 02:11:20 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-08 02:11:20 (8454) [INFO] Trying other mirror. * 2024-11-08 02:12:29 (8454) [INFO] Metadata Cache Created * 2024-11-08 02:12:29 (8471) [INFO] * 2024-11-08 02:12:29 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30598 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-08 02:12:29 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-08 02:12:29 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-08 02:12:29 (8441) [INFO] * 2024-11-08 02:12:29 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 02:12:29 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-08 02:12:29 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-08 02:12:29 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-08 02:12:29 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-08 02:12:29 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-08 02:12:29 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-08 02:12:29 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-08 02:12:29 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-08 02:12:29 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-08 02:12:30 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-08 02:12:30 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-08 02:12:30 (8471) [INFO] * 2024-11-08 02:12:30 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-08 02:12:30 (8441) [INFO] * 2024-11-08 02:12:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 02:12:31 (8454) [INFO] Determining fastest mirrors * 2024-11-08 02:13:04 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-08 02:13:04 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-08 02:13:04 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-08 02:13:04 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-08 02:13:51 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-08 02:13:51 (8454) [INFO] Trying other mirror. * 2024-11-09 01:46:56 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-09 01:50:56 (9513) [INFO] Script is up to date. * 2024-11-09 01:54:58 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-09 01:54:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-09 01:54:59 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-09 01:54:59 (8441) [INFO] * 2024-11-09 01:55:04 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-09 01:55:04 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-09 01:55:04 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-09 01:55:04 (8441) [INFO] * 2024-11-09 01:58:47 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-09 01:58:47 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-09 01:58:47 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-09 01:58:47 (8471) [INFO] * 2024-11-09 01:58:47 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-09 01:58:47 (8441) [INFO] * 2024-11-09 02:04:47 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-09 02:04:53 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-09 02:04:53 (8441) [INFO] * 2024-11-09 02:04:53 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-09 02:04:53 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-09 02:05:23 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-09 02:05:23 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-09 02:05:23 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-09 02:05:23 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-09 02:08:12 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-09 02:08:12 (8454) [INFO] Trying other mirror. * 2024-11-09 02:08:12 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:08:12 (8454) [INFO] Trying other mirror. * 2024-11-09 02:08:42 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-09 02:08:42 (8454) [INFO] Trying other mirror. * 2024-11-09 02:09:17 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-09 02:09:17 (8454) [INFO] Trying other mirror. * 2024-11-09 02:09:51 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:09:51 (8454) [INFO] Trying other mirror. * 2024-11-09 02:10:01 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:10:01 (8454) [INFO] Trying other mirror. * 2024-11-09 02:10:17 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-09 02:10:17 (8454) [INFO] Trying other mirror. * 2024-11-09 02:10:48 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-09 02:10:48 (8454) [INFO] Trying other mirror. * 2024-11-09 02:11:18 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:11:18 (8454) [INFO] Trying other mirror. * 2024-11-09 02:11:19 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:11:19 (8454) [INFO] Trying other mirror. * 2024-11-09 02:11:19 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:11:19 (8454) [INFO] Trying other mirror. * 2024-11-09 02:11:49 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-09 02:11:49 (8454) [INFO] Trying other mirror. * 2024-11-09 02:12:20 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-09 02:12:20 (8454) [INFO] Trying other mirror. * 2024-11-09 02:12:51 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') * 2024-11-09 02:12:51 (8454) [INFO] Trying other mirror. * 2024-11-09 02:12:51 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-09 02:12:51 (8454) [INFO] Trying other mirror. * 2024-11-09 02:12:51 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-09 02:12:51 (8454) [INFO] Trying other mirror. * 2024-11-09 02:13:21 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-09 02:13:21 (8454) [INFO] Trying other mirror. * 2024-11-09 02:14:22 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-09 02:14:22 (8454) [INFO] Trying other mirror. * 2024-11-09 02:14:23 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-09 02:14:23 (8454) [INFO] Trying other mirror. * 2024-11-09 02:14:54 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-09 02:14:54 (8454) [INFO] Trying other mirror. * 2024-11-09 02:15:25 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-09 02:15:25 (8454) [INFO] Trying other mirror. * 2024-11-09 02:15:55 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-09 02:15:55 (8454) [INFO] Trying other mirror. * 2024-11-09 02:16:26 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-09 02:16:26 (8454) [INFO] Trying other mirror. * 2024-11-10 01:47:00 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-10 01:51:01 (9513) [INFO] Script is up to date. * 2024-11-10 01:55:04 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-10 01:55:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-10 01:55:04 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-10 01:55:04 (8441) [INFO] * 2024-11-10 01:55:08 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-10 01:55:08 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-10 01:55:08 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-10 01:55:08 (8441) [INFO] * 2024-11-10 01:58:45 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-10 01:58:45 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-10 01:58:45 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-10 01:58:45 (8471) [INFO] * 2024-11-10 01:58:45 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-10 01:58:45 (8441) [INFO] * 2024-11-10 01:58:59 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-10 01:59:04 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-10 01:59:04 (8441) [INFO] * 2024-11-10 01:59:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 01:59:05 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-10 01:59:35 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-10 01:59:35 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-10 01:59:35 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-10 01:59:35 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-10 02:02:23 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:02:23 (8454) [INFO] Trying other mirror. * 2024-11-10 02:02:24 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-11-10 02:02:24 (8454) [INFO] Trying other mirror. * 2024-11-10 02:02:58 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:02:58 (8454) [INFO] Trying other mirror. * 2024-11-10 02:02:59 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-10 02:02:59 (8454) [INFO] Trying other mirror. * 2024-11-10 02:03:33 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:03:33 (8454) [INFO] Trying other mirror. * 2024-11-10 02:03:38 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-10 02:03:38 (8454) [INFO] Trying other mirror. * 2024-11-10 02:03:54 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-10 02:03:54 (8454) [INFO] Trying other mirror. * 2024-11-10 02:04:24 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:04:24 (8454) [INFO] Trying other mirror. * 2024-11-10 02:04:25 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:04:25 (8454) [INFO] Trying other mirror. * 2024-11-10 02:04:55 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:04:55 (8454) [INFO] Trying other mirror. * 2024-11-10 02:04:56 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:04:56 (8454) [INFO] Trying other mirror. * 2024-11-10 02:05:26 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:05:26 (8454) [INFO] Trying other mirror. * 2024-11-10 02:05:26 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-10 02:05:26 (8454) [INFO] Trying other mirror. * 2024-11-10 02:05:57 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:05:57 (8454) [INFO] Trying other mirror. * 2024-11-10 02:05:57 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-10 02:05:57 (8454) [INFO] Trying other mirror. * 2024-11-10 02:06:27 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:06:27 (8454) [INFO] Trying other mirror. * 2024-11-10 02:06:28 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:06:28 (8454) [INFO] Trying other mirror. * 2024-11-10 02:06:58 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-10 02:06:58 (8454) [INFO] Trying other mirror. * 2024-11-10 02:06:59 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-10 02:06:59 (8454) [INFO] Trying other mirror. * 2024-11-10 02:07:29 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-10 02:07:29 (8454) [INFO] Trying other mirror. * 2024-11-10 02:07:29 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:07:29 (8454) [INFO] Trying other mirror. * 2024-11-10 02:08:00 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:08:00 (8454) [INFO] Trying other mirror. * 2024-11-10 02:08:00 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-10 02:08:00 (8454) [INFO] Trying other mirror. * 2024-11-10 02:08:31 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:08:31 (8454) [INFO] Trying other mirror. * 2024-11-10 02:08:31 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:08:31 (8454) [INFO] Trying other mirror. * 2024-11-10 02:09:01 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-10 02:09:01 (8454) [INFO] Trying other mirror. * 2024-11-10 02:09:32 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:09:32 (8454) [INFO] Trying other mirror. * 2024-11-10 02:09:32 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:09:32 (8454) [INFO] Trying other mirror. * 2024-11-10 02:09:32 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:09:32 (8454) [INFO] Trying other mirror. * 2024-11-10 02:10:02 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30064 milliseconds with 0 out of 0 bytes received') * 2024-11-10 02:10:02 (8454) [INFO] Trying other mirror. * 2024-11-10 02:10:02 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:10:02 (8454) [INFO] Trying other mirror. * 2024-11-10 02:10:33 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-10 02:10:33 (8454) [INFO] Trying other mirror. * 2024-11-10 02:10:33 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-10 02:10:33 (8454) [INFO] Trying other mirror. * 2024-11-10 02:10:33 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-10 02:10:33 (8454) [INFO] Trying other mirror. * 2024-11-10 02:11:03 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:11:03 (8454) [INFO] Trying other mirror. * 2024-11-10 02:11:04 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:11:04 (8454) [INFO] Trying other mirror. * 2024-11-10 02:11:34 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:11:34 (8454) [INFO] Trying other mirror. * 2024-11-10 02:11:34 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:11:34 (8454) [INFO] Trying other mirror. * 2024-11-10 02:12:04 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:12:04 (8454) [INFO] Trying other mirror. * 2024-11-10 02:12:34 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:12:34 (8454) [INFO] Trying other mirror. * 2024-11-10 02:13:05 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-10 02:13:05 (8454) [INFO] Trying other mirror. * 2024-11-10 02:14:05 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-10 02:14:05 (8454) [INFO] Trying other mirror. * 2024-11-10 02:14:35 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-10 02:14:35 (8454) [INFO] Trying other mirror. * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] One of the configured repositories failed (Unknown), * 2024-11-10 02:15:06 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-10 02:15:06 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-10 02:15:06 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-10 02:15:06 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-10 02:15:06 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-10 02:15:06 (8454) [INFO] yum --disablerepo= ... * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-10 02:15:06 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-10 02:15:06 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] yum-config-manager --disable * 2024-11-10 02:15:06 (8454) [INFO] or * 2024-11-10 02:15:06 (8454) [INFO] subscription-manager repos --disable= * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-10 02:15:06 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-10 02:15:06 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-10 02:15:06 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-10 02:15:06 (8454) [INFO] compromise: * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-10 02:15:06 (8454) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] base: Check uncompressed DB failed * 2024-11-10 02:15:06 (8471) [INFO] * 2024-11-10 02:15:06 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30064 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') 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 * 2024-11-10 02:15:06 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-10 02:15:06 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-10 02:15:06 (8441) [INFO] * 2024-11-10 02:15:06 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 02:15:07 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-10 02:15:07 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-10 02:15:07 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-10 02:15:07 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-10 02:15:07 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-10 02:15:07 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-10 02:15:07 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-10 02:15:07 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-10 02:15:07 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-10 02:15:08 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-10 02:15:08 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-10 02:15:08 (8471) [INFO] * 2024-11-10 02:15:08 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-10 02:15:08 (8441) [INFO] * 2024-11-10 02:15:08 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 02:15:08 (8454) [INFO] Determining fastest mirrors * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] One of the configured repositories failed (Unknown), * 2024-11-10 02:15:41 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-10 02:15:41 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-10 02:15:41 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-10 02:15:41 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-10 02:15:41 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-10 02:15:41 (8454) [INFO] yum --disablerepo= ... * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-10 02:15:41 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-10 02:15:41 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] yum-config-manager --disable * 2024-11-10 02:15:41 (8454) [INFO] or * 2024-11-10 02:15:41 (8454) [INFO] subscription-manager repos --disable= * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-10 02:15:41 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-10 02:15:41 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-10 02:15:41 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-10 02:15:41 (8454) [INFO] compromise: * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-10 02:15:41 (8454) [INFO] * 2024-11-10 02:15:41 (8454) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-10 02:15:41 (8471) [INFO] * 2024-11-10 02:15:41 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-10 02:15:41 (5518) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-11-10 02:15:42 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-10 02:15:42 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-10 02:15:42 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-10 02:15:42 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-10 02:15:42 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-10 02:15:58 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/WrGcTt1Scu/ea_profile.json * 2024-11-11 01:45:15 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-11 01:49:16 (9513) [INFO] Script is up to date. * 2024-11-11 01:53:19 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-11 01:53:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-11 01:53:19 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-11 01:53:19 (8441) [INFO] * 2024-11-11 01:53:31 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-11 01:53:31 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-11 01:53:31 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-11 01:53:31 (8441) [INFO] * 2024-11-11 01:57:14 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-11 01:57:14 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-11 01:57:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-11 01:57:14 (8471) [INFO] * 2024-11-11 01:57:14 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-11 01:57:14 (8441) [INFO] * 2024-11-11 01:57:25 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-11 01:57:25 (8441) [INFO] * 2024-11-11 01:57:25 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 01:57:25 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-11 01:57:56 (8454) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-11-11 01:57:56 (8454) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') * 2024-11-11 01:57:56 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-11 01:57:56 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-11 01:57:56 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-11 01:57:56 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-11 01:59:41 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMwOTcxODU5OjE3MzEyMzEwNTk6lJHE9MGl0Go2QSrC14IWONVjnVNZmJ7ckrI4w8d9DYj5MVDPH9pgXTJJFxSJINETg5rQ2Bl9HMtp5NoAnaD2sIIuseRBSMA7xIlvoNITQDO9AixRJ6hl6rYYJm3xF4h1SZww2O52ZT1JVnc3gH77_3ixlrBmUnmazGF7hhCRCIjXJnLnWbEyN-mIZ6tk34d3DtrvXduHvO9U70f4RRbyiRh7KXaxuK_PIAvFVELtZvdhsiCZQz9GikGJOXGxPuKlL2GcDj1dR9o_Y9UkviKs1W4tF8ZIHoPOf2PnhnnDYdsYlyjknBGx42GrThUfYIhht7sgtheyAgixyAPDCZIW3owNtFlFrti0Y0GFh8OOmE_XO6v5MtLUG7rxKKHEDOXmNRJARCRwmMBuxak0IYmVjxA21pfjdcsZjy3VP2MxjX2BjcVc77iZ8bytNMwiAPoxBFhai7-DO7kdZuphVBwSco8WOgWLy143BCg1MCALM2ju5d57PGnxe1H1TWOne8byEHT2obc500IGBdpVvbHvwQVtaOnBoGyaCN4RBIgweC8dWmkooFlBxJ8O7ce23LzxoaL6L3xCZxxoCnVSp8iovnMMrHx5MHG8_zj7RDfSsUGHtypvoj8uok3zTjR7soMVcf9nE_KIeVlWIlV6woxj5C8Wg8MODixt3FLYZ862UEo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-11 01:59:41 (8454) [INFO] Trying other mirror. * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-11-11 01:59:42 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-11 01:59:42 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-11 01:59:42 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-11 01:59:42 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-11 01:59:42 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-11 01:59:42 (8454) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-11 01:59:42 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-11 01:59:42 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-11-11 01:59:42 (8454) [INFO] or * 2024-11-11 01:59:42 (8454) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-11 01:59:42 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-11 01:59:42 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-11 01:59:42 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-11 01:59:42 (8454) [INFO] compromise: * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-11-11 01:59:42 (8454) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-11-11 01:59:42 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMwOTcxODU5OjE3MzEyMzEwNTk6lJHE9MGl0Go2QSrC14IWONVjnVNZmJ7ckrI4w8d9DYj5MVDPH9pgXTJJFxSJINETg5rQ2Bl9HMtp5NoAnaD2sIIuseRBSMA7xIlvoNITQDO9AixRJ6hl6rYYJm3xF4h1SZww2O52ZT1JVnc3gH77_3ixlrBmUnmazGF7hhCRCIjXJnLnWbEyN-mIZ6tk34d3DtrvXduHvO9U70f4RRbyiRh7KXaxuK_PIAvFVELtZvdhsiCZQz9GikGJOXGxPuKlL2GcDj1dR9o_Y9UkviKs1W4tF8ZIHoPOf2PnhnnDYdsYlyjknBGx42GrThUfYIhht7sgtheyAgixyAPDCZIW3owNtFlFrti0Y0GFh8OOmE_XO6v5MtLUG7rxKKHEDOXmNRJARCRwmMBuxak0IYmVjxA21pfjdcsZjy3VP2MxjX2BjcVc77iZ8bytNMwiAPoxBFhai7-DO7kdZuphVBwSco8WOgWLy143BCg1MCALM2ju5d57PGnxe1H1TWOne8byEHT2obc500IGBdpVvbHvwQVtaOnBoGyaCN4RBIgweC8dWmkooFlBxJ8O7ce23LzxoaL6L3xCZxxoCnVSp8iovnMMrHx5MHG8_zj7RDfSsUGHtypvoj8uok3zTjR7soMVcf9nE_KIeVlWIlV6woxj5C8Wg8MODixt3FLYZ862UEo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-11 01:59:42 (8471) [INFO] * 2024-11-11 01:59:42 (5507) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMwOTcxODU5OjE3MzEyMzEwNTk6lJHE9MGl0Go2QSrC14IWONVjnVNZmJ7ckrI4w8d9DYj5MVDPH9pgXTJJFxSJINETg5rQ2Bl9HMtp5NoAnaD2sIIuseRBSMA7xIlvoNITQDO9AixRJ6hl6rYYJm3xF4h1SZww2O52ZT1JVnc3gH77_3ixlrBmUnmazGF7hhCRCIjXJnLnWbEyN-mIZ6tk34d3DtrvXduHvO9U70f4RRbyiRh7KXaxuK_PIAvFVELtZvdhsiCZQz9GikGJOXGxPuKlL2GcDj1dR9o_Y9UkviKs1W4tF8ZIHoPOf2PnhnnDYdsYlyjknBGx42GrThUfYIhht7sgtheyAgixyAPDCZIW3owNtFlFrti0Y0GFh8OOmE_XO6v5MtLUG7rxKKHEDOXmNRJARCRwmMBuxak0IYmVjxA21pfjdcsZjy3VP2MxjX2BjcVc77iZ8bytNMwiAPoxBFhai7-DO7kdZuphVBwSco8WOgWLy143BCg1MCALM2ju5d57PGnxe1H1TWOne8byEHT2obc500IGBdpVvbHvwQVtaOnBoGyaCN4RBIgweC8dWmkooFlBxJ8O7ce23LzxoaL6L3xCZxxoCnVSp8iovnMMrHx5MHG8_zj7RDfSsUGHtypvoj8uok3zTjR7soMVcf9nE_KIeVlWIlV6woxj5C8Wg8MODixt3FLYZ862UEo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMwOTcxODU5OjE3MzEyMzEwNTk6lJHE9MGl0Go2QSrC14IWONVjnVNZmJ7ckrI4w8d9DYj5MVDPH9pgXTJJFxSJINETg5rQ2Bl9HMtp5NoAnaD2sIIuseRBSMA7xIlvoNITQDO9AixRJ6hl6rYYJm3xF4h1SZww2O52ZT1JVnc3gH77_3ixlrBmUnmazGF7hhCRCIjXJnLnWbEyN-mIZ6tk34d3DtrvXduHvO9U70f4RRbyiRh7KXaxuK_PIAvFVELtZvdhsiCZQz9GikGJOXGxPuKlL2GcDj1dR9o_Y9UkviKs1W4tF8ZIHoPOf2PnhnnDYdsYlyjknBGx42GrThUfYIhht7sgtheyAgixyAPDCZIW3owNtFlFrti0Y0GFh8OOmE_XO6v5MtLUG7rxKKHEDOXmNRJARCRwmMBuxak0IYmVjxA21pfjdcsZjy3VP2MxjX2BjcVc77iZ8bytNMwiAPoxBFhai7-DO7kdZuphVBwSco8WOgWLy143BCg1MCALM2ju5d57PGnxe1H1TWOne8byEHT2obc500IGBdpVvbHvwQVtaOnBoGyaCN4RBIgweC8dWmkooFlBxJ8O7ce23LzxoaL6L3xCZxxoCnVSp8iovnMMrHx5MHG8_zj7RDfSsUGHtypvoj8uok3zTjR7soMVcf9nE_KIeVlWIlV6woxj5C8Wg8MODixt3FLYZ862UEo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-11 01:59:42 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-11 01:59:42 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-11 01:59:42 (8441) [INFO] * 2024-11-11 01:59:42 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 01:59:42 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-11 01:59:42 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-11 01:59:42 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-11 01:59:42 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-11 01:59:42 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-11 01:59:42 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-11 01:59:42 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-11 01:59:42 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-11 01:59:42 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-11 01:59:42 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-11 01:59:43 (8454) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2024-11-11 01:59:43 (8471) [INFO] * 2024-11-11 01:59:43 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-11 01:59:43 (8441) [INFO] * 2024-11-11 01:59:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 01:59:43 (8454) [INFO] Determining fastest mirrors * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] One of the configured repositories failed (Unknown), * 2024-11-11 02:00:13 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-11 02:00:13 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-11 02:00:13 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-11 02:00:13 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-11 02:00:13 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-11 02:00:13 (8454) [INFO] yum --disablerepo= ... * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-11 02:00:13 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-11 02:00:13 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] yum-config-manager --disable * 2024-11-11 02:00:13 (8454) [INFO] or * 2024-11-11 02:00:13 (8454) [INFO] subscription-manager repos --disable= * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-11 02:00:13 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-11 02:00:13 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-11 02:00:13 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-11 02:00:13 (8454) [INFO] compromise: * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-11 02:00:13 (8454) [INFO] * 2024-11-11 02:00:13 (8454) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-11 02:00:13 (8471) [INFO] * 2024-11-11 02:00:13 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-11 02:00:13 (5518) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-11-11 02:00:14 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-11 02:00:14 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-11 02:00:14 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-11 02:00:14 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-11 02:00:14 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-11 02:06:27 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dV0gHMRmGA/ea_profile.json * 2024-11-11 02:09:46 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dV0gHMRmGA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-11 02:09:46 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-12 01:54:03 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-12 01:58:04 (9513) [INFO] Script is up to date. * 2024-11-12 02:02:06 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-12 02:02:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-12 02:02:07 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-12 02:02:07 (8441) [INFO] * 2024-11-12 02:02:17 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-12 02:02:17 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-12 02:02:17 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-12 02:02:17 (8441) [INFO] * 2024-11-12 02:05:58 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-12 02:05:58 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-12 02:05:58 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-12 02:05:58 (8471) [INFO] * 2024-11-12 02:05:58 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-12 02:05:58 (8441) [INFO] * 2024-11-12 02:14:50 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-12 02:14:53 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-12 02:14:53 (8441) [INFO] * 2024-11-12 02:14:53 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-12 02:14:54 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-12 02:15:24 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-12 02:15:24 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-12 02:15:24 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-12 02:15:24 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-12 02:18:12 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:18:12 (8454) [INFO] Trying other mirror. * 2024-11-12 02:18:13 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') * 2024-11-12 02:18:13 (8454) [INFO] Trying other mirror. * 2024-11-12 02:18:47 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:18:47 (8454) [INFO] Trying other mirror. * 2024-11-12 02:18:47 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:18:47 (8454) [INFO] Trying other mirror. * 2024-11-12 02:19:23 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2024-11-12 02:19:23 (8454) [INFO] Trying other mirror. * 2024-11-12 02:19:27 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:19:27 (8454) [INFO] Trying other mirror. * 2024-11-12 02:19:43 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:19:43 (8454) [INFO] Trying other mirror. * 2024-11-12 02:20:14 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-12 02:20:14 (8454) [INFO] Trying other mirror. * 2024-11-12 02:20:14 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-12 02:20:14 (8454) [INFO] Trying other mirror. * 2024-11-12 02:20:45 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-12 02:20:45 (8454) [INFO] Trying other mirror. * 2024-11-12 02:20:45 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-12 02:20:45 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:15 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:21:15 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:15 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:21:15 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:16 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-12 02:21:16 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:46 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-12 02:21:46 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:46 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-12 02:21:46 (8454) [INFO] Trying other mirror. * 2024-11-12 02:21:47 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-12 02:21:47 (8454) [INFO] Trying other mirror. * 2024-11-12 02:22:17 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:22:17 (8454) [INFO] Trying other mirror. * 2024-11-12 02:22:17 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:22:17 (8454) [INFO] Trying other mirror. * 2024-11-12 02:22:17 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:22:17 (8454) [INFO] Trying other mirror. * 2024-11-12 02:22:47 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:22:47 (8454) [INFO] Trying other mirror. * 2024-11-12 02:23:17 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:23:17 (8454) [INFO] Trying other mirror. * 2024-11-12 02:23:17 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-12 02:23:17 (8454) [INFO] Trying other mirror. * 2024-11-12 02:23:48 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-12 02:23:48 (8454) [INFO] Trying other mirror. * 2024-11-12 02:23:48 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-12 02:23:48 (8454) [INFO] Trying other mirror. * 2024-11-13 01:46:53 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-13 01:50:53 (9513) [INFO] Script is up to date. * 2024-11-13 01:54:56 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-13 01:54:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-13 01:54:57 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-13 01:54:57 (8441) [INFO] * 2024-11-13 01:55:10 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-13 01:55:10 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-13 01:55:10 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-13 01:55:10 (8441) [INFO] * 2024-11-13 01:58:55 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-13 01:58:55 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-13 01:58:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-13 01:58:55 (8471) [INFO] * 2024-11-13 01:58:55 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-13 01:58:55 (8441) [INFO] * 2024-11-13 01:59:11 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-13 01:59:15 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-13 01:59:15 (8441) [INFO] * 2024-11-13 01:59:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 01:59:16 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-13 01:59:46 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-13 01:59:46 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-13 01:59:46 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-13 01:59:46 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-13 02:02:35 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:02:35 (8454) [INFO] Trying other mirror. * 2024-11-13 02:02:35 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:02:35 (8454) [INFO] Trying other mirror. * 2024-11-13 02:03:12 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2024-11-13 02:03:12 (8454) [INFO] Trying other mirror. * 2024-11-13 02:03:47 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:03:47 (8454) [INFO] Trying other mirror. * 2024-11-13 02:03:51 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2024-11-13 02:03:51 (8454) [INFO] Trying other mirror. * 2024-11-13 02:04:06 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:04:06 (8454) [INFO] Trying other mirror. * 2024-11-13 02:04:36 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:04:36 (8454) [INFO] Trying other mirror. * 2024-11-13 02:04:36 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:04:36 (8454) [INFO] Trying other mirror. * 2024-11-13 02:05:07 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-13 02:05:07 (8454) [INFO] Trying other mirror. * 2024-11-13 02:05:37 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-13 02:05:37 (8454) [INFO] Trying other mirror. * 2024-11-13 02:05:37 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:05:37 (8454) [INFO] Trying other mirror. * 2024-11-13 02:06:07 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-13 02:06:07 (8454) [INFO] Trying other mirror. * 2024-11-13 02:07:10 (8454) [INFO] Metadata Cache Created * 2024-11-13 02:07:11 (8471) [INFO] * 2024-11-13 02:07:11 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-13 02:07:11 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-13 02:07:11 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-13 02:07:11 (8441) [INFO] * 2024-11-13 02:07:11 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 02:07:11 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-13 02:07:11 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-13 02:07:11 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-13 02:07:11 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-13 02:07:11 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-13 02:07:11 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-13 02:07:11 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-13 02:07:11 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-13 02:07:11 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-13 02:07:12 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-13 02:07:12 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-13 02:07:12 (8471) [INFO] * 2024-11-13 02:07:12 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-13 02:07:12 (8441) [INFO] * 2024-11-13 02:07:13 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 02:07:13 (8454) [INFO] Determining fastest mirrors * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] One of the configured repositories failed (Unknown), * 2024-11-13 02:07:44 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-13 02:07:44 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-13 02:07:44 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-13 02:07:44 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-13 02:07:44 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-13 02:07:44 (8454) [INFO] yum --disablerepo= ... * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-13 02:07:44 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-13 02:07:44 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] yum-config-manager --disable * 2024-11-13 02:07:44 (8454) [INFO] or * 2024-11-13 02:07:44 (8454) [INFO] subscription-manager repos --disable= * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-13 02:07:44 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-13 02:07:44 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-13 02:07:44 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-13 02:07:44 (8454) [INFO] compromise: * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-13 02:07:44 (8454) [INFO] * 2024-11-13 02:07:44 (8454) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-13 02:07:44 (8471) [INFO] * 2024-11-13 02:07:44 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-13 02:07:44 (5518) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-11-13 02:07:45 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-13 02:07:45 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-13 02:07:45 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-13 02:07:45 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-13 02:07:45 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-13 02:08:06 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jHJ3MOc3HX/ea_profile.json * 2024-11-14 01:46:43 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-14 01:50:44 (9513) [INFO] Script is up to date. * 2024-11-14 01:54:46 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-14 01:54:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-14 01:54:46 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-14 01:54:46 (8441) [INFO] * 2024-11-14 01:55:00 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-14 01:55:00 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-14 01:55:00 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-14 01:55:00 (8441) [INFO] * 2024-11-14 01:58:41 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-14 01:58:41 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-14 01:58:41 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-14 01:58:41 (8471) [INFO] * 2024-11-14 01:58:41 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-14 01:58:41 (8441) [INFO] * 2024-11-14 01:59:16 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-14 01:59:16 (8441) [INFO] * 2024-11-14 01:59:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-14 01:59:17 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-14 01:59:50 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-14 01:59:50 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-14 01:59:50 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-14 01:59:50 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-14 02:00:37 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:00:37 (8454) [INFO] Trying other mirror. * 2024-11-14 02:03:28 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:03:28 (8454) [INFO] Trying other mirror. * 2024-11-14 02:03:28 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') * 2024-11-14 02:03:28 (8454) [INFO] Trying other mirror. * 2024-11-14 02:03:58 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-14 02:03:58 (8454) [INFO] Trying other mirror. * 2024-11-14 02:04:28 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-11-14 02:04:28 (8454) [INFO] Trying other mirror. * 2024-11-14 02:06:25 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-14 02:06:25 (8454) [INFO] Trying other mirror. * 2024-11-14 02:09:35 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:09:35 (8454) [INFO] Trying other mirror. * 2024-11-14 02:09:35 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-14 02:09:35 (8454) [INFO] Trying other mirror. * 2024-11-14 02:09:50 (8454) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.4/wp-toolkit/repodata/a1eb3f8abc61d982b63c7cdcd40d494105fa9f65bf0346a2f5ac764227ac2abd-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-11-14 02:09:50 (8454) [INFO] Trying other mirror. * 2024-11-14 02:10:05 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2024-11-14 02:10:05 (8454) [INFO] Trying other mirror. * 2024-11-14 02:10:06 (8454) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.5.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-11-14 02:10:06 (8454) [INFO] Trying other mirror. * 2024-11-14 02:10:36 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-14 02:10:36 (8454) [INFO] Trying other mirror. * 2024-11-14 02:11:37 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-14 02:11:37 (8454) [INFO] Trying other mirror. * 2024-11-14 02:11:37 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-14 02:11:37 (8454) [INFO] Trying other mirror. * 2024-11-14 02:12:08 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2024-11-14 02:12:08 (8454) [INFO] Trying other mirror. * 2024-11-14 02:12:39 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-14 02:12:39 (8454) [INFO] Trying other mirror. * 2024-11-14 02:12:39 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-14 02:12:39 (8454) [INFO] Trying other mirror. * 2024-11-14 02:12:39 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:12:39 (8454) [INFO] Trying other mirror. * 2024-11-14 02:13:09 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-14 02:13:09 (8454) [INFO] Trying other mirror. * 2024-11-14 02:13:40 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-14 02:13:40 (8454) [INFO] Trying other mirror. * 2024-11-14 02:14:11 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-14 02:14:11 (8454) [INFO] Trying other mirror. * 2024-11-14 02:14:11 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:14:11 (8454) [INFO] Trying other mirror. * 2024-11-14 02:14:11 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:14:11 (8454) [INFO] Trying other mirror. * 2024-11-14 02:14:42 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-14 02:14:42 (8454) [INFO] Trying other mirror. * 2024-11-14 02:15:12 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-14 02:15:12 (8454) [INFO] Trying other mirror. * 2024-11-14 02:15:13 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-14 02:15:13 (8454) [INFO] Trying other mirror. * 2024-11-14 02:15:42 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-14 02:15:42 (8454) [INFO] Trying other mirror. * 2024-11-14 02:15:43 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-14 02:15:43 (8454) [INFO] Trying other mirror. * 2024-11-14 02:16:14 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-14 02:16:14 (8454) [INFO] Trying other mirror. * 2024-11-15 01:45:16 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-15 01:49:16 (9513) [INFO] Script is up to date. * 2024-11-15 01:53:19 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-15 01:53:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-15 01:53:20 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-15 01:53:20 (8441) [INFO] * 2024-11-15 01:58:04 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-15 01:58:04 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-15 01:58:04 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-15 01:58:04 (8441) [INFO] * 2024-11-15 02:01:55 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-15 02:01:55 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-15 02:01:55 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-15 02:01:55 (8471) [INFO] * 2024-11-15 02:01:55 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-15 02:01:55 (8441) [INFO] * 2024-11-15 02:02:05 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-15 02:02:05 (8441) [INFO] * 2024-11-15 02:02:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 02:02:06 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-15 02:02:37 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-15 02:02:37 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-15 02:02:37 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-15 02:02:37 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-15 02:03:23 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-15 02:03:23 (8454) [INFO] Trying other mirror. * 2024-11-15 02:03:54 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-15 02:03:54 (8454) [INFO] Trying other mirror. * 2024-11-15 02:04:25 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-15 02:04:25 (8454) [INFO] Trying other mirror. * 2024-11-15 02:05:54 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:05:54 (8454) [INFO] Trying other mirror. * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-11-15 02:05:54 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-15 02:05:54 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-15 02:05:54 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-15 02:05:54 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-15 02:05:54 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-15 02:05:54 (8454) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-15 02:05:54 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-15 02:05:54 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-11-15 02:05:54 (8454) [INFO] or * 2024-11-15 02:05:54 (8454) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-15 02:05:54 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-15 02:05:54 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-15 02:05:54 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-15 02:05:54 (8454) [INFO] compromise: * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-11-15 02:05:54 (8454) [INFO] * 2024-11-15 02:05:54 (8454) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-11-15 02:05:54 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:05:54 (8471) [INFO] * 2024-11-15 02:05:54 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:05:54 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-15 02:05:54 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-15 02:05:54 (8441) [INFO] * 2024-11-15 02:05:55 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 02:05:55 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-15 02:05:55 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-15 02:05:55 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-15 02:05:55 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-15 02:05:55 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-15 02:05:55 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-15 02:05:55 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-15 02:05:55 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-15 02:05:55 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-15 02:05:55 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-15 02:05:55 (8454) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-11-15 02:05:55 (8471) [INFO] * 2024-11-15 02:05:55 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-15 02:05:55 (8441) [INFO] * 2024-11-15 02:05:56 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 02:05:56 (8454) [INFO] Determining fastest mirrors * 2024-11-15 02:06:27 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-15 02:06:27 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-15 02:06:27 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-15 02:06:27 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-15 02:07:14 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-15 02:07:14 (8454) [INFO] Trying other mirror. * 2024-11-15 02:07:45 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-15 02:07:45 (8454) [INFO] Trying other mirror. * 2024-11-15 02:08:16 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-15 02:08:16 (8454) [INFO] Trying other mirror. * 2024-11-15 02:08:47 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') * 2024-11-15 02:08:47 (8454) [INFO] Trying other mirror. * 2024-11-15 02:09:17 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-15 02:09:17 (8454) [INFO] Trying other mirror. * 2024-11-15 02:10:48 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:10:48 (8454) [INFO] Trying other mirror. * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-11-15 02:10:48 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-15 02:10:48 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-15 02:10:48 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-15 02:10:48 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-15 02:10:48 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-15 02:10:48 (8454) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-15 02:10:48 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-15 02:10:48 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-11-15 02:10:48 (8454) [INFO] or * 2024-11-15 02:10:48 (8454) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-15 02:10:48 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-15 02:10:48 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-15 02:10:48 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-15 02:10:48 (8454) [INFO] compromise: * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-11-15 02:10:48 (8454) [INFO] * 2024-11-15 02:10:48 (8454) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-11-15 02:10:48 (8454) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:10:48 (8471) [INFO] * 2024-11-15 02:10:48 (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 02:10:48 (5518) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMxMzE5ODk0OjE3MzE1NzkwOTQ6h9IjZmq-jrecjusJgOfes2vzCnt_m47bVvL7UgwaAfzAMN1RUifVslWrgcTVRQ4B5r1LjVQK0zmao3aRkA_vI82NPCTikTik7ChJrctuQBAmyjz8uuFnxExKN6ZjJIAlUbqeXJfAO5RNtEKfCLdI6crpcfEAFQP6hSex22KigAmfsw2vfqdXb6zmArwboEo1gzu63KWQLr4a6JIV8RlreKeizhByLBgBpFsvQezCzyYji4SPPzt2zr175kHfGnm5aKg5sKb7SNC9pe4Al9P3BcelGIWdxCBiGApspj5gfmKEDoPKk-Mkg0JCJjXK73WtfsAusigJ-bLABl8MpqA6t-UibBFq7OFrUPwvCRS7bOS94uO2T0mCu8Bu-iZcko2aQg9w9lTwtgZk5EVeChSmUXddvKgumBl8aifxbySRyDSluRKbhACUeN0NIpmx23M7Ee9lNgphMzY_w99jTWv791iX5GKYY2T4MzivM-pwnmemkYGleI8qPNpaVbFbD_Nb_mgC8EbEfYmvaCv9sUZI5JSpkp6BFuLdRkFmvxGoNuM5uqgOrItuZbSFNyPwXZr9k_Nz8sb-Y9FNomo0C5FDMo76_1tBwa_xib7vupIBza7Tqh0erKW1VVrSDVogK9b1jmiR97UZfgl7mktJjngitePMa3q096BCk7I2cH8vOa0=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-11-15 02:10:49 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-15 02:10:49 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-15 02:10:49 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-15 02:10:49 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-15 02:10:49 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-15 02:11:05 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iqWM1yPwrJ/ea_profile.json * 2024-11-15 02:13:24 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iqWM1yPwrJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-15 02:13:24 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-16 01:03:14 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-16 01:07:14 (9513) [INFO] Script is up to date. * 2024-11-16 01:11:17 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-16 01:11:17 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-16 01:11:17 (8441) [INFO] * 2024-11-16 01:11:31 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-16 01:11:31 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-16 01:11:31 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-16 01:11:31 (8441) [INFO] * 2024-11-16 01:14:26 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-16 01:14:26 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-16 01:14:26 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-16 01:14:26 (8471) [INFO] * 2024-11-16 01:14:26 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-16 01:14:26 (8441) [INFO] * 2024-11-16 01:14:41 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-16 01:14:44 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-16 01:14:44 (8441) [INFO] * 2024-11-16 01:14:44 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 01:14:45 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-16 01:15:15 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-16 01:15:15 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-16 01:15:15 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-16 01:15:15 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-16 01:18:03 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-16 01:18:03 (8454) [INFO] Trying other mirror. * 2024-11-16 01:18:21 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-16 01:18:21 (8454) [INFO] Trying other mirror. * 2024-11-16 01:18:52 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-16 01:18:52 (8454) [INFO] Trying other mirror. * 2024-11-16 01:19:07 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-16 01:19:07 (8454) [INFO] Trying other mirror. * 2024-11-16 01:19:08 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-16 01:19:08 (8454) [INFO] Trying other mirror. * 2024-11-16 01:19:22 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-16 01:19:22 (8454) [INFO] Trying other mirror. * 2024-11-16 01:19:38 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:19:38 (8454) [INFO] Trying other mirror. * 2024-11-16 01:20:09 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-16 01:20:09 (8454) [INFO] Trying other mirror. * 2024-11-16 01:20:40 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-16 01:20:40 (8454) [INFO] Trying other mirror. * 2024-11-16 01:21:10 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-16 01:21:10 (8454) [INFO] Trying other mirror. * 2024-11-16 01:21:51 (8454) [INFO] Metadata Cache Created * 2024-11-16 01:21:51 (8471) [INFO] * 2024-11-16 01:21:51 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-16 01:21:51 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-16 01:21:51 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-16 01:21:51 (8441) [INFO] * 2024-11-16 01:21:51 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 01:21:51 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-16 01:21:51 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-16 01:21:51 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-16 01:21:51 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-16 01:21:51 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-16 01:21:51 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-16 01:21:51 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-16 01:21:51 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-16 01:21:51 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-16 01:21:52 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-16 01:21:52 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-16 01:21:52 (8471) [INFO] * 2024-11-16 01:21:52 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-16 01:21:52 (8441) [INFO] * 2024-11-16 01:21:52 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 01:21:53 (8454) [INFO] Determining fastest mirrors * 2024-11-16 01:22:26 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-16 01:22:26 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-16 01:22:26 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-16 01:22:26 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-16 01:25:33 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:25:33 (8454) [INFO] Trying other mirror. * 2024-11-16 01:25:33 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:25:33 (8454) [INFO] Trying other mirror. * 2024-11-16 01:26:03 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-16 01:26:03 (8454) [INFO] Trying other mirror. * 2024-11-16 01:26:34 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2024-11-16 01:26:34 (8454) [INFO] Trying other mirror. * 2024-11-16 01:28:29 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-16 01:28:29 (8454) [INFO] Trying other mirror. * 2024-11-16 01:28:30 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:28:30 (8454) [INFO] Trying other mirror. * 2024-11-16 01:31:39 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-16 01:31:39 (8454) [INFO] Trying other mirror. * 2024-11-16 01:32:11 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:32:11 (8454) [INFO] Trying other mirror. * 2024-11-16 01:32:42 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-16 01:32:42 (8454) [INFO] Trying other mirror. * 2024-11-17 01:55:11 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-17 01:59:11 (9513) [INFO] Script is up to date. * 2024-11-17 02:03:14 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-17 02:03:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-17 02:03:14 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-17 02:03:14 (8441) [INFO] * 2024-11-17 02:03:26 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-17 02:03:26 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-17 02:03:26 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-17 02:03:26 (8441) [INFO] * 2024-11-17 02:06:27 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-17 02:06:27 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-17 02:06:27 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-17 02:06:27 (8471) [INFO] * 2024-11-17 02:06:27 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-17 02:06:27 (8441) [INFO] * 2024-11-17 02:06:40 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-17 02:06:45 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-17 02:06:45 (8441) [INFO] * 2024-11-17 02:06:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 02:06:46 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-17 02:07:16 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-17 02:07:16 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-17 02:07:16 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-17 02:07:16 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-17 02:08:01 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30004 milliseconds with 0 out of 0 bytes received') * 2024-11-17 02:08:01 (8454) [INFO] Trying other mirror. * 2024-11-17 02:08:32 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-17 02:08:32 (8454) [INFO] Trying other mirror. * 2024-11-17 02:09:03 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-17 02:09:03 (8454) [INFO] Trying other mirror. * 2024-11-17 02:11:36 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-17 02:11:36 (8454) [INFO] Trying other mirror. * 2024-11-17 02:11:52 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-17 02:11:52 (8454) [INFO] Trying other mirror. * 2024-11-17 02:12:24 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-17 02:12:24 (8454) [INFO] Trying other mirror. * 2024-11-17 02:12:37 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-17 02:12:37 (8454) [INFO] Trying other mirror. * 2024-11-17 02:12:39 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-17 02:12:39 (8454) [INFO] Trying other mirror. * 2024-11-17 02:13:08 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-17 02:13:08 (8454) [INFO] Trying other mirror. * 2024-11-17 02:13:09 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-17 02:13:09 (8454) [INFO] Trying other mirror. * 2024-11-17 02:13:40 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-17 02:13:40 (8454) [INFO] Trying other mirror. * 2024-11-17 02:14:24 (8454) [INFO] Metadata Cache Created * 2024-11-17 02:14:24 (8471) [INFO] * 2024-11-17 02:14:24 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30004 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-11-17 02:14:24 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-17 02:14:24 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-17 02:14:24 (8441) [INFO] * 2024-11-17 02:14:24 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 02:14:25 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-17 02:14:25 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-17 02:14:25 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-17 02:14:25 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-17 02:14:25 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-17 02:14:25 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-17 02:14:25 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-17 02:14:25 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-17 02:14:25 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-17 02:14:25 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-17 02:14:25 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-17 02:14:25 (8471) [INFO] * 2024-11-17 02:14:25 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-17 02:14:25 (8441) [INFO] * 2024-11-17 02:14:26 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 02:14:26 (8454) [INFO] Determining fastest mirrors * 2024-11-17 02:14:58 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-17 02:14:58 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-17 02:14:58 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-17 02:14:58 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-17 02:18:04 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-17 02:18:04 (8454) [INFO] Trying other mirror. * 2024-11-17 02:18:04 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-17 02:18:04 (8454) [INFO] Trying other mirror. * 2024-11-17 02:21:02 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-17 02:21:02 (8454) [INFO] Trying other mirror. * 2024-11-17 02:23:40 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-17 02:23:40 (8454) [INFO] Trying other mirror. * 2024-11-17 02:24:42 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-11-17 02:24:42 (8454) [INFO] Trying other mirror. * 2024-11-17 02:24:42 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-17 02:24:42 (8454) [INFO] Trying other mirror. * 2024-11-18 01:54:01 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-18 01:58:01 (9513) [INFO] Script is up to date. * 2024-11-18 02:02:04 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-18 02:02:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-18 02:02:05 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-18 02:02:05 (8441) [INFO] * 2024-11-18 02:02:14 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-18 02:02:14 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-18 02:02:14 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-18 02:02:14 (8441) [INFO] * 2024-11-18 02:05:14 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-18 02:05:14 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-18 02:05:14 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-18 02:05:14 (8471) [INFO] * 2024-11-18 02:05:14 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-18 02:05:14 (8441) [INFO] * 2024-11-18 02:05:29 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-18 02:05:33 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-18 02:05:33 (8441) [INFO] * 2024-11-18 02:05:33 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 02:05:33 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-18 02:06:03 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-18 02:06:03 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-18 02:06:03 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-18 02:06:03 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-18 02:08:52 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:08:52 (8454) [INFO] Trying other mirror. * 2024-11-18 02:09:09 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:09:09 (8454) [INFO] Trying other mirror. * 2024-11-18 02:09:54 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:09:54 (8454) [INFO] Trying other mirror. * 2024-11-18 02:09:55 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:09:55 (8454) [INFO] Trying other mirror. * 2024-11-18 02:10:26 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-18 02:10:26 (8454) [INFO] Trying other mirror. * 2024-11-18 02:11:10 (8454) [INFO] Metadata Cache Created * 2024-11-18 02:11:10 (8471) [INFO] * 2024-11-18 02:11:10 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-11-18 02:11:10 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-18 02:11:10 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-18 02:11:10 (8441) [INFO] * 2024-11-18 02:11:10 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 02:11:10 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-18 02:11:10 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-18 02:11:10 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-18 02:11:10 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-18 02:11:10 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-18 02:11:10 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-18 02:11:10 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-18 02:11:10 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-18 02:11:10 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-18 02:11:11 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-18 02:11:11 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-18 02:11:11 (8471) [INFO] * 2024-11-18 02:11:11 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-18 02:11:11 (8441) [INFO] * 2024-11-18 02:11:11 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 02:11:11 (8454) [INFO] Determining fastest mirrors * 2024-11-18 02:11:44 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-18 02:11:44 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-18 02:11:44 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-18 02:11:44 (8454) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-18 02:12:30 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-18 02:12:30 (8454) [INFO] Trying other mirror. * 2024-11-18 02:13:01 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-18 02:13:01 (8454) [INFO] Trying other mirror. * 2024-11-18 02:13:31 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-11-18 02:13:31 (8454) [INFO] Trying other mirror. * 2024-11-18 02:16:21 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-18 02:16:21 (8454) [INFO] Trying other mirror. * 2024-11-18 02:16:21 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:16:21 (8454) [INFO] Trying other mirror. * 2024-11-18 02:19:18 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:19:18 (8454) [INFO] Trying other mirror. * 2024-11-18 02:21:57 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:21:57 (8454) [INFO] Trying other mirror. * 2024-11-18 02:21:58 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-18 02:21:58 (8454) [INFO] Trying other mirror. * 2024-11-18 02:22:59 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:22:59 (8454) [INFO] Trying other mirror. * 2024-11-18 02:22:59 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-18 02:22:59 (8454) [INFO] Trying other mirror. * 2024-11-18 02:23:29 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:23:29 (8454) [INFO] Trying other mirror. * 2024-11-18 02:23:30 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-18 02:23:30 (8454) [INFO] Trying other mirror. * 2024-11-19 02:02:57 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-19 02:06:58 (9513) [INFO] Script is up to date. * 2024-11-19 02:11:01 (5931) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-19 02:11:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-19 02:11:01 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-19 02:11:01 (8441) [INFO] * 2024-11-19 02:11:12 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-19 02:11:12 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-19 02:11:12 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-19 02:11:12 (8441) [INFO] * 2024-11-19 02:14:17 (8454) [INFO] api_ios_ishipstats.device_main * 2024-11-19 02:14:17 (8454) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8454) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-19 02:14:17 (8454) [INFO] note : The storage engine for the table doesn't support check * 2024-11-19 02:14:17 (8471) [INFO] * 2024-11-19 02:14:17 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-19 02:14:17 (8441) [INFO] * 2024-11-19 02:14:31 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-19 02:14:34 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-19 02:14:34 (8441) [INFO] * 2024-11-19 02:14:35 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 02:14:35 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-19 02:15:05 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-19 02:15:05 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-19 02:15:05 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-19 02:15:05 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-19 02:17:53 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:17:53 (8454) [INFO] Trying other mirror. * 2024-11-19 02:18:10 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:18:10 (8454) [INFO] Trying other mirror. * 2024-11-19 02:18:55 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:18:55 (8454) [INFO] Trying other mirror. * 2024-11-19 02:18:57 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-19 02:18:57 (8454) [INFO] Trying other mirror. * 2024-11-19 02:19:26 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-19 02:19:26 (8454) [INFO] Trying other mirror. * 2024-11-19 02:19:28 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-19 02:19:28 (8454) [INFO] Trying other mirror. * 2024-11-19 02:19:58 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:19:58 (8454) [INFO] Trying other mirror. * 2024-11-19 02:20:29 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-19 02:20:29 (8454) [INFO] Trying other mirror. * 2024-11-19 02:21:12 (8454) [INFO] Metadata Cache Created * 2024-11-19 02:21:12 (8471) [INFO] * 2024-11-19 02:21:12 (5507) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-19 02:21:12 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-19 02:21:12 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-19 02:21:12 (8441) [INFO] * 2024-11-19 02:21:13 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 02:21:13 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-19 02:21:13 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-19 02:21:13 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-19 02:21:13 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-19 02:21:13 (8454) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-19 02:21:13 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-19 02:21:13 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-19 02:21:13 (8454) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-19 02:21:13 (8454) [INFO] : wp-toolkit-thirdparties * 2024-11-19 02:21:14 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-19 02:21:14 (8454) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-19 02:21:14 (8471) [INFO] * 2024-11-19 02:21:14 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-19 02:21:14 (8441) [INFO] * 2024-11-19 02:21:14 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 02:21:15 (8454) [INFO] Determining fastest mirrors * 2024-11-19 02:21:46 (8454) [INFO] * EA4: 107.178.98.171 * 2024-11-19 02:21:46 (8454) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-19 02:21:46 (8454) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-19 02:21:46 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-19 02:24:51 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-19 02:24:51 (8454) [INFO] Trying other mirror. * 2024-11-19 02:24:51 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:24:51 (8454) [INFO] Trying other mirror. * 2024-11-19 02:27:48 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:27:48 (8454) [INFO] Trying other mirror. * 2024-11-19 02:30:27 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:30:27 (8454) [INFO] Trying other mirror. * 2024-11-19 02:30:58 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-19 02:30:58 (8454) [INFO] Trying other mirror. * 2024-11-19 02:31:29 (8454) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-19 02:31:29 (8454) [INFO] Trying other mirror. * 2024-11-19 02:31:59 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:31:59 (8454) [INFO] Trying other mirror. * 2024-11-19 02:31:59 (8454) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-19 02:31:59 (8454) [INFO] Trying other mirror. * 2024-11-19 02:32:30 (8454) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-19 02:32:30 (8454) [INFO] Trying other mirror. * 2024-11-20 01:54:36 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-20 01:58:36 (9496) [INFO] Newer version of script found. Downloading. * 2024-11-20 02:02:38 (9505) [INFO] Script update to version 58 successful. * 2024-11-20 02:06:41 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-20 02:06:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-20 02:06:41 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-20 02:06:41 (8445) [INFO] * 2024-11-20 02:06:52 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-20 02:06:52 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-20 02:06:52 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-20 02:06:52 (8445) [INFO] * 2024-11-20 02:09:53 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-20 02:09:53 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-20 02:09:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 02:09:53 (8475) [INFO] * 2024-11-20 02:09:53 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-20 02:09:53 (8445) [INFO] * 2024-11-20 02:10:01 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-20 02:10:06 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 02:10:06 (8445) [INFO] * 2024-11-20 02:10:06 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 02:10:07 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-20 02:10:37 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-20 02:10:37 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-20 02:10:37 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-20 02:10:37 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-20 02:13:25 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2024-11-20 02:13:25 (8458) [INFO] Trying other mirror. * 2024-11-20 02:13:42 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 02:13:42 (8458) [INFO] Trying other mirror. * 2024-11-20 02:14:29 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 02:14:29 (8458) [INFO] Trying other mirror. * 2024-11-20 02:14:29 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 02:14:29 (8458) [INFO] Trying other mirror. * 2024-11-20 02:14:59 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 02:14:59 (8458) [INFO] Trying other mirror. * 2024-11-20 02:15:00 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 02:15:00 (8458) [INFO] Trying other mirror. * 2024-11-20 02:15:30 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 02:15:30 (8458) [INFO] Trying other mirror. * 2024-11-20 02:16:01 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 02:16:01 (8458) [INFO] Trying other mirror. * 2024-11-20 02:16:31 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30012 milliseconds with 0 out of 0 bytes received') * 2024-11-20 02:16:31 (8458) [INFO] Trying other mirror. * 2024-11-20 02:17:16 (8458) [INFO] Metadata Cache Created * 2024-11-20 02:17:16 (8475) [INFO] * 2024-11-20 02:17:16 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30012 milliseconds with 0 out of 0 bytes received') Trying other mirror. * 2024-11-20 02:17:16 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-20 02:17:16 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-20 02:17:16 (8445) [INFO] * 2024-11-20 02:17:17 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 02:17:17 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-20 02:17:17 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-20 02:17:17 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-20 02:17:17 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-20 02:17:17 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-20 02:17:17 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-20 02:17:17 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-20 02:17:17 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-20 02:17:17 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-20 02:17:18 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-20 02:17:18 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-20 02:17:18 (8475) [INFO] * 2024-11-20 02:17:18 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 02:17:18 (8445) [INFO] * 2024-11-20 02:17:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 02:17:18 (8458) [INFO] Determining fastest mirrors * 2024-11-20 02:17:50 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-20 02:17:50 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-20 02:17:50 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-20 02:17:50 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-20 02:20:55 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 02:20:55 (8458) [INFO] Trying other mirror. * 2024-11-20 02:20:56 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 02:20:56 (8458) [INFO] Trying other mirror. * 2024-11-20 02:23:53 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 02:23:53 (8458) [INFO] Trying other mirror. * 2024-11-20 18:55:14 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-20 18:59:15 (9517) [INFO] Script is up to date. * 2024-11-20 19:03:18 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-20 19:03:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-20 19:03:18 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-20 19:03:18 (8445) [INFO] * 2024-11-20 19:03:30 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-20 19:03:30 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-20 19:03:30 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-20 19:03:30 (8445) [INFO] * 2024-11-20 19:06:41 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-20 19:06:41 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-20 19:06:41 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-20 19:06:41 (8475) [INFO] * 2024-11-20 19:06:41 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-20 19:06:41 (8445) [INFO] * 2024-11-20 19:06:57 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-20 19:07:02 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 19:07:02 (8445) [INFO] * 2024-11-20 19:07:03 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 19:07:03 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-20 19:07:33 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-20 19:07:33 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-20 19:07:33 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-20 19:07:33 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-20 19:10:09 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:10:09 (8458) [INFO] Trying other mirror. * 2024-11-20 19:10:31 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2024-11-20 19:10:31 (8458) [INFO] Trying other mirror. * 2024-11-20 19:10:39 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-11-20 19:10:39 (8458) [INFO] Trying other mirror. * 2024-11-20 19:11:11 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2024-11-20 19:11:11 (8458) [INFO] Trying other mirror. * 2024-11-20 19:11:11 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2024-11-20 19:11:11 (8458) [INFO] Trying other mirror. * 2024-11-20 19:11:32 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 19:11:32 (8458) [INFO] Trying other mirror. * 2024-11-20 19:11:57 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:11:57 (8458) [INFO] Trying other mirror. * 2024-11-20 19:11:57 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:11:57 (8458) [INFO] Trying other mirror. * 2024-11-20 19:12:27 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') * 2024-11-20 19:12:27 (8458) [INFO] Trying other mirror. * 2024-11-20 19:12:27 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30029 milliseconds with 0 out of 0 bytes received') * 2024-11-20 19:12:27 (8458) [INFO] Trying other mirror. * 2024-11-20 19:12:57 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') * 2024-11-20 19:12:57 (8458) [INFO] Trying other mirror. * 2024-11-20 19:12:57 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:12:57 (8458) [INFO] Trying other mirror. * 2024-11-20 19:12:58 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-20 19:12:58 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:04 (8458) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" * 2024-11-20 19:13:04 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:35 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-11-20 19:13:35 (8458) [INFO] Trying other mirror. * 2024-11-20 19:13:35 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30798 milliseconds') * 2024-11-20 19:13:35 (8458) [INFO] Trying other mirror. * 2024-11-20 19:14:05 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:14:05 (8458) [INFO] Trying other mirror. * 2024-11-20 19:14:06 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30948 milliseconds') * 2024-11-20 19:14:06 (8458) [INFO] Trying other mirror. * 2024-11-20 19:14:36 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 19:14:36 (8458) [INFO] Trying other mirror. * 2024-11-20 19:15:07 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:15:07 (8458) [INFO] Trying other mirror. * 2024-11-20 19:15:37 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 19:15:37 (8458) [INFO] Trying other mirror. * 2024-11-20 19:16:08 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 19:16:08 (8458) [INFO] Trying other mirror. * 2024-11-20 19:16:39 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-20 19:16:39 (8458) [INFO] Trying other mirror. * 2024-11-20 19:17:32 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-20 19:17:32 (8458) [INFO] Trying other mirror. * 2024-11-20 19:18:02 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:18:02 (8458) [INFO] Trying other mirror. * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] One of the configured repositories failed (Unknown), * 2024-11-20 19:18:34 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-20 19:18:34 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-20 19:18:34 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-20 19:18:34 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-20 19:18:34 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-20 19:18:34 (8458) [INFO] yum --disablerepo= ... * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-20 19:18:34 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-20 19:18:34 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] yum-config-manager --disable * 2024-11-20 19:18:34 (8458) [INFO] or * 2024-11-20 19:18:34 (8458) [INFO] subscription-manager repos --disable= * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-20 19:18:34 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-20 19:18:34 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-20 19:18:34 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-20 19:18:34 (8458) [INFO] compromise: * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-20 19:18:34 (8458) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] centos7-els: Check uncompressed DB failed * 2024-11-20 19:18:34 (8475) [INFO] * 2024-11-20 19:18:34 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/22ce3d6eeb0a1c3d032931f309a84de9d3cca0765444be04b9876b0264586771-filelists.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30029 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 12] Timeout on https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/20fd87b2110444f8f01a1b509b5f07b4fd441611116fe0f3b500805164f8c999-other.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to repo.tuxcare.com:443; Connection refused" Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30798 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30948 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') 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 centos7-els: Check uncompressed DB failed * 2024-11-20 19:18:34 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-20 19:18:34 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-20 19:18:34 (8445) [INFO] * 2024-11-20 19:18:34 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 19:18:35 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-20 19:18:35 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-20 19:18:35 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-20 19:18:35 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-20 19:18:35 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-20 19:18:35 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-20 19:18:35 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-20 19:18:35 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-20 19:18:35 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-20 19:18:35 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-20 19:18:35 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-20 19:18:35 (8475) [INFO] * 2024-11-20 19:18:35 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 19:18:35 (8445) [INFO] * 2024-11-20 19:18:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 19:18:36 (8458) [INFO] Determining fastest mirrors * 2024-11-20 19:19:09 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-20 19:19:09 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-20 19:19:09 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-20 19:19:09 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-20 19:22:00 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-20 19:22:00 (8458) [INFO] Trying other mirror. * 2024-11-20 19:22:00 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-20 19:22:00 (8458) [INFO] Trying other mirror. * 2024-11-20 19:22:30 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 19:22:30 (8458) [INFO] Trying other mirror. * 2024-11-20 19:23:01 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-20 19:23:01 (8458) [INFO] Trying other mirror. * 2024-11-20 19:24:44 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-20 19:24:44 (8458) [INFO] Trying other mirror. * 2024-11-21 01:53:10 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-21 01:57:11 (9517) [INFO] Script is up to date. * 2024-11-21 02:01:14 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-21 02:01:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-21 02:01:14 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-21 02:01:14 (8445) [INFO] * 2024-11-21 02:01:18 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-21 02:01:18 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-21 02:01:18 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-21 02:01:18 (8445) [INFO] * 2024-11-21 02:04:14 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-21 02:04:14 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-21 02:04:14 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-21 02:04:14 (8475) [INFO] * 2024-11-21 02:04:14 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-21 02:04:14 (8445) [INFO] * 2024-11-21 02:04:28 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-21 02:04:32 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 02:04:32 (8445) [INFO] * 2024-11-21 02:04:32 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 02:04:32 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-21 02:05:02 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-21 02:05:02 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-21 02:05:02 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-21 02:05:02 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-21 02:07:43 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-21 02:07:43 (8458) [INFO] Trying other mirror. * 2024-11-21 02:08:01 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-21 02:08:01 (8458) [INFO] Trying other mirror. * 2024-11-21 02:08:32 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-21 02:08:32 (8458) [INFO] Trying other mirror. * 2024-11-21 02:09:15 (8458) [INFO] Metadata Cache Created * 2024-11-21 02:09:15 (8475) [INFO] * 2024-11-21 02:09:15 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-21 02:09:15 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-21 02:09:15 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-21 02:09:15 (8445) [INFO] * 2024-11-21 02:09:15 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 02:09:16 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-21 02:09:16 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-21 02:09:16 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-21 02:09:16 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-21 02:09:16 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-21 02:09:16 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-21 02:09:16 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-21 02:09:16 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-21 02:09:16 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-21 02:09:16 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-21 02:09:16 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-21 02:09:16 (8475) [INFO] * 2024-11-21 02:09:16 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 02:09:16 (8445) [INFO] * 2024-11-21 02:09:17 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 02:09:17 (8458) [INFO] Determining fastest mirrors * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] One of the configured repositories failed (Unknown), * 2024-11-21 02:09:49 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-21 02:09:49 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-21 02:09:49 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-21 02:09:49 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-21 02:09:49 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-21 02:09:49 (8458) [INFO] yum --disablerepo= ... * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-21 02:09:49 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-21 02:09:49 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] yum-config-manager --disable * 2024-11-21 02:09:49 (8458) [INFO] or * 2024-11-21 02:09:49 (8458) [INFO] subscription-manager repos --disable= * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-21 02:09:49 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-21 02:09:49 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-21 02:09:49 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-21 02:09:49 (8458) [INFO] compromise: * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-21 02:09:49 (8458) [INFO] * 2024-11-21 02:09:49 (8458) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-21 02:09:49 (8475) [INFO] * 2024-11-21 02:09:49 (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 02:09:49 (5521) [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 * 2024-11-21 02:09:50 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-21 02:09:50 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-21 02:09:50 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-21 02:09:50 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-21 02:09:50 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-21 02:10:05 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0KfyB5rrjz/ea_profile.json * 2024-11-21 02:17:29 (7608) [INFO] Backed up EA4 profile to /tmp/0KfyB5rrjz/ea_profile.json * 2024-11-21 02:17:30 (249) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-11-21 02:18:04 (618) [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-11-21 02:18:04 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-22 01:56:51 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-22 02:00:51 (9517) [INFO] Script is up to date. * 2024-11-22 02:04:54 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-22 02:04:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-22 02:04:55 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-22 02:04:55 (8445) [INFO] * 2024-11-22 02:04:58 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-22 02:04:58 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-22 02:04:58 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-22 02:04:58 (8445) [INFO] * 2024-11-22 02:07:54 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-22 02:07:54 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-22 02:07:54 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-22 02:07:54 (8475) [INFO] * 2024-11-22 02:07:54 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-22 02:07:54 (8445) [INFO] * 2024-11-22 02:08:11 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-22 02:08:17 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-22 02:08:17 (8445) [INFO] * 2024-11-22 02:08:17 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 02:08:17 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-22 02:08:47 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-22 02:08:47 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-22 02:08:47 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-22 02:08:47 (8458) [INFO] * epel: mirror.math.princeton.edu * 2024-11-22 02:11:22 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:11:22 (8458) [INFO] Trying other mirror. * 2024-11-22 02:11:39 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-22 02:11:39 (8458) [INFO] Trying other mirror. * 2024-11-22 02:12:00 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-22 02:12:00 (8458) [INFO] Trying other mirror. * 2024-11-22 02:12:09 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:12:09 (8458) [INFO] Trying other mirror. * 2024-11-22 02:12:10 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:12:10 (8458) [INFO] Trying other mirror. * 2024-11-22 02:12:30 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:12:30 (8458) [INFO] Trying other mirror. * 2024-11-22 02:12:40 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:12:40 (8458) [INFO] Trying other mirror. * 2024-11-22 02:13:01 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:13:01 (8458) [INFO] Trying other mirror. * 2024-11-22 02:13:44 (8458) [INFO] Metadata Cache Created * 2024-11-22 02:13:44 (8475) [INFO] * 2024-11-22 02:13:44 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-22 02:13:44 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-22 02:13:44 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-22 02:13:44 (8445) [INFO] * 2024-11-22 02:13:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 02:13:44 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-22 02:13:44 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-22 02:13:44 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-22 02:13:44 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-22 02:13:44 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-22 02:13:44 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-22 02:13:44 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-22 02:13:44 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-22 02:13:44 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-22 02:13:45 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-22 02:13:45 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-22 02:13:45 (8475) [INFO] * 2024-11-22 02:13:45 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-22 02:13:45 (8445) [INFO] * 2024-11-22 02:13:45 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 02:13:45 (8458) [INFO] Determining fastest mirrors * 2024-11-22 02:14:18 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-22 02:14:18 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-22 02:14:18 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-22 02:14:18 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-22 02:15:04 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:15:04 (8458) [INFO] Trying other mirror. * 2024-11-22 02:17:39 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-22 02:17:39 (8458) [INFO] Trying other mirror. * 2024-11-22 02:17:40 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-22 02:17:40 (8458) [INFO] Trying other mirror. * 2024-11-22 02:20:21 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:20:21 (8458) [INFO] Trying other mirror. * 2024-11-22 02:23:00 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:23:00 (8458) [INFO] Trying other mirror. * 2024-11-22 02:23:01 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30691 milliseconds') * 2024-11-22 02:23:01 (8458) [INFO] Trying other mirror. * 2024-11-22 02:24:01 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:24:01 (8458) [INFO] Trying other mirror. * 2024-11-22 02:24:02 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:24:02 (8458) [INFO] Trying other mirror. * 2024-11-22 02:24:32 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:24:32 (8458) [INFO] Trying other mirror. * 2024-11-22 02:24:32 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:24:32 (8458) [INFO] Trying other mirror. * 2024-11-22 02:25:02 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Operation timed out after 30131 milliseconds with 0 out of 0 bytes received') * 2024-11-22 02:25:02 (8458) [INFO] Trying other mirror. * 2024-11-22 02:25:33 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:25:33 (8458) [INFO] Trying other mirror. * 2024-11-22 02:25:33 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-22 02:25:33 (8458) [INFO] Trying other mirror. * 2024-11-22 02:26:04 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-22 02:26:04 (8458) [INFO] Trying other mirror. * 2024-11-22 02:26:35 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-22 02:26:35 (8458) [INFO] Trying other mirror. * 2024-11-23 01:54:11 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-23 01:58:11 (9517) [INFO] Script is up to date. * 2024-11-23 02:02:15 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-23 02:02:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-23 02:02:15 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-23 02:02:15 (8445) [INFO] * 2024-11-23 02:02:26 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-23 02:02:26 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-23 02:02:26 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-23 02:02:26 (8445) [INFO] * 2024-11-23 02:05:28 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-23 02:05:28 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-23 02:05:28 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-23 02:05:28 (8475) [INFO] * 2024-11-23 02:05:28 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-23 02:05:28 (8445) [INFO] * 2024-11-23 02:05:42 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-23 02:05:46 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-23 02:05:46 (8445) [INFO] * 2024-11-23 02:05:47 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 02:05:47 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-23 02:06:17 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-23 02:06:17 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-23 02:06:17 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-23 02:06:17 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-23 02:08:51 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:08:51 (8458) [INFO] Trying other mirror. * 2024-11-23 02:09:09 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-23 02:09:09 (8458) [INFO] Trying other mirror. * 2024-11-23 02:09:39 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:09:39 (8458) [INFO] Trying other mirror. * 2024-11-23 02:09:39 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:09:39 (8458) [INFO] Trying other mirror. * 2024-11-23 02:10:21 (8458) [INFO] Metadata Cache Created * 2024-11-23 02:10:21 (8475) [INFO] * 2024-11-23 02:10:21 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-23 02:10:21 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-23 02:10:21 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-23 02:10:21 (8445) [INFO] * 2024-11-23 02:10:21 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 02:10:22 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-23 02:10:22 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-23 02:10:22 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-23 02:10:22 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-23 02:10:22 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-23 02:10:22 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-23 02:10:22 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-23 02:10:22 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-23 02:10:22 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-23 02:10:22 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-23 02:10:22 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-23 02:10:22 (8475) [INFO] * 2024-11-23 02:10:22 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-23 02:10:22 (8445) [INFO] * 2024-11-23 02:10:22 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 02:10:23 (8458) [INFO] Determining fastest mirrors * 2024-11-23 02:10:54 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-23 02:10:54 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-23 02:10:54 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-23 02:10:54 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-23 02:13:46 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-23 02:13:46 (8458) [INFO] Trying other mirror. * 2024-11-23 02:13:46 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-23 02:13:46 (8458) [INFO] Trying other mirror. * 2024-11-23 02:14:16 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:14:16 (8458) [INFO] Trying other mirror. * 2024-11-23 02:14:47 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-23 02:14:47 (8458) [INFO] Trying other mirror. * 2024-11-23 02:16:28 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-23 02:16:28 (8458) [INFO] Trying other mirror. * 2024-11-23 02:19:37 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-23 02:19:37 (8458) [INFO] Trying other mirror. * 2024-11-23 02:19:37 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-23 02:19:37 (8458) [INFO] Trying other mirror. * 2024-11-23 02:20:07 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:20:07 (8458) [INFO] Trying other mirror. * 2024-11-23 02:21:09 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:21:09 (8458) [INFO] Trying other mirror. * 2024-11-23 02:21:09 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:21:09 (8458) [INFO] Trying other mirror. * 2024-11-23 02:22:10 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-23 02:22:10 (8458) [INFO] Trying other mirror. * 2024-11-23 02:22:41 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-11-23 02:22:41 (8458) [INFO] Trying other mirror. * 2024-11-23 02:23:12 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-23 02:23:12 (8458) [INFO] Trying other mirror. * 2024-11-23 02:23:43 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-23 02:23:43 (8458) [INFO] Trying other mirror. * 2024-11-24 01:56:49 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-24 02:00:50 (9517) [INFO] Script is up to date. * 2024-11-24 02:04:53 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-24 02:04:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-24 02:04:53 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-24 02:04:53 (8445) [INFO] * 2024-11-24 02:05:04 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-24 02:05:04 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-24 02:05:04 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-24 02:05:04 (8445) [INFO] * 2024-11-24 02:08:10 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-24 02:08:10 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-24 02:08:10 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-24 02:08:10 (8475) [INFO] * 2024-11-24 02:08:10 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-24 02:08:10 (8445) [INFO] * 2024-11-24 02:08:24 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-24 02:08:29 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-24 02:08:29 (8445) [INFO] * 2024-11-24 02:08:29 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 02:08:29 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-24 02:08:59 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-24 02:08:59 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-24 02:08:59 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-24 02:08:59 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-24 02:11:32 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:11:32 (8458) [INFO] Trying other mirror. * 2024-11-24 02:11:50 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:11:50 (8458) [INFO] Trying other mirror. * 2024-11-24 02:12:20 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-24 02:12:20 (8458) [INFO] Trying other mirror. * 2024-11-24 02:12:20 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:12:20 (8458) [INFO] Trying other mirror. * 2024-11-24 02:13:02 (8458) [INFO] Metadata Cache Created * 2024-11-24 02:13:02 (8475) [INFO] * 2024-11-24 02:13:02 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-24 02:13:03 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-24 02:13:03 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-24 02:13:03 (8445) [INFO] * 2024-11-24 02:13:03 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 02:13:03 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-24 02:13:03 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-24 02:13:03 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-24 02:13:03 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-24 02:13:03 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-24 02:13:03 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-24 02:13:03 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-24 02:13:03 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-24 02:13:03 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-24 02:13:04 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-24 02:13:04 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-24 02:13:04 (8475) [INFO] * 2024-11-24 02:13:04 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-24 02:13:04 (8445) [INFO] * 2024-11-24 02:13:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 02:13:05 (8458) [INFO] Determining fastest mirrors * 2024-11-24 02:13:37 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-24 02:13:37 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-24 02:13:37 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-24 02:13:37 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-24 02:14:23 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-24 02:14:23 (8458) [INFO] Trying other mirror. * 2024-11-24 02:14:54 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-24 02:14:54 (8458) [INFO] Trying other mirror. * 2024-11-24 02:17:30 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:17:30 (8458) [INFO] Trying other mirror. * 2024-11-24 02:17:30 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-24 02:17:30 (8458) [INFO] Trying other mirror. * 2024-11-24 02:18:00 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-24 02:18:00 (8458) [INFO] Trying other mirror. * 2024-11-24 02:18:31 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-24 02:18:31 (8458) [INFO] Trying other mirror. * 2024-11-24 02:20:12 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:20:12 (8458) [INFO] Trying other mirror. * 2024-11-24 02:23:22 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-24 02:23:22 (8458) [INFO] Trying other mirror. * 2024-11-24 02:24:24 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:24:24 (8458) [INFO] Trying other mirror. * 2024-11-24 02:24:24 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-24 02:24:24 (8458) [INFO] Trying other mirror. * 2024-11-24 02:24:55 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-24 02:24:55 (8458) [INFO] Trying other mirror. * 2024-11-24 02:26:09 (8458) [INFO] Metadata Cache Created * 2024-11-24 02:26:09 (8475) [INFO] * 2024-11-24 02:26: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-11-24 02:26:09 (5521) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-24 02:26:10 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-24 02:26:10 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-24 02:26:10 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-24 02:26:10 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-24 02:26:10 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-24 02:26:24 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0NXTM0g7iO/ea_profile.json * 2024-11-24 02:26:25 (7608) [INFO] Backed up EA4 profile to /tmp/0NXTM0g7iO/ea_profile.json * 2024-11-24 02:26:26 (249) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-11-25 01:57:21 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-25 02:01:21 (9517) [INFO] Script is up to date. * 2024-11-25 02:05:24 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-25 02:05:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-25 02:05:24 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-25 02:05:24 (8445) [INFO] * 2024-11-25 02:05:35 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-25 02:05:35 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-25 02:05:35 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-25 02:05:35 (8445) [INFO] * 2024-11-25 02:08:30 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-25 02:08:30 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-25 02:08:30 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-25 02:08:30 (8475) [INFO] * 2024-11-25 02:08:30 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-25 02:08:30 (8445) [INFO] * 2024-11-25 02:08:45 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-25 02:08:50 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-25 02:08:50 (8445) [INFO] * 2024-11-25 02:08:50 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 02:08:51 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-25 02:09:21 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-25 02:09:21 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-25 02:09:21 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-25 02:09:21 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-25 02:11:54 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-25 02:11:54 (8458) [INFO] Trying other mirror. * 2024-11-25 02:12:11 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-25 02:12:11 (8458) [INFO] Trying other mirror. * 2024-11-25 02:12:42 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-25 02:12:42 (8458) [INFO] Trying other mirror. * 2024-11-25 02:12:43 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-25 02:12:43 (8458) [INFO] Trying other mirror. * 2024-11-25 02:13:13 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-25 02:13:13 (8458) [INFO] Trying other mirror. * 2024-11-25 02:13:14 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-25 02:13:14 (8458) [INFO] Trying other mirror. * 2024-11-25 02:13:43 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-25 02:13:43 (8458) [INFO] Trying other mirror. * 2024-11-25 02:13:44 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-25 02:13:44 (8458) [INFO] Trying other mirror. * 2024-11-25 02:14:25 (8458) [INFO] Metadata Cache Created * 2024-11-25 02:14:25 (8475) [INFO] * 2024-11-25 02:14:25 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-25 02:14:25 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-25 02:14:25 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-25 02:14:25 (8445) [INFO] * 2024-11-25 02:14:26 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 02:14:26 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-25 02:14:26 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-25 02:14:26 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-25 02:14:26 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-25 02:14:26 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-25 02:14:26 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-25 02:14:26 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-25 02:14:26 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-25 02:14:26 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-25 02:14:27 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-25 02:14:27 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-25 02:14:27 (8475) [INFO] * 2024-11-25 02:14:27 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-25 02:14:27 (8445) [INFO] * 2024-11-25 02:14:27 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 02:14:27 (8458) [INFO] Determining fastest mirrors * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] One of the configured repositories failed (Unknown), * 2024-11-25 02:14:58 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-25 02:14:58 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-25 02:14:58 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-25 02:14:58 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-25 02:14:58 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-25 02:14:58 (8458) [INFO] yum --disablerepo= ... * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-25 02:14:58 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-25 02:14:58 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] yum-config-manager --disable * 2024-11-25 02:14:58 (8458) [INFO] or * 2024-11-25 02:14:58 (8458) [INFO] subscription-manager repos --disable= * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-25 02:14:58 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-25 02:14:58 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-25 02:14:58 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-25 02:14:58 (8458) [INFO] compromise: * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-25 02:14:58 (8458) [INFO] * 2024-11-25 02:14:58 (8458) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-25 02:14:58 (8475) [INFO] * 2024-11-25 02:14:58 (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 02:14:58 (5521) [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 * 2024-11-25 02:14:59 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-25 02:14:59 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-25 02:14:59 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-25 02:14:59 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-25 02:14:59 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-25 02:23:26 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/BvZtp6QSUJ/ea_profile.json * 2024-11-26 02:04:22 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-26 02:08:22 (9517) [INFO] Script is up to date. * 2024-11-26 02:12:25 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-26 02:12:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-26 02:12:25 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-26 02:12:25 (8445) [INFO] * 2024-11-26 02:12:28 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-26 02:12:28 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-26 02:12:28 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-26 02:12:28 (8445) [INFO] * 2024-11-26 02:15:27 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-26 02:15:27 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-26 02:15:27 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-26 02:15:27 (8475) [INFO] * 2024-11-26 02:15:28 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-26 02:15:28 (8445) [INFO] * 2024-11-26 02:15:42 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-26 02:15:44 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-26 02:15:44 (8445) [INFO] * 2024-11-26 02:15:45 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 02:15:45 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-26 02:16:15 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-26 02:16:15 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-26 02:16:15 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-26 02:16:15 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-26 02:17:01 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2024-11-26 02:17:01 (8458) [INFO] Trying other mirror. * 2024-11-26 02:17:32 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-26 02:17:32 (8458) [INFO] Trying other mirror. * 2024-11-26 02:18:03 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30597 milliseconds') * 2024-11-26 02:18:03 (8458) [INFO] Trying other mirror. * 2024-11-26 02:20:20 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:20:20 (8458) [INFO] Trying other mirror. * 2024-11-26 02:20:37 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:20:37 (8458) [INFO] Trying other mirror. * 2024-11-26 02:21:07 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-26 02:21:07 (8458) [INFO] Trying other mirror. * 2024-11-26 02:21:08 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-26 02:21:08 (8458) [INFO] Trying other mirror. * 2024-11-26 02:21:37 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-26 02:21:37 (8458) [INFO] Trying other mirror. * 2024-11-26 02:22:08 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-26 02:22:08 (8458) [INFO] Trying other mirror. * 2024-11-26 02:22:38 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:22:38 (8458) [INFO] Trying other mirror. * 2024-11-26 02:23:09 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-26 02:23:09 (8458) [INFO] Trying other mirror. * 2024-11-26 02:23:52 (8458) [INFO] Metadata Cache Created * 2024-11-26 02:23:52 (8475) [INFO] * 2024-11-26 02:23:52 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-11-26 02:23:52 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-26 02:23:52 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-26 02:23:52 (8445) [INFO] * 2024-11-26 02:23:52 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 02:23:53 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-26 02:23:53 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-26 02:23:53 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-26 02:23:53 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-26 02:23:53 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-26 02:23:53 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-26 02:23:53 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-26 02:23:53 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-26 02:23:53 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-26 02:23:53 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-26 02:23:53 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-26 02:23:53 (8475) [INFO] * 2024-11-26 02:23:53 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-26 02:23:53 (8445) [INFO] * 2024-11-26 02:23:54 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 02:23:54 (8458) [INFO] Determining fastest mirrors * 2024-11-26 02:24:25 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-26 02:24:25 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-26 02:24:25 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-26 02:24:25 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-26 02:27:17 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:27:17 (8458) [INFO] Trying other mirror. * 2024-11-26 02:27:17 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-26 02:27:17 (8458) [INFO] Trying other mirror. * 2024-11-26 02:27:47 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-26 02:27:47 (8458) [INFO] Trying other mirror. * 2024-11-26 02:30:00 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:30:00 (8458) [INFO] Trying other mirror. * 2024-11-26 02:32:39 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:32:39 (8458) [INFO] Trying other mirror. * 2024-11-26 02:33:41 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:33:41 (8458) [INFO] Trying other mirror. * 2024-11-26 02:33:41 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-26 02:33:41 (8458) [INFO] Trying other mirror. * 2024-11-26 02:34:11 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-26 02:34:11 (8458) [INFO] Trying other mirror. * 2024-11-27 02:06:34 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-27 02:10:34 (9517) [INFO] Script is up to date. * 2024-11-27 02:14:38 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-27 02:14:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-27 02:14:38 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-27 02:14:38 (8445) [INFO] * 2024-11-27 02:14:41 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-27 02:14:41 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-27 02:14:41 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-27 02:14:41 (8445) [INFO] * 2024-11-27 02:17:36 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-27 02:17:36 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-27 02:17:36 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-27 02:17:36 (8475) [INFO] * 2024-11-27 02:17:36 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-27 02:17:36 (8445) [INFO] * 2024-11-27 02:17:47 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-27 02:17:51 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-27 02:17:51 (8445) [INFO] * 2024-11-27 02:17:52 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 02:17:52 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-27 02:18:23 (8458) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-11-27 02:18:23 (8458) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30851 milliseconds') * 2024-11-27 02:18:23 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-27 02:18:23 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-27 02:18:23 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-27 02:18:23 (8458) [INFO] * epel: mirror.math.princeton.edu * 2024-11-27 02:20:57 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:20:57 (8458) [INFO] Trying other mirror. * 2024-11-27 02:21:13 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:21:13 (8458) [INFO] Trying other mirror. * 2024-11-27 02:21:35 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-27 02:21:35 (8458) [INFO] Trying other mirror. * 2024-11-27 02:21:45 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:21:45 (8458) [INFO] Trying other mirror. * 2024-11-27 02:22:06 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-11-27 02:22:06 (8458) [INFO] Trying other mirror. * 2024-11-27 02:22:53 (8458) [INFO] Metadata Cache Created * 2024-11-27 02:22:53 (8475) [INFO] * 2024-11-27 02:22:53 (5510) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30851 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2024-11-27 02:22:53 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-27 02:22:53 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-27 02:22:53 (8445) [INFO] * 2024-11-27 02:22:53 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 02:22:54 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-27 02:22:54 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-27 02:22:54 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-27 02:22:54 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-27 02:22:54 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-27 02:22:54 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-27 02:22:54 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-27 02:22:54 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-27 02:22:54 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-27 02:22:54 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-27 02:22:54 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-27 02:22:54 (8475) [INFO] * 2024-11-27 02:22:54 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-27 02:22:54 (8445) [INFO] * 2024-11-27 02:22:55 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 02:22:55 (8458) [INFO] Determining fastest mirrors * 2024-11-27 02:23:27 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-27 02:23:27 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-27 02:23:27 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-27 02:23:27 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-27 02:26:18 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:26:18 (8458) [INFO] Trying other mirror. * 2024-11-27 02:26:18 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-27 02:26:18 (8458) [INFO] Trying other mirror. * 2024-11-27 02:29:00 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-27 02:29:00 (8458) [INFO] Trying other mirror. * 2024-11-27 02:31:38 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:31:38 (8458) [INFO] Trying other mirror. * 2024-11-27 02:31:39 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-27 02:31:39 (8458) [INFO] Trying other mirror. * 2024-11-27 02:32:09 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-27 02:32:09 (8458) [INFO] Trying other mirror. * 2024-11-27 02:33:10 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:33:10 (8458) [INFO] Trying other mirror. * 2024-11-27 02:33:11 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-27 02:33:11 (8458) [INFO] Trying other mirror. * 2024-11-27 02:33:41 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:33:41 (8458) [INFO] Trying other mirror. * 2024-11-27 02:34:11 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-27 02:34:11 (8458) [INFO] Trying other mirror. * 2024-11-27 02:34:12 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-27 02:34:12 (8458) [INFO] Trying other mirror. * 2024-11-27 02:34:42 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-27 02:34:42 (8458) [INFO] Trying other mirror. * 2024-11-27 02:35:43 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-27 02:35:43 (8458) [INFO] Trying other mirror. * 2024-11-27 02:36:14 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-27 02:36:14 (8458) [INFO] Trying other mirror. * 2024-11-28 01:43:46 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-28 01:47:46 (9517) [INFO] Script is up to date. * 2024-11-28 01:51:50 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-28 01:51:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-28 01:51:50 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-28 01:51:50 (8445) [INFO] * 2024-11-28 01:51:53 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-28 01:51:53 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-28 01:51:53 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-28 01:51:53 (8445) [INFO] * 2024-11-28 01:54:53 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-28 01:54:53 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-28 01:54:53 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-28 01:54:53 (8475) [INFO] * 2024-11-28 01:54:53 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-28 01:54:53 (8445) [INFO] * 2024-11-28 01:55:09 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-28 01:55:13 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-28 01:55:13 (8445) [INFO] * 2024-11-28 01:55:14 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 01:55:14 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-28 01:55:44 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-28 01:55:44 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-28 01:55:44 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-28 01:55:44 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-28 01:57:46 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-28 01:57:46 (8458) [INFO] Trying other mirror. * 2024-11-28 01:57:46 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 01:57:46 (8458) [INFO] Trying other mirror. * 2024-11-28 01:58:17 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 01:58:17 (8458) [INFO] Trying other mirror. * 2024-11-28 01:58:20 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 01:58:20 (8458) [INFO] Trying other mirror. * 2024-11-28 01:58:50 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 01:58:50 (8458) [INFO] Trying other mirror. * 2024-11-28 01:58:50 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-28 01:58:50 (8458) [INFO] Trying other mirror. * 2024-11-28 01:59:06 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2024-11-28 01:59:06 (8458) [INFO] Trying other mirror. * 2024-11-28 01:59:37 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-28 01:59:37 (8458) [INFO] Trying other mirror. * 2024-11-28 02:00:07 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:00:07 (8458) [INFO] Trying other mirror. * 2024-11-28 02:00:07 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:00:07 (8458) [INFO] Trying other mirror. * 2024-11-28 02:00:08 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-28 02:00:08 (8458) [INFO] Trying other mirror. * 2024-11-28 02:01:08 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:01:08 (8458) [INFO] Trying other mirror. * 2024-11-28 02:01:09 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:01:09 (8458) [INFO] Trying other mirror. * 2024-11-28 02:01:39 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:01:39 (8458) [INFO] Trying other mirror. * 2024-11-28 02:02:10 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2024-11-28 02:02:10 (8458) [INFO] Trying other mirror. * 2024-11-28 02:03:18 (8458) [INFO] Metadata Cache Created * 2024-11-28 02:03:18 (8475) [INFO] * 2024-11-28 02:03:18 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. * 2024-11-28 02:03:18 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-28 02:03:18 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-28 02:03:18 (8445) [INFO] * 2024-11-28 02:03:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 02:03:19 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-28 02:03:19 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-28 02:03:19 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-28 02:03:19 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-28 02:03:19 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-28 02:03:19 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-28 02:03:19 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-28 02:03:19 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-28 02:03:19 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-28 02:03:19 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-28 02:03:19 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-28 02:03:19 (8475) [INFO] * 2024-11-28 02:03:19 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-28 02:03:19 (8445) [INFO] * 2024-11-28 02:03:20 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 02:03:20 (8458) [INFO] Determining fastest mirrors * 2024-11-28 02:03:54 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-28 02:03:54 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-28 02:03:54 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-28 02:03:54 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-28 02:06:14 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-28 02:06:14 (8458) [INFO] Trying other mirror. * 2024-11-28 02:06:15 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30916 milliseconds') * 2024-11-28 02:06:15 (8458) [INFO] Trying other mirror. * 2024-11-28 02:06:45 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-28 02:06:45 (8458) [INFO] Trying other mirror. * 2024-11-28 02:07:23 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:07:24 (8458) [INFO] Trying other mirror. * 2024-11-28 02:07:24 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:07:24 (8458) [INFO] Trying other mirror. * 2024-11-28 02:08:30 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:08:30 (8458) [INFO] Trying other mirror. * 2024-11-28 02:09:01 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:09:01 (8458) [INFO] Trying other mirror. * 2024-11-28 02:09:31 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30067 milliseconds') * 2024-11-28 02:09:31 (8458) [INFO] Trying other mirror. * 2024-11-28 02:10:01 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:10:01 (8458) [INFO] Trying other mirror. * 2024-11-28 02:10:02 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:10:02 (8458) [INFO] Trying other mirror. * 2024-11-28 02:10:32 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:10:32 (8458) [INFO] Trying other mirror. * 2024-11-28 02:10:32 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-28 02:10:32 (8458) [INFO] Trying other mirror. * 2024-11-28 02:11:02 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-11-28 02:11:02 (8458) [INFO] Trying other mirror. * 2024-11-28 02:11:33 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:11:33 (8458) [INFO] Trying other mirror. * 2024-11-28 02:11:33 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:11:33 (8458) [INFO] Trying other mirror. * 2024-11-28 02:12:03 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-11-28 02:12:03 (8458) [INFO] Trying other mirror. * 2024-11-28 02:12:03 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-28 02:12:03 (8458) [INFO] Trying other mirror. * 2024-11-28 02:12:34 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-28 02:12:34 (8458) [INFO] Trying other mirror. * 2024-11-28 02:13:05 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-11-28 02:13:05 (8458) [INFO] Trying other mirror. * 2024-11-28 02:13:35 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-11-28 02:13:35 (8458) [INFO] Trying other mirror. * 2024-11-29 01:57:13 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-29 02:01:13 (9517) [INFO] Script is up to date. * 2024-11-29 02:05:16 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-29 02:05:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-29 02:05:17 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-29 02:05:17 (8445) [INFO] * 2024-11-29 02:05:20 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-29 02:05:20 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-29 02:05:20 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-29 02:05:20 (8445) [INFO] * 2024-11-29 02:08:22 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-29 02:08:22 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-29 02:08:22 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-29 02:08:22 (8475) [INFO] * 2024-11-29 02:08:22 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-29 02:08:22 (8445) [INFO] * 2024-11-29 02:08:36 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-29 02:08:41 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-29 02:08:41 (8445) [INFO] * 2024-11-29 02:08:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 02:08:42 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-29 02:09:12 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-29 02:09:12 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-29 02:09:12 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-29 02:09:12 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-29 02:12:22 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-11-29 02:12:22 (8458) [INFO] Trying other mirror. * 2024-11-29 02:12:47 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-29 02:12:47 (8458) [INFO] Trying other mirror. * 2024-11-29 02:13:16 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-29 02:13:16 (8458) [INFO] Trying other mirror. * 2024-11-29 02:13:33 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-29 02:13:33 (8458) [INFO] Trying other mirror. * 2024-11-29 02:13:37 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-29 02:13:37 (8458) [INFO] Trying other mirror. * 2024-11-29 02:13:46 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-29 02:13:46 (8458) [INFO] Trying other mirror. * 2024-11-29 02:14:08 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-29 02:14:08 (8458) [INFO] Trying other mirror. * 2024-11-29 02:14:17 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-29 02:14:17 (8458) [INFO] Trying other mirror. * 2024-11-29 02:14:57 (8458) [INFO] Metadata Cache Created * 2024-11-29 02:14:57 (8475) [INFO] * 2024-11-29 02:14:57 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-11-29 02:14:57 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-29 02:14:57 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-29 02:14:57 (8445) [INFO] * 2024-11-29 02:14:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 02:14:58 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-29 02:14:58 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-29 02:14:58 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-29 02:14:58 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-29 02:14:58 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-29 02:14:58 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-29 02:14:58 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-29 02:14:58 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-29 02:14:58 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-29 02:14:58 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-29 02:14:58 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-29 02:14:59 (8475) [INFO] * 2024-11-29 02:14:59 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-29 02:14:59 (8445) [INFO] * 2024-11-29 02:14:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 02:14:59 (8458) [INFO] Determining fastest mirrors * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] One of the configured repositories failed (Unknown), * 2024-11-29 02:15:30 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-29 02:15:30 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-29 02:15:30 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-29 02:15:30 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-29 02:15:30 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-29 02:15:30 (8458) [INFO] yum --disablerepo= ... * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-29 02:15:30 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-29 02:15:30 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] yum-config-manager --disable * 2024-11-29 02:15:30 (8458) [INFO] or * 2024-11-29 02:15:30 (8458) [INFO] subscription-manager repos --disable= * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-29 02:15:30 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-29 02:15:30 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-29 02:15:30 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-29 02:15:30 (8458) [INFO] compromise: * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-11-29 02:15:30 (8458) [INFO] * 2024-11-29 02:15:30 (8458) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-11-29 02:15:30 (8475) [INFO] * 2024-11-29 02:15:30 (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 02:15:30 (5521) [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 * 2024-11-29 02:15:31 (3096) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-11-29 02:15:31 (249) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-11-29 02:15:31 (3920) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-11-29 02:15:31 (3926) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-11-29 02:15:31 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-29 02:15:36 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SbQ_ftveD0/ea_profile.json * 2024-11-29 02:23:00 (7608) [INFO] Backed up EA4 profile to /tmp/SbQ_ftveD0/ea_profile.json * 2024-11-29 02:23:01 (249) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-11-29 02:23:35 (618) [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-11-29 02:23:35 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-30 01:59:27 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-30 02:03:27 (9517) [INFO] Script is up to date. * 2024-11-30 02:07:30 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-11-30 02:07:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-30 02:07:31 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-30 02:07:31 (8445) [INFO] * 2024-11-30 02:07:34 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-11-30 02:07:34 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-30 02:07:34 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-30 02:07:34 (8445) [INFO] * 2024-11-30 02:10:34 (8458) [INFO] api_ios_ishipstats.device_main * 2024-11-30 02:10:34 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-11-30 02:10:34 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-11-30 02:10:34 (8475) [INFO] * 2024-11-30 02:10:34 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-30 02:10:34 (8445) [INFO] * 2024-11-30 02:10:45 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-11-30 02:10:49 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-30 02:10:49 (8445) [INFO] * 2024-11-30 02:10:49 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 02:10:49 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-30 02:11:20 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-30 02:11:20 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-30 02:11:20 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-30 02:11:20 (8458) [INFO] * epel: mirror.math.princeton.edu * 2024-11-30 02:14:30 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-30 02:14:30 (8458) [INFO] Trying other mirror. * 2024-11-30 02:14:56 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-11-30 02:14:56 (8458) [INFO] Trying other mirror. * 2024-11-30 02:15:42 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-30 02:15:42 (8458) [INFO] Trying other mirror. * 2024-11-30 02:15:45 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-11-30 02:15:45 (8458) [INFO] Trying other mirror. * 2024-11-30 02:16:15 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-30 02:16:15 (8458) [INFO] Trying other mirror. * 2024-11-30 02:16:56 (8458) [INFO] Metadata Cache Created * 2024-11-30 02:16:56 (8475) [INFO] * 2024-11-30 02:16:56 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-11-30 02:16:56 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-30 02:16:56 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-30 02:16:56 (8445) [INFO] * 2024-11-30 02:16:56 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 02:16:57 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-11-30 02:16:57 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-30 02:16:57 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-30 02:16:57 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-11-30 02:16:57 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-11-30 02:16:57 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-30 02:16:57 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-30 02:16:57 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-11-30 02:16:57 (8458) [INFO] : wp-toolkit-thirdparties * 2024-11-30 02:16:57 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-30 02:16:57 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-11-30 02:16:57 (8475) [INFO] * 2024-11-30 02:16:57 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-30 02:16:57 (8445) [INFO] * 2024-11-30 02:16:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 02:16:58 (8458) [INFO] Determining fastest mirrors * 2024-11-30 02:17:31 (8458) [INFO] * EA4: 107.178.98.171 * 2024-11-30 02:17:31 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-11-30 02:17:31 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-11-30 02:17:31 (8458) [INFO] * epel: pubmirror1.math.uh.edu * 2024-11-30 02:20:56 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-11-30 02:20:56 (8458) [INFO] Trying other mirror. * 2024-11-30 02:20:56 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-11-30 02:20:56 (8458) [INFO] Trying other mirror. * 2024-11-30 02:24:24 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-11-30 02:24:24 (8458) [INFO] Trying other mirror. * 2024-11-30 02:28:23 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-11-30 02:28:23 (8458) [INFO] Trying other mirror. * 2024-12-01 01:55:03 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-01 01:59:03 (9517) [INFO] Script is up to date. * 2024-12-01 02:03:06 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-01 02:03:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-01 02:03:06 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-01 02:03:06 (8445) [INFO] * 2024-12-01 02:03:11 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-01 02:03:11 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-01 02:03:11 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-01 02:03:11 (8445) [INFO] * 2024-12-01 02:06:07 (8458) [INFO] api_ios_ishipstats.device_main * 2024-12-01 02:06:07 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-12-01 02:06:07 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-01 02:06:07 (8475) [INFO] * 2024-12-01 02:06:07 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-01 02:06:07 (8445) [INFO] * 2024-12-01 02:06:19 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-01 02:06:23 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-01 02:06:23 (8445) [INFO] * 2024-12-01 02:06:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 02:06:24 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-01 02:06:54 (8458) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-12-01 02:06:54 (8458) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2024-12-01 02:06:54 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-01 02:06:54 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-01 02:06:54 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-01 02:06:54 (8458) [INFO] * epel: mirror.math.princeton.edu * 2024-12-01 02:10:04 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2024-12-01 02:10:04 (8458) [INFO] Trying other mirror. * 2024-12-01 02:10:27 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:10:27 (8458) [INFO] Trying other mirror. * 2024-12-01 02:10:58 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-01 02:10:58 (8458) [INFO] Trying other mirror. * 2024-12-01 02:11:18 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:11:18 (8458) [INFO] Trying other mirror. * 2024-12-01 02:11:21 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-01 02:11:21 (8458) [INFO] Trying other mirror. * 2024-12-01 02:11:49 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-01 02:11:49 (8458) [INFO] Trying other mirror. * 2024-12-01 02:11:51 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:11:51 (8458) [INFO] Trying other mirror. * 2024-12-01 02:12:37 (8458) [INFO] Metadata Cache Created * 2024-12-01 02:12:37 (8475) [INFO] * 2024-12-01 02:12:37 (5510) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-01 02:12:37 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-01 02:12:37 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-01 02:12:37 (8445) [INFO] * 2024-12-01 02:12:37 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 02:12:37 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-01 02:12:37 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-01 02:12:37 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-01 02:12:37 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-01 02:12:37 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-01 02:12:37 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-01 02:12:37 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-01 02:12:37 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-01 02:12:37 (8458) [INFO] : wp-toolkit-thirdparties * 2024-12-01 02:12:38 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-01 02:12:38 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-01 02:12:38 (8475) [INFO] * 2024-12-01 02:12:38 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-01 02:12:38 (8445) [INFO] * 2024-12-01 02:12:38 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 02:12:39 (8458) [INFO] Determining fastest mirrors * 2024-12-01 02:13:10 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-01 02:13:10 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-01 02:13:10 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-01 02:13:10 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-01 02:13:57 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-01 02:13:57 (8458) [INFO] Trying other mirror. * 2024-12-01 02:17:08 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:17:08 (8458) [INFO] Trying other mirror. * 2024-12-01 02:17:08 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-01 02:17:08 (8458) [INFO] Trying other mirror. * 2024-12-01 02:20:35 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:20:35 (8458) [INFO] Trying other mirror. * 2024-12-01 02:24:35 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-01 02:24:35 (8458) [INFO] Trying other mirror. * 2024-12-01 02:24:35 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-01 02:24:35 (8458) [INFO] Trying other mirror. * 2024-12-02 01:55:36 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-02 01:59:36 (9517) [INFO] Script is up to date. * 2024-12-02 02:03:39 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-02 02:03:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-02 02:03:39 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-02 02:03:39 (8445) [INFO] * 2024-12-02 02:03:43 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-02 02:03:43 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-02 02:03:43 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-02 02:03:43 (8445) [INFO] * 2024-12-02 02:06:39 (8458) [INFO] api_ios_ishipstats.device_main * 2024-12-02 02:06:39 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-12-02 02:06:39 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-02 02:06:39 (8475) [INFO] * 2024-12-02 02:06:39 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-02 02:06:39 (8445) [INFO] * 2024-12-02 02:06:53 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-02 02:06:58 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-02 02:06:58 (8445) [INFO] * 2024-12-02 02:06:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 02:06:59 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-02 02:07:29 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-02 02:07:29 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-02 02:07:29 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-02 02:07:29 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-02 02:08:15 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2024-12-02 02:08:15 (8458) [INFO] Trying other mirror. * 2024-12-02 02:11:10 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-02 02:11:10 (8458) [INFO] Trying other mirror. * 2024-12-02 02:11:34 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-02 02:11:34 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:05 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-02 02:12:05 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:20 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-02 02:12:20 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:24 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-02 02:12:24 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:36 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-02 02:12:36 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:50 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-02 02:12:50 (8458) [INFO] Trying other mirror. * 2024-12-02 02:12:54 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-02 02:12:54 (8458) [INFO] Trying other mirror. * 2024-12-02 02:13:06 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-02 02:13:06 (8458) [INFO] Trying other mirror. * 2024-12-02 02:13:25 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-02 02:13:25 (8458) [INFO] Trying other mirror. * 2024-12-02 02:13:36 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-02 02:13:36 (8458) [INFO] Trying other mirror. * 2024-12-02 02:13:55 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-02 02:13:55 (8458) [INFO] Trying other mirror. * 2024-12-02 02:14:07 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-02 02:14:07 (8458) [INFO] Trying other mirror. * 2024-12-02 02:14:49 (8458) [INFO] Metadata Cache Created * 2024-12-02 02:14:49 (8475) [INFO] * 2024-12-02 02:14:49 (5510) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-12-02 02:14:49 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-02 02:14:49 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-02 02:14:49 (8445) [INFO] * 2024-12-02 02:14:50 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 02:14:50 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-02 02:14:50 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-02 02:14:50 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-02 02:14:50 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-02 02:14:50 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-02 02:14:50 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-02 02:14:50 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-02 02:14:50 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-02 02:14:50 (8458) [INFO] : wp-toolkit-thirdparties * 2024-12-02 02:14:51 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-02 02:14:51 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-02 02:14:51 (8475) [INFO] * 2024-12-02 02:14:51 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-02 02:14:51 (8445) [INFO] * 2024-12-02 02:14:51 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 02:14:51 (8458) [INFO] Determining fastest mirrors * 2024-12-02 02:15:25 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-02 02:15:25 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-02 02:15:25 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-02 02:15:25 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-02 02:18:51 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-02 02:18:51 (8458) [INFO] Trying other mirror. * 2024-12-02 02:18:51 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-02 02:18:51 (8458) [INFO] Trying other mirror. * 2024-12-02 02:22:17 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-02 02:22:17 (8458) [INFO] Trying other mirror. * 2024-12-03 02:01:01 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-03 02:05:01 (9517) [INFO] Script is up to date. * 2024-12-03 02:09:04 (5935) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-03 02:09:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-03 02:09:04 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-03 02:09:04 (8445) [INFO] * 2024-12-03 02:09:07 (3710) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-03 02:09:07 (3717) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-03 02:09:07 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-03 02:09:07 (8445) [INFO] * 2024-12-03 02:12:01 (8458) [INFO] api_ios_ishipstats.device_main * 2024-12-03 02:12:01 (8458) [INFO] warning : Found row where the auto_increment column has the value 0 * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_category_product_index_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_decimal_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_eav_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_opt_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_sel_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_bundle_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_agr_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_cfg_opt_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_downlod_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_final_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_agr_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_opt_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.catalog_product_index_price_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8458) [INFO] healthybeads_magento.cataloginventory_stock_status_tmp * 2024-12-03 02:12:01 (8458) [INFO] note : The storage engine for the table doesn't support check * 2024-12-03 02:12:01 (8475) [INFO] * 2024-12-03 02:12:01 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-03 02:12:01 (8445) [INFO] * 2024-12-03 02:12:15 (249) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-03 02:12:20 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-03 02:12:20 (8445) [INFO] * 2024-12-03 02:12:20 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 02:12:20 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-03 02:12:51 (8458) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-12-03 02:12:51 (8458) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30600 milliseconds') * 2024-12-03 02:12:51 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-03 02:12:51 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-03 02:12:51 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-03 02:12:51 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-03 02:13:38 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-03 02:13:38 (8458) [INFO] Trying other mirror. * 2024-12-03 02:16:33 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-03 02:16:33 (8458) [INFO] Trying other mirror. * 2024-12-03 02:16:56 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-03 02:16:56 (8458) [INFO] Trying other mirror. * 2024-12-03 02:17:28 (8458) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-03 02:17:28 (8458) [INFO] Trying other mirror. * 2024-12-03 02:17:48 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-03 02:17:48 (8458) [INFO] Trying other mirror. * 2024-12-03 02:17:50 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-03 02:17:50 (8458) [INFO] Trying other mirror. * 2024-12-03 02:18:21 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-03 02:18:21 (8458) [INFO] Trying other mirror. * 2024-12-03 02:18:51 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-03 02:18:51 (8458) [INFO] Trying other mirror. * 2024-12-03 02:19:22 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-03 02:19:22 (8458) [INFO] Trying other mirror. * 2024-12-03 02:19:52 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-03 02:19:52 (8458) [INFO] Trying other mirror. * 2024-12-03 02:20:35 (8458) [INFO] Metadata Cache Created * 2024-12-03 02:20:35 (8475) [INFO] * 2024-12-03 02:20:35 (5510) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30600 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2024-12-03 02:20:35 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-03 02:20:35 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-03 02:20:35 (8445) [INFO] * 2024-12-03 02:20:35 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 02:20:36 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-03 02:20:36 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-03 02:20:36 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-03 02:20:36 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-03 02:20:36 (8458) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-03 02:20:36 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-03 02:20:36 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-03 02:20:36 (8458) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-03 02:20:36 (8458) [INFO] : wp-toolkit-thirdparties * 2024-12-03 02:20:36 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-03 02:20:36 (8458) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-03 02:20:36 (8475) [INFO] * 2024-12-03 02:20:36 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-03 02:20:36 (8445) [INFO] * 2024-12-03 02:20:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 02:20:37 (8458) [INFO] Determining fastest mirrors * 2024-12-03 02:21:09 (8458) [INFO] * EA4: 107.178.98.171 * 2024-12-03 02:21:09 (8458) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-03 02:21:09 (8458) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-03 02:21:09 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-03 02:24:36 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-03 02:24:36 (8458) [INFO] Trying other mirror. * 2024-12-03 02:24:37 (8458) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-03 02:24:37 (8458) [INFO] Trying other mirror. * 2024-12-03 02:28:03 (8458) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2024-12-03 02:28:03 (8458) [INFO] Trying other mirror. * 2024-12-04 01:57:45 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-04 02:01:45 (9500) [INFO] Newer version of script found. Downloading. * 2024-12-04 02:05:47 (9509) [INFO] Script update to version 59 successful. * 2024-12-04 02:09:50 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-04 02:09:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-04 02:09:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-04 02:09:50 (9238) [INFO] * 2024-12-04 02:09:53 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-04 02:09:53 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-04 02:09:53 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-04 02:09:53 (9238) [INFO] * 2024-12-04 02:10:05 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-04 02:10:08 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-04 02:10:08 (9238) [INFO] * 2024-12-04 02:10:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 02:10:09 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-04 02:10:39 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-04 02:10:39 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-04 02:10:39 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-04 02:10:39 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-04 02:13:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-04 02:13:49 (9251) [INFO] Trying other mirror. * 2024-12-04 02:14:14 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-04 02:14:14 (9251) [INFO] Trying other mirror. * 2024-12-04 02:14:43 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-04 02:14:43 (9251) [INFO] Trying other mirror. * 2024-12-04 02:15:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-04 02:15:00 (9251) [INFO] Trying other mirror. * 2024-12-04 02:15:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-04 02:15:04 (9251) [INFO] Trying other mirror. * 2024-12-04 02:15:14 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-04 02:15:14 (9251) [INFO] Trying other mirror. * 2024-12-04 02:15:35 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-04 02:15:35 (9251) [INFO] Trying other mirror. * 2024-12-04 02:16:16 (9251) [INFO] Metadata Cache Created * 2024-12-04 02:16:16 (9268) [INFO] * 2024-12-04 02:16:16 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-12-04 02:16:16 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-04 02:16:16 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-04 02:16:16 (9238) [INFO] * 2024-12-04 02:16:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 02:16:17 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-04 02:16:17 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-04 02:16:17 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-04 02:16:17 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-04 02:16:17 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-04 02:16:17 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-04 02:16:17 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-04 02:16:17 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-04 02:16:17 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-04 02:16:18 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-04 02:16:18 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-04 02:16:18 (9268) [INFO] * 2024-12-04 02:16:18 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-04 02:16:18 (9238) [INFO] * 2024-12-04 02:16:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 02:16:19 (9251) [INFO] Determining fastest mirrors * 2024-12-04 02:16:50 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-04 02:16:50 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-04 02:16:50 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-04 02:16:50 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-04 02:17:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-04 02:17:37 (9251) [INFO] Trying other mirror. * 2024-12-04 02:20:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-04 02:20:49 (9251) [INFO] Trying other mirror. * 2024-12-04 02:20:50 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-04 02:20:50 (9251) [INFO] Trying other mirror. * 2024-12-04 02:21:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-04 02:21:20 (9251) [INFO] Trying other mirror. * 2024-12-04 02:21:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-04 02:21:51 (9251) [INFO] Trying other mirror. * 2024-12-04 02:24:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-04 02:24:27 (9251) [INFO] Trying other mirror. * 2024-12-05 01:56:14 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-05 02:00:14 (10313) [INFO] Script is up to date. * 2024-12-05 02:04:17 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-05 02:04:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-05 02:04:17 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-05 02:04:17 (9238) [INFO] * 2024-12-05 02:04:21 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-05 02:04:21 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-05 02:04:21 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-05 02:04:21 (9238) [INFO] * 2024-12-05 02:04:31 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-05 02:04:34 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-05 02:04:34 (9238) [INFO] * 2024-12-05 02:04:35 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 02:04:35 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-05 02:05:06 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-12-05 02:05:06 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30600 milliseconds') * 2024-12-05 02:05:06 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-05 02:05:06 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-05 02:05:06 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-05 02:05:06 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-05 02:08:15 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:08:15 (9251) [INFO] Trying other mirror. * 2024-12-05 02:08:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:08:39 (9251) [INFO] Trying other mirror. * 2024-12-05 02:09:31 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:09:31 (9251) [INFO] Trying other mirror. * 2024-12-05 02:09:48 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:09:48 (9251) [INFO] Trying other mirror. * 2024-12-05 02:09:48 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-05 02:09:48 (9251) [INFO] Trying other mirror. * 2024-12-05 02:10:18 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-05 02:10:18 (9251) [INFO] Trying other mirror. * 2024-12-05 02:10:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-05 02:10:19 (9251) [INFO] Trying other mirror. * 2024-12-05 02:10:49 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-05 02:10:49 (9251) [INFO] Trying other mirror. * 2024-12-05 02:10:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-05 02:10:49 (9251) [INFO] Trying other mirror. * 2024-12-05 02:11:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:11:20 (9251) [INFO] Trying other mirror. * 2024-12-05 02:12:38 (9251) [INFO] Metadata Cache Created * 2024-12-05 02:12:38 (9268) [INFO] * 2024-12-05 02:12:38 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30600 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-05 02:12:38 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-05 02:12:38 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-05 02:12:38 (9238) [INFO] * 2024-12-05 02:12:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 02:12:39 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-05 02:12:39 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-05 02:12:39 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-05 02:12:39 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-05 02:12:39 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-05 02:12:39 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-05 02:12:39 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-05 02:12:39 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-05 02:12:39 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-05 02:12:40 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-05 02:12:40 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-05 02:12:40 (9268) [INFO] * 2024-12-05 02:12:40 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-05 02:12:40 (9238) [INFO] * 2024-12-05 02:12:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 02:12:41 (9251) [INFO] Determining fastest mirrors * 2024-12-05 02:13:12 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-05 02:13:12 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-05 02:13:12 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-05 02:13:12 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-05 02:13:58 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30316 milliseconds') * 2024-12-05 02:13:58 (9251) [INFO] Trying other mirror. * 2024-12-05 02:14:29 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-05 02:14:29 (9251) [INFO] Trying other mirror. * 2024-12-05 02:17:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:17:42 (9251) [INFO] Trying other mirror. * 2024-12-05 02:17:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-05 02:17:42 (9251) [INFO] Trying other mirror. * 2024-12-05 02:21:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:21:07 (9251) [INFO] Trying other mirror. * 2024-12-05 02:25:06 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-05 02:25:06 (9251) [INFO] Trying other mirror. * 2024-12-06 01:58:42 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-06 02:02:42 (10313) [INFO] Script is up to date. * 2024-12-06 02:06:45 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-06 02:06:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-06 02:06:46 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-06 02:06:46 (9238) [INFO] * 2024-12-06 02:06:58 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-06 02:06:58 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-06 02:06:58 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-06 02:06:58 (9238) [INFO] * 2024-12-06 02:07:09 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-06 02:07:13 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-06 02:07:13 (9238) [INFO] * 2024-12-06 02:07:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 02:07:13 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-06 02:07:44 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-06 02:07:44 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-06 02:07:44 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-06 02:07:44 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-06 02:08:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-06 02:08:30 (9251) [INFO] Trying other mirror. * 2024-12-06 02:09:01 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-06 02:09:01 (9251) [INFO] Trying other mirror. * 2024-12-06 02:11:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-06 02:11:56 (9251) [INFO] Trying other mirror. * 2024-12-06 02:11:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-06 02:11:56 (9251) [INFO] Trying other mirror. * 2024-12-06 02:12:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-06 02:12:21 (9251) [INFO] Trying other mirror. * 2024-12-06 02:12:51 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-06 02:12:51 (9251) [INFO] Trying other mirror. * 2024-12-06 02:13:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-06 02:13:29 (9251) [INFO] Trying other mirror. * 2024-12-06 02:13:29 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2024-12-06 02:13:29 (9251) [INFO] Trying other mirror. * 2024-12-06 02:13:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-06 02:13:59 (9251) [INFO] Trying other mirror. * 2024-12-06 02:14:00 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-06 02:14:00 (9251) [INFO] Trying other mirror. * 2024-12-06 02:14:31 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-06 02:14:31 (9251) [INFO] Trying other mirror. * 2024-12-06 02:15:02 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-06 02:15:02 (9251) [INFO] Trying other mirror. * 2024-12-06 02:15:32 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-06 02:15:32 (9251) [INFO] Trying other mirror. * 2024-12-06 02:16:15 (9251) [INFO] Metadata Cache Created * 2024-12-06 02:16:15 (9268) [INFO] * 2024-12-06 02:16:15 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-06 02:16:15 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-06 02:16:15 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-06 02:16:15 (9238) [INFO] * 2024-12-06 02:16:15 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 02:16:16 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-06 02:16:16 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-06 02:16:16 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-06 02:16:16 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-06 02:16:16 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-06 02:16:16 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-06 02:16:16 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-06 02:16:16 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-06 02:16:16 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-06 02:16:16 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-06 02:16:16 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-06 02:16:16 (9268) [INFO] * 2024-12-06 02:16:16 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-06 02:16:16 (9238) [INFO] * 2024-12-06 02:16:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 02:16:17 (9251) [INFO] Determining fastest mirrors * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-06 02:16:49 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-06 02:16:49 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-06 02:16:49 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-06 02:16:49 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-06 02:16:49 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-06 02:16:49 (9251) [INFO] yum --disablerepo= ... * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-06 02:16:49 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-06 02:16:49 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] yum-config-manager --disable * 2024-12-06 02:16:49 (9251) [INFO] or * 2024-12-06 02:16:49 (9251) [INFO] subscription-manager repos --disable= * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-06 02:16:49 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-06 02:16:49 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-06 02:16:49 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-06 02:16:49 (9251) [INFO] compromise: * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-06 02:16:49 (9251) [INFO] * 2024-12-06 02:16:49 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-06 02:16:49 (9268) [INFO] * 2024-12-06 02:16: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-06 02:16:49 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-06 02:16:49 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-06 02:16:49 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-06 02:16:50 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-06 02:16:50 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-06 02:16:50 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-06 02:19:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MYMubyUXCp/ea_profile.json * 2024-12-06 02:27:15 (8385) [INFO] Backed up EA4 profile to /tmp/MYMubyUXCp/ea_profile.json * 2024-12-06 02:27:16 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-06 02:27:50 (627) [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-12-06 02:27:50 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-07 01:48:00 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-07 01:52:01 (10313) [INFO] Script is up to date. * 2024-12-07 01:56:04 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-07 01:56:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-07 01:56:04 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-07 01:56:04 (9238) [INFO] * 2024-12-07 01:56:07 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-07 01:56:07 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-07 01:56:07 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-07 01:56:07 (9238) [INFO] * 2024-12-07 01:56:38 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-07 01:56:38 (9238) [INFO] * 2024-12-07 01:56:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 01:56:39 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-07 01:57:09 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-07 01:57:09 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-07 01:57:09 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-07 01:57:09 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-07 01:57:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-07 01:57:56 (9251) [INFO] Trying other mirror. * 2024-12-07 01:59:39 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 01:59:39 (9251) [INFO] Trying other mirror. * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-07 01:59:39 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-07 01:59:39 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-07 01:59:39 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-07 01:59:39 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-07 01:59:39 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-07 01:59:39 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-07 01:59:39 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-07 01:59:39 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-07 01:59:39 (9251) [INFO] or * 2024-12-07 01:59:39 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-07 01:59:39 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-07 01:59:39 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-07 01:59:39 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-07 01:59:39 (9251) [INFO] compromise: * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-07 01:59:39 (9251) [INFO] * 2024-12-07 01:59:39 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-07 01:59:39 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 01:59:40 (9268) [INFO] * 2024-12-07 01:59:40 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 01:59:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-07 01:59:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-07 01:59:40 (9238) [INFO] * 2024-12-07 01:59:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 01:59:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-07 01:59:40 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-07 01:59:40 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-07 01:59:40 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-07 01:59:40 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-07 01:59:40 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-07 01:59:40 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-07 01:59:40 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-07 01:59:40 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-07 01:59:40 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-07 01:59:40 (9251) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-12-07 01:59:41 (9268) [INFO] * 2024-12-07 01:59:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-07 01:59:41 (9238) [INFO] * 2024-12-07 01:59:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 01:59:41 (9251) [INFO] Determining fastest mirrors * 2024-12-07 02:00:15 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-07 02:00:15 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-07 02:00:15 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-07 02:00:15 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-07 02:02:17 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 02:02:17 (9251) [INFO] Trying other mirror. * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-07 02:02:17 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-07 02:02:17 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-07 02:02:17 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-07 02:02:17 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-07 02:02:17 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-07 02:02:17 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-07 02:02:17 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-07 02:02:17 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-07 02:02:17 (9251) [INFO] or * 2024-12-07 02:02:17 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-07 02:02:17 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-07 02:02:17 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-07 02:02:17 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-07 02:02:17 (9251) [INFO] compromise: * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-07 02:02:17 (9251) [INFO] * 2024-12-07 02:02:17 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-07 02:02:17 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 02:02:17 (9268) [INFO] * 2024-12-07 02:02:17 (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 02:02:17 (5804) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-07 02:02:17 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-07 02:02:17 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-07 02:02:17 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-07 02:02:17 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-07 02:02:17 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-07 02:08:05 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ADqeNRWIHx/ea_profile.json * 2024-12-07 02:11:37 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ADqeNRWIHx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-07 02:11:37 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-08 01:46:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-08 01:50:47 (10313) [INFO] Script is up to date. * 2024-12-08 01:54:49 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-08 01:54:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-08 01:54:49 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-08 01:54:49 (9238) [INFO] * 2024-12-08 01:54:53 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-08 01:54:53 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-08 01:54:53 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-08 01:54:53 (9238) [INFO] * 2024-12-08 01:56:49 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-08 01:56:49 (9238) [INFO] * 2024-12-08 01:56:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 01:56:49 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-08 01:57:20 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-08 01:57:20 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-08 01:57:20 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-08 01:57:20 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-08 01:59:19 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 01:59:19 (9251) [INFO] Trying other mirror. * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-08 01:59:19 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-08 01:59:19 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-08 01:59:19 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-08 01:59:19 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-08 01:59:19 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-08 01:59:19 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-08 01:59:19 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-08 01:59:19 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-08 01:59:19 (9251) [INFO] or * 2024-12-08 01:59:19 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-08 01:59:19 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-08 01:59:19 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-08 01:59:19 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-08 01:59:19 (9251) [INFO] compromise: * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-08 01:59:19 (9251) [INFO] * 2024-12-08 01:59:19 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-08 01:59:19 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 01:59:19 (9268) [INFO] * 2024-12-08 01:59:19 (5793) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 01:59:19 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-08 01:59:19 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-08 01:59:19 (9238) [INFO] * 2024-12-08 01:59:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 01:59:20 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-08 01:59:20 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-08 01:59:20 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-08 01:59:20 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-08 01:59:20 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-08 01:59:20 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-08 01:59:20 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-08 01:59:20 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-08 01:59:20 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-08 01:59:20 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-08 01:59:20 (9251) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2024-12-08 01:59:20 (9268) [INFO] * 2024-12-08 01:59:20 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-08 01:59:20 (9238) [INFO] * 2024-12-08 01:59:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 01:59:21 (9251) [INFO] Determining fastest mirrors * 2024-12-08 01:59:52 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-08 01:59:52 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-08 01:59:52 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-08 01:59:52 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-08 02:01:52 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 02:01:52 (9251) [INFO] Trying other mirror. * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-08 02:01:52 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-08 02:01:52 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-08 02:01:52 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-08 02:01:52 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-08 02:01:52 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-08 02:01:52 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-08 02:01:52 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-08 02:01:52 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-08 02:01:52 (9251) [INFO] or * 2024-12-08 02:01:52 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-08 02:01:52 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-08 02:01:52 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-08 02:01:52 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-08 02:01:52 (9251) [INFO] compromise: * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-08 02:01:52 (9251) [INFO] * 2024-12-08 02:01:52 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-08 02:01:52 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 02:01:52 (9268) [INFO] * 2024-12-08 02:01: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/ * 2024-12-08 02:01:52 (5804) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-08 02:01:53 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-08 02:01:53 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-08 02:01:53 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-08 02:01:53 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-08 02:01:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-08 02:01:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QR9sjukZdJ/ea_profile.json * 2024-12-08 02:04:31 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QR9sjukZdJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-08 02:04:31 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-09 01:46:45 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-09 01:50:45 (10313) [INFO] Script is up to date. * 2024-12-09 01:54:48 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-09 01:54:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-09 01:54:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-09 01:54:48 (9238) [INFO] * 2024-12-09 01:54:52 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-09 01:54:52 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-09 01:54:52 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-09 01:54:52 (9238) [INFO] * 2024-12-09 01:55:20 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-09 01:55:20 (9238) [INFO] * 2024-12-09 01:55:21 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 01:55:21 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-09 01:55:52 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-09 01:55:52 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-09 01:55:52 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-09 01:55:52 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-09 01:57:51 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 01:57:51 (9251) [INFO] Trying other mirror. * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-09 01:57:51 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-09 01:57:51 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-09 01:57:51 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-09 01:57:51 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-09 01:57:51 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-09 01:57:51 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-09 01:57:51 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-09 01:57:51 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-09 01:57:51 (9251) [INFO] or * 2024-12-09 01:57:51 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-09 01:57:51 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-09 01:57:51 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-09 01:57:51 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-09 01:57:51 (9251) [INFO] compromise: * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-09 01:57:51 (9251) [INFO] * 2024-12-09 01:57:51 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-09 01:57:51 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 01:57:51 (9268) [INFO] * 2024-12-09 01:57:51 (5793) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 01:57:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-09 01:57:51 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-09 01:57:51 (9238) [INFO] * 2024-12-09 01:57:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 01:57:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-09 01:57:52 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-09 01:57:52 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-09 01:57:52 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-09 01:57:52 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-09 01:57:52 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-09 01:57:52 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-09 01:57:52 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-09 01:57:52 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-09 01:57:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-09 01:57:52 (9251) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2024-12-09 01:57:52 (9268) [INFO] * 2024-12-09 01:57:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-09 01:57:52 (9238) [INFO] * 2024-12-09 01:57:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 01:57:53 (9251) [INFO] Determining fastest mirrors * 2024-12-09 01:58:24 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-09 01:58:24 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-09 01:58:24 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-09 01:58:24 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-09 01:59:11 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-09 01:59:11 (9251) [INFO] Trying other mirror. * 2024-12-09 02:00:56 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 02:00:56 (9251) [INFO] Trying other mirror. * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-09 02:00:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-09 02:00:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-09 02:00:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-09 02:00:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-09 02:00:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-09 02:00:56 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-09 02:00:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-09 02:00:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-09 02:00:56 (9251) [INFO] or * 2024-12-09 02:00:56 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-09 02:00:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-09 02:00:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-09 02:00:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-09 02:00:56 (9251) [INFO] compromise: * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-09 02:00:56 (9251) [INFO] * 2024-12-09 02:00:56 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-09 02:00:56 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 02:00:56 (9268) [INFO] * 2024-12-09 02:00:56 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-09 02:00:56 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-09 02:00:57 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-09 02:00:57 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-09 02:00:57 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-09 02:00:57 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-09 02:00:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-09 02:01:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sS50m1sUvq/ea_profile.json * 2024-12-09 02:04:36 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sS50m1sUvq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-09 02:04:36 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-10 01:45:43 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-10 01:49:44 (10313) [INFO] Script is up to date. * 2024-12-10 01:53:47 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-10 01:53:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-10 01:53:47 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-10 01:53:47 (9238) [INFO] * 2024-12-10 01:53:51 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-10 01:53:51 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-10 01:53:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-10 01:53:51 (9238) [INFO] * 2024-12-10 01:54:22 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-10 01:54:22 (9238) [INFO] * 2024-12-10 01:54:22 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 01:54:22 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-10 01:54:53 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-10 01:54:53 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-10 01:54:53 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-10 01:54:53 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-10 01:55:40 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') * 2024-12-10 01:55:40 (9251) [INFO] Trying other mirror. * 2024-12-10 01:56:10 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') * 2024-12-10 01:56:10 (9251) [INFO] Trying other mirror. * 2024-12-10 01:57:54 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 01:57:54 (9251) [INFO] Trying other mirror. * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-10 01:57:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-10 01:57:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-10 01:57:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-10 01:57:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-10 01:57:54 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-10 01:57:54 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-10 01:57:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-10 01:57:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-10 01:57:54 (9251) [INFO] or * 2024-12-10 01:57:54 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-10 01:57:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-10 01:57:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-10 01:57:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-10 01:57:54 (9251) [INFO] compromise: * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-10 01:57:54 (9251) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-10 01:57:54 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 01:57:54 (9268) [INFO] * 2024-12-10 01:57:54 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 01:57:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-10 01:57:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-10 01:57:54 (9238) [INFO] * 2024-12-10 01:57:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 01:57:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-10 01:57:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-10 01:57:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-10 01:57:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-10 01:57:55 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-10 01:57:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-10 01:57:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-10 01:57:55 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-10 01:57:55 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-10 01:57:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-10 01:57:55 (9251) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2024-12-10 01:57:55 (9268) [INFO] * 2024-12-10 01:57:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-10 01:57:55 (9238) [INFO] * 2024-12-10 01:57:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 01:57:56 (9251) [INFO] Determining fastest mirrors * 2024-12-10 01:58:28 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-10 01:58:28 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-10 01:58:28 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-10 01:58:28 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-10 02:00:28 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 02:00:28 (9251) [INFO] Trying other mirror. * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2024-12-10 02:00:28 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-10 02:00:28 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-10 02:00:28 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-10 02:00:28 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-10 02:00:28 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-10 02:00:28 (9251) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-10 02:00:28 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-10 02:00:28 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2024-12-10 02:00:28 (9251) [INFO] or * 2024-12-10 02:00:28 (9251) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-10 02:00:28 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-10 02:00:28 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-10 02:00:28 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-10 02:00:28 (9251) [INFO] compromise: * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2024-12-10 02:00:28 (9251) [INFO] * 2024-12-10 02:00:28 (9251) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2024-12-10 02:00:28 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 02:00:28 (9268) [INFO] * 2024-12-10 02:00:28 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-10 02:00:28 (5804) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzMjUyMDY1OjE3MzM1MTEyNjU6W6CI9rDEftMUUAJZ2UGKw6hYKPZSRHJ3ZQq-HH3oQJe3LUKYmxH18OEc6YPK6lQSzJjd9bXMyATCtbr_Kgp_FizY3c-nVAllFXbypKpA0KHjTTrFm7H7yBXHXDVrld_Vhz2bCisHg0kIicsdjGlT736TBkz3qZBSP307WOoGUGnALg_IxS1_EZmnvevsKLrftgy6MtQRmky68VaKw3frynG-BTJcy3jOeU69dASqbuhFS4aEoJJucl7KFVdus5UTmwIyJFCGVigA6nNOmRGDU8G4i7JvhEebvUN-gtv7GnCgB0R7aMbDE037wmLVZ6R-wL4spxtVKBW6TM-SMMLHf-m7vKBEwU24yAqdEUKTD2P2imY6sFLq19llnrhpI1HaRXyLNnc7ZkQl0RRwlxaCuyeKulwY8Kpn75JvQP5j4qXystKFOm4_UppVGZ0Sa_921vVdBfC1oqYNTJPhdQOEa9oPUN84AKlDeIL7VhO1rl-_cu8zs7siIGCqifCNSZHujtswB4fAc2Rhq__jlPMmNq1q3uhM4Vde9mfWV_r1NOF0Zq8LzT7OlpiPSpOylgWZ9SiBrCMpZ5Z_ZZofUOQWFp80q4kYTuTuIGwcQ2m5zgL7lu32bB3vnha5vscMPESjWO8bKlB6L7g6FmKKY7vLAxQsQUFAndzamgA1SaKeITo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2024-12-10 02:00:29 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-10 02:00:29 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-10 02:00:29 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-10 02:00:29 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-10 02:00:29 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-10 02:00:35 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/m3cns1iAlT/ea_profile.json * 2024-12-10 02:04:38 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/m3cns1iAlT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-10 02:04:38 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-11 02:10:01 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-11 02:14:02 (10313) [INFO] Script is up to date. * 2024-12-11 02:18:05 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-11 02:18:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-11 02:18:05 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-11 02:18:05 (9238) [INFO] * 2024-12-11 02:18:09 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-11 02:18:09 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-11 02:18:09 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-11 02:18:09 (9238) [INFO] * 2024-12-11 02:18:20 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-11 02:18:24 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-11 02:18:24 (9238) [INFO] * 2024-12-11 02:18:24 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 02:18:24 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-11 02:18:54 (9251) [INFO] * EA4: 208.74.123.62 * 2024-12-11 02:18:54 (9251) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2024-12-11 02:18:54 (9251) [INFO] * cpanel-plugins: 208.74.123.62 * 2024-12-11 02:18:54 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-11 02:22:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-11 02:22:04 (9251) [INFO] Trying other mirror. * 2024-12-11 02:22:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-11 02:22:28 (9251) [INFO] Trying other mirror. * 2024-12-11 02:22:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-11 02:22:59 (9251) [INFO] Trying other mirror. * 2024-12-11 02:23:19 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-11 02:23:19 (9251) [INFO] Trying other mirror. * 2024-12-11 02:23:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-11 02:23:29 (9251) [INFO] Trying other mirror. * 2024-12-11 02:23:49 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-11 02:23:49 (9251) [INFO] Trying other mirror. * 2024-12-11 02:23:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-11 02:23:59 (9251) [INFO] Trying other mirror. * 2024-12-11 02:24:44 (9251) [INFO] Metadata Cache Created * 2024-12-11 02:24:44 (9268) [INFO] * 2024-12-11 02:24:44 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-11 02:24:44 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-11 02:24:44 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-11 02:24:44 (9238) [INFO] * 2024-12-11 02:24:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 02:24:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-11 02:24:45 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-11 02:24:45 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-11 02:24:45 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-11 02:24:45 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-11 02:24:45 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-11 02:24:45 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-11 02:24:45 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-11 02:24:45 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-11 02:24:45 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-11 02:24:45 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-11 02:24:45 (9268) [INFO] * 2024-12-11 02:24:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-11 02:24:45 (9238) [INFO] * 2024-12-11 02:24:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 02:24:46 (9251) [INFO] Determining fastest mirrors * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-11 02:25:17 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-11 02:25:17 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-11 02:25:17 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-11 02:25:17 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-11 02:25:17 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-11 02:25:17 (9251) [INFO] yum --disablerepo= ... * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-11 02:25:17 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-11 02:25:17 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] yum-config-manager --disable * 2024-12-11 02:25:17 (9251) [INFO] or * 2024-12-11 02:25:17 (9251) [INFO] subscription-manager repos --disable= * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-11 02:25:17 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-11 02:25:17 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-11 02:25:17 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-11 02:25:17 (9251) [INFO] compromise: * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-11 02:25:17 (9251) [INFO] * 2024-12-11 02:25:17 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-11 02:25:17 (9268) [INFO] * 2024-12-11 02:25:17 (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 02:25:17 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-11 02:25:17 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-11 02:25:17 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-11 02:25:17 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-11 02:25:17 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-11 02:25:17 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-11 02:25:23 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6CeXsGROLz/ea_profile.json * 2024-12-11 02:33:15 (8385) [INFO] Backed up EA4 profile to /tmp/6CeXsGROLz/ea_profile.json * 2024-12-11 02:33:16 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-11 02:33:50 (627) [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-12-11 02:33:50 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-12 01:55:35 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-12 01:59:36 (10313) [INFO] Script is up to date. * 2024-12-12 02:03:39 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-12 02:03:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-12 02:03:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-12 02:03:39 (9238) [INFO] * 2024-12-12 02:03:42 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-12 02:03:42 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-12 02:03:42 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-12 02:03:42 (9238) [INFO] * 2024-12-12 02:03:53 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-12 02:03:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-12 02:03:56 (9238) [INFO] * 2024-12-12 02:03:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 02:03:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-12 02:04:27 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-12 02:04:27 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-12 02:04:27 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-12 02:04:27 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-12 02:06:44 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/055ffdba7dd2c76f71e5358c574c82966a18561b0ee0fd5720eb8ce8deba512f-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-12-12 02:06:44 (9251) [INFO] Trying other mirror. * 2024-12-12 02:06:44 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-12 02:06:44 (9251) [INFO] * 2024-12-12 02:06:44 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-12 02:06:44 (9251) [INFO] * 2024-12-12 02:06:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-12 02:06:44 (9251) [INFO] * 2024-12-12 02:07:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:07:13 (9251) [INFO] Trying other mirror. * 2024-12-12 02:07:30 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:07:30 (9251) [INFO] Trying other mirror. * 2024-12-12 02:08:01 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-12 02:08:01 (9251) [INFO] Trying other mirror. * 2024-12-12 02:08:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:08:03 (9251) [INFO] Trying other mirror. * 2024-12-12 02:08:48 (9251) [INFO] Metadata Cache Created * 2024-12-12 02:08:48 (9268) [INFO] * 2024-12-12 02:08:48 (5793) [WARN] Initial run of "yum makecache" failed: https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/055ffdba7dd2c76f71e5358c574c82966a18561b0ee0fd5720eb8ce8deba512f-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-12 02:08:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-12 02:08:48 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-12 02:08:48 (9238) [INFO] * 2024-12-12 02:08:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 02:08:49 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-12 02:08:49 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-12 02:08:49 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-12 02:08:49 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-12 02:08:49 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-12 02:08:49 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-12 02:08:49 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-12 02:08:49 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-12 02:08:49 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-12 02:08:50 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-12 02:08:50 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-12 02:08:50 (9268) [INFO] * 2024-12-12 02:08:50 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-12 02:08:50 (9238) [INFO] * 2024-12-12 02:08:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 02:08:51 (9251) [INFO] Determining fastest mirrors * 2024-12-12 02:09:22 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-12 02:09:22 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-12 02:09:22 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-12 02:09:22 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-12 02:12:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-12 02:12:26 (9251) [INFO] Trying other mirror. * 2024-12-12 02:12:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:12:26 (9251) [INFO] Trying other mirror. * 2024-12-12 02:12:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Operation timed out after 30013 milliseconds with 0 out of 0 bytes received') * 2024-12-12 02:12:56 (9251) [INFO] Trying other mirror. * 2024-12-12 02:13:44 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-12 02:13:44 (9251) [INFO] Trying other mirror. * 2024-12-12 02:14:00 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:14:00 (9251) [INFO] Trying other mirror. * 2024-12-12 02:14:16 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:14:16 (9251) [INFO] Trying other mirror. * 2024-12-12 02:14:31 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:14:31 (9251) [INFO] Trying other mirror. * 2024-12-12 02:14:34 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:14:34 (9251) [INFO] Trying other mirror. * 2024-12-12 02:15:01 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e34361c0373b3fa07851c6dbb0bbf83429f5250bb77b9e9e7acff232196fc4b1-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:15:01 (9251) [INFO] Trying other mirror. * 2024-12-12 02:15:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:15:04 (9251) [INFO] Trying other mirror. * 2024-12-12 02:15:17 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzODIwNjk0OjE3MzQwNzk4OTQ6XTEyzerAL1yw62-olRQCPdio1w4pw46IPH104S9b9jokHzOvR1zBr7Oy3nvsZm6OTPtpLJKjpcN4nO5h5DRo2N8Iv86egI2Om7L6AOgO-S3C1EI3AQzLckg59ddZIuMlufHkfOWNeOkDt0Dhr8KiWSqwdzGxfXw-Wm-2Y5A36_DEkicn4tBdasIjNzuoe7TN_vyqZ2xtju1w4Lfh7_-f3PAZ1b-Gk0-7dF9A6uieQKRhx5Kw94Uo7ffnilMZ41PV9L9F4jZcdK9IoAAKNwXOfvpzgA-Yj_wOg3wgTQZ-19Q-YRoG-EpXydsf1LEm2dgoHdNBzXJHEj9ptfi0q5dyypVD3kmFAOpZ_BKF4aMoQNRIb1lJb-pNOa9j1gLXw7161Z7q36r8-hy_DsyHF_JkgQdXLAtZD9RHko15pyLma3cJqTOxBYDOVnna-UavoxS6EOtlLkKWAKWmm8qD7JiksNo-H79EErqSrJk2iq2coXoNlFewb-KK7jkLAtq9FSoiu_kEtkowHMnRWZ64N5XJNSm3dFlbpVYtAfKBOIefaqAOXPjBjo_9uX3GYlVy6fe6fnxlM9yiDYAqnUBYjrhi9p0V8RvRC7xGntM9HxiKKRnvh7JzGkTzyZrgtKel2rrdaDmqx7QVtcOSQFuAaux5DsirmSTw54RscdFja9YDtWA%3D/ea-php/7/updates/x86_64/repodata/0505f48892f6112cb51f916c016fd005f72200f2866c40a81e69523ff701a565-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:15:17 (9251) [INFO] Trying other mirror. * 2024-12-12 02:15:33 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:15:33 (9251) [INFO] Trying other mirror. * 2024-12-12 02:15:49 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:15:49 (9251) [INFO] Trying other mirror. * 2024-12-12 02:16:05 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:16:05 (9251) [INFO] Trying other mirror. * 2024-12-12 02:16:21 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/48a77a62d4604505b0f1785fbb652346b08c97dc6eeeef096723cbb0d0e3dcaf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:16:21 (9251) [INFO] Trying other mirror. * 2024-12-12 02:16:37 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:16:37 (9251) [INFO] Trying other mirror. * 2024-12-12 02:16:53 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:16:53 (9251) [INFO] Trying other mirror. * 2024-12-12 02:17:09 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:17:09 (9251) [INFO] Trying other mirror. * 2024-12-12 02:17:25 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:17:25 (9251) [INFO] Trying other mirror. * 2024-12-12 02:17:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:17:55 (9251) [INFO] Trying other mirror. * 2024-12-12 02:18:11 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/wp-toolkit/repodata/72a443e975a4b26eb9cc44419e7690d660111d51f3d20dfcd234a7baa0f32269-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:18:11 (9251) [INFO] Trying other mirror. * 2024-12-12 02:18:26 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:18:26 (9251) [INFO] Trying other mirror. * 2024-12-12 02:18:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:18:26 (9251) [INFO] Trying other mirror. * 2024-12-12 02:18:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:18:57 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:13 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:13 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:14 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:14 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:14 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:14 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:19:27 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:27 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-12 02:19:27 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:30 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:30 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:47 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:47 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:57 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:57 (9251) [INFO] Trying other mirror. * 2024-12-12 02:19:57 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:19:57 (9251) [INFO] Trying other mirror. * 2024-12-12 02:20:17 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2024-12-12 02:20:17 (9251) [INFO] Trying other mirror. * 2024-12-12 02:20:33 (9251) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:20:33 (9251) [INFO] Trying other mirror. * 2024-12-12 02:20:49 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:20:49 (9251) [INFO] Trying other mirror. * 2024-12-12 02:21:16 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:21:16 (9251) [INFO] Trying other mirror. * 2024-12-12 02:21:33 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-12 02:21:33 (9251) [INFO] Trying other mirror. * 2024-12-12 02:22:21 (9251) [INFO] Metadata Cache Created * 2024-12-12 02:22:21 (9268) [INFO] * 2024-12-12 02:22:21 (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 02:22:21 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Operation timed out after 30013 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e34361c0373b3fa07851c6dbb0bbf83429f5250bb77b9e9e7acff232196fc4b1-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzMzODIwNjk0OjE3MzQwNzk4OTQ6XTEyzerAL1yw62-olRQCPdio1w4pw46IPH104S9b9jokHzOvR1zBr7Oy3nvsZm6OTPtpLJKjpcN4nO5h5DRo2N8Iv86egI2Om7L6AOgO-S3C1EI3AQzLckg59ddZIuMlufHkfOWNeOkDt0Dhr8KiWSqwdzGxfXw-Wm-2Y5A36_DEkicn4tBdasIjNzuoe7TN_vyqZ2xtju1w4Lfh7_-f3PAZ1b-Gk0-7dF9A6uieQKRhx5Kw94Uo7ffnilMZ41PV9L9F4jZcdK9IoAAKNwXOfvpzgA-Yj_wOg3wgTQZ-19Q-YRoG-EpXydsf1LEm2dgoHdNBzXJHEj9ptfi0q5dyypVD3kmFAOpZ_BKF4aMoQNRIb1lJb-pNOa9j1gLXw7161Z7q36r8-hy_DsyHF_JkgQdXLAtZD9RHko15pyLma3cJqTOxBYDOVnna-UavoxS6EOtlLkKWAKWmm8qD7JiksNo-H79EErqSrJk2iq2coXoNlFewb-KK7jkLAtq9FSoiu_kEtkowHMnRWZ64N5XJNSm3dFlbpVYtAfKBOIefaqAOXPjBjo_9uX3GYlVy6fe6fnxlM9yiDYAqnUBYjrhi9p0V8RvRC7xGntM9HxiKKRnvh7JzGkTzyZrgtKel2rrdaDmqx7QVtcOSQFuAaux5DsirmSTw54RscdFja9YDtWA%3D/ea-php/7/updates/x86_64/repodata/0505f48892f6112cb51f916c016fd005f72200f2866c40a81e69523ff701a565-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/48a77a62d4604505b0f1785fbb652346b08c97dc6eeeef096723cbb0d0e3dcaf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/wp-toolkit/repodata/72a443e975a4b26eb9cc44419e7690d660111d51f3d20dfcd234a7baa0f32269-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2024-12-12 02:22:22 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-12 02:22:22 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-12 02:22:22 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-12 02:22:22 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-12 02:22:22 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-12 02:22:28 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/R8JhO0tN4N/ea_profile.json * 2024-12-12 02:22:30 (8385) [INFO] Backed up EA4 profile to /tmp/R8JhO0tN4N/ea_profile.json * 2024-12-12 02:22:32 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-12 02:23:05 (627) [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-12-12 02:23:05 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-13 01:44:42 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-13 01:48:42 (10313) [INFO] Script is up to date. * 2024-12-13 01:52:45 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-13 01:52:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-13 01:52:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-13 01:52:45 (9238) [INFO] * 2024-12-13 01:52:49 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-13 01:52:49 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-13 01:52:49 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-13 01:52:49 (9238) [INFO] * 2024-12-13 01:52:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-13 01:52:55 (9238) [INFO] * 2024-12-13 01:52:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 01:52:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-13 01:53:27 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-13 01:53:27 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-13 01:53:27 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-13 01:53:27 (9251) [INFO] * epel: dl.fedoraproject.org * 2024-12-13 01:56:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 01:56:13 (9251) [INFO] Trying other mirror. * 2024-12-13 01:56:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-13 01:56:13 (9251) [INFO] Trying other mirror. * 2024-12-13 01:56:44 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-13 01:56:44 (9251) [INFO] Trying other mirror. * 2024-12-13 01:57:02 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 01:57:02 (9251) [INFO] Trying other mirror. * 2024-12-13 01:57:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-13 01:57:03 (9251) [INFO] Trying other mirror. * 2024-12-13 01:57:47 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-13 01:57:47 (9251) [INFO] Trying other mirror. * 2024-12-13 01:57:48 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 01:57:48 (9251) [INFO] Trying other mirror. * 2024-12-13 01:58:05 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-13 01:58:05 (9251) [INFO] Trying other mirror. * 2024-12-13 01:58:35 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-13 01:58:35 (9251) [INFO] Trying other mirror. * 2024-12-13 01:59:05 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30025 milliseconds with 0 out of 0 bytes received') * 2024-12-13 01:59:05 (9251) [INFO] Trying other mirror. * 2024-12-13 01:59:06 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-13 01:59:06 (9251) [INFO] Trying other mirror. * 2024-12-13 01:59:36 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 01:59:36 (9251) [INFO] Trying other mirror. * 2024-12-13 01:59:36 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 01:59:36 (9251) [INFO] Trying other mirror. * 2024-12-13 02:00:07 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:00:07 (9251) [INFO] Trying other mirror. * 2024-12-13 02:01:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:01:07 (9251) [INFO] Trying other mirror. * 2024-12-13 02:01:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:01:37 (9251) [INFO] Trying other mirror. * 2024-12-13 02:01:37 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:01:37 (9251) [INFO] Trying other mirror. * 2024-12-13 02:02:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-13 02:02:08 (9251) [INFO] Trying other mirror. * 2024-12-13 02:02:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-13 02:02:08 (9251) [INFO] Trying other mirror. * 2024-12-13 02:02:39 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-13 02:02:39 (9251) [INFO] Trying other mirror. * 2024-12-13 02:03:09 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-13 02:03:09 (9251) [INFO] Trying other mirror. * 2024-12-13 02:03:40 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-13 02:03:40 (9251) [INFO] Trying other mirror. * 2024-12-13 02:04:50 (9251) [INFO] Metadata Cache Created * 2024-12-13 02:04:50 (9268) [INFO] * 2024-12-13 02:04:50 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30025 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-12-13 02:04:50 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-13 02:04:50 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-13 02:04:50 (9238) [INFO] * 2024-12-13 02:04:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 02:04:51 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-13 02:04:51 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-13 02:04:51 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-13 02:04:51 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-13 02:04:51 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-13 02:04:51 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-13 02:04:51 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-13 02:04:51 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-13 02:04:51 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-13 02:04:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-13 02:04:52 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-13 02:04:52 (9268) [INFO] * 2024-12-13 02:04:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-13 02:04:52 (9238) [INFO] * 2024-12-13 02:04:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 02:04:53 (9251) [INFO] Determining fastest mirrors * 2024-12-13 02:05:24 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-13 02:05:24 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-13 02:05:24 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-13 02:05:24 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-13 02:08:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:08:27 (9251) [INFO] Trying other mirror. * 2024-12-13 02:08:28 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-13 02:08:28 (9251) [INFO] Trying other mirror. * 2024-12-13 02:08:58 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-13 02:08:58 (9251) [INFO] Trying other mirror. * 2024-12-13 02:08:58 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/18175b328ba997f6a064a147ab33fd5885d26a059e1afbc3ede702570b1e9ede-updateinfo.xml.gz: [Errno 14] HTTPS Error 404 - Not Found * 2024-12-13 02:08:58 (9251) [INFO] Trying other mirror. * 2024-12-13 02:08:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-13 02:08:58 (9251) [INFO] * 2024-12-13 02:08:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-13 02:08:58 (9251) [INFO] * 2024-12-13 02:08:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-13 02:08:58 (9251) [INFO] * 2024-12-13 02:08:59 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/44cf8b0de14653cde53e609df79fd95f84da1eb6a6abf34e5001877d86879fbf-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-12-13 02:08:59 (9251) [INFO] Trying other mirror. * 2024-12-13 02:09:31 (9251) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-13 02:09:31 (9251) [INFO] Trying other mirror. * 2024-12-13 02:09:46 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:09:46 (9251) [INFO] Trying other mirror. * 2024-12-13 02:10:02 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:10:02 (9251) [INFO] Trying other mirror. * 2024-12-13 02:10:18 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:10:18 (9251) [INFO] Trying other mirror. * 2024-12-13 02:10:33 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:10:33 (9251) [INFO] Trying other mirror. * 2024-12-13 02:10:37 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:10:37 (9251) [INFO] Trying other mirror. * 2024-12-13 02:11:04 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/fe733f178332dbc7c023e0ae1a87f1b6eb81cff75d3dc80706471accb314c123-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:11:04 (9251) [INFO] Trying other mirror. * 2024-12-13 02:11:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-13 02:11:07 (9251) [INFO] Trying other mirror. * 2024-12-13 02:11:19 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM0MDU3MjM2OjE3MzQzMTY0MzY6l6SaUqtaJ6iiSOnyXEEIHrCJGiMC4uw7bX9j2DHfKKH8ZAEKUkCIoS55ErdyFCtEvad5JSzsVUbni_TgPzxLVMMk_hgPRecDcqXW4KFy2k_LDnwoswvzvxC3qW3qwYY4LMFyJ9RSYv8nSoNAcKwpMDkDNT4HYDhUQQ5gbr55r19m5iv0qpE-zODGtOuiDKPihIPA18Eo2i_BmBnBfPrpuNYAMMCIpnsPU1TMxRL1Pqr5NgZKSQRYaccRDmLJJK6UxOVl9Bsd7GMVQckBIhtD7Jk2g3ftq-SkOkhZ0Re7YFpVBpuV02mgU58ThilMYXxmfpU-v2IZqx0zDNhKUaEo_E24odDxh0agpsBgo940vlc4GruHdtoZZ467GVNrvpvFqGIasjaM8Vl-dzfKzYQoakWWgfSO26T5peJouruoeEkG3dYo4y6S0_8ZAzWfvV2rADGDmhT_uDwYEuX7NxHsNLZ9L8qyCE5x-So7fOD-6NeGgkadlG4k20Ou-SYjK00TwBj5FeuIsvrYrGqr0wbDof6iKyTSZ32NrD7z6RZBgHrfns71GbTXUDc_MesoWwA2r2rR6XcYvQNM9LfrnG02rRliBM2pzIENaPx2yO71kVR2an0dWRoQpFLZD48s4CiDOcPDWUkOjJHAEv93UgUMMQbeSEFCC7NdgM1ga9lmKX8%3D/ea-php/7/updates/x86_64/repodata/0505f48892f6112cb51f916c016fd005f72200f2866c40a81e69523ff701a565-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:11:19 (9251) [INFO] Trying other mirror. * 2024-12-13 02:11:35 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:11:35 (9251) [INFO] Trying other mirror. * 2024-12-13 02:11:51 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:11:51 (9251) [INFO] Trying other mirror. * 2024-12-13 02:12:06 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:12:06 (9251) [INFO] Trying other mirror. * 2024-12-13 02:12:22 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:12:22 (9251) [INFO] Trying other mirror. * 2024-12-13 02:12:38 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:12:38 (9251) [INFO] Trying other mirror. * 2024-12-13 02:12:53 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:12:53 (9251) [INFO] Trying other mirror. * 2024-12-13 02:13:09 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:13:09 (9251) [INFO] Trying other mirror. * 2024-12-13 02:13:24 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:13:24 (9251) [INFO] Trying other mirror. * 2024-12-13 02:13:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-13 02:13:55 (9251) [INFO] Trying other mirror. * 2024-12-13 02:13:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-13 02:13:55 (9251) [INFO] Trying other mirror. * 2024-12-13 02:14:11 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/wp-toolkit/repodata/72a443e975a4b26eb9cc44419e7690d660111d51f3d20dfcd234a7baa0f32269-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:14:11 (9251) [INFO] Trying other mirror. * 2024-12-13 02:14:26 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.0/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:14:26 (9251) [INFO] Trying other mirror. * 2024-12-13 02:14:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-13 02:14:27 (9251) [INFO] Trying other mirror. * 2024-12-14 01:54:57 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-14 01:58:57 (10313) [INFO] Script is up to date. * 2024-12-14 02:03:00 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-14 02:03:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-14 02:03:00 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-14 02:03:00 (9238) [INFO] * 2024-12-14 02:03:03 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-14 02:03:03 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-14 02:03:03 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-14 02:03:03 (9238) [INFO] * 2024-12-14 02:03:15 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-14 02:03:18 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-14 02:03:18 (9238) [INFO] * 2024-12-14 02:03:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 02:03:19 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-14 02:03:49 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-12-14 02:03:49 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30728 milliseconds') * 2024-12-14 02:03:49 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-14 02:03:49 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-14 02:03:49 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-14 02:03:49 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-14 02:04:36 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-14 02:04:36 (9251) [INFO] Trying other mirror. * 2024-12-14 02:05:07 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-14 02:05:07 (9251) [INFO] Trying other mirror. * 2024-12-14 02:05:38 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-14 02:05:38 (9251) [INFO] Trying other mirror. * 2024-12-14 02:06:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-14 02:06:08 (9251) [INFO] Trying other mirror. * 2024-12-14 02:08:38 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:08:38 (9251) [INFO] Trying other mirror. * 2024-12-14 02:08:54 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:08:54 (9251) [INFO] Trying other mirror. * 2024-12-14 02:09:24 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:09:24 (9251) [INFO] Trying other mirror. * 2024-12-14 02:09:25 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-14 02:09:25 (9251) [INFO] Trying other mirror. * 2024-12-14 02:09:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-14 02:09:54 (9251) [INFO] Trying other mirror. * 2024-12-14 02:10:40 (9251) [INFO] Metadata Cache Created * 2024-12-14 02:10:40 (9268) [INFO] * 2024-12-14 02:10:40 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30728 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-12-14 02:10:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-14 02:10:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-14 02:10:40 (9238) [INFO] * 2024-12-14 02:10:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 02:10:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-14 02:10:41 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-14 02:10:41 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-14 02:10:41 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-14 02:10:41 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-14 02:10:41 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-14 02:10:41 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-14 02:10:41 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-14 02:10:41 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-14 02:10:42 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-14 02:10:42 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-14 02:10:42 (9268) [INFO] * 2024-12-14 02:10:42 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-14 02:10:42 (9238) [INFO] * 2024-12-14 02:10:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 02:10:42 (9251) [INFO] Determining fastest mirrors * 2024-12-14 02:11:14 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-14 02:11:14 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-14 02:11:14 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-14 02:11:14 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-14 02:14:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-14 02:14:19 (9251) [INFO] Trying other mirror. * 2024-12-14 02:14:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-14 02:14:20 (9251) [INFO] Trying other mirror. * 2024-12-14 02:14:50 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/83c6d35d3f0896225a54f662523c16cedf98fbc3379eff190626ab06ce1dab96-updateinfo.xml.gz: [Errno 14] HTTPS Error 404 - Not Found * 2024-12-14 02:14:50 (9251) [INFO] Trying other mirror. * 2024-12-14 02:14:50 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-14 02:14:50 (9251) [INFO] * 2024-12-14 02:14:50 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-14 02:14:50 (9251) [INFO] * 2024-12-14 02:14:50 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-14 02:14:50 (9251) [INFO] * 2024-12-14 02:14:50 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/182756f08cb23f7ef628a62c9110d52c73357bec86079222a211023b42bbeb4b-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2024-12-14 02:14:50 (9251) [INFO] Trying other mirror. * 2024-12-14 02:16:58 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:16:58 (9251) [INFO] Trying other mirror. * 2024-12-14 02:19:46 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:19:46 (9251) [INFO] Trying other mirror. * 2024-12-14 02:19:47 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:19:47 (9251) [INFO] Trying other mirror. * 2024-12-14 02:20:17 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-14 02:20:17 (9251) [INFO] Trying other mirror. * 2024-12-14 02:21:18 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:21:18 (9251) [INFO] Trying other mirror. * 2024-12-14 02:21:18 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:21:18 (9251) [INFO] Trying other mirror. * 2024-12-14 02:21:48 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-14 02:21:48 (9251) [INFO] Trying other mirror. * 2024-12-14 02:22:19 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-14 02:22:19 (9251) [INFO] Trying other mirror. * 2024-12-14 02:22:50 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-14 02:22:50 (9251) [INFO] Trying other mirror. * 2024-12-14 02:23:22 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-14 02:23:22 (9251) [INFO] Trying other mirror. * 2024-12-14 02:23:53 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-14 02:23:53 (9251) [INFO] Trying other mirror. * 2024-12-14 02:24:23 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-14 02:24:23 (9251) [INFO] Trying other mirror. * 2024-12-15 01:58:10 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-15 02:02:10 (10313) [INFO] Script is up to date. * 2024-12-15 02:06:13 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-15 02:06:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-15 02:06:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-15 02:06:14 (9238) [INFO] * 2024-12-15 02:06:17 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-15 02:06:17 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-15 02:06:17 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-15 02:06:17 (9238) [INFO] * 2024-12-15 02:06:29 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-15 02:06:32 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-15 02:06:32 (9238) [INFO] * 2024-12-15 02:06:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 02:06:33 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-15 02:07:03 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2024-12-15 02:07:03 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30541 milliseconds') * 2024-12-15 02:07:03 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-15 02:07:03 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-15 02:07:03 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-15 02:07:03 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-15 02:09:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:09:51 (9251) [INFO] Trying other mirror. * 2024-12-15 02:10:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:10:07 (9251) [INFO] Trying other mirror. * 2024-12-15 02:10:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-15 02:10:38 (9251) [INFO] Trying other mirror. * 2024-12-15 02:10:43 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2024-12-15 02:10:43 (9251) [INFO] Trying other mirror. * 2024-12-15 02:10:51 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-15 02:10:51 (9251) [INFO] Trying other mirror. * 2024-12-15 02:11:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2024-12-15 02:11:09 (9251) [INFO] Trying other mirror. * 2024-12-15 02:11:22 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:11:22 (9251) [INFO] Trying other mirror. * 2024-12-15 02:11:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2024-12-15 02:11:39 (9251) [INFO] Trying other mirror. * 2024-12-15 02:12:23 (9251) [INFO] Metadata Cache Created * 2024-12-15 02:12:23 (9268) [INFO] * 2024-12-15 02:12:23 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30541 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') Trying other mirror. * 2024-12-15 02:12:23 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-15 02:12:23 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-15 02:12:23 (9238) [INFO] * 2024-12-15 02:12:24 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 02:12:24 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-15 02:12:24 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-15 02:12:24 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-15 02:12:24 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-15 02:12:24 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-15 02:12:24 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-15 02:12:24 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-15 02:12:24 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-15 02:12:24 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-15 02:12:25 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-15 02:12:25 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-15 02:12:25 (9268) [INFO] * 2024-12-15 02:12:25 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-15 02:12:25 (9238) [INFO] * 2024-12-15 02:12:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 02:12:26 (9251) [INFO] Determining fastest mirrors * 2024-12-15 02:12:57 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-15 02:12:57 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-15 02:12:57 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-15 02:12:57 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-15 02:16:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:16:00 (9251) [INFO] Trying other mirror. * 2024-12-15 02:16:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-15 02:16:00 (9251) [INFO] Trying other mirror. * 2024-12-15 02:16:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-15 02:16:30 (9251) [INFO] Trying other mirror. * 2024-12-15 02:18:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') * 2024-12-15 02:18:40 (9251) [INFO] Trying other mirror. * 2024-12-15 02:21:28 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:21:28 (9251) [INFO] Trying other mirror. * 2024-12-15 02:21:28 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:21:28 (9251) [INFO] Trying other mirror. * 2024-12-15 02:21:58 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-15 02:21:58 (9251) [INFO] Trying other mirror. * 2024-12-15 02:22:59 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:22:59 (9251) [INFO] Trying other mirror. * 2024-12-15 02:23:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-15 02:23:00 (9251) [INFO] Trying other mirror. * 2024-12-15 02:23:30 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:23:30 (9251) [INFO] Trying other mirror. * 2024-12-15 02:24:01 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-15 02:24:01 (9251) [INFO] Trying other mirror. * 2024-12-15 02:24:32 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-15 02:24:32 (9251) [INFO] Trying other mirror. * 2024-12-15 02:25:02 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-15 02:25:02 (9251) [INFO] Trying other mirror. * 2024-12-15 02:25:33 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-15 02:25:33 (9251) [INFO] Trying other mirror. * 2024-12-15 02:26:50 (9251) [INFO] Metadata Cache Created * 2024-12-15 02:26:50 (9268) [INFO] * 2024-12-15 02:26:50 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-15 02:26:50 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-12-15 02:26:51 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-15 02:26:51 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-15 02:26:51 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-15 02:26:51 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-15 02:26:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-15 02:26:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Ds4G_dVVo9/ea_profile.json * 2024-12-15 02:26:59 (8385) [INFO] Backed up EA4 profile to /tmp/Ds4G_dVVo9/ea_profile.json * 2024-12-15 02:27:00 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-15 02:27:35 (627) [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-12-15 02:27:35 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-16 01:55:18 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-16 01:59:18 (10313) [INFO] Script is up to date. * 2024-12-16 02:03:21 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-16 02:03:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-16 02:03:21 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-16 02:03:21 (9238) [INFO] * 2024-12-16 02:03:24 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-16 02:03:24 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-16 02:03:24 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-16 02:03:24 (9238) [INFO] * 2024-12-16 02:03:35 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-16 02:03:38 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-16 02:03:38 (9238) [INFO] * 2024-12-16 02:03:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 02:03:39 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-16 02:04:09 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-16 02:04:09 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-16 02:04:09 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-16 02:04:09 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-16 02:06:55 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-16 02:06:55 (9251) [INFO] Trying other mirror. * 2024-12-16 02:07:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-16 02:07:12 (9251) [INFO] Trying other mirror. * 2024-12-16 02:07:28 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-16 02:07:28 (9251) [INFO] Trying other mirror. * 2024-12-16 02:07:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-16 02:07:42 (9251) [INFO] Trying other mirror. * 2024-12-16 02:07:42 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-16 02:07:42 (9251) [INFO] Trying other mirror. * 2024-12-16 02:08:12 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-16 02:08:12 (9251) [INFO] Trying other mirror. * 2024-12-16 02:08:54 (9251) [INFO] Metadata Cache Created * 2024-12-16 02:08:54 (9268) [INFO] * 2024-12-16 02:08:54 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-16 02:08:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-16 02:08:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-16 02:08:54 (9238) [INFO] * 2024-12-16 02:08:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 02:08:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-16 02:08:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-16 02:08:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-16 02:08:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-16 02:08:55 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-16 02:08:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-16 02:08:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-16 02:08:55 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-16 02:08:55 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-16 02:08:56 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-16 02:08:56 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-16 02:08:56 (9268) [INFO] * 2024-12-16 02:08:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-16 02:08:56 (9238) [INFO] * 2024-12-16 02:08:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 02:08:56 (9251) [INFO] Determining fastest mirrors * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-16 02:09:28 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-16 02:09:28 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-16 02:09:28 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-16 02:09:28 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-16 02:09:28 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-16 02:09:28 (9251) [INFO] yum --disablerepo= ... * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-16 02:09:28 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-16 02:09:28 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] yum-config-manager --disable * 2024-12-16 02:09:28 (9251) [INFO] or * 2024-12-16 02:09:28 (9251) [INFO] subscription-manager repos --disable= * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-16 02:09:28 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-16 02:09:28 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-16 02:09:28 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-16 02:09:28 (9251) [INFO] compromise: * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-16 02:09:28 (9251) [INFO] * 2024-12-16 02:09:28 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-16 02:09:28 (9268) [INFO] * 2024-12-16 02:09:28 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-16 02:09:28 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-16 02:09:29 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-16 02:09:29 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-16 02:09:29 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-16 02:09:29 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-16 02:09:29 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-16 02:09:35 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/vuvRh7tTcm/ea_profile.json * 2024-12-16 02:15:13 (8385) [INFO] Backed up EA4 profile to /tmp/vuvRh7tTcm/ea_profile.json * 2024-12-16 02:15:15 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-16 02:15:49 (627) [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-12-16 02:15:49 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-17 01:56:27 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-17 02:00:27 (10313) [INFO] Script is up to date. * 2024-12-17 02:04:30 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-17 02:04:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-17 02:04:31 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-17 02:04:31 (9238) [INFO] * 2024-12-17 02:04:34 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-17 02:04:34 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-17 02:04:34 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-17 02:04:34 (9238) [INFO] * 2024-12-17 02:04:44 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-17 02:04:47 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-17 02:04:47 (9238) [INFO] * 2024-12-17 02:04:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 02:04:48 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-17 02:05:18 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-17 02:05:18 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-17 02:05:18 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-17 02:05:18 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-17 02:08:03 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-17 02:08:03 (9251) [INFO] Trying other mirror. * 2024-12-17 02:08:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-17 02:08:20 (9251) [INFO] Trying other mirror. * 2024-12-17 02:08:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2024-12-17 02:08:38 (9251) [INFO] Trying other mirror. * 2024-12-17 02:08:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-17 02:08:49 (9251) [INFO] Trying other mirror. * 2024-12-17 02:09:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-17 02:09:08 (9251) [INFO] Trying other mirror. * 2024-12-17 02:09:51 (9251) [INFO] Metadata Cache Created * 2024-12-17 02:09:51 (9268) [INFO] * 2024-12-17 02:09:51 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-12-17 02:09:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-17 02:09:51 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-17 02:09:51 (9238) [INFO] * 2024-12-17 02:09:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 02:09:51 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-17 02:09:51 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-17 02:09:51 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-17 02:09:51 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-17 02:09:51 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-17 02:09:51 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-17 02:09:51 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-17 02:09:51 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-17 02:09:51 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-17 02:09:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-17 02:09:52 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-17 02:09:52 (9268) [INFO] * 2024-12-17 02:09:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-17 02:09:52 (9238) [INFO] * 2024-12-17 02:09:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 02:09:53 (9251) [INFO] Determining fastest mirrors * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-17 02:10:23 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-17 02:10:23 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-17 02:10:23 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-17 02:10:23 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-17 02:10:23 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-17 02:10:23 (9251) [INFO] yum --disablerepo= ... * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-17 02:10:23 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-17 02:10:23 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] yum-config-manager --disable * 2024-12-17 02:10:23 (9251) [INFO] or * 2024-12-17 02:10:23 (9251) [INFO] subscription-manager repos --disable= * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-17 02:10:23 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-17 02:10:23 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-17 02:10:23 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-17 02:10:23 (9251) [INFO] compromise: * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-17 02:10:23 (9251) [INFO] * 2024-12-17 02:10:23 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-17 02:10:23 (9268) [INFO] * 2024-12-17 02:10:23 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-17 02:10:23 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-17 02:10:24 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-17 02:10:24 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-17 02:10:24 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-17 02:10:24 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-17 02:10:24 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-17 02:10:30 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VdeqvrRHBv/ea_profile.json * 2024-12-17 02:17:09 (8385) [INFO] Backed up EA4 profile to /tmp/VdeqvrRHBv/ea_profile.json * 2024-12-17 02:17:10 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-17 02:17:44 (627) [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-12-17 02:17:44 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-18 01:57:49 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-18 02:01:50 (10313) [INFO] Script is up to date. * 2024-12-18 02:05:53 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-18 02:05:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-18 02:05:53 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-18 02:05:53 (9238) [INFO] * 2024-12-18 02:05:56 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-18 02:05:56 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-18 02:05:56 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-18 02:05:56 (9238) [INFO] * 2024-12-18 02:06:07 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-18 02:06:10 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-18 02:06:10 (9238) [INFO] * 2024-12-18 02:06:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 02:06:11 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-18 02:06:41 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-18 02:06:41 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-18 02:06:41 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-18 02:06:41 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-18 02:09:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:09:26 (9251) [INFO] Trying other mirror. * 2024-12-18 02:09:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:09:43 (9251) [INFO] Trying other mirror. * 2024-12-18 02:10:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') * 2024-12-18 02:10:12 (9251) [INFO] Trying other mirror. * 2024-12-18 02:10:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-18 02:10:17 (9251) [INFO] Trying other mirror. * 2024-12-18 02:10:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-18 02:10:27 (9251) [INFO] Trying other mirror. * 2024-12-18 02:10:43 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-18 02:10:43 (9251) [INFO] Trying other mirror. * 2024-12-18 02:10:57 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:10:57 (9251) [INFO] Trying other mirror. * 2024-12-18 02:11:40 (9251) [INFO] Metadata Cache Created * 2024-12-18 02:11:40 (9268) [INFO] * 2024-12-18 02:11:40 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-18 02:11:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-18 02:11:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-18 02:11:40 (9238) [INFO] * 2024-12-18 02:11:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 02:11:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-18 02:11:41 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-18 02:11:41 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-18 02:11:41 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-18 02:11:41 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-18 02:11:41 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-18 02:11:41 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-18 02:11:41 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-18 02:11:41 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-18 02:11:41 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-18 02:11:41 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-18 02:11:41 (9268) [INFO] * 2024-12-18 02:11:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-18 02:11:41 (9238) [INFO] * 2024-12-18 02:11:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 02:11:42 (9251) [INFO] Determining fastest mirrors * 2024-12-18 02:12:14 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-18 02:12:14 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-18 02:12:14 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-18 02:12:14 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-18 02:13:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-18 02:13:00 (9251) [INFO] Trying other mirror. * 2024-12-18 02:15:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-18 02:15:47 (9251) [INFO] Trying other mirror. * 2024-12-18 02:15:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:15:47 (9251) [INFO] Trying other mirror. * 2024-12-18 02:18:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-18 02:18:27 (9251) [INFO] Trying other mirror. * 2024-12-18 02:21:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:21:15 (9251) [INFO] Trying other mirror. * 2024-12-18 02:21:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:21:15 (9251) [INFO] Trying other mirror. * 2024-12-18 02:22:17 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-18 02:22:17 (9251) [INFO] Trying other mirror. * 2024-12-18 02:22:17 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-18 02:22:17 (9251) [INFO] Trying other mirror. * 2024-12-18 02:22:47 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:22:47 (9251) [INFO] Trying other mirror. * 2024-12-18 02:22:47 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:22:47 (9251) [INFO] Trying other mirror. * 2024-12-18 02:23:18 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-18 02:23:18 (9251) [INFO] Trying other mirror. * 2024-12-18 02:23:48 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30314 milliseconds') * 2024-12-18 02:23:48 (9251) [INFO] Trying other mirror. * 2024-12-18 02:24:19 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-18 02:24:19 (9251) [INFO] Trying other mirror. * 2024-12-18 02:25:37 (9251) [INFO] Metadata Cache Created * 2024-12-18 02:25:37 (9268) [INFO] * 2024-12-18 02:25:37 (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 02:25:37 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30314 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-18 02:25:38 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-18 02:25:38 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-18 02:25:38 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-18 02:25:38 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-18 02:25:38 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-18 02:25:44 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Z_6Rofr8UX/ea_profile.json * 2024-12-18 02:25:47 (8385) [INFO] Backed up EA4 profile to /tmp/Z_6Rofr8UX/ea_profile.json * 2024-12-18 02:25:48 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-18 02:26:22 (627) [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-12-18 02:26:22 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-19 02:08:50 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-19 02:12:50 (10313) [INFO] Script is up to date. * 2024-12-19 02:16:53 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-19 02:16:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-19 02:16:54 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-19 02:16:54 (9238) [INFO] * 2024-12-19 02:17:07 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-19 02:17:07 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-19 02:17:07 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-19 02:17:07 (9238) [INFO] * 2024-12-19 02:17:19 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-19 02:17:22 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-19 02:17:22 (9238) [INFO] * 2024-12-19 02:17:23 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 02:17:23 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-19 02:17:53 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-19 02:17:53 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-19 02:17:53 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-19 02:17:53 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-19 02:20:39 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-19 02:20:39 (9251) [INFO] Trying other mirror. * 2024-12-19 02:20:56 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-19 02:20:56 (9251) [INFO] Trying other mirror. * 2024-12-19 02:21:29 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-19 02:21:29 (9251) [INFO] Trying other mirror. * 2024-12-19 02:21:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-19 02:21:39 (9251) [INFO] Trying other mirror. * 2024-12-19 02:22:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-19 02:22:00 (9251) [INFO] Trying other mirror. * 2024-12-19 02:22:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-19 02:22:09 (9251) [INFO] Trying other mirror. * 2024-12-19 02:22:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-19 02:22:30 (9251) [INFO] Trying other mirror. * 2024-12-19 02:23:14 (9251) [INFO] Metadata Cache Created * 2024-12-19 02:23:14 (9268) [INFO] * 2024-12-19 02:23:14 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-19 02:23:14 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-19 02:23:14 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-19 02:23:14 (9238) [INFO] * 2024-12-19 02:23:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 02:23:15 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-19 02:23:15 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-19 02:23:15 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-19 02:23:15 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-19 02:23:15 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-19 02:23:15 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-19 02:23:15 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-19 02:23:15 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-19 02:23:15 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-19 02:23:15 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-19 02:23:15 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-19 02:23:15 (9268) [INFO] * 2024-12-19 02:23:15 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-19 02:23:15 (9238) [INFO] * 2024-12-19 02:23:16 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 02:23:16 (9251) [INFO] Determining fastest mirrors * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-19 02:23:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-19 02:23:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-19 02:23:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-19 02:23:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-19 02:23:47 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-19 02:23:47 (9251) [INFO] yum --disablerepo= ... * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-19 02:23:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-19 02:23:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] yum-config-manager --disable * 2024-12-19 02:23:47 (9251) [INFO] or * 2024-12-19 02:23:47 (9251) [INFO] subscription-manager repos --disable= * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-19 02:23:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-19 02:23:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-19 02:23:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-19 02:23:47 (9251) [INFO] compromise: * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-19 02:23:47 (9251) [INFO] * 2024-12-19 02:23:47 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-19 02:23:47 (9268) [INFO] * 2024-12-19 02:23: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-19 02:23:47 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-19 02:23:48 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-19 02:23:48 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-19 02:23:48 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-19 02:23:48 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-19 02:23:48 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-19 02:30:39 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gtMkAPqTPv/ea_profile.json * 2024-12-20 01:55:21 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-20 01:59:21 (10313) [INFO] Script is up to date. * 2024-12-20 02:03:25 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-20 02:03:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-20 02:03:25 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-20 02:03:25 (9238) [INFO] * 2024-12-20 02:08:29 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-20 02:08:29 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-20 02:08:30 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-20 02:08:30 (9238) [INFO] * 2024-12-20 02:08:38 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-20 02:08:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-20 02:08:41 (9238) [INFO] * 2024-12-20 02:08:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 02:08:42 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-20 02:09:12 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-20 02:09:12 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-20 02:09:12 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-20 02:09:12 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-20 02:11:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:11:57 (9251) [INFO] Trying other mirror. * 2024-12-20 02:12:14 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:12:14 (9251) [INFO] Trying other mirror. * 2024-12-20 02:12:47 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:12:47 (9251) [INFO] Trying other mirror. * 2024-12-20 02:13:17 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-20 02:13:17 (9251) [INFO] Trying other mirror. * 2024-12-20 02:14:00 (9251) [INFO] Metadata Cache Created * 2024-12-20 02:14:00 (9268) [INFO] * 2024-12-20 02:14:00 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2024-12-20 02:14:00 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-20 02:14:00 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-20 02:14:00 (9238) [INFO] * 2024-12-20 02:14:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 02:14:01 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-20 02:14:01 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-20 02:14:01 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-20 02:14:01 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-20 02:14:01 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-20 02:14:01 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-20 02:14:01 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-20 02:14:01 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-20 02:14:01 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-20 02:14:02 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-20 02:14:02 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-20 02:14:02 (9268) [INFO] * 2024-12-20 02:14:02 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-20 02:14:02 (9238) [INFO] * 2024-12-20 02:14:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 02:14:03 (9251) [INFO] Determining fastest mirrors * 2024-12-20 02:14:34 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-20 02:14:34 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-20 02:14:34 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-20 02:14:34 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-20 02:17:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30537 milliseconds') * 2024-12-20 02:17:37 (9251) [INFO] Trying other mirror. * 2024-12-20 02:17:38 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30850 milliseconds') * 2024-12-20 02:17:38 (9251) [INFO] Trying other mirror. * 2024-12-20 02:18:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-20 02:18:08 (9251) [INFO] Trying other mirror. * 2024-12-20 02:18:39 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-20 02:18:39 (9251) [INFO] Trying other mirror. * 2024-12-20 02:20:17 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:20:17 (9251) [INFO] Trying other mirror. * 2024-12-20 02:20:18 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-20 02:20:18 (9251) [INFO] Trying other mirror. * 2024-12-20 02:23:36 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:23:36 (9251) [INFO] Trying other mirror. * 2024-12-20 02:24:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-20 02:24:08 (9251) [INFO] Trying other mirror. * 2024-12-20 02:25:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-20 02:25:09 (9251) [INFO] Trying other mirror. * 2024-12-21 01:51:51 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-21 01:55:51 (10313) [INFO] Script is up to date. * 2024-12-21 01:59:55 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-21 01:59:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-21 01:59:55 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-21 01:59:55 (9238) [INFO] * 2024-12-21 02:00:05 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-21 02:00:05 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-21 02:00:05 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-21 02:00:05 (9238) [INFO] * 2024-12-21 02:00:15 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-21 02:00:18 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-21 02:00:18 (9238) [INFO] * 2024-12-21 02:00:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 02:00:19 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-21 02:00:49 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-21 02:00:49 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-21 02:00:49 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-21 02:00:49 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-21 02:01:36 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-21 02:01:36 (9251) [INFO] Trying other mirror. * 2024-12-21 02:02:06 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-21 02:02:06 (9251) [INFO] Trying other mirror. * 2024-12-21 02:02:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-21 02:02:37 (9251) [INFO] Trying other mirror. * 2024-12-21 02:03:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-21 02:03:08 (9251) [INFO] Trying other mirror. * 2024-12-21 02:03:38 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-21 02:03:38 (9251) [INFO] Trying other mirror. * 2024-12-21 02:06:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-21 02:06:08 (9251) [INFO] Trying other mirror. * 2024-12-21 02:06:09 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2024-12-21 02:06:09 (9251) [INFO] Trying other mirror. * 2024-12-21 02:06:57 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:06:57 (9251) [INFO] Trying other mirror. * 2024-12-21 02:06:57 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:06:57 (9251) [INFO] Trying other mirror. * 2024-12-21 02:07:41 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-21 02:07:41 (9251) [INFO] Trying other mirror. * 2024-12-21 02:07:41 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-21 02:07:41 (9251) [INFO] Trying other mirror. * 2024-12-21 02:07:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-21 02:07:57 (9251) [INFO] Trying other mirror. * 2024-12-21 02:08:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:08:28 (9251) [INFO] Trying other mirror. * 2024-12-21 02:08:28 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-21 02:08:28 (9251) [INFO] Trying other mirror. * 2024-12-21 02:08:58 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:08:58 (9251) [INFO] Trying other mirror. * 2024-12-21 02:08:58 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-21 02:08:58 (9251) [INFO] Trying other mirror. * 2024-12-21 02:09:28 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-21 02:09:28 (9251) [INFO] Trying other mirror. * 2024-12-21 02:09:58 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:09:58 (9251) [INFO] Trying other mirror. * 2024-12-21 02:10:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-21 02:10:29 (9251) [INFO] Trying other mirror. * 2024-12-21 02:11:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-21 02:11:00 (9251) [INFO] Trying other mirror. * 2024-12-21 02:11:30 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:11:30 (9251) [INFO] Trying other mirror. * 2024-12-21 02:12:28 (9251) [INFO] Metadata Cache Created * 2024-12-21 02:12:28 (9268) [INFO] * 2024-12-21 02:12:28 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-21 02:12:28 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-21 02:12:28 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-21 02:12:28 (9238) [INFO] * 2024-12-21 02:12:28 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 02:12:28 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-21 02:12:28 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-21 02:12:28 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-21 02:12:28 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-21 02:12:28 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-21 02:12:28 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-21 02:12:28 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-21 02:12:28 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-21 02:12:28 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-21 02:12:29 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-21 02:12:29 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-21 02:12:29 (9268) [INFO] * 2024-12-21 02:12:29 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-21 02:12:29 (9238) [INFO] * 2024-12-21 02:12:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 02:12:30 (9251) [INFO] Determining fastest mirrors * 2024-12-21 02:13:01 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-21 02:13:01 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-21 02:13:01 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-21 02:13:01 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-21 02:16:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-21 02:16:04 (9251) [INFO] Trying other mirror. * 2024-12-21 02:16:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-21 02:16:04 (9251) [INFO] Trying other mirror. * 2024-12-21 02:16:34 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-21 02:16:34 (9251) [INFO] Trying other mirror. * 2024-12-21 02:18:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:18:43 (9251) [INFO] Trying other mirror. * 2024-12-21 02:21:32 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-21 02:21:32 (9251) [INFO] Trying other mirror. * 2024-12-21 02:21:32 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-21 02:21:32 (9251) [INFO] Trying other mirror. * 2024-12-22 01:54:04 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-22 01:58:04 (10313) [INFO] Script is up to date. * 2024-12-22 02:02:08 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-22 02:02:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-22 02:02:08 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-22 02:02:08 (9238) [INFO] * 2024-12-22 02:02:20 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-22 02:02:20 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-22 02:02:20 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-22 02:02:20 (9238) [INFO] * 2024-12-22 02:02:29 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-22 02:02:32 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-22 02:02:32 (9238) [INFO] * 2024-12-22 02:02:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 02:02:33 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-22 02:03:03 (9251) [INFO] * EA4: 184.94.196.92 * 2024-12-22 02:03:03 (9251) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2024-12-22 02:03:03 (9251) [INFO] * cpanel-plugins: 184.94.196.92 * 2024-12-22 02:03:03 (9251) [INFO] * epel: mirror.math.princeton.edu * 2024-12-22 02:05:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-22 02:05:49 (9251) [INFO] Trying other mirror. * 2024-12-22 02:06:05 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:06:05 (9251) [INFO] Trying other mirror. * 2024-12-22 02:06:22 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:06:22 (9251) [INFO] Trying other mirror. * 2024-12-22 02:06:38 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-22 02:06:38 (9251) [INFO] Trying other mirror. * 2024-12-22 02:07:08 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:07:08 (9251) [INFO] Trying other mirror. * 2024-12-22 02:07:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-22 02:07:39 (9251) [INFO] Trying other mirror. * 2024-12-22 02:08:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-22 02:08:09 (9251) [INFO] Trying other mirror. * 2024-12-22 02:08:51 (9251) [INFO] Metadata Cache Created * 2024-12-22 02:08:51 (9268) [INFO] * 2024-12-22 02:08:51 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2024-12-22 02:08:51 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-22 02:08:51 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-22 02:08:51 (9238) [INFO] * 2024-12-22 02:08:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 02:08:51 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-22 02:08:51 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-22 02:08:51 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-22 02:08:51 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-22 02:08:51 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-22 02:08:51 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-22 02:08:51 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-22 02:08:51 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-22 02:08:51 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-22 02:08:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-22 02:08:52 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-22 02:08:52 (9268) [INFO] * 2024-12-22 02:08:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-22 02:08:52 (9238) [INFO] * 2024-12-22 02:08:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 02:08:53 (9251) [INFO] Determining fastest mirrors * 2024-12-22 02:09:24 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-22 02:09:24 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-22 02:09:24 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-22 02:09:24 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-22 02:12:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:12:27 (9251) [INFO] Trying other mirror. * 2024-12-22 02:12:28 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-22 02:12:28 (9251) [INFO] Trying other mirror. * 2024-12-22 02:12:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-22 02:12:57 (9251) [INFO] Trying other mirror. * 2024-12-22 02:12:58 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/18175b328ba997f6a064a147ab33fd5885d26a059e1afbc3ede702570b1e9ede-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:12:58 (9251) [INFO] Trying other mirror. * 2024-12-22 02:12:58 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/44cf8b0de14653cde53e609df79fd95f84da1eb6a6abf34e5001877d86879fbf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:12:58 (9251) [INFO] Trying other mirror. * 2024-12-22 02:13:14 (9251) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:13:14 (9251) [INFO] Trying other mirror. * 2024-12-22 02:13:30 (9251) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:13:30 (9251) [INFO] Trying other mirror. * 2024-12-22 02:13:46 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:13:46 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:01 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:01 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:17 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:17 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:33 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:33 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:33 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:33 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:35 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:35 (9251) [INFO] Trying other mirror. * 2024-12-22 02:14:35 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:14:35 (9251) [INFO] Trying other mirror. * 2024-12-22 02:15:03 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/7075159f5e3cfed3ccd67af0ad2e2c04e7bd6619e75fa4dde893d6d4b58ce751-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:15:03 (9251) [INFO] Trying other mirror. * 2024-12-22 02:15:06 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:15:06 (9251) [INFO] Trying other mirror. * 2024-12-22 02:15:18 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM0ODU4NTIxOjE3MzUxMTc3MjE6XS_INUHww0QOsuZ--lZna8UDeUxChhFjpIUf591ipfghG1f6yNrfWLYn5M_pDAt2nBwWG0GYhDOxAUJryFd70jIhJrSlQRiLQ3axtzUb1pshq4IF9H9ZB6RH00H3QW45I8WCn-vlJ953aq0rj5FRLCMwmaFrntaXef7C5pOmf1k0gwNiiO1NY0cD5kCtQvQSEVZO4xTWl1wCxCiB4Bb9Sbrh8kWckMxvxQ40TGLYcmv6Hm_0lUqEs_ZCaz3VjrfVtt5rM6n_f6tUavUFH1RFemcqlfI4o0oEwJdSnrn-Cv7hw4krmg7dGJsxIe6nJDAFeb1yM0FsiTZz8OpFmU4KPX96TYP53F10fnELQhJIk602jSONP_ZzZs90TMeW1QAH-ox6XllsAlWHQSTm0W5zv9iFD9agQkjS6OHzg6mbFRHdBZowKQyjik6FhCdnwOCof3JsetmEn_BejpflmtuqHeKtVavo1er4EyHNkj3CSR1ranfAqh2nNMS3T7PNjb3w99vJvZce9aGBXrGcGoSUCYU9z-i7WJL1OUujoyAmaud0hyccNd2EQBLGpdW5WVp6n3KdLTT22Psve7odR9nVMQitv9qZ7EY_N_SY1GCrxqExsKQ2bRMGiq7WErjfgEZ7lBo_0C4GWzOvH0R__jUTKF0E6blkuqVwIdUDMy3avbc%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:15:18 (9251) [INFO] Trying other mirror. * 2024-12-22 02:15:34 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM0ODU4NTIxOjE3MzUxMTc3MjE6XS_INUHww0QOsuZ--lZna8UDeUxChhFjpIUf591ipfghG1f6yNrfWLYn5M_pDAt2nBwWG0GYhDOxAUJryFd70jIhJrSlQRiLQ3axtzUb1pshq4IF9H9ZB6RH00H3QW45I8WCn-vlJ953aq0rj5FRLCMwmaFrntaXef7C5pOmf1k0gwNiiO1NY0cD5kCtQvQSEVZO4xTWl1wCxCiB4Bb9Sbrh8kWckMxvxQ40TGLYcmv6Hm_0lUqEs_ZCaz3VjrfVtt5rM6n_f6tUavUFH1RFemcqlfI4o0oEwJdSnrn-Cv7hw4krmg7dGJsxIe6nJDAFeb1yM0FsiTZz8OpFmU4KPX96TYP53F10fnELQhJIk602jSONP_ZzZs90TMeW1QAH-ox6XllsAlWHQSTm0W5zv9iFD9agQkjS6OHzg6mbFRHdBZowKQyjik6FhCdnwOCof3JsetmEn_BejpflmtuqHeKtVavo1er4EyHNkj3CSR1ranfAqh2nNMS3T7PNjb3w99vJvZce9aGBXrGcGoSUCYU9z-i7WJL1OUujoyAmaud0hyccNd2EQBLGpdW5WVp6n3KdLTT22Psve7odR9nVMQitv9qZ7EY_N_SY1GCrxqExsKQ2bRMGiq7WErjfgEZ7lBo_0C4GWzOvH0R__jUTKF0E6blkuqVwIdUDMy3avbc%3D/ea-php/7/updates/x86_64/repodata/0505f48892f6112cb51f916c016fd005f72200f2866c40a81e69523ff701a565-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:15:34 (9251) [INFO] Trying other mirror. * 2024-12-22 02:15:49 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:15:49 (9251) [INFO] Trying other mirror. * 2024-12-22 02:16:05 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:16:05 (9251) [INFO] Trying other mirror. * 2024-12-22 02:16:21 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:16:21 (9251) [INFO] Trying other mirror. * 2024-12-22 02:16:36 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:16:36 (9251) [INFO] Trying other mirror. * 2024-12-22 02:16:52 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:16:52 (9251) [INFO] Trying other mirror. * 2024-12-22 02:17:07 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:17:07 (9251) [INFO] Trying other mirror. * 2024-12-22 02:17:23 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:17:23 (9251) [INFO] Trying other mirror. * 2024-12-22 02:17:39 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:17:39 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:18:09 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:25 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.1/wp-toolkit/repodata/279098e5fe35faeb6e3ab6c9da0adcf9fe110a09d3f2c3857b1e9118e75ee91f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:25 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:40 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.1/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:40 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:40 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:40 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:41 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:41 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:41 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:41 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:57 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:57 (9251) [INFO] Trying other mirror. * 2024-12-22 02:18:57 (9251) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:18:57 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:11 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2024-12-22 02:19:11 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:11 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:11 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-22 02:19:12 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:13 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:13 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:25 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:25 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:28 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:28 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:30 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:30 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:41 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:41 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:42 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:19:42 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:45 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:45 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:55 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: (28, 'timed out before SSL handshake') * 2024-12-22 02:19:55 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:55 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:55 (9251) [INFO] Trying other mirror. * 2024-12-22 02:19:55 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:19:55 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:11 (9251) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:11 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:12 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:12 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:25 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:25 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:26 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-22 02:20:26 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:27 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:27 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:27 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:27 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:42 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:42 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:53 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:53 (9251) [INFO] Trying other mirror. * 2024-12-22 02:20:53 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:20:53 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:08 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:08 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:09 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:09 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:09 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:09 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:20 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:20 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:24 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:24 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:25 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:25 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:35 (9251) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:35 (9251) [INFO] Trying other mirror. * 2024-12-22 02:21:41 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:21:41 (9251) [INFO] Trying other mirror. * 2024-12-22 02:22:05 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-22 02:22:05 (9251) [INFO] Trying other mirror. * 2024-12-22 02:23:09 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-22 02:23:09 (9251) [INFO] Trying other mirror. * 2024-12-22 02:23:39 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-22 02:23:39 (9251) [INFO] Trying other mirror. * 2024-12-23 01:48:54 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-23 01:52:54 (10313) [INFO] Script is up to date. * 2024-12-23 01:56:57 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-23 01:56:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-23 01:56:58 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-23 01:56:58 (9238) [INFO] * 2024-12-23 01:57:10 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-23 01:57:10 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-23 01:57:10 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-23 01:57:10 (9238) [INFO] * 2024-12-23 01:57:30 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-23 01:57:33 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-23 01:57:33 (9238) [INFO] * 2024-12-23 01:57:33 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 01:57:33 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-23 01:58:03 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-23 01:58:03 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-23 01:58:03 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-23 01:58:03 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-23 02:00:50 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-23 02:00:50 (9251) [INFO] Trying other mirror. * 2024-12-23 02:00:50 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-23 02:00:50 (9251) [INFO] Trying other mirror. * 2024-12-23 02:01:11 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-23 02:01:11 (9251) [INFO] Trying other mirror. * 2024-12-23 02:01:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-23 02:01:21 (9251) [INFO] Trying other mirror. * 2024-12-23 02:01:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:01:55 (9251) [INFO] Trying other mirror. * 2024-12-23 02:01:57 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-23 02:01:57 (9251) [INFO] Trying other mirror. * 2024-12-23 02:02:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-23 02:02:19 (9251) [INFO] Trying other mirror. * 2024-12-23 02:02:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:02:49 (9251) [INFO] Trying other mirror. * 2024-12-23 02:02:49 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:02:49 (9251) [INFO] Trying other mirror. * 2024-12-23 02:03:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-23 02:03:20 (9251) [INFO] Trying other mirror. * 2024-12-23 02:03:20 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-23 02:03:20 (9251) [INFO] Trying other mirror. * 2024-12-23 02:03:51 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:03:51 (9251) [INFO] Trying other mirror. * 2024-12-23 02:03:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:03:51 (9251) [INFO] Trying other mirror. * 2024-12-23 02:04:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:04:21 (9251) [INFO] Trying other mirror. * 2024-12-23 02:04:21 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-23 02:04:21 (9251) [INFO] Trying other mirror. * 2024-12-23 02:04:51 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:04:51 (9251) [INFO] Trying other mirror. * 2024-12-23 02:05:22 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:05:22 (9251) [INFO] Trying other mirror. * 2024-12-23 02:05:22 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:05:22 (9251) [INFO] Trying other mirror. * 2024-12-23 02:05:52 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:05:52 (9251) [INFO] Trying other mirror. * 2024-12-23 02:06:22 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-23 02:06:22 (9251) [INFO] Trying other mirror. * 2024-12-23 02:06:23 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-23 02:06:23 (9251) [INFO] Trying other mirror. * 2024-12-23 02:06:53 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-23 02:06:53 (9251) [INFO] Trying other mirror. * 2024-12-23 02:07:54 (9251) [INFO] Metadata Cache Created * 2024-12-23 02:07:54 (9268) [INFO] * 2024-12-23 02:07:54 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-23 02:07:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-23 02:07:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-23 02:07:54 (9238) [INFO] * 2024-12-23 02:07:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 02:07:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-23 02:07:54 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-23 02:07:54 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-23 02:07:54 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-23 02:07:54 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-23 02:07:54 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-23 02:07:54 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-23 02:07:54 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-23 02:07:54 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-23 02:07:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-23 02:07:55 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-23 02:07:55 (9268) [INFO] * 2024-12-23 02:07:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-23 02:07:55 (9238) [INFO] * 2024-12-23 02:07:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 02:07:56 (9251) [INFO] Determining fastest mirrors * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-23 02:08:28 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-23 02:08:28 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-23 02:08:28 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-23 02:08:28 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-23 02:08:28 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-23 02:08:28 (9251) [INFO] yum --disablerepo= ... * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-23 02:08:28 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-23 02:08:28 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] yum-config-manager --disable * 2024-12-23 02:08:28 (9251) [INFO] or * 2024-12-23 02:08:28 (9251) [INFO] subscription-manager repos --disable= * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-23 02:08:28 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-23 02:08:28 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-23 02:08:28 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-23 02:08:28 (9251) [INFO] compromise: * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-23 02:08:28 (9251) [INFO] * 2024-12-23 02:08:28 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-23 02:08:28 (9268) [INFO] * 2024-12-23 02:08:28 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-23 02:08:28 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-23 02:08:29 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-23 02:08:29 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-23 02:08:29 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-23 02:08:29 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-23 02:08:29 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-23 02:10:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/F4nS6WYc6f/ea_profile.json * 2024-12-23 02:14:13 (8385) [INFO] Backed up EA4 profile to /tmp/F4nS6WYc6f/ea_profile.json * 2024-12-23 02:14:14 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fileinfo - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-intl - ea-php56-php-ioncube10 - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mcrypt - ea-php56-php-mssql - ea-php56-php-mysqlnd - ea-php56-php-odbc - ea-php56-php-pdo - ea-php56-php-pgsql - ea-php56-php-posix - ea-php56-php-process - ea-php56-php-snmp - ea-php56-php-soap - ea-php56-php-sockets - ea-php56-php-sourceguardian - ea-php56-php-xml - ea-php56-php-xmlrpc - ea-php56-php-zip - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fileinfo - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-intl - 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-snmp - ea-php71-php-soap - ea-php71-php-xml - ea-php71-php-xmlrpc - ea-php71-php-zip - ea-php71-runtime - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-23 02:14:48 (627) [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-12-23 02:14:48 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-24 02:21:04 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-24 02:25:05 (10313) [INFO] Script is up to date. * 2024-12-24 02:29:08 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-24 02:29:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-24 02:29:08 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-24 02:29:08 (9238) [INFO] * 2024-12-24 02:29:11 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-24 02:29:11 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-24 02:29:11 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-24 02:29:11 (9238) [INFO] * 2024-12-24 02:29:20 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-24 02:29:23 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-24 02:29:23 (9238) [INFO] * 2024-12-24 02:29:24 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 02:29:24 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-24 02:29:54 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-24 02:29:54 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-24 02:29:54 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-24 02:29:54 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-24 02:30:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-24 02:30:41 (9251) [INFO] Trying other mirror. * 2024-12-24 02:31:11 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-24 02:31:11 (9251) [INFO] Trying other mirror. * 2024-12-24 02:33:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:33:41 (9251) [INFO] Trying other mirror. * 2024-12-24 02:33:58 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-24 02:33:58 (9251) [INFO] Trying other mirror. * 2024-12-24 02:34:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30537 milliseconds') * 2024-12-24 02:34:15 (9251) [INFO] Trying other mirror. * 2024-12-24 02:34:29 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-24 02:34:29 (9251) [INFO] Trying other mirror. * 2024-12-24 02:34:30 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:34:30 (9251) [INFO] Trying other mirror. * 2024-12-24 02:34:46 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-24 02:34:46 (9251) [INFO] Trying other mirror. * 2024-12-24 02:34:59 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:34:59 (9251) [INFO] Trying other mirror. * 2024-12-24 02:35:44 (9251) [INFO] Metadata Cache Created * 2024-12-24 02:35:44 (9268) [INFO] * 2024-12-24 02:35:44 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30537 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-24 02:35:44 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-24 02:35:44 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-24 02:35:44 (9238) [INFO] * 2024-12-24 02:35:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 02:35:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-24 02:35:45 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-24 02:35:45 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-24 02:35:45 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-24 02:35:45 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-24 02:35:45 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-24 02:35:45 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-24 02:35:45 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-24 02:35:45 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-24 02:35:45 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-24 02:35:45 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-24 02:35:46 (9268) [INFO] * 2024-12-24 02:35:46 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-24 02:35:46 (9238) [INFO] * 2024-12-24 02:35:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 02:35:46 (9251) [INFO] Determining fastest mirrors * 2024-12-24 02:36:19 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-24 02:36:19 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-24 02:36:19 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-24 02:36:19 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-24 02:37:05 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-24 02:37:05 (9251) [INFO] Trying other mirror. * 2024-12-24 02:37:36 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-24 02:37:36 (9251) [INFO] Trying other mirror. * 2024-12-24 02:40:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-24 02:40:26 (9251) [INFO] Trying other mirror. * 2024-12-24 02:40:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:40:26 (9251) [INFO] Trying other mirror. * 2024-12-24 02:40:57 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/44cf8b0de14653cde53e609df79fd95f84da1eb6a6abf34e5001877d86879fbf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:40:57 (9251) [INFO] Trying other mirror. * 2024-12-24 02:41:13 (9251) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:41:13 (9251) [INFO] Trying other mirror. * 2024-12-24 02:41:28 (9251) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:41:28 (9251) [INFO] Trying other mirror. * 2024-12-24 02:41:44 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:41:44 (9251) [INFO] Trying other mirror. * 2024-12-24 02:41:59 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:41:59 (9251) [INFO] Trying other mirror. * 2024-12-24 02:42:15 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:42:15 (9251) [INFO] Trying other mirror. * 2024-12-24 02:42:31 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:42:31 (9251) [INFO] Trying other mirror. * 2024-12-24 02:42:34 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:42:34 (9251) [INFO] Trying other mirror. * 2024-12-24 02:43:01 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e9d5398a26bc9639935a58dd568a61a673e2d348137b6e2030004575cfdc712f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:43:01 (9251) [INFO] Trying other mirror. * 2024-12-24 02:43:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:43:04 (9251) [INFO] Trying other mirror. * 2024-12-24 02:43:16 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1MDMyMzkxOjE3MzUyOTE1OTE6MRdaYfgsFF6GCnUtHWbF28G9hC-ttfVg76eva8VRzSO65XGkxZzV-fNgwr6DHQQETmJRycRGNCv798AkqHx_kUhI344SfymR0gyrs4rSKYHNmG7bUeYnJD5DHuii5q6d5BBLQAZuNo4BpkaZz41I9-U4j5xK736p9EmitLNkXLTlHkONpf8P-9gbJP-TGGwIhDrEh1Bj_yA1FGIMQ_uxtuWB7rO4xNzQmsoDjaDRCwbiX40XbqetXKU2cthyNIyp5Qjyo7b2FcKMUAQXt5sudcVfwGL3g26lwypxos6vnVyqw-gcwAXG2J83s3KaJ8DpZJL8ivf-v7eN2Boal5Gn_H2mQW_cmPSviUg48qrL3LPczWi6HtHWmfF_B6X7FAbnE5VZ2IjGc9LneTVduOVHVdAx2EQ3VTt4iFgi5QPQBlZQQuJvXPMipzc3Bjya3JBSDN66An0LZDQzwdOKf4r7zG246s-HvCylYrMn_KVgRH8Bt3GdirC-EkS0xEzIHehFsjbxANjnjf-PXzmdELgdkTLVjuobCSu2WJm-yHefz49rg4wz8ODY0n3zKMdoYDOrT5LCtqigQbovNu6qiXzxRj_wmaBFpg07hhDktExtAbU-P_TsD3mf2lkCX7CTTaXbInaxG-sTqH63TEkZltRCE20vJ0x5757tQW8j_L_rZ3I%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:43:16 (9251) [INFO] Trying other mirror. * 2024-12-24 02:43:32 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1MDMyMzkxOjE3MzUyOTE1OTE6MRdaYfgsFF6GCnUtHWbF28G9hC-ttfVg76eva8VRzSO65XGkxZzV-fNgwr6DHQQETmJRycRGNCv798AkqHx_kUhI344SfymR0gyrs4rSKYHNmG7bUeYnJD5DHuii5q6d5BBLQAZuNo4BpkaZz41I9-U4j5xK736p9EmitLNkXLTlHkONpf8P-9gbJP-TGGwIhDrEh1Bj_yA1FGIMQ_uxtuWB7rO4xNzQmsoDjaDRCwbiX40XbqetXKU2cthyNIyp5Qjyo7b2FcKMUAQXt5sudcVfwGL3g26lwypxos6vnVyqw-gcwAXG2J83s3KaJ8DpZJL8ivf-v7eN2Boal5Gn_H2mQW_cmPSviUg48qrL3LPczWi6HtHWmfF_B6X7FAbnE5VZ2IjGc9LneTVduOVHVdAx2EQ3VTt4iFgi5QPQBlZQQuJvXPMipzc3Bjya3JBSDN66An0LZDQzwdOKf4r7zG246s-HvCylYrMn_KVgRH8Bt3GdirC-EkS0xEzIHehFsjbxANjnjf-PXzmdELgdkTLVjuobCSu2WJm-yHefz49rg4wz8ODY0n3zKMdoYDOrT5LCtqigQbovNu6qiXzxRj_wmaBFpg07hhDktExtAbU-P_TsD3mf2lkCX7CTTaXbInaxG-sTqH63TEkZltRCE20vJ0x5757tQW8j_L_rZ3I%3D/ea-php/7/updates/x86_64/repodata/57a575bcda54fea8c85463fdeb7da3862ed24d81b6ec1f09f8eada3276760fba-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:43:32 (9251) [INFO] Trying other mirror. * 2024-12-24 02:43:47 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:43:47 (9251) [INFO] Trying other mirror. * 2024-12-24 02:44:03 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:44:03 (9251) [INFO] Trying other mirror. * 2024-12-24 02:44:19 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:44:19 (9251) [INFO] Trying other mirror. * 2024-12-24 02:44:34 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:44:34 (9251) [INFO] Trying other mirror. * 2024-12-24 02:44:50 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:44:50 (9251) [INFO] Trying other mirror. * 2024-12-24 02:45:05 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:45:05 (9251) [INFO] Trying other mirror. * 2024-12-24 02:45:21 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:45:21 (9251) [INFO] Trying other mirror. * 2024-12-24 02:45:37 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:45:37 (9251) [INFO] Trying other mirror. * 2024-12-24 02:46:07 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2024-12-24 02:46:07 (9251) [INFO] Trying other mirror. * 2024-12-24 02:46:07 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-24 02:46:07 (9251) [INFO] Trying other mirror. * 2024-12-24 02:46:23 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/wp-toolkit/repodata/48342a99b2f6d6b8817cf525b46227649da53e4dd538bed4da6b6959df8fd0c9-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:46:23 (9251) [INFO] Trying other mirror. * 2024-12-24 02:46:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-24 02:46:38 (9251) [INFO] Trying other mirror. * 2024-12-24 02:46:38 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:46:38 (9251) [INFO] Trying other mirror. * 2024-12-24 02:47:09 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:47:09 (9251) [INFO] Trying other mirror. * 2024-12-24 02:47:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:47:39 (9251) [INFO] Trying other mirror. * 2024-12-24 02:47:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:47:39 (9251) [INFO] Trying other mirror. * 2024-12-24 02:48:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-24 02:48:09 (9251) [INFO] Trying other mirror. * 2024-12-24 02:48:26 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:48:26 (9251) [INFO] Trying other mirror. * 2024-12-24 02:48:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:48:40 (9251) [INFO] Trying other mirror. * 2024-12-24 02:48:40 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:48:40 (9251) [INFO] Trying other mirror. * 2024-12-24 02:48:57 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:48:57 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:11 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-24 02:49:11 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:24 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:49:24 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:25 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:49:25 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:41 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:49:41 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:41 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:49:41 (9251) [INFO] Trying other mirror. * 2024-12-24 02:49:58 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:49:58 (9251) [INFO] Trying other mirror. * 2024-12-24 02:50:14 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-24 02:50:14 (9251) [INFO] Trying other mirror. * 2024-12-24 02:50:45 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-24 02:50:45 (9251) [INFO] Trying other mirror. * 2024-12-25 01:53:48 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-25 01:57:49 (10313) [INFO] Script is up to date. * 2024-12-25 02:01:52 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-25 02:01:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-25 02:01:52 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-25 02:01:52 (9238) [INFO] * 2024-12-25 02:01:55 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-25 02:01:55 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-25 02:01:55 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-25 02:01:55 (9238) [INFO] * 2024-12-25 02:02:08 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-25 02:02:11 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-25 02:02:11 (9238) [INFO] * 2024-12-25 02:02:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 02:02:12 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-25 02:02:42 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-25 02:02:42 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-25 02:02:42 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-25 02:02:42 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-25 02:05:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2024-12-25 02:05:27 (9251) [INFO] Trying other mirror. * 2024-12-25 02:05:44 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:05:44 (9251) [INFO] Trying other mirror. * 2024-12-25 02:06:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:06:00 (9251) [INFO] Trying other mirror. * 2024-12-25 02:06:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:06:13 (9251) [INFO] Trying other mirror. * 2024-12-25 02:06:31 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-25 02:06:31 (9251) [INFO] Trying other mirror. * 2024-12-25 02:07:02 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-25 02:07:02 (9251) [INFO] Trying other mirror. * 2024-12-25 02:07:32 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-25 02:07:32 (9251) [INFO] Trying other mirror. * 2024-12-25 02:08:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-25 02:08:03 (9251) [INFO] Trying other mirror. * 2024-12-25 02:08:46 (9251) [INFO] Metadata Cache Created * 2024-12-25 02:08:46 (9268) [INFO] * 2024-12-25 02:08:46 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2024-12-25 02:08:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-25 02:08:46 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-25 02:08:46 (9238) [INFO] * 2024-12-25 02:08:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 02:08:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-25 02:08:47 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-25 02:08:47 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-25 02:08:47 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-25 02:08:47 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-25 02:08:47 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-25 02:08:47 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-25 02:08:47 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-25 02:08:47 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-25 02:08:48 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-25 02:08:48 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-25 02:08:48 (9268) [INFO] * 2024-12-25 02:08:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-25 02:08:48 (9238) [INFO] * 2024-12-25 02:08:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 02:08:48 (9251) [INFO] Determining fastest mirrors * 2024-12-25 02:09:20 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-25 02:09:20 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-25 02:09:20 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-25 02:09:20 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-25 02:10:07 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-25 02:10:07 (9251) [INFO] Trying other mirror. * 2024-12-25 02:12:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-25 02:12:54 (9251) [INFO] Trying other mirror. * 2024-12-25 02:12:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:12:54 (9251) [INFO] Trying other mirror. * 2024-12-25 02:13:24 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-25 02:13:24 (9251) [INFO] Trying other mirror. * 2024-12-25 02:13:25 (9251) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/44cf8b0de14653cde53e609df79fd95f84da1eb6a6abf34e5001877d86879fbf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:13:25 (9251) [INFO] Trying other mirror. * 2024-12-25 02:13:41 (9251) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-25 02:13:41 (9251) [INFO] Trying other mirror. * 2024-12-25 02:13:56 (9251) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:13:56 (9251) [INFO] Trying other mirror. * 2024-12-25 02:14:12 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:14:12 (9251) [INFO] Trying other mirror. * 2024-12-25 02:14:28 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:14:28 (9251) [INFO] Trying other mirror. * 2024-12-25 02:14:43 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:14:43 (9251) [INFO] Trying other mirror. * 2024-12-25 02:14:59 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:14:59 (9251) [INFO] Trying other mirror. * 2024-12-25 02:15:02 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:15:02 (9251) [INFO] Trying other mirror. * 2024-12-25 02:15:29 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e9d5398a26bc9639935a58dd568a61a673e2d348137b6e2030004575cfdc712f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:15:29 (9251) [INFO] Trying other mirror. * 2024-12-25 02:15:32 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:15:32 (9251) [INFO] Trying other mirror. * 2024-12-25 02:15:45 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1MDMyMzkxOjE3MzUyOTE1OTE6MRdaYfgsFF6GCnUtHWbF28G9hC-ttfVg76eva8VRzSO65XGkxZzV-fNgwr6DHQQETmJRycRGNCv798AkqHx_kUhI344SfymR0gyrs4rSKYHNmG7bUeYnJD5DHuii5q6d5BBLQAZuNo4BpkaZz41I9-U4j5xK736p9EmitLNkXLTlHkONpf8P-9gbJP-TGGwIhDrEh1Bj_yA1FGIMQ_uxtuWB7rO4xNzQmsoDjaDRCwbiX40XbqetXKU2cthyNIyp5Qjyo7b2FcKMUAQXt5sudcVfwGL3g26lwypxos6vnVyqw-gcwAXG2J83s3KaJ8DpZJL8ivf-v7eN2Boal5Gn_H2mQW_cmPSviUg48qrL3LPczWi6HtHWmfF_B6X7FAbnE5VZ2IjGc9LneTVduOVHVdAx2EQ3VTt4iFgi5QPQBlZQQuJvXPMipzc3Bjya3JBSDN66An0LZDQzwdOKf4r7zG246s-HvCylYrMn_KVgRH8Bt3GdirC-EkS0xEzIHehFsjbxANjnjf-PXzmdELgdkTLVjuobCSu2WJm-yHefz49rg4wz8ODY0n3zKMdoYDOrT5LCtqigQbovNu6qiXzxRj_wmaBFpg07hhDktExtAbU-P_TsD3mf2lkCX7CTTaXbInaxG-sTqH63TEkZltRCE20vJ0x5757tQW8j_L_rZ3I%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:15:45 (9251) [INFO] Trying other mirror. * 2024-12-25 02:16:00 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1MDMyMzkxOjE3MzUyOTE1OTE6MRdaYfgsFF6GCnUtHWbF28G9hC-ttfVg76eva8VRzSO65XGkxZzV-fNgwr6DHQQETmJRycRGNCv798AkqHx_kUhI344SfymR0gyrs4rSKYHNmG7bUeYnJD5DHuii5q6d5BBLQAZuNo4BpkaZz41I9-U4j5xK736p9EmitLNkXLTlHkONpf8P-9gbJP-TGGwIhDrEh1Bj_yA1FGIMQ_uxtuWB7rO4xNzQmsoDjaDRCwbiX40XbqetXKU2cthyNIyp5Qjyo7b2FcKMUAQXt5sudcVfwGL3g26lwypxos6vnVyqw-gcwAXG2J83s3KaJ8DpZJL8ivf-v7eN2Boal5Gn_H2mQW_cmPSviUg48qrL3LPczWi6HtHWmfF_B6X7FAbnE5VZ2IjGc9LneTVduOVHVdAx2EQ3VTt4iFgi5QPQBlZQQuJvXPMipzc3Bjya3JBSDN66An0LZDQzwdOKf4r7zG246s-HvCylYrMn_KVgRH8Bt3GdirC-EkS0xEzIHehFsjbxANjnjf-PXzmdELgdkTLVjuobCSu2WJm-yHefz49rg4wz8ODY0n3zKMdoYDOrT5LCtqigQbovNu6qiXzxRj_wmaBFpg07hhDktExtAbU-P_TsD3mf2lkCX7CTTaXbInaxG-sTqH63TEkZltRCE20vJ0x5757tQW8j_L_rZ3I%3D/ea-php/7/updates/x86_64/repodata/57a575bcda54fea8c85463fdeb7da3862ed24d81b6ec1f09f8eada3276760fba-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:16:00 (9251) [INFO] Trying other mirror. * 2024-12-25 02:16:16 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:16:16 (9251) [INFO] Trying other mirror. * 2024-12-25 02:16:31 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:16:31 (9251) [INFO] Trying other mirror. * 2024-12-25 02:16:47 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:16:47 (9251) [INFO] Trying other mirror. * 2024-12-25 02:17:03 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:17:03 (9251) [INFO] Trying other mirror. * 2024-12-25 02:17:18 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:17:18 (9251) [INFO] Trying other mirror. * 2024-12-25 02:17:34 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:17:34 (9251) [INFO] Trying other mirror. * 2024-12-25 02:17:50 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:17:50 (9251) [INFO] Trying other mirror. * 2024-12-25 02:18:05 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:18:05 (9251) [INFO] Trying other mirror. * 2024-12-25 02:18:36 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:18:36 (9251) [INFO] Trying other mirror. * 2024-12-25 02:18:36 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-25 02:18:36 (9251) [INFO] Trying other mirror. * 2024-12-25 02:18:51 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/wp-toolkit/repodata/48342a99b2f6d6b8817cf525b46227649da53e4dd538bed4da6b6959df8fd0c9-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:18:51 (9251) [INFO] Trying other mirror. * 2024-12-25 02:19:06 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-25 02:19:06 (9251) [INFO] Trying other mirror. * 2024-12-25 02:19:07 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:19:07 (9251) [INFO] Trying other mirror. * 2024-12-25 02:19:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:19:37 (9251) [INFO] Trying other mirror. * 2024-12-25 02:19:38 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:19:38 (9251) [INFO] Trying other mirror. * 2024-12-25 02:20:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:20:07 (9251) [INFO] Trying other mirror. * 2024-12-25 02:20:07 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:20:07 (9251) [INFO] Trying other mirror. * 2024-12-25 02:20:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-25 02:20:38 (9251) [INFO] Trying other mirror. * 2024-12-25 02:20:54 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:20:54 (9251) [INFO] Trying other mirror. * 2024-12-25 02:21:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-25 02:21:08 (9251) [INFO] Trying other mirror. * 2024-12-25 02:21:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-25 02:21:09 (9251) [INFO] Trying other mirror. * 2024-12-25 02:21:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:21:38 (9251) [INFO] Trying other mirror. * 2024-12-25 02:21:55 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:21:55 (9251) [INFO] Trying other mirror. * 2024-12-25 02:22:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-25 02:22:09 (9251) [INFO] Trying other mirror. * 2024-12-25 02:22:37 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:22:37 (9251) [INFO] Trying other mirror. * 2024-12-25 02:22:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:22:39 (9251) [INFO] Trying other mirror. * 2024-12-25 02:22:40 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-25 02:22:40 (9251) [INFO] Trying other mirror. * 2024-12-25 02:22:40 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:22:40 (9251) [INFO] Trying other mirror. * 2024-12-25 02:23:10 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-25 02:23:10 (9251) [INFO] Trying other mirror. * 2024-12-25 02:23:26 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-25 02:23:26 (9251) [INFO] Trying other mirror. * 2024-12-26 01:55:22 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-26 01:59:22 (10313) [INFO] Script is up to date. * 2024-12-26 02:03:26 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-26 02:03:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-26 02:03:26 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-26 02:03:26 (9238) [INFO] * 2024-12-26 02:03:29 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-26 02:03:29 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-26 02:03:29 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-26 02:03:29 (9238) [INFO] * 2024-12-26 02:03:41 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-26 02:03:44 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-26 02:03:44 (9238) [INFO] * 2024-12-26 02:03:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 02:03:45 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-26 02:04:15 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-26 02:04:15 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-26 02:04:15 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-26 02:04:15 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-26 02:07:02 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-26 02:07:02 (9251) [INFO] Trying other mirror. * 2024-12-26 02:07:19 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-26 02:07:19 (9251) [INFO] Trying other mirror. * 2024-12-26 02:07:35 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-26 02:07:35 (9251) [INFO] Trying other mirror. * 2024-12-26 02:07:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-26 02:07:49 (9251) [INFO] Trying other mirror. * 2024-12-26 02:07:51 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-26 02:07:51 (9251) [INFO] Trying other mirror. * 2024-12-26 02:08:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-26 02:08:21 (9251) [INFO] Trying other mirror. * 2024-12-26 02:09:02 (9251) [INFO] Metadata Cache Created * 2024-12-26 02:09:02 (9268) [INFO] * 2024-12-26 02:09:02 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-26 02:09:02 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-26 02:09:02 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-26 02:09:02 (9238) [INFO] * 2024-12-26 02:09:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 02:09:03 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-26 02:09:03 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-26 02:09:03 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-26 02:09:03 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-26 02:09:03 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-26 02:09:03 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-26 02:09:03 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-26 02:09:03 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-26 02:09:03 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-26 02:09:03 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-26 02:09:03 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-26 02:09:03 (9268) [INFO] * 2024-12-26 02:09:03 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-26 02:09:03 (9238) [INFO] * 2024-12-26 02:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 02:09:04 (9251) [INFO] Determining fastest mirrors * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] One of the configured repositories failed (Unknown), * 2024-12-26 02:09:35 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-26 02:09:35 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-26 02:09:35 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-26 02:09:35 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-26 02:09:35 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-26 02:09:35 (9251) [INFO] yum --disablerepo= ... * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-26 02:09:35 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-26 02:09:35 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] yum-config-manager --disable * 2024-12-26 02:09:35 (9251) [INFO] or * 2024-12-26 02:09:35 (9251) [INFO] subscription-manager repos --disable= * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-26 02:09:35 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-26 02:09:35 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-26 02:09:35 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-26 02:09:35 (9251) [INFO] compromise: * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2024-12-26 02:09:35 (9251) [INFO] * 2024-12-26 02:09:35 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2024-12-26 02:09:35 (9268) [INFO] * 2024-12-26 02:09:35 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-26 02:09:35 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2024-12-26 02:09:36 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-26 02:09:36 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-26 02:09:36 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-26 02:09:36 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-26 02:09:36 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-26 02:09:42 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dCYGBXk1VL/ea_profile.json * 2024-12-26 02:17:21 (8385) [INFO] Backed up EA4 profile to /tmp/dCYGBXk1VL/ea_profile.json * 2024-12-26 02:17:22 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-26 02:17:56 (627) [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-12-26 02:17:56 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-27 01:54:55 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-27 01:58:55 (10313) [INFO] Script is up to date. * 2024-12-27 02:02:59 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-27 02:02:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-27 02:02:59 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-27 02:02:59 (9238) [INFO] * 2024-12-27 02:03:03 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-27 02:03:03 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-27 02:03:03 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-27 02:03:03 (9238) [INFO] * 2024-12-27 02:03:13 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-27 02:03:17 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-27 02:03:17 (9238) [INFO] * 2024-12-27 02:03:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 02:03:18 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-27 02:03:48 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-27 02:03:48 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-27 02:03:48 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-27 02:03:48 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-27 02:06:34 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-27 02:06:34 (9251) [INFO] Trying other mirror. * 2024-12-27 02:06:50 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:06:50 (9251) [INFO] Trying other mirror. * 2024-12-27 02:07:20 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:07:20 (9251) [INFO] Trying other mirror. * 2024-12-27 02:07:23 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:07:23 (9251) [INFO] Trying other mirror. * 2024-12-27 02:07:33 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:07:33 (9251) [INFO] Trying other mirror. * 2024-12-27 02:07:51 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-27 02:07:51 (9251) [INFO] Trying other mirror. * 2024-12-27 02:08:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-27 02:08:04 (9251) [INFO] Trying other mirror. * 2024-12-27 02:08:21 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:08:21 (9251) [INFO] Trying other mirror. * 2024-12-27 02:08:35 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-27 02:08:35 (9251) [INFO] Trying other mirror. * 2024-12-27 02:09:06 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-27 02:09:06 (9251) [INFO] Trying other mirror. * 2024-12-27 02:09:37 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-27 02:09:37 (9251) [INFO] Trying other mirror. * 2024-12-27 02:10:08 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:10:08 (9251) [INFO] Trying other mirror. * 2024-12-27 02:10:38 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:10:38 (9251) [INFO] Trying other mirror. * 2024-12-27 02:11:17 (9251) [INFO] Metadata Cache Created * 2024-12-27 02:11:17 (9268) [INFO] * 2024-12-27 02:11:17 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-27 02:11:17 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-27 02:11:17 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-27 02:11:17 (9238) [INFO] * 2024-12-27 02:11:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 02:11:18 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-27 02:11:18 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-27 02:11:18 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-27 02:11:18 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-27 02:11:18 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-27 02:11:18 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-27 02:11:18 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-27 02:11:18 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-27 02:11:18 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-27 02:11:19 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-27 02:11:19 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-27 02:11:19 (9268) [INFO] * 2024-12-27 02:11:19 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-27 02:11:19 (9238) [INFO] * 2024-12-27 02:11:19 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 02:11:20 (9251) [INFO] Determining fastest mirrors * 2024-12-27 02:11:53 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-27 02:11:53 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-27 02:11:53 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-27 02:11:53 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-27 02:14:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-27 02:14:56 (9251) [INFO] Trying other mirror. * 2024-12-27 02:14:56 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:14:56 (9251) [INFO] Trying other mirror. * 2024-12-27 02:15:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-27 02:15:26 (9251) [INFO] Trying other mirror. * 2024-12-27 02:15:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-27 02:15:57 (9251) [INFO] Trying other mirror. * 2024-12-27 02:17:37 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2024-12-27 02:17:37 (9251) [INFO] Trying other mirror. * 2024-12-27 02:20:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:20:55 (9251) [INFO] Trying other mirror. * 2024-12-27 02:20:55 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-27 02:20:55 (9251) [INFO] Trying other mirror. * 2024-12-27 02:21:26 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:21:26 (9251) [INFO] Trying other mirror. * 2024-12-27 02:21:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-27 02:21:57 (9251) [INFO] Trying other mirror. * 2024-12-27 02:22:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-27 02:22:27 (9251) [INFO] Trying other mirror. * 2024-12-27 02:23:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:23:28 (9251) [INFO] Trying other mirror. * 2024-12-27 02:23:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-27 02:23:29 (9251) [INFO] Trying other mirror. * 2024-12-27 02:23:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-27 02:23:59 (9251) [INFO] Trying other mirror. * 2024-12-27 02:24:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-27 02:24:30 (9251) [INFO] Trying other mirror. * 2024-12-28 01:56:10 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-28 02:00:10 (10313) [INFO] Script is up to date. * 2024-12-28 02:04:13 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-28 02:04:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-28 02:04:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-28 02:04:14 (9238) [INFO] * 2024-12-28 02:04:17 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-28 02:04:17 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-28 02:04:17 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-28 02:04:17 (9238) [INFO] * 2024-12-28 02:04:27 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-28 02:04:31 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-28 02:04:31 (9238) [INFO] * 2024-12-28 02:04:31 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 02:04:31 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-28 02:05:01 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-28 02:05:01 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-28 02:05:01 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-28 02:05:01 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-28 02:07:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:07:47 (9251) [INFO] Trying other mirror. * 2024-12-28 02:08:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:08:04 (9251) [INFO] Trying other mirror. * 2024-12-28 02:08:36 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:08:36 (9251) [INFO] Trying other mirror. * 2024-12-28 02:09:20 (9251) [INFO] Metadata Cache Created * 2024-12-28 02:09:20 (9268) [INFO] * 2024-12-28 02:09:20 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-28 02:09:20 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-28 02:09:20 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-28 02:09:20 (9238) [INFO] * 2024-12-28 02:09:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 02:09:21 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-28 02:09:21 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-28 02:09:21 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-28 02:09:21 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-28 02:09:21 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-28 02:09:21 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-28 02:09:21 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-28 02:09:21 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-28 02:09:21 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-28 02:09:22 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-28 02:09:22 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-28 02:09:22 (9268) [INFO] * 2024-12-28 02:09:22 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-28 02:09:22 (9238) [INFO] * 2024-12-28 02:09:22 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 02:09:23 (9251) [INFO] Determining fastest mirrors * 2024-12-28 02:09:56 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-28 02:09:56 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-28 02:09:56 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-28 02:09:56 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-28 02:10:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-28 02:10:42 (9251) [INFO] Trying other mirror. * 2024-12-28 02:11:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-28 02:11:13 (9251) [INFO] Trying other mirror. * 2024-12-28 02:14:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-28 02:14:00 (9251) [INFO] Trying other mirror. * 2024-12-28 02:14:00 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:14:00 (9251) [INFO] Trying other mirror. * 2024-12-28 02:14:31 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-28 02:14:31 (9251) [INFO] Trying other mirror. * 2024-12-28 02:16:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:16:40 (9251) [INFO] Trying other mirror. * 2024-12-28 02:19:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:19:29 (9251) [INFO] Trying other mirror. * 2024-12-28 02:19:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-28 02:19:59 (9251) [INFO] Trying other mirror. * 2024-12-28 02:21:00 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:21:00 (9251) [INFO] Trying other mirror. * 2024-12-28 02:21:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:21:00 (9251) [INFO] Trying other mirror. * 2024-12-28 02:21:31 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-28 02:21:31 (9251) [INFO] Trying other mirror. * 2024-12-28 02:22:50 (9251) [INFO] Metadata Cache Created * 2024-12-28 02:22:50 (9268) [INFO] * 2024-12-28 02:22:50 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-28 02:22:50 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-28 02:22:51 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-28 02:22:51 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-28 02:22:51 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-28 02:22:51 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-28 02:22:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-28 02:22:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Lvf9_sBdww/ea_profile.json * 2024-12-28 02:23:00 (8385) [INFO] Backed up EA4 profile to /tmp/Lvf9_sBdww/ea_profile.json * 2024-12-28 02:23:01 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-28 02:23:35 (627) [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-12-28 02:23:35 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-29 01:56:18 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-29 02:00:18 (10313) [INFO] Script is up to date. * 2024-12-29 02:04:20 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-29 02:04:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-29 02:04:21 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-29 02:04:21 (9238) [INFO] * 2024-12-29 02:04:24 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-29 02:04:24 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-29 02:04:24 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-29 02:04:24 (9238) [INFO] * 2024-12-29 02:04:35 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-29 02:04:39 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-29 02:04:39 (9238) [INFO] * 2024-12-29 02:04:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 02:04:39 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-29 02:05:09 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-29 02:05:09 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-29 02:05:09 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-29 02:05:09 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-29 02:07:55 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:07:55 (9251) [INFO] Trying other mirror. * 2024-12-29 02:08:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:08:12 (9251) [INFO] Trying other mirror. * 2024-12-29 02:08:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:08:29 (9251) [INFO] Trying other mirror. * 2024-12-29 02:08:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:08:42 (9251) [INFO] Trying other mirror. * 2024-12-29 02:08:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:08:43 (9251) [INFO] Trying other mirror. * 2024-12-29 02:08:59 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:08:59 (9251) [INFO] Trying other mirror. * 2024-12-29 02:09:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:09:13 (9251) [INFO] Trying other mirror. * 2024-12-29 02:09:13 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:09:13 (9251) [INFO] Trying other mirror. * 2024-12-29 02:09:43 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:09:43 (9251) [INFO] Trying other mirror. * 2024-12-29 02:10:25 (9251) [INFO] Metadata Cache Created * 2024-12-29 02:10:25 (9268) [INFO] * 2024-12-29 02:10:25 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-29 02:10:25 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-29 02:10:25 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-29 02:10:25 (9238) [INFO] * 2024-12-29 02:10:26 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 02:10:26 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-29 02:10:26 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-29 02:10:26 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-29 02:10:26 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-29 02:10:26 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-29 02:10:26 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-29 02:10:26 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-29 02:10:26 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-29 02:10:26 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-29 02:10:27 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-29 02:10:27 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-29 02:10:27 (9268) [INFO] * 2024-12-29 02:10:27 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-29 02:10:27 (9238) [INFO] * 2024-12-29 02:10:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 02:10:28 (9251) [INFO] Determining fastest mirrors * 2024-12-29 02:10:59 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-29 02:10:59 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-29 02:10:59 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-29 02:10:59 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-29 02:14:02 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:14:02 (9251) [INFO] Trying other mirror. * 2024-12-29 02:14:02 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-29 02:14:02 (9251) [INFO] Trying other mirror. * 2024-12-29 02:16:41 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:16:41 (9251) [INFO] Trying other mirror. * 2024-12-29 02:19:30 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:19:30 (9251) [INFO] Trying other mirror. * 2024-12-29 02:20:01 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-29 02:20:01 (9251) [INFO] Trying other mirror. * 2024-12-29 02:21:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-29 02:21:03 (9251) [INFO] Trying other mirror. * 2024-12-29 02:21:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-29 02:21:03 (9251) [INFO] Trying other mirror. * 2024-12-29 02:21:33 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:21:33 (9251) [INFO] Trying other mirror. * 2024-12-29 02:21:33 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:21:33 (9251) [INFO] Trying other mirror. * 2024-12-29 02:22:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2024-12-29 02:22:04 (9251) [INFO] Trying other mirror. * 2024-12-29 02:22:34 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-29 02:22:34 (9251) [INFO] Trying other mirror. * 2024-12-29 02:22:34 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-29 02:22:34 (9251) [INFO] Trying other mirror. * 2024-12-29 02:23:36 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-29 02:23:36 (9251) [INFO] Trying other mirror. * 2024-12-29 02:24:06 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-29 02:24:06 (9251) [INFO] Trying other mirror. * 2024-12-29 02:24:37 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-29 02:24:37 (9251) [INFO] Trying other mirror. * 2024-12-29 02:25:51 (9251) [INFO] Metadata Cache Created * 2024-12-29 02:25:51 (9268) [INFO] * 2024-12-29 02:25:51 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-29 02:25:51 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2024-12-29 02:25:51 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2024-12-29 02:25:51 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2024-12-29 02:25:51 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2024-12-29 02:25:51 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2024-12-29 02:25:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-29 02:25:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NcFVVeqvP8/ea_profile.json * 2024-12-29 02:26:00 (8385) [INFO] Backed up EA4 profile to /tmp/NcFVVeqvP8/ea_profile.json * 2024-12-29 02:26:01 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2024-12-30 01:55:48 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-30 01:59:48 (10313) [INFO] Script is up to date. * 2024-12-30 02:03:51 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-30 02:03:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-30 02:03:51 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-30 02:03:51 (9238) [INFO] * 2024-12-30 02:03:54 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-30 02:03:54 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-30 02:03:54 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-30 02:03:54 (9238) [INFO] * 2024-12-30 02:04:05 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-30 02:04:08 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-30 02:04:08 (9238) [INFO] * 2024-12-30 02:04:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 02:04:09 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-30 02:04:39 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-30 02:04:39 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-30 02:04:39 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-30 02:04:39 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-30 02:05:25 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2024-12-30 02:05:25 (9251) [INFO] Trying other mirror. * 2024-12-30 02:07:55 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-30 02:07:55 (9251) [INFO] Trying other mirror. * 2024-12-30 02:08:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30660 milliseconds') * 2024-12-30 02:08:12 (9251) [INFO] Trying other mirror. * 2024-12-30 02:08:28 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:08:28 (9251) [INFO] Trying other mirror. * 2024-12-30 02:08:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:08:42 (9251) [INFO] Trying other mirror. * 2024-12-30 02:08:45 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-30 02:08:45 (9251) [INFO] Trying other mirror. * 2024-12-30 02:09:15 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-30 02:09:15 (9251) [INFO] Trying other mirror. * 2024-12-30 02:09:46 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:09:46 (9251) [INFO] Trying other mirror. * 2024-12-30 02:10:29 (9251) [INFO] Metadata Cache Created * 2024-12-30 02:10:29 (9268) [INFO] * 2024-12-30 02:10:29 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30660 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2024-12-30 02:10:29 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-30 02:10:29 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-30 02:10:29 (9238) [INFO] * 2024-12-30 02:10:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 02:10:30 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-30 02:10:30 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-30 02:10:30 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-30 02:10:30 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-30 02:10:30 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-30 02:10:30 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-30 02:10:30 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-30 02:10:30 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-30 02:10:30 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-30 02:10:31 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-30 02:10:31 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-30 02:10:31 (9268) [INFO] * 2024-12-30 02:10:31 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-30 02:10:31 (9238) [INFO] * 2024-12-30 02:10:31 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 02:10:31 (9251) [INFO] Determining fastest mirrors * 2024-12-30 02:11:05 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-30 02:11:05 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-30 02:11:05 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-30 02:11:05 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-30 02:14:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:14:08 (9251) [INFO] Trying other mirror. * 2024-12-30 02:14:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-30 02:14:08 (9251) [INFO] Trying other mirror. * 2024-12-30 02:14:39 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-30 02:14:39 (9251) [INFO] Trying other mirror. * 2024-12-30 02:15:09 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2024-12-30 02:15:09 (9251) [INFO] Trying other mirror. * 2024-12-30 02:16:48 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:16:48 (9251) [INFO] Trying other mirror. * 2024-12-30 02:16:48 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30720 milliseconds') * 2024-12-30 02:16:48 (9251) [INFO] Trying other mirror. * 2024-12-30 02:17:19 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-30 02:17:19 (9251) [INFO] Trying other mirror. * 2024-12-30 02:20:07 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:20:07 (9251) [INFO] Trying other mirror. * 2024-12-30 02:20:07 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') * 2024-12-30 02:20:07 (9251) [INFO] Trying other mirror. * 2024-12-30 02:21:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:21:09 (9251) [INFO] Trying other mirror. * 2024-12-30 02:22:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-30 02:22:09 (9251) [INFO] Trying other mirror. * 2024-12-30 02:22:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:22:39 (9251) [INFO] Trying other mirror. * 2024-12-30 02:22:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:22:40 (9251) [INFO] Trying other mirror. * 2024-12-30 02:23:41 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-30 02:23:41 (9251) [INFO] Trying other mirror. * 2024-12-30 02:24:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2024-12-30 02:24:12 (9251) [INFO] Trying other mirror. * 2024-12-30 02:24:42 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-30 02:24:42 (9251) [INFO] Trying other mirror. * 2024-12-30 02:25:13 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-30 02:25:13 (9251) [INFO] Trying other mirror. * 2024-12-31 01:53:58 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-31 01:57:58 (10313) [INFO] Script is up to date. * 2024-12-31 02:02:02 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2024-12-31 02:02:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-12-31 02:02:02 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-31 02:02:02 (9238) [INFO] * 2024-12-31 02:02:06 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2024-12-31 02:02:06 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-31 02:02:06 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-31 02:02:06 (9238) [INFO] * 2024-12-31 02:02:19 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2024-12-31 02:02:22 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-31 02:02:22 (9238) [INFO] * 2024-12-31 02:02:22 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 02:02:22 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-31 02:02:52 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-31 02:02:52 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-31 02:02:52 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-31 02:02:52 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-31 02:05:38 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:05:38 (9251) [INFO] Trying other mirror. * 2024-12-31 02:05:55 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:05:55 (9251) [INFO] Trying other mirror. * 2024-12-31 02:06:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2024-12-31 02:06:12 (9251) [INFO] Trying other mirror. * 2024-12-31 02:06:24 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:06:24 (9251) [INFO] Trying other mirror. * 2024-12-31 02:06:25 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-31 02:06:25 (9251) [INFO] Trying other mirror. * 2024-12-31 02:06:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-31 02:06:54 (9251) [INFO] Trying other mirror. * 2024-12-31 02:07:25 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2024-12-31 02:07:25 (9251) [INFO] Trying other mirror. * 2024-12-31 02:08:05 (9251) [INFO] Metadata Cache Created * 2024-12-31 02:08:05 (9268) [INFO] * 2024-12-31 02:08:05 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2024-12-31 02:08:05 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-31 02:08:05 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-31 02:08:05 (9238) [INFO] * 2024-12-31 02:08:06 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 02:08:06 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2024-12-31 02:08:06 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-31 02:08:06 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-31 02:08:06 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2024-12-31 02:08:06 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2024-12-31 02:08:06 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-31 02:08:06 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-31 02:08:06 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2024-12-31 02:08:06 (9251) [INFO] : wp-toolkit-thirdparties * 2024-12-31 02:08:07 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-31 02:08:07 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2024-12-31 02:08:07 (9268) [INFO] * 2024-12-31 02:08:07 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-31 02:08:07 (9238) [INFO] * 2024-12-31 02:08:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 02:08:08 (9251) [INFO] Determining fastest mirrors * 2024-12-31 02:08:40 (9251) [INFO] * EA4: 107.178.98.171 * 2024-12-31 02:08:40 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2024-12-31 02:08:40 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2024-12-31 02:08:40 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2024-12-31 02:09:26 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-31 02:09:26 (9251) [INFO] Trying other mirror. * 2024-12-31 02:12:13 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-31 02:12:13 (9251) [INFO] Trying other mirror. * 2024-12-31 02:12:14 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2024-12-31 02:12:14 (9251) [INFO] Trying other mirror. * 2024-12-31 02:13:31 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2024-12-31 02:13:31 (9251) [INFO] Trying other mirror. * 2024-12-31 02:13:47 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:13:47 (9251) [INFO] Trying other mirror. * 2024-12-31 02:14:03 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:14:03 (9251) [INFO] Trying other mirror. * 2024-12-31 02:14:18 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:14:18 (9251) [INFO] Trying other mirror. * 2024-12-31 02:14:21 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:14:21 (9251) [INFO] Trying other mirror. * 2024-12-31 02:14:48 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e9d5398a26bc9639935a58dd568a61a673e2d348137b6e2030004575cfdc712f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:14:48 (9251) [INFO] Trying other mirror. * 2024-12-31 02:14:52 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-31 02:14:52 (9251) [INFO] Trying other mirror. * 2024-12-31 02:15:04 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1NDk5MDg3OjE3MzU3NTgyODc6DzyT5Pd0k1cHFHnUvhOEFvwqKUTaNQ295iIB9tCT7nInPKRaARCFOOTnVx-yK8bWmOz3RQxul-617LAKwJ3dfvZroYuSI_9MqYhbTMtFyZ8orqZvOVqMCVZndPGTqMQjUw_lZxT8jMAS9InQ88z3uLnN_vGUWqEt5umxGPrXDbFZyvnx_km1ZqS7izp9UTiY600soLeB_vlMbdzBuHWUWvKTmzI3HaWVRWmalfhtCfFlT6k-VxMECCTj69RE2QlOMnAchxgzLi5hEjw2CdRIJzNkT7T2AACDH7cRiG_DrasYRYfd5kvzXk9H8gfyxTnFjYXPdhFrTa9t_E7pW-IQ818yYAHa1By5f_xJUPDEeZPf6uRX2VCc6XJTYjoCOPENv8HqvFcZmNkA08hqnY8wlbFz9KAQBgev9tPQPXZ24-4U4YVTeq4F6WbpxTCGslNJBTgGN7SOjT_HA7jYnH-90IrQdIqIHKgGKyNJPTykvwn-Et9yLOyCt5CLVzEZ9nUxUKHmeunKIEmd9RJ8PockREf436NZhd3Dq_21SVJPS69CeJM8avIRCIcXV-VlwHlZrbqYh5hQfs7JsSgP87uRSX7NXCsnIFKgU6BkJv_Zu0hibQ-PtoSklO5F8Dt85A1tEpynS-Yq73LYGyYP_mSwVqyZeuCdoSzo5BBKqyiVlDY%3D/ea-php/7/updates/x86_64/repodata/026bee58294c9c16948c59086436d41a8b839452ce155dc56fcb024e06c3ee13-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:15:04 (9251) [INFO] Trying other mirror. * 2024-12-31 02:15:19 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:15:19 (9251) [INFO] Trying other mirror. * 2024-12-31 02:15:35 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:15:35 (9251) [INFO] Trying other mirror. * 2024-12-31 02:15:51 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:15:51 (9251) [INFO] Trying other mirror. * 2024-12-31 02:16:06 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:16:06 (9251) [INFO] Trying other mirror. * 2024-12-31 02:16:22 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:16:22 (9251) [INFO] Trying other mirror. * 2024-12-31 02:16:38 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:16:38 (9251) [INFO] Trying other mirror. * 2024-12-31 02:16:53 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:16:53 (9251) [INFO] Trying other mirror. * 2024-12-31 02:17:09 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:17:09 (9251) [INFO] Trying other mirror. * 2024-12-31 02:17:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:17:39 (9251) [INFO] Trying other mirror. * 2024-12-31 02:17:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:17:39 (9251) [INFO] Trying other mirror. * 2024-12-31 02:17:55 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/wp-toolkit/repodata/48342a99b2f6d6b8817cf525b46227649da53e4dd538bed4da6b6959df8fd0c9-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:17:55 (9251) [INFO] Trying other mirror. * 2024-12-31 02:18:10 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-31 02:18:10 (9251) [INFO] Trying other mirror. * 2024-12-31 02:18:10 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:18:10 (9251) [INFO] Trying other mirror. * 2024-12-31 02:18:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-31 02:18:41 (9251) [INFO] Trying other mirror. * 2024-12-31 02:18:41 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:18:41 (9251) [INFO] Trying other mirror. * 2024-12-31 02:19:11 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2024-12-31 02:19:11 (9251) [INFO] Trying other mirror. * 2024-12-31 02:19:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-31 02:19:12 (9251) [INFO] Trying other mirror. * 2024-12-31 02:19:42 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:19:42 (9251) [INFO] Trying other mirror. * 2024-12-31 02:19:42 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:19:42 (9251) [INFO] Trying other mirror. * 2024-12-31 02:20:12 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-31 02:20:12 (9251) [INFO] Trying other mirror. * 2024-12-31 02:20:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:20:12 (9251) [INFO] Trying other mirror. * 2024-12-31 02:20:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2024-12-31 02:20:12 (9251) [INFO] Trying other mirror. * 2024-12-31 02:20:43 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30915 milliseconds') * 2024-12-31 02:20:43 (9251) [INFO] Trying other mirror. * 2024-12-31 02:21:00 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:21:00 (9251) [INFO] Trying other mirror. * 2024-12-31 02:21:14 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2024-12-31 02:21:14 (9251) [INFO] Trying other mirror. * 2024-12-31 02:21:14 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2024-12-31 02:21:14 (9251) [INFO] Trying other mirror. * 2024-12-31 02:21:14 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-31 02:21:14 (9251) [INFO] Trying other mirror. * 2024-12-31 02:21:45 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-31 02:21:45 (9251) [INFO] Trying other mirror. * 2024-12-31 02:22:01 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:22:01 (9251) [INFO] Trying other mirror. * 2024-12-31 02:22:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2024-12-31 02:22:15 (9251) [INFO] Trying other mirror. * 2024-12-31 02:22:15 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2024-12-31 02:22:15 (9251) [INFO] Trying other mirror. * 2024-12-31 02:22:16 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2024-12-31 02:22:16 (9251) [INFO] Trying other mirror. * 2024-12-31 02:22:46 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2024-12-31 02:22:46 (9251) [INFO] Trying other mirror. * 2024-12-31 02:23:13 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:23:13 (9251) [INFO] Trying other mirror. * 2024-12-31 02:23:17 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2024-12-31 02:23:17 (9251) [INFO] Trying other mirror. * 2024-12-31 02:23:47 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30006 milliseconds') * 2024-12-31 02:23:47 (9251) [INFO] Trying other mirror. * 2024-12-31 02:23:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2024-12-31 02:23:47 (9251) [INFO] Trying other mirror. * 2024-12-31 02:23:47 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2024-12-31 02:23:47 (9251) [INFO] Trying other mirror. * 2025-01-01 01:53:53 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-01 01:57:53 (10313) [INFO] Script is up to date. * 2025-01-01 02:01:56 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-01 02:01:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-01 02:01:56 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-01 02:01:56 (9238) [INFO] * 2025-01-01 02:02:00 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-01 02:02:00 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-01 02:02:00 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-01 02:02:00 (9238) [INFO] * 2025-01-01 02:02:10 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-01 02:02:13 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-01 02:02:13 (9238) [INFO] * 2025-01-01 02:02:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 02:02:14 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-01 02:02:44 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-01 02:02:44 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-01 02:02:44 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-01 02:02:44 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-01 02:05:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-01 02:05:30 (9251) [INFO] Trying other mirror. * 2025-01-01 02:05:46 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:05:46 (9251) [INFO] Trying other mirror. * 2025-01-01 02:06:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:06:03 (9251) [INFO] Trying other mirror. * 2025-01-01 02:06:16 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:06:16 (9251) [INFO] Trying other mirror. * 2025-01-01 02:06:34 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:06:34 (9251) [INFO] Trying other mirror. * 2025-01-01 02:06:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:06:46 (9251) [INFO] Trying other mirror. * 2025-01-01 02:07:04 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:07:04 (9251) [INFO] Trying other mirror. * 2025-01-01 02:07:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-01 02:07:17 (9251) [INFO] Trying other mirror. * 2025-01-01 02:07:48 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:07:48 (9251) [INFO] Trying other mirror. * 2025-01-01 02:08:18 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:08:18 (9251) [INFO] Trying other mirror. * 2025-01-01 02:08:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-01 02:08:49 (9251) [INFO] Trying other mirror. * 2025-01-01 02:09:33 (9251) [INFO] Metadata Cache Created * 2025-01-01 02:09:33 (9268) [INFO] * 2025-01-01 02:09:33 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-01-01 02:09:33 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-01 02:09:33 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-01 02:09:33 (9238) [INFO] * 2025-01-01 02:09:33 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 02:09:34 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-01 02:09:34 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-01 02:09:34 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-01 02:09:34 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-01 02:09:34 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-01 02:09:34 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-01 02:09:34 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-01 02:09:34 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-01 02:09:34 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-01 02:09:35 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-01 02:09:35 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-01 02:09:35 (9268) [INFO] * 2025-01-01 02:09:35 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-01 02:09:35 (9238) [INFO] * 2025-01-01 02:09:35 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 02:09:35 (9251) [INFO] Determining fastest mirrors * 2025-01-01 02:10:08 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-01 02:10:08 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-01 02:10:08 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-01 02:10:08 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-01 02:13:10 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-01 02:13:10 (9251) [INFO] Trying other mirror. * 2025-01-01 02:13:10 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:13:10 (9251) [INFO] Trying other mirror. * 2025-01-01 02:13:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-01 02:13:41 (9251) [INFO] Trying other mirror. * 2025-01-01 02:15:51 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:15:51 (9251) [INFO] Trying other mirror. * 2025-01-01 02:18:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:18:39 (9251) [INFO] Trying other mirror. * 2025-01-01 02:19:41 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:19:41 (9251) [INFO] Trying other mirror. * 2025-01-01 02:19:42 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-01 02:19:42 (9251) [INFO] Trying other mirror. * 2025-01-01 02:20:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-01 02:20:12 (9251) [INFO] Trying other mirror. * 2025-01-01 02:20:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-01 02:20:12 (9251) [INFO] Trying other mirror. * 2025-01-01 02:20:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-01 02:20:43 (9251) [INFO] Trying other mirror. * 2025-01-01 02:21:59 (9251) [INFO] Metadata Cache Created * 2025-01-01 02:21:59 (9268) [INFO] * 2025-01-01 02:21: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-01 02:21:59 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-01 02:22:00 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-01 02:22:00 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-01 02:22:00 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-01 02:22:00 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-01 02:22:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-01 02:22:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7t6k__rQzQ/ea_profile.json * 2025-01-01 02:22:09 (8385) [INFO] Backed up EA4 profile to /tmp/7t6k__rQzQ/ea_profile.json * 2025-01-01 02:22:10 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-01 02:22:44 (627) [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. * 2025-01-01 02:22:44 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-02 01:53:19 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-02 01:57:20 (10313) [INFO] Script is up to date. * 2025-01-02 02:01:23 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-02 02:01:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-02 02:01:23 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-02 02:01:23 (9238) [INFO] * 2025-01-02 02:01:27 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-02 02:01:27 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-02 02:01:27 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-02 02:01:27 (9238) [INFO] * 2025-01-02 02:01:39 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-02 02:01:42 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-02 02:01:42 (9238) [INFO] * 2025-01-02 02:01:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 02:01:43 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-02 02:02:13 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-02 02:02:13 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-02 02:02:13 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-02 02:02:13 (9251) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-02 02:02:59 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') * 2025-01-02 02:02:59 (9251) [INFO] Trying other mirror. * 2025-01-02 02:03:30 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-02 02:03:30 (9251) [INFO] Trying other mirror. * 2025-01-02 02:06:01 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-02 02:06:01 (9251) [INFO] Trying other mirror. * 2025-01-02 02:06:17 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-02 02:06:17 (9251) [INFO] Trying other mirror. * 2025-01-02 02:06:34 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-02 02:06:34 (9251) [INFO] Trying other mirror. * 2025-01-02 02:06:48 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-02 02:06:48 (9251) [INFO] Trying other mirror. * 2025-01-02 02:06:49 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-02 02:06:49 (9251) [INFO] Trying other mirror. * 2025-01-02 02:07:05 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-02 02:07:05 (9251) [INFO] Trying other mirror. * 2025-01-02 02:07:47 (9251) [INFO] Metadata Cache Created * 2025-01-02 02:07:48 (9268) [INFO] * 2025-01-02 02:07:48 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2025-01-02 02:07:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-02 02:07:48 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-02 02:07:48 (9238) [INFO] * 2025-01-02 02:07:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 02:07:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-02 02:07:48 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-02 02:07:48 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-02 02:07:48 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-02 02:07:48 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-02 02:07:48 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-02 02:07:48 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-02 02:07:48 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-02 02:07:48 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-02 02:07:49 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-02 02:07:49 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-02 02:07:49 (9268) [INFO] * 2025-01-02 02:07:49 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-02 02:07:49 (9238) [INFO] * 2025-01-02 02:07:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 02:07:50 (9251) [INFO] Determining fastest mirrors * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-02 02:08:22 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-02 02:08:22 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-02 02:08:22 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-02 02:08:22 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-02 02:08:22 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-02 02:08:22 (9251) [INFO] yum --disablerepo= ... * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-02 02:08:22 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-02 02:08:22 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] yum-config-manager --disable * 2025-01-02 02:08:22 (9251) [INFO] or * 2025-01-02 02:08:22 (9251) [INFO] subscription-manager repos --disable= * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-02 02:08:22 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-02 02:08:22 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-02 02:08:22 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-02 02:08:22 (9251) [INFO] compromise: * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-02 02:08:22 (9251) [INFO] * 2025-01-02 02:08:22 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-02 02:08:22 (9268) [INFO] * 2025-01-02 02:08:22 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-02 02:08:22 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-02 02:08:23 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-02 02:08:23 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-02 02:08:23 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-02 02:08:23 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-02 02:08:23 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-02 02:08:29 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0iZo27LUxV/ea_profile.json * 2025-01-02 02:15:23 (8385) [INFO] Backed up EA4 profile to /tmp/0iZo27LUxV/ea_profile.json * 2025-01-02 02:15:24 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-02 02:15:58 (627) [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. * 2025-01-02 02:15:58 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-03 01:56:18 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-03 02:00:19 (10313) [INFO] Script is up to date. * 2025-01-03 02:04:21 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-03 02:04:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-03 02:04:21 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-03 02:04:21 (9238) [INFO] * 2025-01-03 02:04:25 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-03 02:04:25 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-03 02:04:25 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-03 02:04:25 (9238) [INFO] * 2025-01-03 02:04:38 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-03 02:04:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-03 02:04:41 (9238) [INFO] * 2025-01-03 02:04:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 02:04:41 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-03 02:05:11 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-03 02:05:11 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-03 02:05:11 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-03 02:05:11 (9251) [INFO] * epel: mirror.math.princeton.edu * 2025-01-03 02:07:59 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-03 02:07:59 (9251) [INFO] Trying other mirror. * 2025-01-03 02:08:15 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-03 02:08:15 (9251) [INFO] Trying other mirror. * 2025-01-03 02:08:32 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-03 02:08:32 (9251) [INFO] Trying other mirror. * 2025-01-03 02:08:45 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-03 02:08:45 (9251) [INFO] Trying other mirror. * 2025-01-03 02:08:46 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-03 02:08:46 (9251) [INFO] Trying other mirror. * 2025-01-03 02:09:15 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-03 02:09:15 (9251) [INFO] Trying other mirror. * 2025-01-03 02:09:58 (9251) [INFO] Metadata Cache Created * 2025-01-03 02:09:58 (9268) [INFO] * 2025-01-03 02:09:58 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. * 2025-01-03 02:09:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-03 02:09:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-03 02:09:58 (9238) [INFO] * 2025-01-03 02:09:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 02:09:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-03 02:09:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-03 02:09:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-03 02:09:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-03 02:09:58 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-03 02:09:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-03 02:09:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-03 02:09:58 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-03 02:09:58 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-03 02:09:59 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-03 02:09:59 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-03 02:09:59 (9268) [INFO] * 2025-01-03 02:09:59 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-03 02:09:59 (9238) [INFO] * 2025-01-03 02:10:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 02:10:00 (9251) [INFO] Determining fastest mirrors * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-03 02:10:30 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-03 02:10:30 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-03 02:10:30 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-03 02:10:30 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-03 02:10:30 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-03 02:10:30 (9251) [INFO] yum --disablerepo= ... * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-03 02:10:30 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-03 02:10:30 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] yum-config-manager --disable * 2025-01-03 02:10:30 (9251) [INFO] or * 2025-01-03 02:10:30 (9251) [INFO] subscription-manager repos --disable= * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-03 02:10:30 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-03 02:10:30 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-03 02:10:30 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-03 02:10:30 (9251) [INFO] compromise: * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-03 02:10:30 (9251) [INFO] * 2025-01-03 02:10:30 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-03 02:10:31 (9268) [INFO] * 2025-01-03 02:10:31 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-03 02:10:31 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-03 02:10:31 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-03 02:10:31 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-03 02:10:31 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-03 02:10:31 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-03 02:10:31 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-03 02:10:38 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4ISBxGBFDI/ea_profile.json * 2025-01-03 02:17:19 (8385) [INFO] Backed up EA4 profile to /tmp/4ISBxGBFDI/ea_profile.json * 2025-01-03 02:17:19 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-03 02:17:53 (627) [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. * 2025-01-03 02:17:53 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-04 01:46:40 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-04 01:50:40 (10313) [INFO] Script is up to date. * 2025-01-04 01:54:43 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-04 01:54:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-04 01:54:44 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-04 01:54:44 (9238) [INFO] * 2025-01-04 01:54:48 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-04 01:54:48 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-04 01:54:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-04 01:54:48 (9238) [INFO] * 2025-01-04 01:54:59 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-04 01:55:03 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-04 01:55:03 (9238) [INFO] * 2025-01-04 01:55:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 01:55:03 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-04 01:55:33 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-04 01:55:33 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-04 01:55:33 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-04 01:55:33 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-04 01:58:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 01:58:19 (9251) [INFO] Trying other mirror. * 2025-01-04 01:58:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-04 01:58:20 (9251) [INFO] Trying other mirror. * 2025-01-04 01:59:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 01:59:09 (9251) [INFO] Trying other mirror. * 2025-01-04 01:59:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 01:59:09 (9251) [INFO] Trying other mirror. * 2025-01-04 01:59:53 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-04 01:59:53 (9251) [INFO] Trying other mirror. * 2025-01-04 01:59:53 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-04 01:59:53 (9251) [INFO] Trying other mirror. * 2025-01-04 02:00:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:00:08 (9251) [INFO] Trying other mirror. * 2025-01-04 02:00:38 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:00:38 (9251) [INFO] Trying other mirror. * 2025-01-04 02:01:09 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-04 02:01:09 (9251) [INFO] Trying other mirror. * 2025-01-04 02:01:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-04 02:01:09 (9251) [INFO] Trying other mirror. * 2025-01-04 02:01:39 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:01:39 (9251) [INFO] Trying other mirror. * 2025-01-04 02:01:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-04 02:01:40 (9251) [INFO] Trying other mirror. * 2025-01-04 02:01:40 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-04 02:01:40 (9251) [INFO] Trying other mirror. * 2025-01-04 02:02:10 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:02:10 (9251) [INFO] Trying other mirror. * 2025-01-04 02:02:11 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-04 02:02:11 (9251) [INFO] Trying other mirror. * 2025-01-04 02:02:42 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-04 02:02:42 (9251) [INFO] Trying other mirror. * 2025-01-04 02:02:42 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-04 02:02:42 (9251) [INFO] Trying other mirror. * 2025-01-04 02:02:42 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-04 02:02:42 (9251) [INFO] Trying other mirror. * 2025-01-04 02:03:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:03:12 (9251) [INFO] Trying other mirror. * 2025-01-04 02:03:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:03:12 (9251) [INFO] Trying other mirror. * 2025-01-04 02:03:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:03:43 (9251) [INFO] Trying other mirror. * 2025-01-04 02:03:43 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2025-01-04 02:03:43 (9251) [INFO] Trying other mirror. * 2025-01-04 02:04:13 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:04:13 (9251) [INFO] Trying other mirror. * 2025-01-04 02:04:13 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-04 02:04:13 (9251) [INFO] Trying other mirror. * 2025-01-04 02:04:44 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-04 02:04:44 (9251) [INFO] Trying other mirror. * 2025-01-04 02:04:44 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-01-04 02:04:44 (9251) [INFO] Trying other mirror. * 2025-01-04 02:05:14 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:05:14 (9251) [INFO] Trying other mirror. * 2025-01-04 02:05:14 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-04 02:05:14 (9251) [INFO] Trying other mirror. * 2025-01-04 02:05:45 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-04 02:05:45 (9251) [INFO] Trying other mirror. * 2025-01-04 02:06:47 (9251) [INFO] Metadata Cache Created * 2025-01-04 02:06:47 (9268) [INFO] * 2025-01-04 02:06:47 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-04 02:06:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-04 02:06:47 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-04 02:06:47 (9238) [INFO] * 2025-01-04 02:06:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 02:06:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-04 02:06:48 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-04 02:06:48 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-04 02:06:48 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-04 02:06:48 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-04 02:06:48 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-04 02:06:48 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-04 02:06:48 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-04 02:06:48 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-04 02:06:48 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-04 02:06:48 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-04 02:06:48 (9268) [INFO] * 2025-01-04 02:06:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-04 02:06:48 (9238) [INFO] * 2025-01-04 02:06:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 02:06:49 (9251) [INFO] Determining fastest mirrors * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-04 02:07:21 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-04 02:07:21 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-04 02:07:21 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-04 02:07:21 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-04 02:07:21 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-04 02:07:21 (9251) [INFO] yum --disablerepo= ... * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-04 02:07:21 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-04 02:07:21 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] yum-config-manager --disable * 2025-01-04 02:07:21 (9251) [INFO] or * 2025-01-04 02:07:21 (9251) [INFO] subscription-manager repos --disable= * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-04 02:07:21 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-04 02:07:21 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-04 02:07:21 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-04 02:07:21 (9251) [INFO] compromise: * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-04 02:07:21 (9251) [INFO] * 2025-01-04 02:07:21 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-04 02:07:21 (9268) [INFO] * 2025-01-04 02:07:21 (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 02:07:21 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-04 02:07:22 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-04 02:07:22 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-04 02:07:22 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-04 02:07:22 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-04 02:07:22 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-04 02:07:27 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mZVJMcxKpP/ea_profile.json * 2025-01-05 01:47:07 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-05 01:51:08 (10313) [INFO] Script is up to date. * 2025-01-05 01:55:11 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-05 01:55:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-05 01:55:11 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-05 01:55:11 (9238) [INFO] * 2025-01-05 01:55:14 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-05 01:55:14 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-05 01:55:14 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-05 01:55:14 (9238) [INFO] * 2025-01-05 01:55:26 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-05 01:55:30 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-05 01:55:30 (9238) [INFO] * 2025-01-05 01:55:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 01:55:31 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-05 01:56:01 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-05 01:56:01 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-05 01:56:01 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-05 01:56:01 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-05 01:58:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-05 01:58:46 (9251) [INFO] Trying other mirror. * 2025-01-05 01:58:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 01:58:46 (9251) [INFO] Trying other mirror. * 2025-01-05 01:59:35 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 01:59:35 (9251) [INFO] Trying other mirror. * 2025-01-05 02:00:21 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:00:21 (9251) [INFO] Trying other mirror. * 2025-01-05 02:00:37 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-05 02:00:37 (9251) [INFO] Trying other mirror. * 2025-01-05 02:01:08 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:01:08 (9251) [INFO] Trying other mirror. * 2025-01-05 02:01:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:01:08 (9251) [INFO] Trying other mirror. * 2025-01-05 02:01:08 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-05 02:01:08 (9251) [INFO] Trying other mirror. * 2025-01-05 02:02:08 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:02:08 (9251) [INFO] Trying other mirror. * 2025-01-05 02:02:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-05 02:02:08 (9251) [INFO] Trying other mirror. * 2025-01-05 02:02:38 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:02:39 (9251) [INFO] Trying other mirror. * 2025-01-05 02:03:09 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-05 02:03:09 (9251) [INFO] Trying other mirror. * 2025-01-05 02:04:11 (9251) [INFO] Metadata Cache Created * 2025-01-05 02:04:11 (9268) [INFO] * 2025-01-05 02:04:11 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2025-01-05 02:04:11 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-05 02:04:11 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-05 02:04:11 (9238) [INFO] * 2025-01-05 02:04:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 02:04:12 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-05 02:04:12 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-05 02:04:12 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-05 02:04:12 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-05 02:04:12 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-05 02:04:12 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-05 02:04:12 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-05 02:04:12 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-05 02:04:12 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-05 02:04:13 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-05 02:04:13 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-05 02:04:13 (9268) [INFO] * 2025-01-05 02:04:13 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-05 02:04:13 (9238) [INFO] * 2025-01-05 02:04:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 02:04:14 (9251) [INFO] Determining fastest mirrors * 2025-01-05 02:04:47 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-05 02:04:47 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-05 02:04:47 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-05 02:04:47 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-05 02:07:50 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-05 02:07:50 (9251) [INFO] Trying other mirror. * 2025-01-05 02:07:50 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-05 02:07:50 (9251) [INFO] Trying other mirror. * 2025-01-05 02:08:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:08:20 (9251) [INFO] Trying other mirror. * 2025-01-05 02:09:24 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-01-05 02:09:24 (9251) [INFO] Trying other mirror. * 2025-01-05 02:09:40 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:09:40 (9251) [INFO] Trying other mirror. * 2025-01-05 02:09:55 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:09:55 (9251) [INFO] Trying other mirror. * 2025-01-05 02:09:59 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:09:59 (9251) [INFO] Trying other mirror. * 2025-01-05 02:10:26 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e9d5398a26bc9639935a58dd568a61a673e2d348137b6e2030004575cfdc712f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:10:26 (9251) [INFO] Trying other mirror. * 2025-01-05 02:10:30 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-05 02:10:30 (9251) [INFO] Trying other mirror. * 2025-01-05 02:10:41 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1OTQwNDI3OjE3MzYxOTk2Mjc6Tsf7rgK0S4huIuRfucTkJ-CkR26OHF8T4RGokdZ7o5rkL33H58n9PZnNdjyXvCmmYb7ax5zq-3H-DDDUP-OgkzrGrdVM9BKxUi6Jpq8oR-gRzgf3ICxbueCAyePgrWcAAuDrXV4V2l5Ns7p-34AlePYpvqSXud2JSdEv5kdJsSarlMsix6-JqT1Ip_WNzZsxAzG-IaSO-1UjnGOsFa5chm6AYVeF-385c9jerojiqJZmmOLv-_er16M0QEDOigRfkkrODP7wnt1yMCYwjQd5jc-X5X8hIm_iU39KtV3lh-JmPEbFKpJkNlqpYPjR5YlGvQO2rxbwG8MnKyYvZ2nF7saP6b5FHtTofQT_mFnUTN23whLcPd1ZBdswpNM5ZVRKz3nacUjC-sccQ5H4BjUgFGf6IIrZN9cmrIUTsT4mDF6YT6RRLcyIESzyO3RzRslO6TaYKtEDwO3NRa4w7uk7couQWcZ4i-JaDiN8jGi5qJQ-R7FiLiUcMjZHnqQmlVDLUaaZNz9dmGx0klMQLXJs9V-2dEHI2DEq8L8LOqBFjIFtReMOGLmK9VF31k7Of-lMwF_Grzz5-Zwm33wNN51VRPNwNZX_yW6vNCuRD6NvwBm_98LQHg5-hC9Rwk9xLsABCuKz-OiUCzozJS4B40SKlXRB_hzZPDiWUBqzqRG3G-g%3D/ea-php/7/updates/x86_64/repodata/026bee58294c9c16948c59086436d41a8b839452ce155dc56fcb024e06c3ee13-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:10:41 (9251) [INFO] Trying other mirror. * 2025-01-05 02:10:57 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:10:57 (9251) [INFO] Trying other mirror. * 2025-01-05 02:11:13 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:11:13 (9251) [INFO] Trying other mirror. * 2025-01-05 02:11:28 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:11:28 (9251) [INFO] Trying other mirror. * 2025-01-05 02:11:44 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:11:44 (9251) [INFO] Trying other mirror. * 2025-01-05 02:12:00 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:12:00 (9251) [INFO] Trying other mirror. * 2025-01-05 02:12:15 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:12:15 (9251) [INFO] Trying other mirror. * 2025-01-05 02:12:31 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:12:31 (9251) [INFO] Trying other mirror. * 2025-01-05 02:12:47 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:12:47 (9251) [INFO] Trying other mirror. * 2025-01-05 02:13:17 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:13:17 (9251) [INFO] Trying other mirror. * 2025-01-05 02:13:17 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-05 02:13:17 (9251) [INFO] Trying other mirror. * 2025-01-05 02:13:32 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/wp-toolkit/repodata/48342a99b2f6d6b8817cf525b46227649da53e4dd538bed4da6b6959df8fd0c9-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:13:32 (9251) [INFO] Trying other mirror. * 2025-01-05 02:13:48 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-05 02:13:48 (9251) [INFO] Trying other mirror. * 2025-01-05 02:13:48 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:13:48 (9251) [INFO] Trying other mirror. * 2025-01-05 02:14:18 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-05 02:14:18 (9251) [INFO] Trying other mirror. * 2025-01-05 02:14:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-05 02:14:49 (9251) [INFO] Trying other mirror. * 2025-01-05 02:15:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:15:19 (9251) [INFO] Trying other mirror. * 2025-01-05 02:15:19 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30002 milliseconds') * 2025-01-05 02:15:19 (9251) [INFO] Trying other mirror. * 2025-01-05 02:15:19 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:15:19 (9251) [INFO] Trying other mirror. * 2025-01-05 02:15:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30315 milliseconds') * 2025-01-05 02:15:20 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:20 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-05 02:16:20 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:37 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:16:37 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:51 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:16:51 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:51 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-05 02:16:51 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-05 02:16:51 (9251) [INFO] Trying other mirror. * 2025-01-05 02:16:52 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-01-05 02:16:52 (9251) [INFO] Trying other mirror. * 2025-01-06 01:53:25 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-06 01:57:25 (10313) [INFO] Script is up to date. * 2025-01-06 02:01:29 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-06 02:01:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-06 02:01:29 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-06 02:01:29 (9238) [INFO] * 2025-01-06 02:01:32 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-06 02:01:32 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-06 02:01:32 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-06 02:01:32 (9238) [INFO] * 2025-01-06 02:01:43 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-06 02:01:46 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-06 02:01:46 (9238) [INFO] * 2025-01-06 02:01:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 02:01:47 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-06 02:02:18 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-06 02:02:18 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30544 milliseconds') * 2025-01-06 02:02:18 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-06 02:02:18 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-06 02:02:18 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-06 02:02:18 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-06 02:03:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30026 milliseconds with 0 out of 0 bytes received') * 2025-01-06 02:03:04 (9251) [INFO] Trying other mirror. * 2025-01-06 02:03:35 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-06 02:03:35 (9251) [INFO] Trying other mirror. * 2025-01-06 02:06:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:06:04 (9251) [INFO] Trying other mirror. * 2025-01-06 02:06:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-06 02:06:21 (9251) [INFO] Trying other mirror. * 2025-01-06 02:06:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:06:51 (9251) [INFO] Trying other mirror. * 2025-01-06 02:06:54 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-06 02:06:54 (9251) [INFO] Trying other mirror. * 2025-01-06 02:07:24 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:07:24 (9251) [INFO] Trying other mirror. * 2025-01-06 02:07:54 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-06 02:07:54 (9251) [INFO] Trying other mirror. * 2025-01-06 02:08:40 (9251) [INFO] Metadata Cache Created * 2025-01-06 02:08:40 (9268) [INFO] * 2025-01-06 02:08:40 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30544 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30026 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-06 02:08:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-06 02:08:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-06 02:08:40 (9238) [INFO] * 2025-01-06 02:08:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 02:08:41 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-06 02:08:41 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-06 02:08:41 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-06 02:08:41 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-06 02:08:41 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-06 02:08:41 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-06 02:08:41 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-06 02:08:41 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-06 02:08:41 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-06 02:08:41 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-06 02:08:41 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-06 02:08:41 (9268) [INFO] * 2025-01-06 02:08:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-06 02:08:41 (9238) [INFO] * 2025-01-06 02:08:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 02:08:42 (9251) [INFO] Determining fastest mirrors * 2025-01-06 02:09:15 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-06 02:09:15 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-06 02:09:15 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-06 02:09:15 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-06 02:12:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-06 02:12:17 (9251) [INFO] Trying other mirror. * 2025-01-06 02:12:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:12:18 (9251) [INFO] Trying other mirror. * 2025-01-06 02:13:36 (9251) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-01-06 02:13:36 (9251) [INFO] Trying other mirror. * 2025-01-06 02:13:51 (9251) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:13:51 (9251) [INFO] Trying other mirror. * 2025-01-06 02:14:07 (9251) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:14:07 (9251) [INFO] Trying other mirror. * 2025-01-06 02:14:23 (9251) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:14:23 (9251) [INFO] Trying other mirror. * 2025-01-06 02:14:26 (9251) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:14:26 (9251) [INFO] Trying other mirror. * 2025-01-06 02:14:53 (9251) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e9d5398a26bc9639935a58dd568a61a673e2d348137b6e2030004575cfdc712f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:14:53 (9251) [INFO] Trying other mirror. * 2025-01-06 02:14:56 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:14:56 (9251) [INFO] Trying other mirror. * 2025-01-06 02:15:09 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1OTQwNDI3OjE3MzYxOTk2Mjc6Tsf7rgK0S4huIuRfucTkJ-CkR26OHF8T4RGokdZ7o5rkL33H58n9PZnNdjyXvCmmYb7ax5zq-3H-DDDUP-OgkzrGrdVM9BKxUi6Jpq8oR-gRzgf3ICxbueCAyePgrWcAAuDrXV4V2l5Ns7p-34AlePYpvqSXud2JSdEv5kdJsSarlMsix6-JqT1Ip_WNzZsxAzG-IaSO-1UjnGOsFa5chm6AYVeF-385c9jerojiqJZmmOLv-_er16M0QEDOigRfkkrODP7wnt1yMCYwjQd5jc-X5X8hIm_iU39KtV3lh-JmPEbFKpJkNlqpYPjR5YlGvQO2rxbwG8MnKyYvZ2nF7saP6b5FHtTofQT_mFnUTN23whLcPd1ZBdswpNM5ZVRKz3nacUjC-sccQ5H4BjUgFGf6IIrZN9cmrIUTsT4mDF6YT6RRLcyIESzyO3RzRslO6TaYKtEDwO3NRa4w7uk7couQWcZ4i-JaDiN8jGi5qJQ-R7FiLiUcMjZHnqQmlVDLUaaZNz9dmGx0klMQLXJs9V-2dEHI2DEq8L8LOqBFjIFtReMOGLmK9VF31k7Of-lMwF_Grzz5-Zwm33wNN51VRPNwNZX_yW6vNCuRD6NvwBm_98LQHg5-hC9Rwk9xLsABCuKz-OiUCzozJS4B40SKlXRB_hzZPDiWUBqzqRG3G-g%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:15:09 (9251) [INFO] Trying other mirror. * 2025-01-06 02:15:24 (9251) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM1OTQwNDI3OjE3MzYxOTk2Mjc6Tsf7rgK0S4huIuRfucTkJ-CkR26OHF8T4RGokdZ7o5rkL33H58n9PZnNdjyXvCmmYb7ax5zq-3H-DDDUP-OgkzrGrdVM9BKxUi6Jpq8oR-gRzgf3ICxbueCAyePgrWcAAuDrXV4V2l5Ns7p-34AlePYpvqSXud2JSdEv5kdJsSarlMsix6-JqT1Ip_WNzZsxAzG-IaSO-1UjnGOsFa5chm6AYVeF-385c9jerojiqJZmmOLv-_er16M0QEDOigRfkkrODP7wnt1yMCYwjQd5jc-X5X8hIm_iU39KtV3lh-JmPEbFKpJkNlqpYPjR5YlGvQO2rxbwG8MnKyYvZ2nF7saP6b5FHtTofQT_mFnUTN23whLcPd1ZBdswpNM5ZVRKz3nacUjC-sccQ5H4BjUgFGf6IIrZN9cmrIUTsT4mDF6YT6RRLcyIESzyO3RzRslO6TaYKtEDwO3NRa4w7uk7couQWcZ4i-JaDiN8jGi5qJQ-R7FiLiUcMjZHnqQmlVDLUaaZNz9dmGx0klMQLXJs9V-2dEHI2DEq8L8LOqBFjIFtReMOGLmK9VF31k7Of-lMwF_Grzz5-Zwm33wNN51VRPNwNZX_yW6vNCuRD6NvwBm_98LQHg5-hC9Rwk9xLsABCuKz-OiUCzozJS4B40SKlXRB_hzZPDiWUBqzqRG3G-g%3D/ea-php/7/updates/x86_64/repodata/026bee58294c9c16948c59086436d41a8b839452ce155dc56fcb024e06c3ee13-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:15:24 (9251) [INFO] Trying other mirror. * 2025-01-06 02:15:40 (9251) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:15:40 (9251) [INFO] Trying other mirror. * 2025-01-06 02:15:55 (9251) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:15:55 (9251) [INFO] Trying other mirror. * 2025-01-06 02:16:11 (9251) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:16:11 (9251) [INFO] Trying other mirror. * 2025-01-06 02:16:27 (9251) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:16:27 (9251) [INFO] Trying other mirror. * 2025-01-06 02:16:42 (9251) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:16:42 (9251) [INFO] Trying other mirror. * 2025-01-06 02:16:58 (9251) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:16:58 (9251) [INFO] Trying other mirror. * 2025-01-06 02:17:14 (9251) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:17:14 (9251) [INFO] Trying other mirror. * 2025-01-06 02:17:29 (9251) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:17:29 (9251) [INFO] Trying other mirror. * 2025-01-06 02:18:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:18:00 (9251) [INFO] Trying other mirror. * 2025-01-06 02:18:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-06 02:18:00 (9251) [INFO] Trying other mirror. * 2025-01-06 02:18:15 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/wp-toolkit/repodata/48342a99b2f6d6b8817cf525b46227649da53e4dd538bed4da6b6959df8fd0c9-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:18:15 (9251) [INFO] Trying other mirror. * 2025-01-06 02:18:31 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:18:31 (9251) [INFO] Trying other mirror. * 2025-01-06 02:18:31 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:18:31 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:01 (9251) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30001 milliseconds') * 2025-01-06 02:19:01 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:01 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:19:01 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:02 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-06 02:19:02 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:18 (9251) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:19:18 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:32 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:19:32 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:32 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:19:32 (9251) [INFO] Trying other mirror. * 2025-01-06 02:19:32 (9251) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:19:32 (9251) [INFO] Trying other mirror. * 2025-01-06 02:20:02 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-06 02:20:02 (9251) [INFO] Trying other mirror. * 2025-01-06 02:20:19 (9251) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:20:19 (9251) [INFO] Trying other mirror. * 2025-01-06 02:20:33 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:20:33 (9251) [INFO] Trying other mirror. * 2025-01-06 02:20:33 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:20:33 (9251) [INFO] Trying other mirror. * 2025-01-06 02:20:50 (9251) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:20:50 (9251) [INFO] Trying other mirror. * 2025-01-06 02:21:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-06 02:21:03 (9251) [INFO] Trying other mirror. * 2025-01-06 02:21:21 (9251) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30536 milliseconds') * 2025-01-06 02:21:21 (9251) [INFO] Trying other mirror. * 2025-01-06 02:21:33 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:21:33 (9251) [INFO] Trying other mirror. * 2025-01-06 02:21:37 (9251) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:21:37 (9251) [INFO] Trying other mirror. * 2025-01-06 02:22:05 (9251) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:22:05 (9251) [INFO] Trying other mirror. * 2025-01-06 02:22:21 (9251) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:22:21 (9251) [INFO] Trying other mirror. * 2025-01-06 02:22:37 (9251) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-06 02:22:37 (9251) [INFO] Trying other mirror. * 2025-01-07 01:54:08 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-07 01:58:09 (10313) [INFO] Script is up to date. * 2025-01-07 02:02:12 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-07 02:02:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-07 02:02:12 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-07 02:02:12 (9238) [INFO] * 2025-01-07 02:02:16 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-07 02:02:16 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-07 02:02:16 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-07 02:02:16 (9238) [INFO] * 2025-01-07 02:02:27 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-07 02:02:30 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-07 02:02:30 (9238) [INFO] * 2025-01-07 02:02:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 02:02:31 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-07 02:03:01 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-07 02:03:01 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30536 milliseconds') * 2025-01-07 02:03:01 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-07 02:03:01 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-07 02:03:01 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-07 02:03:01 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-07 02:05:48 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-07 02:05:48 (9251) [INFO] Trying other mirror. * 2025-01-07 02:06:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-07 02:06:04 (9251) [INFO] Trying other mirror. * 2025-01-07 02:06:35 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-07 02:06:35 (9251) [INFO] Trying other mirror. * 2025-01-07 02:06:37 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-07 02:06:37 (9251) [INFO] Trying other mirror. * 2025-01-07 02:07:21 (9251) [INFO] Metadata Cache Created * 2025-01-07 02:07:21 (9268) [INFO] * 2025-01-07 02:07:21 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30536 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-07 02:07:21 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-07 02:07:21 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-07 02:07:21 (9238) [INFO] * 2025-01-07 02:07:21 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 02:07:21 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-07 02:07:21 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-07 02:07:21 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-07 02:07:21 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-07 02:07:21 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-07 02:07:21 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-07 02:07:21 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-07 02:07:21 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-07 02:07:21 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-07 02:07:22 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-07 02:07:22 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-07 02:07:22 (9268) [INFO] * 2025-01-07 02:07:22 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-07 02:07:22 (9238) [INFO] * 2025-01-07 02:07:23 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 02:07:23 (9251) [INFO] Determining fastest mirrors * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-07 02:07:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-07 02:07:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-07 02:07:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-07 02:07:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-07 02:07:53 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-07 02:07:53 (9251) [INFO] yum --disablerepo= ... * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-07 02:07:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-07 02:07:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] yum-config-manager --disable * 2025-01-07 02:07:53 (9251) [INFO] or * 2025-01-07 02:07:53 (9251) [INFO] subscription-manager repos --disable= * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-07 02:07:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-07 02:07:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-07 02:07:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-07 02:07:53 (9251) [INFO] compromise: * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-07 02:07:53 (9251) [INFO] * 2025-01-07 02:07:53 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-07 02:07:53 (9268) [INFO] * 2025-01-07 02:07:53 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-07 02:07:53 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-07 02:07:54 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-07 02:07:54 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-07 02:07:54 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-07 02:07:54 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-07 02:07:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-07 02:08:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IsrI_wMGBN/ea_profile.json * 2025-01-07 02:15:45 (8385) [INFO] Backed up EA4 profile to /tmp/IsrI_wMGBN/ea_profile.json * 2025-01-07 02:15:46 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-07 02:16:20 (627) [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. * 2025-01-07 02:16:20 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-08 02:00:14 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-08 02:04:14 (10313) [INFO] Script is up to date. * 2025-01-08 02:08:17 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-08 02:08:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-08 02:08:18 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-08 02:08:18 (9238) [INFO] * 2025-01-08 02:08:21 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-08 02:08:21 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-08 02:08:21 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-08 02:08:21 (9238) [INFO] * 2025-01-08 02:08:32 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-08 02:08:34 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-08 02:08:34 (9238) [INFO] * 2025-01-08 02:08:34 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 02:08:35 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-08 02:09:05 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-08 02:09:05 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-08 02:09:05 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-08 02:09:05 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-08 02:11:51 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-08 02:11:51 (9251) [INFO] Trying other mirror. * 2025-01-08 02:12:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:12:07 (9251) [INFO] Trying other mirror. * 2025-01-08 02:12:24 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:12:24 (9251) [INFO] Trying other mirror. * 2025-01-08 02:12:39 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:12:39 (9251) [INFO] Trying other mirror. * 2025-01-08 02:12:54 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-08 02:12:54 (9251) [INFO] Trying other mirror. * 2025-01-08 02:13:10 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-08 02:13:10 (9251) [INFO] Trying other mirror. * 2025-01-08 02:13:54 (9251) [INFO] Metadata Cache Created * 2025-01-08 02:13:54 (9268) [INFO] * 2025-01-08 02:13:54 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-08 02:13:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-08 02:13:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-08 02:13:54 (9238) [INFO] * 2025-01-08 02:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 02:13:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-08 02:13:54 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-08 02:13:54 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-08 02:13:54 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-08 02:13:54 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-08 02:13:54 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-08 02:13:54 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-08 02:13:54 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-08 02:13:54 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-08 02:13:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-08 02:13:55 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-08 02:13:55 (9268) [INFO] * 2025-01-08 02:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-08 02:13:55 (9238) [INFO] * 2025-01-08 02:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 02:13:56 (9251) [INFO] Determining fastest mirrors * 2025-01-08 02:14:29 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-08 02:14:29 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-08 02:14:29 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-08 02:14:29 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-08 02:15:15 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-08 02:15:15 (9251) [INFO] Trying other mirror. * 2025-01-08 02:15:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-08 02:15:46 (9251) [INFO] Trying other mirror. * 2025-01-08 02:18:33 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:18:33 (9251) [INFO] Trying other mirror. * 2025-01-08 02:18:33 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-08 02:18:33 (9251) [INFO] Trying other mirror. * 2025-01-08 02:21:14 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-01-08 02:21:14 (9251) [INFO] Trying other mirror. * 2025-01-08 02:24:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:24:03 (9251) [INFO] Trying other mirror. * 2025-01-08 02:24:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:24:03 (9251) [INFO] Trying other mirror. * 2025-01-08 02:25:05 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:25:05 (9251) [INFO] Trying other mirror. * 2025-01-08 02:25:05 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:25:05 (9251) [INFO] Trying other mirror. * 2025-01-08 02:25:35 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-08 02:25:35 (9251) [INFO] Trying other mirror. * 2025-01-08 02:26:07 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-08 02:26:07 (9251) [INFO] Trying other mirror. * 2025-01-08 02:26:37 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-08 02:26:37 (9251) [INFO] Trying other mirror. * 2025-01-08 02:27:59 (9251) [INFO] Metadata Cache Created * 2025-01-08 02:27:59 (9268) [INFO] * 2025-01-08 02:27: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-08 02:27:59 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-08 02:28:00 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-08 02:28:00 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-08 02:28:00 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-08 02:28:00 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-08 02:28:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-08 02:28:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bNfVE7tIlP/ea_profile.json * 2025-01-08 02:28:10 (8385) [INFO] Backed up EA4 profile to /tmp/bNfVE7tIlP/ea_profile.json * 2025-01-08 02:28:10 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-08 02:28:44 (627) [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. * 2025-01-08 02:28:44 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-09 01:55:15 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-09 01:59:16 (10313) [INFO] Script is up to date. * 2025-01-09 02:03:19 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-09 02:03:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-09 02:03:19 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-09 02:03:19 (9238) [INFO] * 2025-01-09 02:03:23 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-09 02:03:23 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-09 02:03:23 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-09 02:03:23 (9238) [INFO] * 2025-01-09 02:03:35 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-09 02:03:38 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-09 02:03:38 (9238) [INFO] * 2025-01-09 02:03:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 02:03:39 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-09 02:04:09 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-09 02:04:09 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') * 2025-01-09 02:04:09 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-09 02:04:09 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-09 02:04:09 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-09 02:04:10 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-09 02:04:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-09 02:04:57 (9251) [INFO] Trying other mirror. * 2025-01-09 02:05:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-09 02:05:27 (9251) [INFO] Trying other mirror. * 2025-01-09 02:07:57 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-09 02:07:57 (9251) [INFO] Trying other mirror. * 2025-01-09 02:08:13 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-09 02:08:13 (9251) [INFO] Trying other mirror. * 2025-01-09 02:08:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:08:29 (9251) [INFO] Trying other mirror. * 2025-01-09 02:08:43 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:08:43 (9251) [INFO] Trying other mirror. * 2025-01-09 02:08:45 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-09 02:08:45 (9251) [INFO] Trying other mirror. * 2025-01-09 02:09:00 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-09 02:09:00 (9251) [INFO] Trying other mirror. * 2025-01-09 02:09:16 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-09 02:09:16 (9251) [INFO] Trying other mirror. * 2025-01-09 02:09:46 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:09:46 (9251) [INFO] Trying other mirror. * 2025-01-09 02:10:30 (9251) [INFO] Metadata Cache Created * 2025-01-09 02:10:30 (9268) [INFO] * 2025-01-09 02:10:30 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-09 02:10:30 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-09 02:10:30 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-09 02:10:30 (9238) [INFO] * 2025-01-09 02:10:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 02:10:31 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-09 02:10:31 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-09 02:10:31 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-09 02:10:31 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-09 02:10:31 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-09 02:10:31 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-09 02:10:31 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-09 02:10:31 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-09 02:10:31 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-09 02:10:32 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-09 02:10:32 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-09 02:10:32 (9268) [INFO] * 2025-01-09 02:10:32 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-09 02:10:32 (9238) [INFO] * 2025-01-09 02:10:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 02:10:33 (9251) [INFO] Determining fastest mirrors * 2025-01-09 02:11:06 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-09 02:11:06 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-09 02:11:06 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-09 02:11:06 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-09 02:11:53 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-09 02:11:53 (9251) [INFO] Trying other mirror. * 2025-01-09 02:14:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-09 02:14:41 (9251) [INFO] Trying other mirror. * 2025-01-09 02:14:41 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-09 02:14:41 (9251) [INFO] Trying other mirror. * 2025-01-09 02:17:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:17:20 (9251) [INFO] Trying other mirror. * 2025-01-09 02:20:08 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:20:08 (9251) [INFO] Trying other mirror. * 2025-01-09 02:21:10 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-09 02:21:10 (9251) [INFO] Trying other mirror. * 2025-01-09 02:21:10 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2025-01-09 02:21:10 (9251) [INFO] Trying other mirror. * 2025-01-09 02:21:40 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:21:40 (9251) [INFO] Trying other mirror. * 2025-01-09 02:21:41 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-09 02:21:41 (9251) [INFO] Trying other mirror. * 2025-01-09 02:22:11 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-09 02:22:11 (9251) [INFO] Trying other mirror. * 2025-01-09 02:23:29 (9251) [INFO] Metadata Cache Created * 2025-01-09 02:23:30 (9268) [INFO] * 2025-01-09 02:23: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/ * 2025-01-09 02:23:30 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-09 02:23:30 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-09 02:23:30 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-09 02:23:30 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-09 02:23:30 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-09 02:23:30 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-09 02:23:38 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0Gz8IoNrWY/ea_profile.json * 2025-01-09 02:23:40 (8385) [INFO] Backed up EA4 profile to /tmp/0Gz8IoNrWY/ea_profile.json * 2025-01-09 02:23:41 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-09 02:24:15 (627) [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. * 2025-01-09 02:24:15 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-10 02:08:29 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-10 02:12:29 (10313) [INFO] Script is up to date. * 2025-01-10 02:16:32 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-10 02:16:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-10 02:16:33 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-10 02:16:33 (9238) [INFO] * 2025-01-10 02:16:36 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-10 02:16:36 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-10 02:16:36 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-10 02:16:36 (9238) [INFO] * 2025-01-10 02:16:45 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-10 02:16:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-10 02:16:48 (9238) [INFO] * 2025-01-10 02:16:49 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 02:16:49 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-10 02:17:19 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-10 02:17:19 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-10 02:17:19 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-10 02:17:19 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-10 02:18:06 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-10 02:18:06 (9251) [INFO] Trying other mirror. * 2025-01-10 02:20:35 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:20:35 (9251) [INFO] Trying other mirror. * 2025-01-10 02:20:52 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:20:52 (9251) [INFO] Trying other mirror. * 2025-01-10 02:21:23 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-10 02:21:23 (9251) [INFO] Trying other mirror. * 2025-01-10 02:21:25 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:21:25 (9251) [INFO] Trying other mirror. * 2025-01-10 02:21:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-10 02:21:54 (9251) [INFO] Trying other mirror. * 2025-01-10 02:22:38 (9251) [INFO] Metadata Cache Created * 2025-01-10 02:22:38 (9268) [INFO] * 2025-01-10 02:22:38 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. * 2025-01-10 02:22:38 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-10 02:22:38 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-10 02:22:38 (9238) [INFO] * 2025-01-10 02:22:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 02:22:39 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-10 02:22:39 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-10 02:22:39 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-10 02:22:39 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-10 02:22:39 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-10 02:22:39 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-10 02:22:39 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-10 02:22:39 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-10 02:22:39 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-10 02:22:40 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-10 02:22:40 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-10 02:22:40 (9268) [INFO] * 2025-01-10 02:22:40 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-10 02:22:40 (9238) [INFO] * 2025-01-10 02:22:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 02:22:40 (9251) [INFO] Determining fastest mirrors * 2025-01-10 02:23:13 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-10 02:23:13 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-10 02:23:13 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-10 02:23:13 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-10 02:23:59 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-10 02:23:59 (9251) [INFO] Trying other mirror. * 2025-01-10 02:26:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-10 02:26:46 (9251) [INFO] Trying other mirror. * 2025-01-10 02:26:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:26:46 (9251) [INFO] Trying other mirror. * 2025-01-10 02:29:26 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:29:26 (9251) [INFO] Trying other mirror. * 2025-01-10 02:32:14 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:32:14 (9251) [INFO] Trying other mirror. * 2025-01-10 02:33:16 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:33:16 (9251) [INFO] Trying other mirror. * 2025-01-10 02:33:16 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-10 02:33:16 (9251) [INFO] Trying other mirror. * 2025-01-10 02:33:46 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-10 02:33:46 (9251) [INFO] Trying other mirror. * 2025-01-10 02:35:09 (9251) [INFO] Metadata Cache Created * 2025-01-10 02:35:09 (9268) [INFO] * 2025-01-10 02:35:09 (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 02:35:09 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. * 2025-01-10 02:35:10 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-10 02:35:10 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-10 02:35:10 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-10 02:35:10 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-10 02:35:10 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-10 02:35:16 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/o9yTlQu3Ji/ea_profile.json * 2025-01-10 02:35:18 (8385) [INFO] Backed up EA4 profile to /tmp/o9yTlQu3Ji/ea_profile.json * 2025-01-10 02:35:19 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-10 02:35:53 (627) [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. * 2025-01-10 02:35:53 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-11 02:01:44 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-11 02:05:45 (10313) [INFO] Script is up to date. * 2025-01-11 02:09:48 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-11 02:09:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-11 02:09:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-11 02:09:48 (9238) [INFO] * 2025-01-11 02:09:51 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-11 02:09:51 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-11 02:09:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-11 02:09:51 (9238) [INFO] * 2025-01-11 02:10:02 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-11 02:10:06 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-11 02:10:06 (9238) [INFO] * 2025-01-11 02:10:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 02:10:07 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-11 02:10:38 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-11 02:10:38 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30659 milliseconds') * 2025-01-11 02:10:38 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-11 02:10:38 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-11 02:10:38 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-11 02:10:38 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-11 02:11:25 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') * 2025-01-11 02:11:25 (9251) [INFO] Trying other mirror. * 2025-01-11 02:13:54 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:13:54 (9251) [INFO] Trying other mirror. * 2025-01-11 02:14:10 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:14:10 (9251) [INFO] Trying other mirror. * 2025-01-11 02:14:41 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-11 02:14:41 (9251) [INFO] Trying other mirror. * 2025-01-11 02:14:54 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-11 02:14:54 (9251) [INFO] Trying other mirror. * 2025-01-11 02:15:12 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-11 02:15:12 (9251) [INFO] Trying other mirror. * 2025-01-11 02:15:24 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:15:24 (9251) [INFO] Trying other mirror. * 2025-01-11 02:15:43 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-11 02:15:43 (9251) [INFO] Trying other mirror. * 2025-01-11 02:15:54 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-11 02:15:54 (9251) [INFO] Trying other mirror. * 2025-01-11 02:16:25 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-11 02:16:25 (9251) [INFO] Trying other mirror. * 2025-01-11 02:16:56 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-11 02:16:56 (9251) [INFO] Trying other mirror. * 2025-01-11 02:17:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-11 02:17:27 (9251) [INFO] Trying other mirror. * 2025-01-11 02:18:11 (9251) [INFO] Metadata Cache Created * 2025-01-11 02:18:11 (9268) [INFO] * 2025-01-11 02:18:11 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30659 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-11 02:18:11 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-11 02:18:11 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-11 02:18:11 (9238) [INFO] * 2025-01-11 02:18:12 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 02:18:12 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-11 02:18:12 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-11 02:18:12 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-11 02:18:12 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-11 02:18:12 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-11 02:18:12 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-11 02:18:12 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-11 02:18:12 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-11 02:18:12 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-11 02:18:13 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-11 02:18:13 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-11 02:18:13 (9268) [INFO] * 2025-01-11 02:18:13 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-11 02:18:13 (9238) [INFO] * 2025-01-11 02:18:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 02:18:13 (9251) [INFO] Determining fastest mirrors * 2025-01-11 02:18:45 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-11 02:18:45 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-11 02:18:45 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-11 02:18:45 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-11 02:21:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:21:49 (9251) [INFO] Trying other mirror. * 2025-01-11 02:21:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-11 02:21:49 (9251) [INFO] Trying other mirror. * 2025-01-11 02:24:30 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-11 02:24:30 (9251) [INFO] Trying other mirror. * 2025-01-11 02:27:18 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:27:18 (9251) [INFO] Trying other mirror. * 2025-01-11 02:27:19 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-11 02:27:19 (9251) [INFO] Trying other mirror. * 2025-01-11 02:28:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:28:20 (9251) [INFO] Trying other mirror. * 2025-01-11 02:28:20 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:28:20 (9251) [INFO] Trying other mirror. * 2025-01-11 02:28:50 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:28:50 (9251) [INFO] Trying other mirror. * 2025-01-11 02:29:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-11 02:29:21 (9251) [INFO] Trying other mirror. * 2025-01-11 02:30:47 (9251) [INFO] Metadata Cache Created * 2025-01-11 02:30:47 (9268) [INFO] * 2025-01-11 02:30: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/ * 2025-01-11 02:30:47 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-11 02:30:48 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-11 02:30:48 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-11 02:30:48 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-11 02:30:48 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-11 02:30:48 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-11 02:30:54 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jRgvEOj8Rj/ea_profile.json * 2025-01-11 02:30:56 (8385) [INFO] Backed up EA4 profile to /tmp/jRgvEOj8Rj/ea_profile.json * 2025-01-11 02:30:57 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-11 02:31:29 (627) [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. * 2025-01-11 02:31:29 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-12 01:57:51 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-12 02:01:52 (10313) [INFO] Script is up to date. * 2025-01-12 02:05:55 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-12 02:05:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-12 02:05:55 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-12 02:05:55 (9238) [INFO] * 2025-01-12 02:05:58 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-12 02:05:58 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-12 02:05:58 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-12 02:05:58 (9238) [INFO] * 2025-01-12 02:06:10 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-12 02:06:12 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-12 02:06:12 (9238) [INFO] * 2025-01-12 02:06:12 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 02:06:13 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-12 02:06:43 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-12 02:06:43 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-12 02:06:43 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-12 02:06:43 (9251) [INFO] * epel: mirror.math.princeton.edu * 2025-01-12 02:09:28 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:09:28 (9251) [INFO] Trying other mirror. * 2025-01-12 02:09:45 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:09:45 (9251) [INFO] Trying other mirror. * 2025-01-12 02:10:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:10:28 (9251) [INFO] Trying other mirror. * 2025-01-12 02:11:12 (9251) [INFO] Metadata Cache Created * 2025-01-12 02:11:12 (9268) [INFO] * 2025-01-12 02:11:12 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-12 02:11:12 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-12 02:11:12 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-12 02:11:12 (9238) [INFO] * 2025-01-12 02:11:12 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 02:11:12 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-12 02:11:12 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-12 02:11:12 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-12 02:11:12 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-12 02:11:12 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-12 02:11:12 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-12 02:11:12 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-12 02:11:12 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-12 02:11:12 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-12 02:11:13 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-12 02:11:13 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-12 02:11:13 (9268) [INFO] * 2025-01-12 02:11:13 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-12 02:11:13 (9238) [INFO] * 2025-01-12 02:11:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 02:11:14 (9251) [INFO] Determining fastest mirrors * 2025-01-12 02:11:45 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-12 02:11:45 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-12 02:11:45 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-12 02:11:45 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-12 02:12:32 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-12 02:12:32 (9251) [INFO] Trying other mirror. * 2025-01-12 02:15:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:15:19 (9251) [INFO] Trying other mirror. * 2025-01-12 02:15:19 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-12 02:15:19 (9251) [INFO] Trying other mirror. * 2025-01-12 02:17:59 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:17:59 (9251) [INFO] Trying other mirror. * 2025-01-12 02:20:48 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:20:48 (9251) [INFO] Trying other mirror. * 2025-01-12 02:21:19 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-12 02:21:19 (9251) [INFO] Trying other mirror. * 2025-01-12 02:22:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:22:20 (9251) [INFO] Trying other mirror. * 2025-01-12 02:22:20 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:22:20 (9251) [INFO] Trying other mirror. * 2025-01-12 02:22:50 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-12 02:22:50 (9251) [INFO] Trying other mirror. * 2025-01-12 02:23:21 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-12 02:23:21 (9251) [INFO] Trying other mirror. * 2025-01-12 02:23:52 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-12 02:23:52 (9251) [INFO] Trying other mirror. * 2025-01-12 02:25:14 (9251) [INFO] Metadata Cache Created * 2025-01-12 02:25:14 (9268) [INFO] * 2025-01-12 02:25:14 (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 02:25:14 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-01-12 02:25:15 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-12 02:25:15 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-12 02:25:15 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-12 02:25:15 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-12 02:25:15 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-12 02:25:21 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xv4UpNQnGM/ea_profile.json * 2025-01-12 02:25:24 (8385) [INFO] Backed up EA4 profile to /tmp/xv4UpNQnGM/ea_profile.json * 2025-01-12 02:25:24 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-12 02:25:57 (627) [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. * 2025-01-12 02:25:57 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-13 01:53:46 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-13 01:57:47 (10313) [INFO] Script is up to date. * 2025-01-13 02:01:50 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-13 02:01:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-13 02:01:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-13 02:01:50 (9238) [INFO] * 2025-01-13 02:01:54 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-13 02:01:54 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-13 02:01:54 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-13 02:01:54 (9238) [INFO] * 2025-01-13 02:02:07 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-13 02:02:10 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-13 02:02:10 (9238) [INFO] * 2025-01-13 02:02:10 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 02:02:11 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-13 02:02:41 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-13 02:02:41 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-13 02:02:41 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-13 02:02:41 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-13 02:05:27 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-13 02:05:27 (9251) [INFO] Trying other mirror. * 2025-01-13 02:05:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:05:43 (9251) [INFO] Trying other mirror. * 2025-01-13 02:06:13 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:06:13 (9251) [INFO] Trying other mirror. * 2025-01-13 02:06:27 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-13 02:06:27 (9251) [INFO] Trying other mirror. * 2025-01-13 02:06:58 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-13 02:06:58 (9251) [INFO] Trying other mirror. * 2025-01-13 02:07:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:07:28 (9251) [INFO] Trying other mirror. * 2025-01-13 02:08:12 (9251) [INFO] Metadata Cache Created * 2025-01-13 02:08:13 (9268) [INFO] * 2025-01-13 02:08:13 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-13 02:08:13 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-13 02:08:13 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-13 02:08:13 (9238) [INFO] * 2025-01-13 02:08:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 02:08:13 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-13 02:08:13 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-13 02:08:13 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-13 02:08:13 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-13 02:08:13 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-13 02:08:13 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-13 02:08:13 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-13 02:08:13 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-13 02:08:13 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-13 02:08:14 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-13 02:08:14 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-13 02:08:14 (9268) [INFO] * 2025-01-13 02:08:14 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-13 02:08:14 (9238) [INFO] * 2025-01-13 02:08:15 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 02:08:15 (9251) [INFO] Determining fastest mirrors * 2025-01-13 02:08:46 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-13 02:08:46 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-13 02:08:46 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-13 02:08:46 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-13 02:09:33 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-13 02:09:33 (9251) [INFO] Trying other mirror. * 2025-01-13 02:10:04 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-13 02:10:04 (9251) [INFO] Trying other mirror. * 2025-01-13 02:10:35 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-13 02:10:35 (9251) [INFO] Trying other mirror. * 2025-01-13 02:11:05 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-13 02:11:05 (9251) [INFO] Trying other mirror. * 2025-01-13 02:13:53 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:13:53 (9251) [INFO] Trying other mirror. * 2025-01-13 02:13:53 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-13 02:13:53 (9251) [INFO] Trying other mirror. * 2025-01-13 02:14:24 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-13 02:14:24 (9251) [INFO] Trying other mirror. * 2025-01-13 02:15:12 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-13 02:15:12 (9251) [INFO] Trying other mirror. * 2025-01-13 02:15:13 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-13 02:15:13 (9251) [INFO] Trying other mirror. * 2025-01-13 02:15:43 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-13 02:15:43 (9251) [INFO] Trying other mirror. * 2025-01-13 02:16:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:16:15 (9251) [INFO] Trying other mirror. * 2025-01-13 02:16:15 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:16:15 (9251) [INFO] Trying other mirror. * 2025-01-13 02:16:31 (9251) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-13 02:16:31 (9251) [INFO] Trying other mirror. * 2025-01-13 02:17:01 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-13 02:17:01 (9251) [INFO] Trying other mirror. * 2025-01-13 02:17:31 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-13 02:17:31 (9251) [INFO] Trying other mirror. * 2025-01-13 02:17:32 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:17:32 (9251) [INFO] Trying other mirror. * 2025-01-13 02:18:33 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-13 02:18:33 (9251) [INFO] Trying other mirror. * 2025-01-13 02:19:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:19:03 (9251) [INFO] Trying other mirror. * 2025-01-13 02:19:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-01-13 02:19:03 (9251) [INFO] Trying other mirror. * 2025-01-13 02:19:33 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:19:33 (9251) [INFO] Trying other mirror. * 2025-01-13 02:19:34 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:19:34 (9251) [INFO] Trying other mirror. * 2025-01-13 02:20:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-13 02:20:03 (9251) [INFO] Trying other mirror. * 2025-01-13 02:20:34 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:20:34 (9251) [INFO] Trying other mirror. * 2025-01-13 02:21:04 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-13 02:21:04 (9251) [INFO] Trying other mirror. * 2025-01-13 02:21:58 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:21:58 (9251) [INFO] Trying other mirror. * 2025-01-13 02:21:58 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-13 02:21:58 (9251) [INFO] Trying other mirror. * 2025-01-13 02:22:28 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-13 02:22:28 (9251) [INFO] Trying other mirror. * 2025-01-13 02:22:29 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-13 02:22:29 (9251) [INFO] Trying other mirror. * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-13 02:23:00 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-13 02:23:00 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-13 02:23:00 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-13 02:23:00 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-13 02:23:00 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-13 02:23:00 (9251) [INFO] yum --disablerepo= ... * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-13 02:23:00 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-13 02:23:00 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] yum-config-manager --disable * 2025-01-13 02:23:00 (9251) [INFO] or * 2025-01-13 02:23:00 (9251) [INFO] subscription-manager repos --disable= * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-13 02:23:00 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-13 02:23:00 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-13 02:23:00 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-13 02:23:00 (9251) [INFO] compromise: * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-13 02:23:00 (9251) [INFO] * 2025-01-13 02:23:00 (9251) [INFO] extras: Check uncompressed DB failed * 2025-01-13 02:23:00 (9268) [INFO] * 2025-01-13 02:23:00 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-13 02:23:00 (5804) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') 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 extras: Check uncompressed DB failed * 2025-01-13 02:23:01 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-13 02:23:01 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-13 02:23:01 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-13 02:23:01 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-13 02:23:01 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-13 02:23:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JsF2wZN8Z7/ea_profile.json * 2025-01-14 01:56:08 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-14 02:00:09 (10313) [INFO] Script is up to date. * 2025-01-14 02:04:12 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-14 02:04:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-14 02:04:13 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-14 02:04:13 (9238) [INFO] * 2025-01-14 02:04:16 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-14 02:04:16 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-14 02:04:16 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-14 02:04:16 (9238) [INFO] * 2025-01-14 02:04:25 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-14 02:04:29 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-14 02:04:29 (9238) [INFO] * 2025-01-14 02:04:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 02:04:30 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-14 02:05:00 (9251) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-14 02:05:00 (9251) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-14 02:05:00 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-14 02:05:00 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-14 02:05:00 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-14 02:05:00 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-14 02:05:46 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-14 02:05:46 (9251) [INFO] Trying other mirror. * 2025-01-14 02:06:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-14 02:06:17 (9251) [INFO] Trying other mirror. * 2025-01-14 02:08:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-14 02:08:47 (9251) [INFO] Trying other mirror. * 2025-01-14 02:09:03 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-14 02:09:03 (9251) [INFO] Trying other mirror. * 2025-01-14 02:09:35 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-14 02:09:35 (9251) [INFO] Trying other mirror. * 2025-01-14 02:09:48 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-14 02:09:48 (9251) [INFO] Trying other mirror. * 2025-01-14 02:09:50 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-14 02:09:50 (9251) [INFO] Trying other mirror. * 2025-01-14 02:10:18 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-14 02:10:18 (9251) [INFO] Trying other mirror. * 2025-01-14 02:10:20 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-14 02:10:20 (9251) [INFO] Trying other mirror. * 2025-01-14 02:10:49 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-14 02:10:49 (9251) [INFO] Trying other mirror. * 2025-01-14 02:10:51 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-14 02:10:51 (9251) [INFO] Trying other mirror. * 2025-01-14 02:11:22 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-01-14 02:11:22 (9251) [INFO] Trying other mirror. * 2025-01-14 02:12:07 (9251) [INFO] Metadata Cache Created * 2025-01-14 02:12:07 (9268) [INFO] * 2025-01-14 02:12:07 (5793) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. * 2025-01-14 02:12:07 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-14 02:12:07 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-14 02:12:07 (9238) [INFO] * 2025-01-14 02:12:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 02:12:08 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-14 02:12:08 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-14 02:12:08 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-14 02:12:08 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-14 02:12:08 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-14 02:12:08 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-14 02:12:08 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-14 02:12:08 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-14 02:12:08 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-14 02:12:09 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-14 02:12:09 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-14 02:12:09 (9268) [INFO] * 2025-01-14 02:12:09 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-14 02:12:09 (9238) [INFO] * 2025-01-14 02:12:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 02:12:09 (9251) [INFO] Determining fastest mirrors * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-14 02:12:41 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-14 02:12:41 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-14 02:12:41 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-14 02:12:41 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-14 02:12:41 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-14 02:12:41 (9251) [INFO] yum --disablerepo= ... * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-14 02:12:41 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-14 02:12:41 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] yum-config-manager --disable * 2025-01-14 02:12:41 (9251) [INFO] or * 2025-01-14 02:12:41 (9251) [INFO] subscription-manager repos --disable= * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-14 02:12:41 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-14 02:12:41 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-14 02:12:41 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-14 02:12:41 (9251) [INFO] compromise: * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-14 02:12:41 (9251) [INFO] * 2025-01-14 02:12:41 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-14 02:12:41 (9268) [INFO] * 2025-01-14 02:12:41 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-14 02:12:41 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-14 02:12:43 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-14 02:12:43 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-14 02:12:43 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-14 02:12:43 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-14 02:12:43 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-14 02:12:49 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/G6Bz4Fp0Gl/ea_profile.json * 2025-01-14 02:20:03 (8385) [INFO] Backed up EA4 profile to /tmp/G6Bz4Fp0Gl/ea_profile.json * 2025-01-14 02:20:03 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-14 02:20:37 (627) [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. * 2025-01-14 02:20:37 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-15 02:00:38 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-15 02:04:38 (10313) [INFO] Script is up to date. * 2025-01-15 02:08:41 (6225) [WARN] OpenSSH configuration file does not explicitly state the option PermitRootLogin in sshd_config file, which will default in RHEL8 to "prohibit-password". We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-15 02:08:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-15 02:08:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-15 02:08:42 (9238) [INFO] * 2025-01-15 02:08:45 (3963) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-15 02:08:45 (3970) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-15 02:08:45 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-15 02:08:45 (9238) [INFO] * 2025-01-15 02:08:55 (252) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-15 02:08:59 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-15 02:08:59 (9238) [INFO] * 2025-01-15 02:08:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-15 02:09:00 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-15 02:09:30 (9251) [INFO] * EA4: 107.178.98.171 * 2025-01-15 02:09:30 (9251) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-15 02:09:30 (9251) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-15 02:09:30 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-15 02:10:16 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-15 02:10:16 (9251) [INFO] Trying other mirror. * 2025-01-15 02:10:47 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-15 02:10:47 (9251) [INFO] Trying other mirror. * 2025-01-15 02:13:17 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-15 02:13:17 (9251) [INFO] Trying other mirror. * 2025-01-15 02:13:34 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-15 02:13:34 (9251) [INFO] Trying other mirror. * 2025-01-15 02:14:03 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-15 02:14:03 (9251) [INFO] Trying other mirror. * 2025-01-15 02:14:06 (9251) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-15 02:14:06 (9251) [INFO] Trying other mirror. * 2025-01-15 02:14:16 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-15 02:14:16 (9251) [INFO] Trying other mirror. * 2025-01-15 02:14:34 (9251) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-15 02:14:34 (9251) [INFO] Trying other mirror. * 2025-01-15 02:14:47 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-15 02:14:47 (9251) [INFO] Trying other mirror. * 2025-01-15 02:15:18 (9251) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-15 02:15:18 (9251) [INFO] Trying other mirror. * 2025-01-15 02:16:00 (9251) [INFO] Metadata Cache Created * 2025-01-15 02:16:00 (9268) [INFO] * 2025-01-15 02:16:00 (5793) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2025-01-15 02:16:00 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-15 02:16:00 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-15 02:16:00 (9238) [INFO] * 2025-01-15 02:16:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-15 02:16:01 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-15 02:16:01 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-15 02:16:01 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-15 02:16:01 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-15 02:16:01 (9251) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-15 02:16:01 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-15 02:16:01 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-15 02:16:01 (9251) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-15 02:16:01 (9251) [INFO] : wp-toolkit-thirdparties * 2025-01-15 02:16:02 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-15 02:16:02 (9251) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-15 02:16:02 (9268) [INFO] * 2025-01-15 02:16:02 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-15 02:16:02 (9238) [INFO] * 2025-01-15 02:16:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-15 02:16:03 (9251) [INFO] Determining fastest mirrors * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] One of the configured repositories failed (Unknown), * 2025-01-15 02:16:33 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-15 02:16:33 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-15 02:16:33 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-15 02:16:33 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-15 02:16:33 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-15 02:16:33 (9251) [INFO] yum --disablerepo= ... * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-15 02:16:33 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-15 02:16:33 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] yum-config-manager --disable * 2025-01-15 02:16:33 (9251) [INFO] or * 2025-01-15 02:16:33 (9251) [INFO] subscription-manager repos --disable= * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-15 02:16:33 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-15 02:16:33 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-15 02:16:33 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-15 02:16:33 (9251) [INFO] compromise: * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-15 02:16:33 (9251) [INFO] * 2025-01-15 02:16:33 (9251) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-15 02:16:33 (9268) [INFO] * 2025-01-15 02:16:33 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-15 02:16:33 (5804) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-15 02:16:34 (3147) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-15 02:16:34 (252) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-15 02:16:34 (4179) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-15 02:16:34 (4185) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-15 02:16:34 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-15 02:16:40 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uF0qiTHXpc/ea_profile.json * 2025-01-15 02:24:20 (8385) [INFO] Backed up EA4 profile to /tmp/uF0qiTHXpc/ea_profile.json * 2025-01-15 02:24:21 (252) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-15 02:24:55 (627) [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. * 2025-01-15 02:24:55 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-16 02:07:07 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-16 02:11:07 (10296) [INFO] Newer version of script found. Downloading. * 2025-01-16 02:15:09 (10305) [INFO] Script update to version 60 successful. * 2025-01-16 02:19:12 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-16 02:19:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-16 02:19:12 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-16 02:19:12 (9401) [INFO] * 2025-01-16 02:19:16 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-16 02:19:16 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-16 02:19:16 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-16 02:19:16 (9401) [INFO] * 2025-01-16 02:19:25 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-16 02:19:29 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-16 02:19:29 (9401) [INFO] * 2025-01-16 02:19:29 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-16 02:19:29 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-16 02:19:59 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-16 02:19:59 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-16 02:19:59 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-16 02:19:59 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-16 02:22:46 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-01-16 02:22:46 (9414) [INFO] Trying other mirror. * 2025-01-16 02:23:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:23:02 (9414) [INFO] Trying other mirror. * 2025-01-16 02:23:32 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:23:32 (9414) [INFO] Trying other mirror. * 2025-01-16 02:23:46 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:23:46 (9414) [INFO] Trying other mirror. * 2025-01-16 02:24:27 (9414) [INFO] Metadata Cache Created * 2025-01-16 02:24:27 (9431) [INFO] * 2025-01-16 02:24:27 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-16 02:24:27 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-16 02:24:27 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-16 02:24:27 (9401) [INFO] * 2025-01-16 02:24:28 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-16 02:24:28 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-16 02:24:28 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-16 02:24:28 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-16 02:24:28 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-16 02:24:28 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-16 02:24:28 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-16 02:24:28 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-16 02:24:28 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-16 02:24:28 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-16 02:24:28 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-16 02:24:28 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-16 02:24:29 (9431) [INFO] * 2025-01-16 02:24:29 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-16 02:24:29 (9401) [INFO] * 2025-01-16 02:24:29 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-16 02:24:29 (9414) [INFO] Determining fastest mirrors * 2025-01-16 02:25:01 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-16 02:25:01 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-16 02:25:01 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-16 02:25:01 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-16 02:28:04 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30539 milliseconds') * 2025-01-16 02:28:04 (9414) [INFO] Trying other mirror. * 2025-01-16 02:28:04 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30538 milliseconds') * 2025-01-16 02:28:04 (9414) [INFO] Trying other mirror. * 2025-01-16 02:28:34 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:28:34 (9414) [INFO] Trying other mirror. * 2025-01-16 02:29:05 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-16 02:29:05 (9414) [INFO] Trying other mirror. * 2025-01-16 02:30:43 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-16 02:30:43 (9414) [INFO] Trying other mirror. * 2025-01-16 02:30:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-16 02:30:44 (9414) [INFO] Trying other mirror. * 2025-01-16 02:31:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:31:14 (9414) [INFO] Trying other mirror. * 2025-01-16 02:34:02 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:34:02 (9414) [INFO] Trying other mirror. * 2025-01-16 02:35:04 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-16 02:35:04 (9414) [INFO] Trying other mirror. * 2025-01-16 02:35:35 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-16 02:35:35 (9414) [INFO] Trying other mirror. * 2025-01-16 02:36:06 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-16 02:36:06 (9414) [INFO] Trying other mirror. * 2025-01-16 02:36:36 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-16 02:36:36 (9414) [INFO] Trying other mirror. * 2025-01-17 02:04:03 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-17 02:08:03 (10480) [INFO] Script is up to date. * 2025-01-17 02:12:06 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-17 02:12:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-17 02:12:06 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-17 02:12:06 (9401) [INFO] * 2025-01-17 02:12:09 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-17 02:12:09 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-17 02:12:09 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-17 02:12:09 (9401) [INFO] * 2025-01-17 02:12:21 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-17 02:12:25 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-17 02:12:25 (9401) [INFO] * 2025-01-17 02:12:25 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-17 02:12:26 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-17 02:12:56 (9414) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-17 02:12:56 (9414) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') * 2025-01-17 02:12:56 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-17 02:12:56 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-17 02:12:56 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-17 02:12:56 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-17 02:15:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:15:43 (9414) [INFO] Trying other mirror. * 2025-01-17 02:15:59 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:15:59 (9414) [INFO] Trying other mirror. * 2025-01-17 02:16:16 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-17 02:16:16 (9414) [INFO] Trying other mirror. * 2025-01-17 02:16:31 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:16:31 (9414) [INFO] Trying other mirror. * 2025-01-17 02:17:16 (9414) [INFO] Metadata Cache Created * 2025-01-17 02:17:16 (9431) [INFO] * 2025-01-17 02:17:16 (5878) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-17 02:17:16 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-17 02:17:16 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-17 02:17:16 (9401) [INFO] * 2025-01-17 02:17:17 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-17 02:17:17 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-17 02:17:17 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-17 02:17:17 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-17 02:17:17 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-17 02:17:17 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-17 02:17:17 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-17 02:17:17 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-17 02:17:17 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-17 02:17:17 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-17 02:17:18 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-17 02:17:18 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-17 02:17:18 (9431) [INFO] * 2025-01-17 02:17:18 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-17 02:17:18 (9401) [INFO] * 2025-01-17 02:17:18 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-17 02:17:19 (9414) [INFO] Determining fastest mirrors * 2025-01-17 02:17:51 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-17 02:17:51 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-17 02:17:51 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-17 02:17:51 (9414) [INFO] * epel: dl.fedoraproject.org * 2025-01-17 02:20:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-17 02:20:54 (9414) [INFO] Trying other mirror. * 2025-01-17 02:20:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-17 02:20:54 (9414) [INFO] Trying other mirror. * 2025-01-17 02:21:24 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-17 02:21:25 (9414) [INFO] Trying other mirror. * 2025-01-17 02:23:34 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:23:34 (9414) [INFO] Trying other mirror. * 2025-01-17 02:26:23 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-17 02:26:23 (9414) [INFO] Trying other mirror. * 2025-01-17 02:26:23 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:26:23 (9414) [INFO] Trying other mirror. * 2025-01-17 02:26:54 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:26:54 (9414) [INFO] Trying other mirror. * 2025-01-17 02:27:25 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-17 02:27:25 (9414) [INFO] Trying other mirror. * 2025-01-17 02:27:55 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:27:55 (9414) [INFO] Trying other mirror. * 2025-01-17 02:28:26 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:28:26 (9414) [INFO] Trying other mirror. * 2025-01-17 02:28:26 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:28:26 (9414) [INFO] Trying other mirror. * 2025-01-17 02:28:56 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-17 02:28:56 (9414) [INFO] Trying other mirror. * 2025-01-17 02:29:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-17 02:29:26 (9414) [INFO] Trying other mirror. * 2025-01-17 02:29:57 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:29:57 (9414) [INFO] Trying other mirror. * 2025-01-17 02:29:57 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:29:57 (9414) [INFO] Trying other mirror. * 2025-01-17 02:30:28 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-01-17 02:30:28 (9414) [INFO] Trying other mirror. * 2025-01-17 02:30:28 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-17 02:30:28 (9414) [INFO] Trying other mirror. * 2025-01-17 02:30:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:30:28 (9414) [INFO] Trying other mirror. * 2025-01-17 02:30:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:30:58 (9414) [INFO] Trying other mirror. * 2025-01-17 02:31:29 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:31:29 (9414) [INFO] Trying other mirror. * 2025-01-17 02:31:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:31:29 (9414) [INFO] Trying other mirror. * 2025-01-17 02:31:59 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-17 02:31:59 (9414) [INFO] Trying other mirror. * 2025-01-17 02:31:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-17 02:31:59 (9414) [INFO] Trying other mirror. * 2025-01-17 02:32:30 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-17 02:32:30 (9414) [INFO] Trying other mirror. * 2025-01-17 02:33:01 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-17 02:33:01 (9414) [INFO] Trying other mirror. * 2025-01-18 01:47:15 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-18 01:51:15 (10480) [INFO] Script is up to date. * 2025-01-18 01:55:19 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-18 01:55:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-18 01:55:19 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-18 01:55:19 (9401) [INFO] * 2025-01-18 01:55:22 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-18 01:55:22 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-18 01:55:22 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-18 01:55:22 (9401) [INFO] * 2025-01-18 01:55:34 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-18 01:55:39 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-18 01:55:39 (9401) [INFO] * 2025-01-18 01:55:40 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-18 01:55:40 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-18 01:56:10 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-18 01:56:10 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-18 01:56:10 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-18 01:56:10 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-18 01:58:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-18 01:58:56 (9414) [INFO] Trying other mirror. * 2025-01-18 01:58:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-01-18 01:58:56 (9414) [INFO] Trying other mirror. * 2025-01-18 01:59:45 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 01:59:45 (9414) [INFO] Trying other mirror. * 2025-01-18 01:59:45 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-18 01:59:45 (9414) [INFO] Trying other mirror. * 2025-01-18 02:00:29 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-18 02:00:29 (9414) [INFO] Trying other mirror. * 2025-01-18 02:00:29 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') * 2025-01-18 02:00:29 (9414) [INFO] Trying other mirror. * 2025-01-18 02:00:47 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:00:47 (9414) [INFO] Trying other mirror. * 2025-01-18 02:01:17 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:01:17 (9414) [INFO] Trying other mirror. * 2025-01-18 02:01:17 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:01:17 (9414) [INFO] Trying other mirror. * 2025-01-18 02:01:48 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-18 02:01:48 (9414) [INFO] Trying other mirror. * 2025-01-18 02:01:48 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:01:48 (9414) [INFO] Trying other mirror. * 2025-01-18 02:02:19 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:02:19 (9414) [INFO] Trying other mirror. * 2025-01-18 02:02:19 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:02:19 (9414) [INFO] Trying other mirror. * 2025-01-18 02:02:49 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:02:49 (9414) [INFO] Trying other mirror. * 2025-01-18 02:02:50 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-18 02:02:50 (9414) [INFO] Trying other mirror. * 2025-01-18 02:03:20 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:03:20 (9414) [INFO] Trying other mirror. * 2025-01-18 02:03:21 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:03:21 (9414) [INFO] Trying other mirror. * 2025-01-18 02:03:51 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-18 02:03:51 (9414) [INFO] Trying other mirror. * 2025-01-18 02:04:22 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:04:22 (9414) [INFO] Trying other mirror. * 2025-01-18 02:04:22 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-18 02:04:22 (9414) [INFO] Trying other mirror. * 2025-01-18 02:04:22 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-01-18 02:04:22 (9414) [INFO] Trying other mirror. * 2025-01-18 02:04:52 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:04:52 (9414) [INFO] Trying other mirror. * 2025-01-18 02:04:52 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-18 02:04:52 (9414) [INFO] Trying other mirror. * 2025-01-18 02:05:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-18 02:05:23 (9414) [INFO] Trying other mirror. * 2025-01-18 02:05:23 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-18 02:05:23 (9414) [INFO] Trying other mirror. * 2025-01-18 02:05:23 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-18 02:05:23 (9414) [INFO] Trying other mirror. * 2025-01-18 02:05:54 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:05:54 (9414) [INFO] Trying other mirror. * 2025-01-18 02:05:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-18 02:05:54 (9414) [INFO] Trying other mirror. * 2025-01-18 02:06:25 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-18 02:06:25 (9414) [INFO] Trying other mirror. * 2025-01-18 02:06:25 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-18 02:06:25 (9414) [INFO] Trying other mirror. * 2025-01-18 02:06:25 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-18 02:06:25 (9414) [INFO] Trying other mirror. * 2025-01-18 02:06:55 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:06:55 (9414) [INFO] Trying other mirror. * 2025-01-18 02:06:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-18 02:06:56 (9414) [INFO] Trying other mirror. * 2025-01-18 02:07:26 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:07:26 (9414) [INFO] Trying other mirror. * 2025-01-18 02:07:26 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:07:26 (9414) [INFO] Trying other mirror. * 2025-01-18 02:07:57 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-18 02:07:57 (9414) [INFO] Trying other mirror. * 2025-01-18 02:07:57 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') * 2025-01-18 02:07:57 (9414) [INFO] Trying other mirror. * 2025-01-18 02:08:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-18 02:08:58 (9414) [INFO] Trying other mirror. * 2025-01-18 02:09:28 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-18 02:09:28 (9414) [INFO] Trying other mirror. * 2025-01-18 02:10:24 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-18 02:10:24 (9414) [INFO] Trying other mirror. * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] One of the configured repositories failed (Unknown), * 2025-01-18 02:10:54 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-18 02:10:54 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-18 02:10:54 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-18 02:10:54 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-18 02:10:54 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-18 02:10:54 (9414) [INFO] yum --disablerepo= ... * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-18 02:10:54 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-18 02:10:54 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] yum-config-manager --disable * 2025-01-18 02:10:54 (9414) [INFO] or * 2025-01-18 02:10:54 (9414) [INFO] subscription-manager repos --disable= * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-18 02:10:54 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-18 02:10:54 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-18 02:10:54 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-18 02:10:54 (9414) [INFO] compromise: * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-18 02:10:54 (9414) [INFO] * 2025-01-18 02:10:54 (9414) [INFO] updates: Check uncompressed DB failed * 2025-01-18 02:10:55 (9431) [INFO] * 2025-01-18 02:10:55 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') 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 updates: Check uncompressed DB failed * 2025-01-18 02:10:55 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-18 02:10:55 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-18 02:10:55 (9401) [INFO] * 2025-01-18 02:10:55 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-18 02:10:55 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-18 02:10:55 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-18 02:10:55 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-18 02:10:55 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-18 02:10:55 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-18 02:10:55 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-18 02:10:55 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-18 02:10:55 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-18 02:10:55 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-18 02:10:56 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-18 02:10:56 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-18 02:10:56 (9431) [INFO] * 2025-01-18 02:10:56 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-18 02:10:56 (9401) [INFO] * 2025-01-18 02:10:57 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-18 02:10:57 (9414) [INFO] Determining fastest mirrors * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] One of the configured repositories failed (Unknown), * 2025-01-18 02:11:28 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-18 02:11:28 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-18 02:11:28 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-18 02:11:28 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-18 02:11:28 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-18 02:11:28 (9414) [INFO] yum --disablerepo= ... * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-18 02:11:28 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-18 02:11:28 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] yum-config-manager --disable * 2025-01-18 02:11:28 (9414) [INFO] or * 2025-01-18 02:11:28 (9414) [INFO] subscription-manager repos --disable= * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-18 02:11:28 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-18 02:11:28 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-18 02:11:28 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-18 02:11:28 (9414) [INFO] compromise: * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-18 02:11:28 (9414) [INFO] * 2025-01-18 02:11:28 (9414) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-18 02:11:28 (9431) [INFO] * 2025-01-18 02:11:28 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-18 02:11:28 (5889) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-18 02:11:29 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-18 02:11:29 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-18 02:11:29 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-18 02:11:29 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-18 02:11:29 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-18 02:11:35 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uYcsgiUHXe/ea_profile.json * 2025-01-19 01:56:50 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-19 02:00:51 (10480) [INFO] Script is up to date. * 2025-01-19 02:04:53 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-19 02:04:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-19 02:04:54 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-19 02:04:54 (9401) [INFO] * 2025-01-19 02:04:56 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-19 02:04:56 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-19 02:04:56 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-19 02:04:56 (9401) [INFO] * 2025-01-19 02:05:09 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-19 02:05:13 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-19 02:05:13 (9401) [INFO] * 2025-01-19 02:05:13 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-19 02:05:14 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-19 02:05:44 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-19 02:05:44 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-19 02:05:44 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-19 02:05:44 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-19 02:08:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:08:29 (9414) [INFO] Trying other mirror. * 2025-01-19 02:08:47 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-19 02:08:47 (9414) [INFO] Trying other mirror. * 2025-01-19 02:09:17 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:09:17 (9414) [INFO] Trying other mirror. * 2025-01-19 02:09:18 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:09:18 (9414) [INFO] Trying other mirror. * 2025-01-19 02:09:49 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-19 02:09:49 (9414) [INFO] Trying other mirror. * 2025-01-19 02:10:31 (9414) [INFO] Metadata Cache Created * 2025-01-19 02:10:31 (9431) [INFO] * 2025-01-19 02:10:31 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-01-19 02:10:31 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-19 02:10:31 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-19 02:10:31 (9401) [INFO] * 2025-01-19 02:10:31 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-19 02:10:31 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-19 02:10:31 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-19 02:10:31 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-19 02:10:31 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-19 02:10:31 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-19 02:10:31 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-19 02:10:31 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-19 02:10:31 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-19 02:10:31 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-19 02:10:32 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-19 02:10:32 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-19 02:10:32 (9431) [INFO] * 2025-01-19 02:10:32 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-19 02:10:32 (9401) [INFO] * 2025-01-19 02:10:32 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-19 02:10:33 (9414) [INFO] Determining fastest mirrors * 2025-01-19 02:11:05 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-19 02:11:05 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-19 02:11:05 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-19 02:11:05 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-19 02:14:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30536 milliseconds') * 2025-01-19 02:14:09 (9414) [INFO] Trying other mirror. * 2025-01-19 02:14:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-19 02:14:09 (9414) [INFO] Trying other mirror. * 2025-01-19 02:14:40 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-19 02:14:40 (9414) [INFO] Trying other mirror. * 2025-01-19 02:15:10 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-19 02:15:10 (9414) [INFO] Trying other mirror. * 2025-01-19 02:16:49 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:16:49 (9414) [INFO] Trying other mirror. * 2025-01-19 02:16:49 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:16:49 (9414) [INFO] Trying other mirror. * 2025-01-19 02:20:08 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:20:08 (9414) [INFO] Trying other mirror. * 2025-01-19 02:21:10 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:21:10 (9414) [INFO] Trying other mirror. * 2025-01-19 02:21:40 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:21:40 (9414) [INFO] Trying other mirror. * 2025-01-19 02:21:41 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-19 02:21:41 (9414) [INFO] Trying other mirror. * 2025-01-19 02:22:12 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-19 02:22:12 (9414) [INFO] Trying other mirror. * 2025-01-19 02:22:42 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-19 02:22:42 (9414) [INFO] Trying other mirror. * 2025-01-19 02:23:13 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-19 02:23:13 (9414) [INFO] Trying other mirror. * 2025-01-19 02:24:36 (9414) [INFO] Metadata Cache Created * 2025-01-19 02:24:36 (9431) [INFO] * 2025-01-19 02:24:36 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-19 02:24:36 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-19 02:24:37 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-19 02:24:37 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-19 02:24:37 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-19 02:24:37 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-19 02:24:37 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-19 02:24:44 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tsag66f73O/ea_profile.json * 2025-01-19 02:24:46 (8548) [INFO] Backed up EA4 profile to /tmp/tsag66f73O/ea_profile.json * 2025-01-19 02:24:47 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-19 02:24:50 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-01-19 02:25:21 (641) [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. * 2025-01-19 02:25:21 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-20 01:55:22 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-20 01:59:22 (10480) [INFO] Script is up to date. * 2025-01-20 02:03:26 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-20 02:03:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-20 02:03:26 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-20 02:03:26 (9401) [INFO] * 2025-01-20 02:03:30 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-20 02:03:30 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-20 02:03:30 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-20 02:03:30 (9401) [INFO] * 2025-01-20 02:03:40 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-20 02:03:43 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-20 02:03:43 (9401) [INFO] * 2025-01-20 02:03:44 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-20 02:03:44 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-20 02:04:14 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-20 02:04:14 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-20 02:04:14 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-20 02:04:14 (9414) [INFO] * epel: mirror.math.princeton.edu * 2025-01-20 02:06:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:06:59 (9414) [INFO] Trying other mirror. * 2025-01-20 02:07:16 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:07:16 (9414) [INFO] Trying other mirror. * 2025-01-20 02:07:34 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-20 02:07:34 (9414) [INFO] Trying other mirror. * 2025-01-20 02:07:49 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:07:49 (9414) [INFO] Trying other mirror. * 2025-01-20 02:08:05 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') * 2025-01-20 02:08:05 (9414) [INFO] Trying other mirror. * 2025-01-20 02:08:36 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-20 02:08:36 (9414) [INFO] Trying other mirror. * 2025-01-20 02:09:19 (9414) [INFO] Metadata Cache Created * 2025-01-20 02:09:19 (9431) [INFO] * 2025-01-20 02:09:19 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-01-20 02:09:19 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-20 02:09:19 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-20 02:09:19 (9401) [INFO] * 2025-01-20 02:09:19 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-20 02:09:20 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-20 02:09:20 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-20 02:09:20 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-20 02:09:20 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-20 02:09:20 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-20 02:09:20 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-20 02:09:20 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-20 02:09:20 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-20 02:09:20 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-20 02:09:21 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-20 02:09:21 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-20 02:09:21 (9431) [INFO] * 2025-01-20 02:09:21 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-20 02:09:21 (9401) [INFO] * 2025-01-20 02:09:21 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-20 02:09:22 (9414) [INFO] Determining fastest mirrors * 2025-01-20 02:09:56 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-20 02:09:56 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-20 02:09:56 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-20 02:09:56 (9414) [INFO] * epel: mirror.math.princeton.edu * 2025-01-20 02:12:58 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:12:58 (9414) [INFO] Trying other mirror. * 2025-01-20 02:12:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-20 02:12:59 (9414) [INFO] Trying other mirror. * 2025-01-20 02:13:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-20 02:13:29 (9414) [INFO] Trying other mirror. * 2025-01-20 02:15:39 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-20 02:15:39 (9414) [INFO] Trying other mirror. * 2025-01-20 02:18:28 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:18:28 (9414) [INFO] Trying other mirror. * 2025-01-20 02:18:28 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-20 02:18:28 (9414) [INFO] Trying other mirror. * 2025-01-20 02:19:29 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:19:29 (9414) [INFO] Trying other mirror. * 2025-01-20 02:19:30 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-20 02:19:30 (9414) [INFO] Trying other mirror. * 2025-01-20 02:20:00 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:20:00 (9414) [INFO] Trying other mirror. * 2025-01-20 02:20:00 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:20:00 (9414) [INFO] Trying other mirror. * 2025-01-20 02:21:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-20 02:21:02 (9414) [INFO] Trying other mirror. * 2025-01-20 02:22:19 (9414) [INFO] Metadata Cache Created * 2025-01-20 02:22:19 (9431) [INFO] * 2025-01-20 02:22:19 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-20 02:22:19 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-20 02:22:20 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-20 02:22:20 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-20 02:22:20 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-20 02:22:20 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-20 02:22:20 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-20 02:22:25 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/v_ZltFXdri/ea_profile.json * 2025-01-20 02:22:27 (8548) [INFO] Backed up EA4 profile to /tmp/v_ZltFXdri/ea_profile.json * 2025-01-20 02:22:28 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-20 02:22:32 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-01-20 02:23:02 (641) [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. * 2025-01-20 02:23:02 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-21 01:59:32 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-21 02:03:32 (10480) [INFO] Script is up to date. * 2025-01-21 02:07:36 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-21 02:07:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-21 02:07:36 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-21 02:07:36 (9401) [INFO] * 2025-01-21 02:07:39 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-21 02:07:39 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-21 02:07:39 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-21 02:07:39 (9401) [INFO] * 2025-01-21 02:07:48 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-21 02:07:52 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-21 02:07:52 (9401) [INFO] * 2025-01-21 02:07:52 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-21 02:07:53 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-21 02:08:23 (9414) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-21 02:08:23 (9414) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30539 milliseconds') * 2025-01-21 02:08:23 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-21 02:08:23 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-21 02:08:23 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-21 02:08:23 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-21 02:09:10 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-21 02:09:10 (9414) [INFO] Trying other mirror. * 2025-01-21 02:11:40 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-21 02:11:40 (9414) [INFO] Trying other mirror. * 2025-01-21 02:11:56 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-21 02:11:56 (9414) [INFO] Trying other mirror. * 2025-01-21 02:12:13 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-21 02:12:13 (9414) [INFO] Trying other mirror. * 2025-01-21 02:12:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-21 02:12:26 (9414) [INFO] Trying other mirror. * 2025-01-21 02:12:28 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-21 02:12:28 (9414) [INFO] Trying other mirror. * 2025-01-21 02:12:43 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-21 02:12:43 (9414) [INFO] Trying other mirror. * 2025-01-21 02:12:58 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-21 02:12:58 (9414) [INFO] Trying other mirror. * 2025-01-21 02:13:14 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-21 02:13:14 (9414) [INFO] Trying other mirror. * 2025-01-21 02:13:45 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-21 02:13:45 (9414) [INFO] Trying other mirror. * 2025-01-21 02:14:15 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-21 02:14:15 (9414) [INFO] Trying other mirror. * 2025-01-21 02:15:02 (9414) [INFO] Metadata Cache Created * 2025-01-21 02:15:02 (9431) [INFO] * 2025-01-21 02:15:02 (5878) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30539 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-21 02:15:02 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-21 02:15:02 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-21 02:15:02 (9401) [INFO] * 2025-01-21 02:15:03 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-21 02:15:03 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-21 02:15:03 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-21 02:15:03 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-21 02:15:03 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-21 02:15:03 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-21 02:15:03 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-21 02:15:03 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-21 02:15:03 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-21 02:15:03 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-21 02:15:04 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-21 02:15:04 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-21 02:15:04 (9431) [INFO] * 2025-01-21 02:15:04 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-21 02:15:04 (9401) [INFO] * 2025-01-21 02:15:04 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-21 02:15:05 (9414) [INFO] Determining fastest mirrors * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] One of the configured repositories failed (Unknown), * 2025-01-21 02:15:36 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-21 02:15:36 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-21 02:15:36 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-21 02:15:36 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-21 02:15:36 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-21 02:15:36 (9414) [INFO] yum --disablerepo= ... * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-21 02:15:36 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-21 02:15:36 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] yum-config-manager --disable * 2025-01-21 02:15:36 (9414) [INFO] or * 2025-01-21 02:15:36 (9414) [INFO] subscription-manager repos --disable= * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-21 02:15:36 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-21 02:15:36 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-21 02:15:36 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-21 02:15:36 (9414) [INFO] compromise: * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-21 02:15:36 (9414) [INFO] * 2025-01-21 02:15:36 (9414) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-21 02:15:36 (9431) [INFO] * 2025-01-21 02:15:36 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-21 02:15:36 (5889) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-21 02:15:37 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-21 02:15:37 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-21 02:15:37 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-21 02:15:37 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-21 02:15:37 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-21 02:25:46 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tO85EjMq49/ea_profile.json * 2025-01-22 01:59:58 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-22 02:03:58 (10480) [INFO] Script is up to date. * 2025-01-22 02:08:00 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-22 02:08:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-22 02:08:01 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-22 02:08:01 (9401) [INFO] * 2025-01-22 02:10:29 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-22 02:10:29 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-22 02:10:29 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-22 02:10:29 (9401) [INFO] * 2025-01-22 02:10:42 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-22 02:10:46 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-22 02:10:46 (9401) [INFO] * 2025-01-22 02:10:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-22 02:10:47 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-22 02:11:18 (9414) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-22 02:11:18 (9414) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30544 milliseconds') * 2025-01-22 02:11:18 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-22 02:11:18 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-22 02:11:18 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-22 02:11:18 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-22 02:14:03 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:14:03 (9414) [INFO] Trying other mirror. * 2025-01-22 02:14:19 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:14:19 (9414) [INFO] Trying other mirror. * 2025-01-22 02:14:50 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-22 02:14:50 (9414) [INFO] Trying other mirror. * 2025-01-22 02:15:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:15:02 (9414) [INFO] Trying other mirror. * 2025-01-22 02:15:46 (9414) [INFO] Metadata Cache Created * 2025-01-22 02:15:46 (9431) [INFO] * 2025-01-22 02:15:46 (5878) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30544 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-22 02:15:46 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-22 02:15:46 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-22 02:15:46 (9401) [INFO] * 2025-01-22 02:15:47 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-22 02:15:47 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-22 02:15:47 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-22 02:15:47 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-22 02:15:47 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-22 02:15:47 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-22 02:15:47 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-22 02:15:47 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-22 02:15:47 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-22 02:15:47 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-22 02:15:48 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-22 02:15:48 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-22 02:15:48 (9431) [INFO] * 2025-01-22 02:15:48 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-22 02:15:48 (9401) [INFO] * 2025-01-22 02:15:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-22 02:15:49 (9414) [INFO] Determining fastest mirrors * 2025-01-22 02:16:25 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-22 02:16:25 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-22 02:16:25 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-22 02:16:25 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-22 02:19:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:19:28 (9414) [INFO] Trying other mirror. * 2025-01-22 02:19:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-22 02:19:28 (9414) [INFO] Trying other mirror. * 2025-01-22 02:19:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-22 02:19:59 (9414) [INFO] Trying other mirror. * 2025-01-22 02:20:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-22 02:20:29 (9414) [INFO] Trying other mirror. * 2025-01-22 02:22:08 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:22:08 (9414) [INFO] Trying other mirror. * 2025-01-22 02:25:27 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-22 02:25:27 (9414) [INFO] Trying other mirror. * 2025-01-22 02:25:27 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-22 02:25:27 (9414) [INFO] Trying other mirror. * 2025-01-22 02:26:29 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:26:29 (9414) [INFO] Trying other mirror. * 2025-01-22 02:26:30 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-22 02:26:30 (9414) [INFO] Trying other mirror. * 2025-01-22 02:27:31 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-22 02:27:31 (9414) [INFO] Trying other mirror. * 2025-01-22 02:28:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-22 02:28:02 (9414) [INFO] Trying other mirror. * 2025-01-22 02:29:21 (9414) [INFO] Metadata Cache Created * 2025-01-22 02:29:21 (9431) [INFO] * 2025-01-22 02:29:21 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-22 02:29:21 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-22 02:29:22 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-22 02:29:22 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-22 02:29:22 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-22 02:29:22 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-22 02:29:22 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-22 02:29:35 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kbgbM_Grmy/ea_profile.json * 2025-01-22 02:29:37 (8548) [INFO] Backed up EA4 profile to /tmp/kbgbM_Grmy/ea_profile.json * 2025-01-22 02:29:38 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-22 02:29:40 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-01-23 01:53:25 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-23 01:57:25 (10480) [INFO] Script is up to date. * 2025-01-23 02:01:29 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-23 02:01:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-23 02:01:29 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-23 02:01:29 (9401) [INFO] * 2025-01-23 02:07:09 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-23 02:07:09 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-23 02:07:09 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-23 02:07:09 (9401) [INFO] * 2025-01-23 02:07:20 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-23 02:07:23 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-23 02:07:23 (9401) [INFO] * 2025-01-23 02:07:23 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-23 02:07:24 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-23 02:07:54 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-23 02:07:54 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-23 02:07:54 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-23 02:07:54 (9414) [INFO] * epel: mirror.math.princeton.edu * 2025-01-23 02:08:41 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-23 02:08:41 (9414) [INFO] Trying other mirror. * 2025-01-23 02:11:10 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-23 02:11:10 (9414) [INFO] Trying other mirror. * 2025-01-23 02:11:27 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-23 02:11:27 (9414) [INFO] Trying other mirror. * 2025-01-23 02:12:00 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-23 02:12:00 (9414) [INFO] Trying other mirror. * 2025-01-23 02:12:31 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-23 02:12:31 (9414) [INFO] Trying other mirror. * 2025-01-23 02:13:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-01-23 02:13:02 (9414) [INFO] Trying other mirror. * 2025-01-23 02:13:32 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-23 02:13:32 (9414) [INFO] Trying other mirror. * 2025-01-23 02:14:03 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-23 02:14:03 (9414) [INFO] Trying other mirror. * 2025-01-23 02:14:34 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-23 02:14:34 (9414) [INFO] Trying other mirror. * 2025-01-23 02:15:04 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-23 02:15:04 (9414) [INFO] Trying other mirror. * 2025-01-23 02:15:48 (9414) [INFO] Metadata Cache Created * 2025-01-23 02:15:48 (9431) [INFO] * 2025-01-23 02:15:48 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-23 02:15:48 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-23 02:15:48 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-23 02:15:48 (9401) [INFO] * 2025-01-23 02:15:49 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-23 02:15:49 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-23 02:15:49 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-23 02:15:49 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-23 02:15:49 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-23 02:15:49 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-23 02:15:49 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-23 02:15:49 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-23 02:15:49 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-23 02:15:49 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-23 02:15:50 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-23 02:15:50 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-23 02:15:50 (9431) [INFO] * 2025-01-23 02:15:50 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-23 02:15:50 (9401) [INFO] * 2025-01-23 02:15:50 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-23 02:15:51 (9414) [INFO] Determining fastest mirrors * 2025-01-23 02:16:23 (9414) [INFO] * EA4: 208.74.123.62 * 2025-01-23 02:16:23 (9414) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-01-23 02:16:23 (9414) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-01-23 02:16:23 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-23 02:17:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-23 02:17:09 (9414) [INFO] Trying other mirror. * 2025-01-23 02:17:40 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-23 02:17:40 (9414) [INFO] Trying other mirror. * 2025-01-23 02:20:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-23 02:20:28 (9414) [INFO] Trying other mirror. * 2025-01-23 02:20:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-23 02:20:28 (9414) [INFO] Trying other mirror. * 2025-01-23 02:20:58 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-23 02:20:58 (9414) [INFO] Trying other mirror. * 2025-01-23 02:21:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-23 02:21:29 (9414) [INFO] Trying other mirror. * 2025-01-23 02:23:09 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-23 02:23:09 (9414) [INFO] Trying other mirror. * 2025-01-23 02:23:09 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-23 02:23:09 (9414) [INFO] Trying other mirror. * 2025-01-24 01:46:56 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-24 01:50:56 (10480) [INFO] Script is up to date. * 2025-01-24 01:55:00 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-24 01:55:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-24 01:55:00 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-24 01:55:00 (9401) [INFO] * 2025-01-24 01:55:11 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-24 01:55:11 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-24 01:55:11 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-24 01:55:11 (9401) [INFO] * 2025-01-24 01:55:23 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-24 01:55:26 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-24 01:55:26 (9401) [INFO] * 2025-01-24 01:55:26 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-24 01:55:27 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-24 01:55:57 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-24 01:55:57 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-24 01:55:57 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-24 01:55:57 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-24 01:56:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-24 01:56:44 (9414) [INFO] Trying other mirror. * 2025-01-24 01:59:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 01:59:14 (9414) [INFO] Trying other mirror. * 2025-01-24 01:59:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-24 01:59:14 (9414) [INFO] Trying other mirror. * 2025-01-24 01:59:34 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 01:59:34 (9414) [INFO] Trying other mirror. * 2025-01-24 01:59:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-24 01:59:44 (9414) [INFO] Trying other mirror. * 2025-01-24 02:00:20 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:00:20 (9414) [INFO] Trying other mirror. * 2025-01-24 02:00:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-24 02:00:43 (9414) [INFO] Trying other mirror. * 2025-01-24 02:01:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-24 02:01:14 (9414) [INFO] Trying other mirror. * 2025-01-24 02:01:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-24 02:01:14 (9414) [INFO] Trying other mirror. * 2025-01-24 02:01:45 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:01:45 (9414) [INFO] Trying other mirror. * 2025-01-24 02:01:45 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-24 02:01:45 (9414) [INFO] Trying other mirror. * 2025-01-24 02:01:46 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30988 milliseconds') * 2025-01-24 02:01:46 (9414) [INFO] Trying other mirror. * 2025-01-24 02:02:16 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-24 02:02:16 (9414) [INFO] Trying other mirror. * 2025-01-24 02:02:16 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-24 02:02:16 (9414) [INFO] Trying other mirror. * 2025-01-24 02:02:46 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:02:46 (9414) [INFO] Trying other mirror. * 2025-01-24 02:02:46 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:02:46 (9414) [INFO] Trying other mirror. * 2025-01-24 02:02:46 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') * 2025-01-24 02:02:46 (9414) [INFO] Trying other mirror. * 2025-01-24 02:03:17 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30567 milliseconds') * 2025-01-24 02:03:17 (9414) [INFO] Trying other mirror. * 2025-01-24 02:03:47 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:03:47 (9414) [INFO] Trying other mirror. * 2025-01-24 02:03:47 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:03:47 (9414) [INFO] Trying other mirror. * 2025-01-24 02:03:48 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-24 02:03:48 (9414) [INFO] Trying other mirror. * 2025-01-24 02:04:48 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:04:48 (9414) [INFO] Trying other mirror. * 2025-01-24 02:04:48 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-24 02:04:48 (9414) [INFO] Trying other mirror. * 2025-01-24 02:05:18 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-24 02:05:18 (9414) [INFO] Trying other mirror. * 2025-01-24 02:05:18 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:05:18 (9414) [INFO] Trying other mirror. * 2025-01-24 02:06:20 (9414) [INFO] Metadata Cache Created * 2025-01-24 02:06:21 (9431) [INFO] * 2025-01-24 02:06:21 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30988 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30567 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-24 02:06:21 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-24 02:06:21 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-24 02:06:21 (9401) [INFO] * 2025-01-24 02:06:21 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-24 02:06:21 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-24 02:06:21 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-24 02:06:21 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-24 02:06:21 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-24 02:06:21 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-24 02:06:21 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-24 02:06:21 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-24 02:06:21 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-24 02:06:21 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-24 02:06:22 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-24 02:06:22 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-24 02:06:22 (9431) [INFO] * 2025-01-24 02:06:22 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-24 02:06:22 (9401) [INFO] * 2025-01-24 02:06:22 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-24 02:06:23 (9414) [INFO] Determining fastest mirrors * 2025-01-24 02:06:56 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-24 02:06:56 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-24 02:06:56 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-24 02:06:56 (9414) [INFO] * epel: mirror.math.princeton.edu * 2025-01-24 02:07:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-24 02:07:43 (9414) [INFO] Trying other mirror. * 2025-01-24 02:08:13 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-24 02:08:13 (9414) [INFO] Trying other mirror. * 2025-01-24 02:08:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-24 02:08:44 (9414) [INFO] Trying other mirror. * 2025-01-24 02:09:15 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-24 02:09:15 (9414) [INFO] Trying other mirror. * 2025-01-24 02:12:02 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-24 02:12:02 (9414) [INFO] Trying other mirror. * 2025-01-24 02:12:02 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-24 02:12:02 (9414) [INFO] Trying other mirror. * 2025-01-24 02:12:32 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-01-24 02:12:32 (9414) [INFO] Trying other mirror. * 2025-01-24 02:12:33 (9414) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/15780798c62a86df35d30c99d51cbeeb5e97fb8ac027c4a93d53aabac46b8f61-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:12:33 (9414) [INFO] Trying other mirror. * 2025-01-24 02:12:49 (9414) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-01-24 02:12:49 (9414) [INFO] Trying other mirror. * 2025-01-24 02:13:05 (9414) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:13:05 (9414) [INFO] Trying other mirror. * 2025-01-24 02:13:20 (9414) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:13:20 (9414) [INFO] Trying other mirror. * 2025-01-24 02:13:36 (9414) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:13:36 (9414) [INFO] Trying other mirror. * 2025-01-24 02:13:52 (9414) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:13:52 (9414) [INFO] Trying other mirror. * 2025-01-24 02:14:07 (9414) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:14:07 (9414) [INFO] Trying other mirror. * 2025-01-24 02:14:10 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:14:10 (9414) [INFO] Trying other mirror. * 2025-01-24 02:14:37 (9414) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/7daade9c3562c6dde7c43961bb58a03e2811c07f670231eacdf6748167050a66-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:14:37 (9414) [INFO] Trying other mirror. * 2025-01-24 02:14:41 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30065 milliseconds') * 2025-01-24 02:14:41 (9414) [INFO] Trying other mirror. * 2025-01-24 02:14:53 (9414) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM3NjI1MjE2OjE3Mzc4ODQ0MTY6P5DLNngOOGkgy4TVFby_je3W52UdQ7Nvm0GAkoasXbhsx0vxstJfDvBqWwSRVUSI0it6QOHnjYteV-W-F2ViJZPpVUm9Rdp6Ra6bxpZ1gWk1KO_C_YeWpipP2cgvivTKpy1HU4bB274Nb1jIoKxpQp4yHIhwbmnogiPt8UBSWYNdvNxt6FUzbIeAigwiCpoZK0TM4mY-4cgyRl5_zMrjQxhhmr-4mgngjyUu2w5uWLnUcPaR5NaF3eY_a6H3d0YkPX1ui9HZI3cjssgOGG0_U325Sy9Mpy37uLFenktSkR-dV94n20NyRnOzureTHeEszWYMEfNmibR_TflJp0WRphIHdBKhhY9CoBuwnvdbhZqKXfwz1pne8KCimQt74sRJAB9la3dRE2VQ_lwEGnvWU7oPYHrM2jypIYGCCC9T8iEOJDpdr77rlynjvJNB8o-ep2MJx9WUYfHI0pCzWzzJl2XHt_XiPfBxiDVHwSHFjVWk55O3sEGlgfiCercQIIwSWt5YJ_3G9K-PNFqOy3GuuaxaedR8SJU3qVmY2cAAWsdsuiQ5NefUdCix2ULuOEx4-mpFyXnUQuHiu7oLB8nDn_J6taZDL2fd3NwA2xn9tE_sqkx3Dw_h3Zf_6PF3ERTsKduUaGq88c-uCDS3aqivC1RuzAQqF3iU26HgAVhYL4Q%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:14:53 (9414) [INFO] Trying other mirror. * 2025-01-24 02:15:08 (9414) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM3NjI1MjE2OjE3Mzc4ODQ0MTY6P5DLNngOOGkgy4TVFby_je3W52UdQ7Nvm0GAkoasXbhsx0vxstJfDvBqWwSRVUSI0it6QOHnjYteV-W-F2ViJZPpVUm9Rdp6Ra6bxpZ1gWk1KO_C_YeWpipP2cgvivTKpy1HU4bB274Nb1jIoKxpQp4yHIhwbmnogiPt8UBSWYNdvNxt6FUzbIeAigwiCpoZK0TM4mY-4cgyRl5_zMrjQxhhmr-4mgngjyUu2w5uWLnUcPaR5NaF3eY_a6H3d0YkPX1ui9HZI3cjssgOGG0_U325Sy9Mpy37uLFenktSkR-dV94n20NyRnOzureTHeEszWYMEfNmibR_TflJp0WRphIHdBKhhY9CoBuwnvdbhZqKXfwz1pne8KCimQt74sRJAB9la3dRE2VQ_lwEGnvWU7oPYHrM2jypIYGCCC9T8iEOJDpdr77rlynjvJNB8o-ep2MJx9WUYfHI0pCzWzzJl2XHt_XiPfBxiDVHwSHFjVWk55O3sEGlgfiCercQIIwSWt5YJ_3G9K-PNFqOy3GuuaxaedR8SJU3qVmY2cAAWsdsuiQ5NefUdCix2ULuOEx4-mpFyXnUQuHiu7oLB8nDn_J6taZDL2fd3NwA2xn9tE_sqkx3Dw_h3Zf_6PF3ERTsKduUaGq88c-uCDS3aqivC1RuzAQqF3iU26HgAVhYL4Q%3D/ea-php/7/updates/x86_64/repodata/338a90399ae44cf08cb8052357bf356fa8c4c77bc52ab6316d0106e2021c9ea4-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:15:08 (9414) [INFO] Trying other mirror. * 2025-01-24 02:15:24 (9414) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:15:24 (9414) [INFO] Trying other mirror. * 2025-01-24 02:15:39 (9414) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:15:39 (9414) [INFO] Trying other mirror. * 2025-01-24 02:15:55 (9414) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:15:55 (9414) [INFO] Trying other mirror. * 2025-01-24 02:16:11 (9414) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:16:11 (9414) [INFO] Trying other mirror. * 2025-01-24 02:16:27 (9414) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:16:27 (9414) [INFO] Trying other mirror. * 2025-01-24 02:16:42 (9414) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-24 02:16:42 (9414) [INFO] Trying other mirror. * 2025-01-25 01:57:28 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-25 02:01:28 (10480) [INFO] Script is up to date. * 2025-01-25 02:05:32 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-25 02:05:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-25 02:05:32 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-25 02:05:32 (9401) [INFO] * 2025-01-25 02:05:36 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-25 02:05:36 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-25 02:05:36 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-25 02:05:36 (9401) [INFO] * 2025-01-25 02:05:48 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-25 02:05:51 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-25 02:05:51 (9401) [INFO] * 2025-01-25 02:05:51 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-25 02:05:51 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-25 02:06:22 (9414) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-01-25 02:06:22 (9414) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30724 milliseconds') * 2025-01-25 02:06:22 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-25 02:06:22 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-25 02:06:22 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-25 02:06:22 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-25 02:07:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-25 02:07:09 (9414) [INFO] Trying other mirror. * 2025-01-25 02:09:39 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-25 02:09:39 (9414) [INFO] Trying other mirror. * 2025-01-25 02:09:55 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-25 02:09:55 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:11 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-25 02:10:11 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:25 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-25 02:10:25 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:26 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-25 02:10:26 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:42 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-25 02:10:42 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-01-25 02:10:56 (9414) [INFO] Trying other mirror. * 2025-01-25 02:10:57 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-25 02:10:57 (9414) [INFO] Trying other mirror. * 2025-01-25 02:11:27 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-25 02:11:27 (9414) [INFO] Trying other mirror. * 2025-01-25 02:11:58 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-25 02:11:58 (9414) [INFO] Trying other mirror. * 2025-01-25 02:12:28 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-25 02:12:28 (9414) [INFO] Trying other mirror. * 2025-01-25 02:13:12 (9414) [INFO] Metadata Cache Created * 2025-01-25 02:13:12 (9431) [INFO] * 2025-01-25 02:13:12 (5878) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30724 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-25 02:13:12 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-25 02:13:12 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-25 02:13:12 (9401) [INFO] * 2025-01-25 02:13:12 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-25 02:13:12 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-25 02:13:12 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-25 02:13:12 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-25 02:13:12 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-25 02:13:12 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-25 02:13:12 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-25 02:13:12 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-25 02:13:12 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-25 02:13:12 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-25 02:13:13 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-25 02:13:13 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-25 02:13:13 (9431) [INFO] * 2025-01-25 02:13:13 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-25 02:13:13 (9401) [INFO] * 2025-01-25 02:13:14 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-25 02:13:14 (9414) [INFO] Determining fastest mirrors * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] One of the configured repositories failed (Unknown), * 2025-01-25 02:13:45 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-25 02:13:45 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-25 02:13:45 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-25 02:13:45 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-25 02:13:45 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-25 02:13:45 (9414) [INFO] yum --disablerepo= ... * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-25 02:13:45 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-25 02:13:45 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] yum-config-manager --disable * 2025-01-25 02:13:45 (9414) [INFO] or * 2025-01-25 02:13:45 (9414) [INFO] subscription-manager repos --disable= * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-25 02:13:45 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-25 02:13:45 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-25 02:13:45 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-25 02:13:45 (9414) [INFO] compromise: * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-01-25 02:13:45 (9414) [INFO] * 2025-01-25 02:13:45 (9414) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-01-25 02:13:45 (9431) [INFO] * 2025-01-25 02:13:45 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-25 02:13:45 (5889) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 * 2025-01-25 02:13:46 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-25 02:13:46 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-25 02:13:46 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-25 02:13:46 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-25 02:13:46 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-25 02:25:06 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/r9N5dQ2jUr/ea_profile.json * 2025-01-25 02:26:41 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/r9N5dQ2jUr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8527. * 2025-01-25 02:26:41 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-26 01:53:12 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-26 01:57:12 (10480) [INFO] Script is up to date. * 2025-01-26 02:01:15 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-26 02:01:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-26 02:01:15 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-26 02:01:15 (9401) [INFO] * 2025-01-26 02:01:26 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-26 02:01:26 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-26 02:01:26 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-26 02:01:26 (9401) [INFO] * 2025-01-26 02:01:37 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-26 02:01:40 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-26 02:01:40 (9401) [INFO] * 2025-01-26 02:01:40 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-26 02:01:40 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-26 02:02:10 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-26 02:02:10 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-26 02:02:10 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-26 02:02:10 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-26 02:05:26 (9414) [INFO] Metadata Cache Created * 2025-01-26 02:05:26 (9431) [INFO] * 2025-01-26 02:05:27 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-26 02:05:27 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-26 02:05:27 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-26 02:05:27 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-26 02:05:27 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-26 02:05:34 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GRXzI3Zgae/ea_profile.json * 2025-01-26 02:05:36 (8548) [INFO] Backed up EA4 profile to /tmp/GRXzI3Zgae/ea_profile.json * 2025-01-26 02:05:37 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-01-26 02:05:39 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-01-26 02:06:09 (641) [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. * 2025-01-26 02:06:09 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-27 01:56:38 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-27 02:00:38 (10480) [INFO] Script is up to date. * 2025-01-27 02:04:42 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-27 02:04:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-27 02:04:42 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-27 02:04:42 (9401) [INFO] * 2025-01-27 02:04:54 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-27 02:04:54 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-27 02:04:54 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-27 02:04:54 (9401) [INFO] * 2025-01-27 02:05:05 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-27 02:05:09 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-27 02:05:09 (9401) [INFO] * 2025-01-27 02:05:10 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-27 02:05:10 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-27 02:05:40 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-27 02:05:40 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-27 02:05:40 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-27 02:05:40 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-27 02:06:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-27 02:06:26 (9414) [INFO] Trying other mirror. * 2025-01-27 02:08:57 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:08:57 (9414) [INFO] Trying other mirror. * 2025-01-27 02:09:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:09:14 (9414) [INFO] Trying other mirror. * 2025-01-27 02:09:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-27 02:09:43 (9414) [INFO] Trying other mirror. * 2025-01-27 02:10:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:10:14 (9414) [INFO] Trying other mirror. * 2025-01-27 02:10:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:10:44 (9414) [INFO] Trying other mirror. * 2025-01-27 02:11:15 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:11:15 (9414) [INFO] Trying other mirror. * 2025-01-27 02:11:57 (9414) [INFO] Metadata Cache Created * 2025-01-27 02:11:57 (9431) [INFO] * 2025-01-27 02:11:57 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-01-27 02:11:57 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-27 02:11:57 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-27 02:11:57 (9401) [INFO] * 2025-01-27 02:11:58 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-27 02:11:58 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-27 02:11:58 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-27 02:11:58 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-27 02:11:58 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-27 02:11:58 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-27 02:11:58 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-27 02:11:58 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-27 02:11:58 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-27 02:11:58 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-27 02:11:59 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-27 02:11:59 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-27 02:11:59 (9431) [INFO] * 2025-01-27 02:11:59 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-27 02:11:59 (9401) [INFO] * 2025-01-27 02:12:00 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-27 02:12:00 (9414) [INFO] Determining fastest mirrors * 2025-01-27 02:12:31 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-27 02:12:31 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-27 02:12:31 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-27 02:12:31 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-27 02:13:18 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:13:18 (9414) [INFO] Trying other mirror. * 2025-01-27 02:13:48 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-27 02:13:48 (9414) [INFO] Trying other mirror. * 2025-01-27 02:16:36 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-27 02:16:36 (9414) [INFO] Trying other mirror. * 2025-01-27 02:16:36 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:16:36 (9414) [INFO] Trying other mirror. * 2025-01-27 02:19:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:19:14 (9414) [INFO] Trying other mirror. * 2025-01-27 02:22:03 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:22:03 (9414) [INFO] Trying other mirror. * 2025-01-27 02:22:34 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:22:34 (9414) [INFO] Trying other mirror. * 2025-01-27 02:23:04 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-27 02:23:04 (9414) [INFO] Trying other mirror. * 2025-01-27 02:23:35 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:23:35 (9414) [INFO] Trying other mirror. * 2025-01-27 02:23:35 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:23:35 (9414) [INFO] Trying other mirror. * 2025-01-27 02:24:06 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:24:06 (9414) [INFO] Trying other mirror. * 2025-01-27 02:24:36 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-27 02:24:36 (9414) [INFO] Trying other mirror. * 2025-01-27 02:25:06 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-27 02:25:06 (9414) [INFO] Trying other mirror. * 2025-01-27 02:26:28 (9414) [INFO] Metadata Cache Created * 2025-01-27 02:26:28 (9431) [INFO] * 2025-01-27 02:26:28 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-27 02:26:28 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-28 01:54:07 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-28 01:58:08 (10480) [INFO] Script is up to date. * 2025-01-28 02:02:10 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-28 02:02:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-28 02:02:10 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-28 02:02:10 (9401) [INFO] * 2025-01-28 02:02:23 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-28 02:02:23 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-28 02:02:23 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-28 02:02:23 (9401) [INFO] * 2025-01-28 02:02:36 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-28 02:02:40 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-28 02:02:40 (9401) [INFO] * 2025-01-28 02:02:40 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-28 02:02:41 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-28 02:03:11 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-28 02:03:11 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-28 02:03:11 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-28 02:03:11 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-28 02:03:57 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-28 02:03:57 (9414) [INFO] Trying other mirror. * 2025-01-28 02:06:27 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:06:27 (9414) [INFO] Trying other mirror. * 2025-01-28 02:06:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-28 02:06:44 (9414) [INFO] Trying other mirror. * 2025-01-28 02:07:13 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:07:13 (9414) [INFO] Trying other mirror. * 2025-01-28 02:07:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:07:14 (9414) [INFO] Trying other mirror. * 2025-01-28 02:07:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-28 02:07:44 (9414) [INFO] Trying other mirror. * 2025-01-28 02:07:45 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-28 02:07:45 (9414) [INFO] Trying other mirror. * 2025-01-28 02:08:28 (9414) [INFO] Metadata Cache Created * 2025-01-28 02:08:28 (9431) [INFO] * 2025-01-28 02:08:28 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-01-28 02:08:28 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-28 02:08:28 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-28 02:08:28 (9401) [INFO] * 2025-01-28 02:08:28 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-28 02:08:29 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-28 02:08:29 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-28 02:08:29 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-28 02:08:29 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-28 02:08:29 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-28 02:08:29 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-28 02:08:29 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-28 02:08:29 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-28 02:08:29 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-28 02:08:29 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-28 02:08:29 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-28 02:08:30 (9431) [INFO] * 2025-01-28 02:08:30 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-28 02:08:30 (9401) [INFO] * 2025-01-28 02:08:30 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-28 02:08:30 (9414) [INFO] Determining fastest mirrors * 2025-01-28 02:09:03 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-28 02:09:03 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-28 02:09:03 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-28 02:09:03 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-28 02:09:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-28 02:09:50 (9414) [INFO] Trying other mirror. * 2025-01-28 02:10:20 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') * 2025-01-28 02:10:20 (9414) [INFO] Trying other mirror. * 2025-01-28 02:13:07 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-28 02:13:07 (9414) [INFO] Trying other mirror. * 2025-01-28 02:13:07 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:13:07 (9414) [INFO] Trying other mirror. * 2025-01-28 02:13:38 (9414) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/0508817c1f9c0b1e19ef848bf8136f6b5b607bc4fe8fb6878733d8246cdfd261-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:13:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:13:38 (9414) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/15780798c62a86df35d30c99d51cbeeb5e97fb8ac027c4a93d53aabac46b8f61-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:13:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:13:54 (9414) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:13:54 (9414) [INFO] Trying other mirror. * 2025-01-28 02:14:10 (9414) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:14:10 (9414) [INFO] Trying other mirror. * 2025-01-28 02:14:26 (9414) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:14:26 (9414) [INFO] Trying other mirror. * 2025-01-28 02:14:41 (9414) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:14:41 (9414) [INFO] Trying other mirror. * 2025-01-28 02:14:57 (9414) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:14:57 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:13 (9414) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:13 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:13 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:13 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:15 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:15 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:15 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:15 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:42 (9414) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/93cdfd4735bb5125454e48cc376e54f59c45df7f666168147c3d47ff5d92968b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:42 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:45 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:15:45 (9414) [INFO] Trying other mirror. * 2025-01-28 02:15:57 (9414) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM3OTc0MTk0OjE3MzgyMzMzOTQ6PLxEZ4R8zoeQEWq1NLM-FvyX2x9-G64vgEI3bAgE8fekm0F_tFEWn1MTwZXPPgqPi25bSD67WNral3_gcepWVgiBJjbevvSWgagwNrcwPUBLoYke0fTuoO-kNmLqDKIjsqvEvUIc4dfF2sg6H543Tz06CBPaI9MHZr5shg5BX0iN_pHAcOQmlDsrvDM0O7MFPMM3KTIy5zM94io9ugOsgfRV5zigv3VpFStWqMqTo0PNMqLes6q3-Q0xxDInVIkVPexKvNDEa2uSoGgfcUBt0vGcYDbOwyxVSt2V_Q3FThISLMHMqOK0BhtJaWf4UmzI1znF5fbTFaZ-IhF-Dk6JoL2VgG139v09rZAzXvFhSI0cRIUfL-Ad6w4Iwy0j-RGbzUTqTL1oBvDvUy2Yep_yHL92uRdXWylDtMpJvbXq-yDpayFbe7LgRUYovBYIhGVseY56qwlKrUEe7I7BH2Qfi63Tc0aNuUogSXfEVdvB7evkNNkiI54FYhuob7KNeXMjNvbtiY3t9mR6GKb9QuPF13KCCQY2cl4Rm-wlZfxAu6Fxwu7esWGa7pAcM5RULMPLrgH-hnuXqMMCCzSxPABYrEUo-ooWYa_QbjQ19IzVB1TtjaUbSsTZ_BWbRLgPojU7ynB1s7PcTVC8G3zgEJD7X3mSjZq331TPJ08uunpk3mI%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:15:57 (9414) [INFO] Trying other mirror. * 2025-01-28 02:16:13 (9414) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM3OTc0MTk0OjE3MzgyMzMzOTQ6PLxEZ4R8zoeQEWq1NLM-FvyX2x9-G64vgEI3bAgE8fekm0F_tFEWn1MTwZXPPgqPi25bSD67WNral3_gcepWVgiBJjbevvSWgagwNrcwPUBLoYke0fTuoO-kNmLqDKIjsqvEvUIc4dfF2sg6H543Tz06CBPaI9MHZr5shg5BX0iN_pHAcOQmlDsrvDM0O7MFPMM3KTIy5zM94io9ugOsgfRV5zigv3VpFStWqMqTo0PNMqLes6q3-Q0xxDInVIkVPexKvNDEa2uSoGgfcUBt0vGcYDbOwyxVSt2V_Q3FThISLMHMqOK0BhtJaWf4UmzI1znF5fbTFaZ-IhF-Dk6JoL2VgG139v09rZAzXvFhSI0cRIUfL-Ad6w4Iwy0j-RGbzUTqTL1oBvDvUy2Yep_yHL92uRdXWylDtMpJvbXq-yDpayFbe7LgRUYovBYIhGVseY56qwlKrUEe7I7BH2Qfi63Tc0aNuUogSXfEVdvB7evkNNkiI54FYhuob7KNeXMjNvbtiY3t9mR6GKb9QuPF13KCCQY2cl4Rm-wlZfxAu6Fxwu7esWGa7pAcM5RULMPLrgH-hnuXqMMCCzSxPABYrEUo-ooWYa_QbjQ19IzVB1TtjaUbSsTZ_BWbRLgPojU7ynB1s7PcTVC8G3zgEJD7X3mSjZq331TPJ08uunpk3mI%3D/ea-php/7/updates/x86_64/repodata/338a90399ae44cf08cb8052357bf356fa8c4c77bc52ab6316d0106e2021c9ea4-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:16:13 (9414) [INFO] Trying other mirror. * 2025-01-28 02:16:29 (9414) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:16:29 (9414) [INFO] Trying other mirror. * 2025-01-28 02:16:44 (9414) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:16:44 (9414) [INFO] Trying other mirror. * 2025-01-28 02:17:00 (9414) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:17:00 (9414) [INFO] Trying other mirror. * 2025-01-28 02:17:16 (9414) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:17:16 (9414) [INFO] Trying other mirror. * 2025-01-28 02:17:31 (9414) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:17:31 (9414) [INFO] Trying other mirror. * 2025-01-28 02:17:47 (9414) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:17:47 (9414) [INFO] Trying other mirror. * 2025-01-28 02:18:03 (9414) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:18:03 (9414) [INFO] Trying other mirror. * 2025-01-28 02:18:18 (9414) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:18:18 (9414) [INFO] Trying other mirror. * 2025-01-28 02:18:48 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:18:48 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:04 (9414) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.3/wp-toolkit/repodata/615fb2c7dbd2ce86c736d868ad4e9fcae354a3418ccdc65418dd527d71a47922-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:19:04 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:19 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-28 02:19:19 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:19 (9414) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.3/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:19:19 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:49 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:19:49 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:50 (9414) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:19:50 (9414) [INFO] Trying other mirror. * 2025-01-28 02:19:50 (9414) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:19:50 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:06 (9414) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:20:06 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:20 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:20:20 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:21 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-28 02:20:21 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:37 (9414) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:20:37 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:37 (9414) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:20:37 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:51 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:20:51 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:51 (9414) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:20:51 (9414) [INFO] Trying other mirror. * 2025-01-28 02:20:51 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:20:51 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:07 (9414) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:07 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:07 (9414) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:07 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:22 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-01-28 02:21:22 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:39 (9414) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:39 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:51 (9414) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:51 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:52 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:21:52 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:53 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-28 02:21:53 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:53 (9414) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:53 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:53 (9414) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:53 (9414) [INFO] Trying other mirror. * 2025-01-28 02:21:55 (9414) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:21:55 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:23 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:23 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:23 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-28 02:22:23 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:38 (9414) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:38 (9414) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:38 (9414) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:53 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:53 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:54 (9414) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:54 (9414) [INFO] Trying other mirror. * 2025-01-28 02:22:54 (9414) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:22:54 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:08 (9414) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:08 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:08 (9414) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:08 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:09 (9414) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:09 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:23 (9414) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:23 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:38 (9414) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:38 (9414) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:38 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:52 (9414) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:52 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:54 (9414) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:54 (9414) [INFO] Trying other mirror. * 2025-01-28 02:23:55 (9414) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-01-28 02:23:55 (9414) [INFO] Trying other mirror. * 2025-01-29 01:50:43 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-29 01:54:44 (10480) [INFO] Script is up to date. * 2025-01-29 01:58:47 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-29 01:58:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-29 01:58:47 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-29 01:58:47 (9401) [INFO] * 2025-01-29 01:58:59 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-29 01:58:59 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-29 01:58:59 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-29 01:58:59 (9401) [INFO] * 2025-01-29 02:04:39 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-29 02:04:39 (9401) [INFO] * 2025-01-29 02:04:39 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-29 02:04:40 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-29 02:05:10 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-29 02:05:10 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-29 02:05:10 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-29 02:05:10 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-29 02:05:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30006 milliseconds') * 2025-01-29 02:05:56 (9414) [INFO] Trying other mirror. * 2025-01-29 02:06:27 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-29 02:06:27 (9414) [INFO] Trying other mirror. * 2025-01-29 02:06:57 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:06:57 (9414) [INFO] Trying other mirror. * 2025-01-29 02:07:27 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-29 02:07:27 (9414) [INFO] Trying other mirror. * 2025-01-29 02:07:57 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:07:57 (9414) [INFO] Trying other mirror. * 2025-01-29 02:08:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-29 02:08:28 (9414) [INFO] Trying other mirror. * 2025-01-29 02:08:58 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:08:58 (9414) [INFO] Trying other mirror. * 2025-01-29 02:09:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-29 02:09:29 (9414) [INFO] Trying other mirror. * 2025-01-29 02:09:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-29 02:09:59 (9414) [INFO] Trying other mirror. * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (9414) [INFO] Trying other mirror. * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-29 02:10:29 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-29 02:10:29 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-29 02:10:29 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-29 02:10:29 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-29 02:10:29 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-29 02:10:29 (9414) [INFO] yum --disablerepo=base ... * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-29 02:10:29 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-29 02:10:29 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] yum-config-manager --disable base * 2025-01-29 02:10:29 (9414) [INFO] or * 2025-01-29 02:10:29 (9414) [INFO] subscription-manager repos --disable=base * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-29 02:10:29 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-29 02:10:29 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-29 02:10:29 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-29 02:10:29 (9414) [INFO] compromise: * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-29 02:10:29 (9414) [INFO] * 2025-01-29 02:10:29 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30006 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-29 02:10:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (9431) [INFO] * 2025-01-29 02:10:29 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30006 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') 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. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30006 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:10:29 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-29 02:10:29 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-29 02:10:29 (9401) [INFO] * 2025-01-29 02:10:30 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-29 02:10:30 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-29 02:10:30 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-29 02:10:30 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-29 02:10:30 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-29 02:10:30 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-29 02:10:30 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-29 02:10:30 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-29 02:10:30 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-29 02:10:30 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-29 02:10:30 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-29 02:10:30 (9414) [INFO] Other repos take up 944 k of disk space (use --verbose for details) * 2025-01-29 02:10:31 (9431) [INFO] * 2025-01-29 02:10:31 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-29 02:10:31 (9401) [INFO] * 2025-01-29 02:10:31 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-29 02:10:31 (9414) [INFO] Determining fastest mirrors * 2025-01-29 02:11:03 (9414) [INFO] * EA4: 208.74.123.61 * 2025-01-29 02:11:03 (9414) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-01-29 02:11:03 (9414) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-01-29 02:11:03 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-29 02:11:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-29 02:11:50 (9414) [INFO] Trying other mirror. * 2025-01-29 02:12:21 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-29 02:12:21 (9414) [INFO] Trying other mirror. * 2025-01-29 02:12:51 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:12:51 (9414) [INFO] Trying other mirror. * 2025-01-29 02:13:21 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-29 02:13:21 (9414) [INFO] Trying other mirror. * 2025-01-29 02:13:51 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30044 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:13:51 (9414) [INFO] Trying other mirror. * 2025-01-29 02:14:22 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-29 02:14:22 (9414) [INFO] Trying other mirror. * 2025-01-29 02:14:53 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-29 02:14:53 (9414) [INFO] Trying other mirror. * 2025-01-29 02:15:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:15:23 (9414) [INFO] Trying other mirror. * 2025-01-29 02:15:53 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:15:53 (9414) [INFO] Trying other mirror. * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9414) [INFO] Trying other mirror. * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-29 02:16:23 (9414) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-29 02:16:23 (9414) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-29 02:16:23 (9414) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-29 02:16:23 (9414) [INFO] distribution release than is supported by the repository (and the * 2025-01-29 02:16:23 (9414) [INFO] packages for the previous distribution release still work). * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-29 02:16:23 (9414) [INFO] yum --disablerepo=base ... * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-29 02:16:23 (9414) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-29 02:16:23 (9414) [INFO] again or use --enablerepo for temporary usage: * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] yum-config-manager --disable base * 2025-01-29 02:16:23 (9414) [INFO] or * 2025-01-29 02:16:23 (9414) [INFO] subscription-manager repos --disable=base * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-29 02:16:23 (9414) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-29 02:16:23 (9414) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-29 02:16:23 (9414) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-29 02:16:23 (9414) [INFO] compromise: * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-29 02:16:23 (9414) [INFO] * 2025-01-29 02:16:23 (9414) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30044 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:23 (9431) [INFO] * 2025-01-29 02:16:23 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-29 02:16:23 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30044 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') 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. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30044 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-29 02:16:24 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-01-29 02:16:24 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-01-29 02:16:24 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-01-29 02:16:24 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-01-29 02:16:24 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-29 02:16:30 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/BuCCAcV2BG/ea_profile.json * 2025-01-30 01:58:52 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-30 02:02:53 (10480) [INFO] Script is up to date. * 2025-01-30 02:06:56 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-30 02:06:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-30 02:06:56 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-30 02:06:56 (9401) [INFO] * 2025-01-30 02:07:09 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-30 02:07:09 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-30 02:07:09 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-30 02:07:09 (9401) [INFO] * 2025-01-30 02:07:21 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-30 02:07:24 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-30 02:07:24 (9401) [INFO] * 2025-01-30 02:07:24 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-30 02:07:25 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-30 02:07:55 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-30 02:07:55 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-30 02:07:55 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-30 02:07:55 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-30 02:08:42 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-01-30 02:08:42 (9414) [INFO] Trying other mirror. * 2025-01-30 02:11:11 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:11:11 (9414) [INFO] Trying other mirror. * 2025-01-30 02:11:29 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-30 02:11:29 (9414) [INFO] Trying other mirror. * 2025-01-30 02:11:46 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-30 02:11:46 (9414) [INFO] Trying other mirror. * 2025-01-30 02:12:00 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:12:00 (9414) [INFO] Trying other mirror. * 2025-01-30 02:12:00 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-30 02:12:00 (9414) [INFO] Trying other mirror. * 2025-01-30 02:12:17 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-01-30 02:12:17 (9414) [INFO] Trying other mirror. * 2025-01-30 02:12:30 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:12:30 (9414) [INFO] Trying other mirror. * 2025-01-30 02:13:13 (9414) [INFO] Metadata Cache Created * 2025-01-30 02:13:14 (9431) [INFO] * 2025-01-30 02:13:14 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-01-30 02:13:14 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-30 02:13:14 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-30 02:13:14 (9401) [INFO] * 2025-01-30 02:13:14 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-30 02:13:14 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-30 02:13:14 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-30 02:13:14 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-30 02:13:14 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-30 02:13:14 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-30 02:13:14 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-30 02:13:14 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-30 02:13:14 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-30 02:13:14 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-30 02:13:15 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-30 02:13:15 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-30 02:13:15 (9431) [INFO] * 2025-01-30 02:13:15 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-30 02:13:15 (9401) [INFO] * 2025-01-30 02:13:16 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-30 02:13:16 (9414) [INFO] Determining fastest mirrors * 2025-01-30 02:13:47 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-30 02:13:47 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-30 02:13:47 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-30 02:13:47 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-30 02:16:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-30 02:16:50 (9414) [INFO] Trying other mirror. * 2025-01-30 02:16:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:16:50 (9414) [INFO] Trying other mirror. * 2025-01-30 02:19:29 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:19:29 (9414) [INFO] Trying other mirror. * 2025-01-30 02:22:18 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-30 02:22:18 (9414) [INFO] Trying other mirror. * 2025-01-30 02:23:19 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-30 02:23:19 (9414) [INFO] Trying other mirror. * 2025-01-30 02:23:49 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:23:49 (9414) [INFO] Trying other mirror. * 2025-01-30 02:23:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-30 02:23:50 (9414) [INFO] Trying other mirror. * 2025-01-30 02:23:50 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-30 02:23:50 (9414) [INFO] Trying other mirror. * 2025-01-30 02:24:21 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-30 02:24:21 (9414) [INFO] Trying other mirror. * 2025-01-30 02:24:51 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-30 02:24:51 (9414) [INFO] Trying other mirror. * 2025-01-30 02:24:51 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:24:51 (9414) [INFO] Trying other mirror. * 2025-01-30 02:25:21 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-30 02:25:21 (9414) [INFO] Trying other mirror. * 2025-01-30 02:25:22 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-30 02:25:22 (9414) [INFO] Trying other mirror. * 2025-01-30 02:25:51 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30004 milliseconds') * 2025-01-30 02:25:51 (9414) [INFO] Trying other mirror. * 2025-01-30 02:25:52 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Operation timed out after 30042 milliseconds with 0 out of 0 bytes received') * 2025-01-30 02:25:52 (9414) [INFO] Trying other mirror. * 2025-01-30 02:26:22 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-30 02:26:22 (9414) [INFO] Trying other mirror. * 2025-01-30 02:26:22 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-30 02:26:22 (9414) [INFO] Trying other mirror. * 2025-01-30 02:26:52 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-30 02:26:52 (9414) [INFO] Trying other mirror. * 2025-01-30 02:27:22 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Operation timed out after 30011 milliseconds with 0 out of 0 bytes received') * 2025-01-30 02:27:22 (9414) [INFO] Trying other mirror. * 2025-01-30 02:27:53 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-30 02:27:53 (9414) [INFO] Trying other mirror. * 2025-01-31 01:59:34 (10458) [INFO] Self-update of script version 60 requested. * 2025-01-31 02:03:34 (10480) [INFO] Script is up to date. * 2025-01-31 02:07:37 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-01-31 02:07:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-01-31 02:07:38 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-31 02:07:38 (9401) [INFO] * 2025-01-31 02:07:51 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-01-31 02:07:51 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-31 02:07:51 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-01-31 02:07:51 (9401) [INFO] * 2025-01-31 02:08:01 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-01-31 02:08:05 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-31 02:08:05 (9401) [INFO] * 2025-01-31 02:08:05 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-31 02:08:06 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-01-31 02:08:36 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-31 02:08:36 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-31 02:08:36 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-31 02:08:36 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-31 02:11:21 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:11:21 (9414) [INFO] Trying other mirror. * 2025-01-31 02:11:38 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:11:38 (9414) [INFO] Trying other mirror. * 2025-01-31 02:12:07 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:12:07 (9414) [INFO] Trying other mirror. * 2025-01-31 02:12:38 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-31 02:12:38 (9414) [INFO] Trying other mirror. * 2025-01-31 02:13:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-01-31 02:13:09 (9414) [INFO] Trying other mirror. * 2025-01-31 02:13:40 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-01-31 02:13:40 (9414) [INFO] Trying other mirror. * 2025-01-31 02:14:21 (9414) [INFO] Metadata Cache Created * 2025-01-31 02:14:21 (9431) [INFO] * 2025-01-31 02:14:21 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. * 2025-01-31 02:14:21 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-31 02:14:21 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-01-31 02:14:21 (9401) [INFO] * 2025-01-31 02:14:22 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-31 02:14:22 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-01-31 02:14:22 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-31 02:14:22 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-31 02:14:22 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-01-31 02:14:22 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-01-31 02:14:22 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-31 02:14:22 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-31 02:14:22 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-01-31 02:14:22 (9414) [INFO] : wp-toolkit-thirdparties * 2025-01-31 02:14:23 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-01-31 02:14:23 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-01-31 02:14:23 (9431) [INFO] * 2025-01-31 02:14:23 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-01-31 02:14:23 (9401) [INFO] * 2025-01-31 02:14:24 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-31 02:14:24 (9414) [INFO] Determining fastest mirrors * 2025-01-31 02:14:55 (9414) [INFO] * EA4: 107.178.98.171 * 2025-01-31 02:14:55 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-01-31 02:14:55 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-01-31 02:14:55 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-01-31 02:15:42 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30832 milliseconds') * 2025-01-31 02:15:42 (9414) [INFO] Trying other mirror. * 2025-01-31 02:18:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-31 02:18:29 (9414) [INFO] Trying other mirror. * 2025-01-31 02:18:29 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:18:29 (9414) [INFO] Trying other mirror. * 2025-01-31 02:21:09 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:21:09 (9414) [INFO] Trying other mirror. * 2025-01-31 02:23:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:23:58 (9414) [INFO] Trying other mirror. * 2025-01-31 02:23:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-31 02:23:58 (9414) [INFO] Trying other mirror. * 2025-01-31 02:24:29 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-31 02:24:29 (9414) [INFO] Trying other mirror. * 2025-01-31 02:25:00 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30799 milliseconds') * 2025-01-31 02:25:00 (9414) [INFO] Trying other mirror. * 2025-01-31 02:25:30 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:25:30 (9414) [INFO] Trying other mirror. * 2025-01-31 02:25:30 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:25:30 (9414) [INFO] Trying other mirror. * 2025-01-31 02:26:00 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-01-31 02:26:00 (9414) [INFO] Trying other mirror. * 2025-01-31 02:26:31 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:26:31 (9414) [INFO] Trying other mirror. * 2025-01-31 02:26:31 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-31 02:26:31 (9414) [INFO] Trying other mirror. * 2025-01-31 02:26:31 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-01-31 02:26:31 (9414) [INFO] Trying other mirror. * 2025-01-31 02:27:02 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-31 02:27:02 (9414) [INFO] Trying other mirror. * 2025-01-31 02:27:32 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:27:32 (9414) [INFO] Trying other mirror. * 2025-01-31 02:27:33 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-01-31 02:27:33 (9414) [INFO] Trying other mirror. * 2025-01-31 02:28:03 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-01-31 02:28:03 (9414) [INFO] Trying other mirror. * 2025-01-31 02:28:03 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-01-31 02:28:03 (9414) [INFO] Trying other mirror. * 2025-01-31 02:28:34 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30800 milliseconds') * 2025-01-31 02:28:34 (9414) [INFO] Trying other mirror. * 2025-02-01 02:00:02 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-01 02:04:03 (10480) [INFO] Script is up to date. * 2025-02-01 02:08:06 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-01 02:08:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-01 02:08:06 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-01 02:08:06 (9401) [INFO] * 2025-02-01 02:08:19 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-01 02:08:19 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-01 02:08:19 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-01 02:08:19 (9401) [INFO] * 2025-02-01 02:08:31 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-01 02:08:35 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-01 02:08:35 (9401) [INFO] * 2025-02-01 02:08:35 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-01 02:08:36 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-01 02:09:06 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-01 02:09:06 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-01 02:09:06 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-01 02:09:06 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-01 02:09:53 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-01 02:09:53 (9414) [INFO] Trying other mirror. * 2025-02-01 02:12:23 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:12:23 (9414) [INFO] Trying other mirror. * 2025-02-01 02:12:39 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:12:39 (9414) [INFO] Trying other mirror. * 2025-02-01 02:12:57 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-01 02:12:57 (9414) [INFO] Trying other mirror. * 2025-02-01 02:13:09 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:13:09 (9414) [INFO] Trying other mirror. * 2025-02-01 02:13:10 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-01 02:13:10 (9414) [INFO] Trying other mirror. * 2025-02-01 02:13:39 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-01 02:13:39 (9414) [INFO] Trying other mirror. * 2025-02-01 02:13:41 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-01 02:13:41 (9414) [INFO] Trying other mirror. * 2025-02-01 02:14:23 (9414) [INFO] Metadata Cache Created * 2025-02-01 02:14:23 (9431) [INFO] * 2025-02-01 02:14:23 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-02-01 02:14:23 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-01 02:14:23 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-01 02:14:23 (9401) [INFO] * 2025-02-01 02:14:24 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-01 02:14:24 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-01 02:14:24 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-01 02:14:24 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-01 02:14:24 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-01 02:14:24 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-01 02:14:24 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-01 02:14:24 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-01 02:14:24 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-01 02:14:24 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-01 02:14:25 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-01 02:14:25 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-01 02:14:25 (9431) [INFO] * 2025-02-01 02:14:25 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-01 02:14:25 (9401) [INFO] * 2025-02-01 02:14:26 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-01 02:14:26 (9414) [INFO] Determining fastest mirrors * 2025-02-01 02:14:57 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-01 02:14:57 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-01 02:14:57 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-01 02:14:57 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-01 02:15:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-01 02:15:44 (9414) [INFO] Trying other mirror. * 2025-02-01 02:16:15 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-01 02:16:15 (9414) [INFO] Trying other mirror. * 2025-02-01 02:19:03 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-01 02:19:03 (9414) [INFO] Trying other mirror. * 2025-02-01 02:19:03 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-01 02:19:03 (9414) [INFO] Trying other mirror. * 2025-02-01 02:21:42 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-01 02:21:42 (9414) [INFO] Trying other mirror. * 2025-02-01 02:24:31 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:24:31 (9414) [INFO] Trying other mirror. * 2025-02-01 02:24:31 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:24:31 (9414) [INFO] Trying other mirror. * 2025-02-01 02:25:32 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:25:32 (9414) [INFO] Trying other mirror. * 2025-02-01 02:25:33 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-01 02:25:33 (9414) [INFO] Trying other mirror. * 2025-02-01 02:26:34 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-01 02:26:34 (9414) [INFO] Trying other mirror. * 2025-02-01 02:27:53 (9414) [INFO] Metadata Cache Created * 2025-02-01 02:27:53 (9431) [INFO] * 2025-02-01 02:27:53 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-01 02:27:53 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-01 02:27:54 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-01 02:27:54 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-01 02:27:54 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-01 02:27:54 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-01 02:27:54 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-01 02:28:09 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DO4Vveh3eK/ea_profile.json * 2025-02-01 02:28:11 (8548) [INFO] Backed up EA4 profile to /tmp/DO4Vveh3eK/ea_profile.json * 2025-02-01 02:28:11 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-01 02:28:14 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-01 02:28:45 (641) [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. * 2025-02-01 02:28:45 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-02 01:57:00 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-02 02:01:00 (10480) [INFO] Script is up to date. * 2025-02-02 02:05:03 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-02 02:05:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-02 02:05:04 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-02 02:05:04 (9401) [INFO] * 2025-02-02 02:05:16 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-02 02:05:16 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-02 02:05:16 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-02 02:05:16 (9401) [INFO] * 2025-02-02 02:05:27 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-02 02:05:30 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-02 02:05:30 (9401) [INFO] * 2025-02-02 02:05:30 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-02 02:05:30 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-02 02:06:00 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-02 02:06:00 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-02 02:06:00 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-02 02:06:00 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-02 02:06:47 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:06:47 (9414) [INFO] Trying other mirror. * 2025-02-02 02:07:18 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:07:18 (9414) [INFO] Trying other mirror. * 2025-02-02 02:09:50 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-02 02:09:50 (9414) [INFO] Trying other mirror. * 2025-02-02 02:10:07 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:10:07 (9414) [INFO] Trying other mirror. * 2025-02-02 02:10:23 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:10:23 (9414) [INFO] Trying other mirror. * 2025-02-02 02:10:36 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:10:36 (9414) [INFO] Trying other mirror. * 2025-02-02 02:11:22 (9414) [INFO] Metadata Cache Created * 2025-02-02 02:11:22 (9431) [INFO] * 2025-02-02 02:11:22 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-02 02:11:22 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-02 02:11:22 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-02 02:11:22 (9401) [INFO] * 2025-02-02 02:11:22 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-02 02:11:23 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-02 02:11:23 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-02 02:11:23 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-02 02:11:23 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-02 02:11:23 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-02 02:11:23 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-02 02:11:23 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-02 02:11:23 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-02 02:11:23 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-02 02:11:23 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-02 02:11:24 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-02 02:11:24 (9431) [INFO] * 2025-02-02 02:11:24 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-02 02:11:24 (9401) [INFO] * 2025-02-02 02:11:24 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-02 02:11:24 (9414) [INFO] Determining fastest mirrors * 2025-02-02 02:11:57 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-02 02:11:57 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-02 02:11:57 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-02 02:11:57 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-02 02:12:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-02 02:12:43 (9414) [INFO] Trying other mirror. * 2025-02-02 02:13:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:13:14 (9414) [INFO] Trying other mirror. * 2025-02-02 02:16:01 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-02 02:16:01 (9414) [INFO] Trying other mirror. * 2025-02-02 02:16:02 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:16:02 (9414) [INFO] Trying other mirror. * 2025-02-02 02:18:42 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:18:42 (9414) [INFO] Trying other mirror. * 2025-02-02 02:21:31 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:21:31 (9414) [INFO] Trying other mirror. * 2025-02-02 02:21:31 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-02 02:21:31 (9414) [INFO] Trying other mirror. * 2025-02-02 02:22:02 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-02 02:22:02 (9414) [INFO] Trying other mirror. * 2025-02-02 02:23:02 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:23:02 (9414) [INFO] Trying other mirror. * 2025-02-02 02:23:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:23:02 (9414) [INFO] Trying other mirror. * 2025-02-02 02:23:33 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-02 02:23:33 (9414) [INFO] Trying other mirror. * 2025-02-02 02:24:04 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-02 02:24:04 (9414) [INFO] Trying other mirror. * 2025-02-02 02:24:34 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:24:34 (9414) [INFO] Trying other mirror. * 2025-02-02 02:24:35 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') * 2025-02-02 02:24:35 (9414) [INFO] Trying other mirror. * 2025-02-02 02:25:36 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-02 02:25:36 (9414) [INFO] Trying other mirror. * 2025-02-03 01:55:16 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-03 01:59:17 (10480) [INFO] Script is up to date. * 2025-02-03 02:03:20 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-03 02:03:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-03 02:03:20 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-03 02:03:20 (9401) [INFO] * 2025-02-03 02:03:34 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-03 02:03:34 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-03 02:03:34 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-03 02:03:34 (9401) [INFO] * 2025-02-03 02:03:47 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-03 02:03:51 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-03 02:03:51 (9401) [INFO] * 2025-02-03 02:03:51 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-03 02:03:52 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-03 02:04:22 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-03 02:04:22 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-03 02:04:22 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-03 02:04:22 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-03 02:07:08 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-03 02:07:08 (9414) [INFO] Trying other mirror. * 2025-02-03 02:07:25 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:07:25 (9414) [INFO] Trying other mirror. * 2025-02-03 02:07:42 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:07:42 (9414) [INFO] Trying other mirror. * 2025-02-03 02:07:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:07:54 (9414) [INFO] Trying other mirror. * 2025-02-03 02:08:12 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-03 02:08:12 (9414) [INFO] Trying other mirror. * 2025-02-03 02:08:43 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:08:43 (9414) [INFO] Trying other mirror. * 2025-02-03 02:09:27 (9414) [INFO] Metadata Cache Created * 2025-02-03 02:09:27 (9431) [INFO] * 2025-02-03 02:09:27 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-02-03 02:09:27 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-03 02:09:27 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-03 02:09:27 (9401) [INFO] * 2025-02-03 02:09:28 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-03 02:09:28 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-03 02:09:28 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-03 02:09:28 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-03 02:09:28 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-03 02:09:28 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-03 02:09:28 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-03 02:09:28 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-03 02:09:28 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-03 02:09:28 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-03 02:09:29 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-03 02:09:29 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-03 02:09:29 (9431) [INFO] * 2025-02-03 02:09:29 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-03 02:09:29 (9401) [INFO] * 2025-02-03 02:09:29 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-03 02:09:29 (9414) [INFO] Determining fastest mirrors * 2025-02-03 02:10:02 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-03 02:10:02 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-03 02:10:02 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-03 02:10:02 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-03 02:10:49 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-03 02:10:49 (9414) [INFO] Trying other mirror. * 2025-02-03 02:13:36 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:13:36 (9414) [INFO] Trying other mirror. * 2025-02-03 02:13:37 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-03 02:13:37 (9414) [INFO] Trying other mirror. * 2025-02-03 02:14:07 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:14:07 (9414) [INFO] Trying other mirror. * 2025-02-03 02:16:16 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-02-03 02:16:16 (9414) [INFO] Trying other mirror. * 2025-02-03 02:19:04 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:19:04 (9414) [INFO] Trying other mirror. * 2025-02-03 02:19:05 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:19:05 (9414) [INFO] Trying other mirror. * 2025-02-03 02:20:07 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-03 02:20:07 (9414) [INFO] Trying other mirror. * 2025-02-03 02:20:07 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-03 02:20:07 (9414) [INFO] Trying other mirror. * 2025-02-03 02:20:37 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:20:37 (9414) [INFO] Trying other mirror. * 2025-02-03 02:20:38 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:20:38 (9414) [INFO] Trying other mirror. * 2025-02-03 02:21:08 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:21:08 (9414) [INFO] Trying other mirror. * 2025-02-03 02:21:38 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:21:38 (9414) [INFO] Trying other mirror. * 2025-02-03 02:22:09 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-03 02:22:09 (9414) [INFO] Trying other mirror. * 2025-02-03 02:22:40 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-03 02:22:40 (9414) [INFO] Trying other mirror. * 2025-02-03 02:23:11 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-03 02:23:11 (9414) [INFO] Trying other mirror. * 2025-02-03 02:24:36 (9414) [INFO] Metadata Cache Created * 2025-02-03 02:24:36 (9431) [INFO] * 2025-02-03 02:24:36 (5888) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-03 02:24:36 (5889) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-02-03 02:24:37 (3232) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-03 02:24:37 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-03 02:24:37 (4264) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-03 02:24:37 (4270) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-03 02:24:37 (2006) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-03 02:24:52 (8525) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7wFZa_NEaA/ea_profile.json * 2025-02-03 02:24:55 (8548) [INFO] Backed up EA4 profile to /tmp/7wFZa_NEaA/ea_profile.json * 2025-02-03 02:24:55 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-03 02:24:59 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-04 01:56:38 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-04 02:00:38 (10480) [INFO] Script is up to date. * 2025-02-04 02:04:41 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-04 02:04:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-04 02:04:41 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-04 02:04:41 (9401) [INFO] * 2025-02-04 02:04:52 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-04 02:04:52 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-04 02:04:52 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-04 02:04:52 (9401) [INFO] * 2025-02-04 02:05:05 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-04 02:05:08 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-04 02:05:08 (9401) [INFO] * 2025-02-04 02:05:08 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-04 02:05:09 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-04 02:05:39 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-04 02:05:39 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-04 02:05:39 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-04 02:05:39 (9414) [INFO] * epel: mirror.math.princeton.edu * 2025-02-04 02:06:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:06:26 (9414) [INFO] Trying other mirror. * 2025-02-04 02:06:56 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') * 2025-02-04 02:06:56 (9414) [INFO] Trying other mirror. * 2025-02-04 02:09:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:09:26 (9414) [INFO] Trying other mirror. * 2025-02-04 02:09:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-04 02:09:44 (9414) [INFO] Trying other mirror. * 2025-02-04 02:10:13 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:10:13 (9414) [INFO] Trying other mirror. * 2025-02-04 02:10:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:10:14 (9414) [INFO] Trying other mirror. * 2025-02-04 02:10:43 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:10:43 (9414) [INFO] Trying other mirror. * 2025-02-04 02:11:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:11:14 (9414) [INFO] Trying other mirror. * 2025-02-04 02:11:45 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:11:45 (9414) [INFO] Trying other mirror. * 2025-02-04 02:12:27 (9414) [INFO] Metadata Cache Created * 2025-02-04 02:12:27 (9431) [INFO] * 2025-02-04 02:12:27 (5878) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-02-04 02:12:27 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-04 02:12:27 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-04 02:12:27 (9401) [INFO] * 2025-02-04 02:12:27 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-04 02:12:28 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-04 02:12:28 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-04 02:12:28 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-04 02:12:28 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-04 02:12:28 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-04 02:12:28 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-04 02:12:28 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-04 02:12:28 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-04 02:12:28 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-04 02:12:29 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-04 02:12:29 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-04 02:12:29 (9431) [INFO] * 2025-02-04 02:12:29 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-04 02:12:29 (9401) [INFO] * 2025-02-04 02:12:29 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-04 02:12:30 (9414) [INFO] Determining fastest mirrors * 2025-02-04 02:13:01 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-04 02:13:01 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-04 02:13:01 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-04 02:13:01 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-04 02:13:48 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:13:48 (9414) [INFO] Trying other mirror. * 2025-02-04 02:14:19 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:14:19 (9414) [INFO] Trying other mirror. * 2025-02-04 02:14:49 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:14:49 (9414) [INFO] Trying other mirror. * 2025-02-04 02:17:37 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:17:37 (9414) [INFO] Trying other mirror. * 2025-02-04 02:17:37 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:17:37 (9414) [INFO] Trying other mirror. * 2025-02-04 02:18:08 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:18:08 (9414) [INFO] Trying other mirror. * 2025-02-04 02:20:17 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:20:17 (9414) [INFO] Trying other mirror. * 2025-02-04 02:23:05 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:23:05 (9414) [INFO] Trying other mirror. * 2025-02-04 02:23:06 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:23:06 (9414) [INFO] Trying other mirror. * 2025-02-04 02:24:07 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:24:07 (9414) [INFO] Trying other mirror. * 2025-02-04 02:24:08 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-04 02:24:08 (9414) [INFO] Trying other mirror. * 2025-02-04 02:24:38 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:24:38 (9414) [INFO] Trying other mirror. * 2025-02-04 02:24:39 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-04 02:24:39 (9414) [INFO] Trying other mirror. * 2025-02-04 02:25:09 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:25:09 (9414) [INFO] Trying other mirror. * 2025-02-04 02:25:39 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:25:39 (9414) [INFO] Trying other mirror. * 2025-02-04 02:25:39 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-04 02:25:39 (9414) [INFO] Trying other mirror. * 2025-02-04 02:26:10 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-04 02:26:10 (9414) [INFO] Trying other mirror. * 2025-02-05 01:46:09 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-05 01:50:09 (10480) [INFO] Script is up to date. * 2025-02-05 01:54:13 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-05 01:54:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-05 01:54:13 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-05 01:54:13 (9401) [INFO] * 2025-02-05 01:54:23 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-05 01:54:23 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-05 01:54:23 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-05 01:54:23 (9401) [INFO] * 2025-02-05 01:54:33 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-05 01:54:37 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-05 01:54:37 (9401) [INFO] * 2025-02-05 01:54:38 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-05 01:54:38 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-05 01:55:08 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-05 01:55:08 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-05 01:55:08 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-05 01:55:08 (9414) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-05 01:55:38 (9414) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-02-05 01:55:38 (9414) [INFO] Trying other mirror. * 2025-02-05 01:58:25 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-05 01:58:25 (9414) [INFO] Trying other mirror. * 2025-02-05 01:58:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-05 01:58:26 (9414) [INFO] Trying other mirror. * 2025-02-05 01:59:14 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 01:59:14 (9414) [INFO] Trying other mirror. * 2025-02-05 01:59:15 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 01:59:15 (9414) [INFO] Trying other mirror. * 2025-02-05 02:00:10 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-05 02:00:10 (9414) [INFO] Trying other mirror. * 2025-02-05 02:00:10 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:00:10 (9414) [INFO] Trying other mirror. * 2025-02-05 02:00:26 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-05 02:00:26 (9414) [INFO] Trying other mirror. * 2025-02-05 02:00:57 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-05 02:00:57 (9414) [INFO] Trying other mirror. * 2025-02-05 02:00:57 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-05 02:00:57 (9414) [INFO] Trying other mirror. * 2025-02-05 02:01:27 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:01:27 (9414) [INFO] Trying other mirror. * 2025-02-05 02:01:27 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:01:27 (9414) [INFO] Trying other mirror. * 2025-02-05 02:01:58 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-05 02:01:58 (9414) [INFO] Trying other mirror. * 2025-02-05 02:01:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-05 02:01:58 (9414) [INFO] Trying other mirror. * 2025-02-05 02:02:28 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:02:28 (9414) [INFO] Trying other mirror. * 2025-02-05 02:02:28 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-05 02:02:28 (9414) [INFO] Trying other mirror. * 2025-02-05 02:02:58 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:02:58 (9414) [INFO] Trying other mirror. * 2025-02-05 02:02:59 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-05 02:02:59 (9414) [INFO] Trying other mirror. * 2025-02-05 02:02:59 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30597 milliseconds') * 2025-02-05 02:02:59 (9414) [INFO] Trying other mirror. * 2025-02-05 02:03:29 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-05 02:03:29 (9414) [INFO] Trying other mirror. * 2025-02-05 02:04:00 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-05 02:04:00 (9414) [INFO] Trying other mirror. * 2025-02-05 02:04:00 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-02-05 02:04:00 (9414) [INFO] Trying other mirror. * 2025-02-05 02:05:01 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-05 02:05:01 (9414) [INFO] Trying other mirror. * 2025-02-05 02:05:31 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-05 02:05:31 (9414) [INFO] Trying other mirror. * 2025-02-05 02:06:02 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:06:02 (9414) [INFO] Trying other mirror. * 2025-02-05 02:06:32 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-05 02:06:32 (9414) [INFO] Trying other mirror. * 2025-02-05 02:07:39 (9414) [INFO] Metadata Cache Created * 2025-02-05 02:07:39 (9431) [INFO] * 2025-02-05 02:07:39 (5878) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-02-05 02:07:39 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-05 02:07:39 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-05 02:07:39 (9401) [INFO] * 2025-02-05 02:07:39 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-05 02:07:40 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-05 02:07:40 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-05 02:07:40 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-05 02:07:40 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-05 02:07:40 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-05 02:07:40 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-05 02:07:40 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-05 02:07:40 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-05 02:07:40 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-05 02:07:41 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-05 02:07:41 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-05 02:07:41 (9431) [INFO] * 2025-02-05 02:07:41 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-05 02:07:41 (9401) [INFO] * 2025-02-05 02:07:41 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-05 02:07:41 (9414) [INFO] Determining fastest mirrors * 2025-02-05 02:08:14 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-05 02:08:14 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-05 02:08:14 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-05 02:08:14 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-05 02:11:27 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-05 02:11:27 (9414) [INFO] Trying other mirror. * 2025-02-05 02:11:27 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:11:27 (9414) [INFO] Trying other mirror. * 2025-02-05 02:11:58 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-05 02:11:58 (9414) [INFO] Trying other mirror. * 2025-02-05 02:13:36 (9414) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:13:36 (9414) [INFO] Trying other mirror. * 2025-02-05 02:13:36 (9414) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:13:36 (9414) [INFO] Trying other mirror. * 2025-02-05 02:14:07 (9414) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:14:07 (9414) [INFO] Trying other mirror. * 2025-02-05 02:14:23 (9414) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:14:23 (9414) [INFO] Trying other mirror. * 2025-02-05 02:14:39 (9414) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:14:39 (9414) [INFO] Trying other mirror. * 2025-02-05 02:14:54 (9414) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:14:54 (9414) [INFO] Trying other mirror. * 2025-02-05 02:15:17 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:15:17 (9414) [INFO] Trying other mirror. * 2025-02-05 02:15:44 (9414) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/0a57f1ef2808a3f5a8f3cf070180210c87a1b4456ff162cd30f4d5413bc4873b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-05 02:15:44 (9414) [INFO] Trying other mirror. * 2025-02-05 02:15:48 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-05 02:15:48 (9414) [INFO] Trying other mirror. * 2025-02-06 01:47:06 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-06 01:51:06 (10480) [INFO] Script is up to date. * 2025-02-06 01:55:09 (6310) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-06 01:55:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-06 01:55:10 (9400) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-06 01:55:10 (9401) [INFO] * 2025-02-06 01:55:20 (4048) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-06 01:55:20 (4055) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-06 01:55:20 (9400) [INFO] Running: /usr/bin/yum list extras * 2025-02-06 01:55:20 (9401) [INFO] * 2025-02-06 01:55:32 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-06 01:55:35 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-06 01:55:35 (9401) [INFO] * 2025-02-06 01:55:35 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-06 01:55:36 (9414) [INFO] Loading mirror speeds from cached hostfile * 2025-02-06 01:56:07 (9414) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-02-06 01:56:07 (9414) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30792 milliseconds') * 2025-02-06 01:56:07 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-06 01:56:07 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-06 01:56:07 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-06 01:56:07 (9414) [INFO] * epel: dl.fedoraproject.org * 2025-02-06 01:58:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 01:58:54 (9414) [INFO] Trying other mirror. * 2025-02-06 01:58:54 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 01:58:54 (9414) [INFO] Trying other mirror. * 2025-02-06 01:59:12 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 01:59:12 (9414) [INFO] Trying other mirror. * 2025-02-06 01:59:13 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 01:59:13 (9414) [INFO] Trying other mirror. * 2025-02-06 01:59:59 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 01:59:59 (9414) [INFO] Trying other mirror. * 2025-02-06 02:00:14 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:00:14 (9414) [INFO] Trying other mirror. * 2025-02-06 02:00:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:00:44 (9414) [INFO] Trying other mirror. * 2025-02-06 02:01:15 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-06 02:01:15 (9414) [INFO] Trying other mirror. * 2025-02-06 02:01:15 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-06 02:01:15 (9414) [INFO] Trying other mirror. * 2025-02-06 02:01:46 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:01:46 (9414) [INFO] Trying other mirror. * 2025-02-06 02:01:46 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-06 02:01:46 (9414) [INFO] Trying other mirror. * 2025-02-06 02:02:16 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-06 02:02:16 (9414) [INFO] Trying other mirror. * 2025-02-06 02:02:16 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:02:16 (9414) [INFO] Trying other mirror. * 2025-02-06 02:03:24 (9414) [INFO] Metadata Cache Created * 2025-02-06 02:03:24 (9431) [INFO] * 2025-02-06 02:03:24 (5878) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30792 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-06 02:03:24 (5879) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-06 02:03:24 (9400) [INFO] Running: /usr/bin/yum clean all * 2025-02-06 02:03:24 (9401) [INFO] * 2025-02-06 02:03:25 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-06 02:03:25 (9414) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-06 02:03:25 (9414) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-06 02:03:25 (9414) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-06 02:03:25 (9414) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-06 02:03:25 (9414) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-06 02:03:25 (9414) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-06 02:03:25 (9414) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-06 02:03:25 (9414) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-06 02:03:25 (9414) [INFO] : wp-toolkit-thirdparties * 2025-02-06 02:03:26 (9414) [INFO] Cleaning up list of fastest mirrors * 2025-02-06 02:03:26 (9414) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-06 02:03:26 (9431) [INFO] * 2025-02-06 02:03:26 (9400) [INFO] Running: /usr/bin/yum makecache * 2025-02-06 02:03:26 (9401) [INFO] * 2025-02-06 02:03:27 (9414) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-06 02:03:27 (9414) [INFO] Determining fastest mirrors * 2025-02-06 02:03:59 (9414) [INFO] * EA4: 107.178.98.171 * 2025-02-06 02:03:59 (9414) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-06 02:03:59 (9414) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-06 02:03:59 (9414) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-06 02:07:04 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-06 02:07:04 (9414) [INFO] Trying other mirror. * 2025-02-06 02:07:04 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:07:04 (9414) [INFO] Trying other mirror. * 2025-02-06 02:09:21 (9414) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:09:21 (9414) [INFO] Trying other mirror. * 2025-02-06 02:09:48 (9414) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/30fbbe036ea57e7b61c5ab97b681de8b8a756f942967541ae3eb925327b45b2b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-02-06 02:09:48 (9414) [INFO] Trying other mirror. * 2025-02-06 02:09:51 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:09:51 (9414) [INFO] Trying other mirror. * 2025-02-06 02:10:03 (9414) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:10:03 (9414) [INFO] Trying other mirror. * 2025-02-06 02:10:19 (9414) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:10:19 (9414) [INFO] Trying other mirror. * 2025-02-06 02:10:35 (9414) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:10:35 (9414) [INFO] Trying other mirror. * 2025-02-06 02:10:50 (9414) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:10:50 (9414) [INFO] Trying other mirror. * 2025-02-06 02:11:06 (9414) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:11:06 (9414) [INFO] Trying other mirror. * 2025-02-06 02:11:22 (9414) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:11:22 (9414) [INFO] Trying other mirror. * 2025-02-06 02:11:37 (9414) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:11:37 (9414) [INFO] Trying other mirror. * 2025-02-06 02:11:53 (9414) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:11:53 (9414) [INFO] Trying other mirror. * 2025-02-06 02:12:09 (9414) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:12:09 (9414) [INFO] Trying other mirror. * 2025-02-06 02:12:40 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-06 02:12:40 (9414) [INFO] Trying other mirror. * 2025-02-06 02:12:55 (9414) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:12:55 (9414) [INFO] Trying other mirror. * 2025-02-06 02:13:11 (9414) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:13:11 (9414) [INFO] Trying other mirror. * 2025-02-06 02:13:41 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-06 02:13:41 (9414) [INFO] Trying other mirror. * 2025-02-06 02:13:42 (9414) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:13:42 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:11 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:14:11 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:12 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-06 02:14:12 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:12 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-06 02:14:12 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:28 (9414) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:14:28 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:42 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:14:42 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:42 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-06 02:14:42 (9414) [INFO] Trying other mirror. * 2025-02-06 02:14:58 (9414) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:14:58 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:13 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:15:13 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:13 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:15:13 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:13 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-06 02:15:13 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:43 (9414) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-02-06 02:15:43 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:44 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:15:44 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:44 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-06 02:15:44 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:44 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30887 milliseconds') * 2025-02-06 02:15:44 (9414) [INFO] Trying other mirror. * 2025-02-06 02:15:45 (9414) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:15:45 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:14 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:16:14 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:15 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-06 02:16:15 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:15 (9414) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-06 02:16:15 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:34 (9414) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-06 02:16:34 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:45 (9414) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-06 02:16:45 (9414) [INFO] Trying other mirror. * 2025-02-06 02:16:46 (9414) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-06 02:16:46 (9414) [INFO] Trying other mirror. * 2025-02-07 01:55:20 (10458) [INFO] Self-update of script version 60 requested. * 2025-02-07 01:59:21 (10463) [INFO] Newer version of script found. Downloading. * 2025-02-07 02:03:23 (10472) [INFO] Script update to version 61 successful. * 2025-02-07 02:07:26 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-07 02:07:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-07 02:07:26 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-07 02:07:26 (9407) [INFO] * 2025-02-07 02:07:39 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-07 02:07:39 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-07 02:07:39 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-07 02:07:39 (9407) [INFO] * 2025-02-07 02:07:49 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-07 02:07:52 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-07 02:07:52 (9407) [INFO] * 2025-02-07 02:07:53 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-07 02:07:53 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-07 02:08:24 (9420) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-02-07 02:08:24 (9420) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30542 milliseconds') * 2025-02-07 02:08:24 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-07 02:08:24 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-07 02:08:24 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-07 02:08:24 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-07 02:09:10 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-07 02:09:10 (9420) [INFO] Trying other mirror. * 2025-02-07 02:09:41 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-07 02:09:41 (9420) [INFO] Trying other mirror. * 2025-02-07 02:12:12 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-07 02:12:12 (9420) [INFO] Trying other mirror. * 2025-02-07 02:12:28 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-07 02:12:28 (9420) [INFO] Trying other mirror. * 2025-02-07 02:13:12 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-07 02:13:12 (9420) [INFO] Trying other mirror. * 2025-02-07 02:13:14 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-07 02:13:14 (9420) [INFO] Trying other mirror. * 2025-02-07 02:13:44 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-07 02:13:44 (9420) [INFO] Trying other mirror. * 2025-02-07 02:14:15 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-07 02:14:15 (9420) [INFO] Trying other mirror. * 2025-02-07 02:15:02 (9420) [INFO] Metadata Cache Created * 2025-02-07 02:15:03 (9437) [INFO] * 2025-02-07 02:15:03 (5884) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30542 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2025-02-07 02:15:03 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-07 02:15:03 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-07 02:15:03 (9407) [INFO] * 2025-02-07 02:15:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-07 02:15:04 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-07 02:15:04 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-07 02:15:04 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-07 02:15:04 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-07 02:15:04 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-07 02:15:04 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-07 02:15:04 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-07 02:15:04 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-07 02:15:04 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-07 02:15:04 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-07 02:15:04 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-07 02:15:04 (9437) [INFO] * 2025-02-07 02:15:04 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-07 02:15:04 (9407) [INFO] * 2025-02-07 02:15:05 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-07 02:15:05 (9420) [INFO] Determining fastest mirrors * 2025-02-07 02:15:38 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-07 02:15:38 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-07 02:15:38 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-07 02:15:38 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-07 02:16:24 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-07 02:16:24 (9420) [INFO] Trying other mirror. * 2025-02-07 02:19:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-07 02:19:11 (9420) [INFO] Trying other mirror. * 2025-02-07 02:19:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-07 02:19:11 (9420) [INFO] Trying other mirror. * 2025-02-07 02:21:52 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-07 02:21:52 (9420) [INFO] Trying other mirror. * 2025-02-07 02:24:40 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-07 02:24:40 (9420) [INFO] Trying other mirror. * 2025-02-07 02:24:41 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-07 02:24:41 (9420) [INFO] Trying other mirror. * 2025-02-08 01:47:03 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-08 01:51:04 (10486) [INFO] Script is up to date. * 2025-02-08 01:55:07 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-08 01:55:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-08 01:55:07 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-08 01:55:07 (9407) [INFO] * 2025-02-08 01:55:11 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-08 01:55:11 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-08 01:55:11 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-08 01:55:11 (9407) [INFO] * 2025-02-08 01:55:33 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-08 01:55:33 (9407) [INFO] * 2025-02-08 01:55:34 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-08 01:55:34 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-08 01:56:05 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-08 01:56:05 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-08 01:56:05 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-08 01:56:05 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-08 01:56:52 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-08 01:56:52 (9420) [INFO] Trying other mirror. * 2025-02-08 01:58:20 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-08 01:58:20 (9420) [INFO] Trying other mirror. * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-08 01:58:20 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-08 01:58:20 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-08 01:58:20 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-08 01:58:20 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-08 01:58:20 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-08 01:58:20 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-08 01:58:20 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-08 01:58:20 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-08 01:58:20 (9420) [INFO] or * 2025-02-08 01:58:20 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-08 01:58:20 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-08 01:58:20 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-08 01:58:20 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-08 01:58:20 (9420) [INFO] compromise: * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-08 01:58:20 (9420) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-08 01:58:20 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-08 01:58:20 (9437) [INFO] * 2025-02-08 01:58:20 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-08 01:58:20 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-08 01:58:20 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-08 01:58:20 (9407) [INFO] * 2025-02-08 01:58:20 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-08 01:58:21 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-08 01:58:21 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-08 01:58:21 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-08 01:58:21 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-08 01:58:21 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-08 01:58:21 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-08 01:58:21 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-08 01:58:21 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-08 01:58:21 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-08 01:58:21 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-08 01:58:21 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-08 01:58:21 (9437) [INFO] * 2025-02-08 01:58:21 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-08 01:58:21 (9407) [INFO] * 2025-02-08 01:58:21 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-08 01:58:22 (9420) [INFO] Determining fastest mirrors * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-02-08 01:58:53 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-08 01:58:53 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-08 01:58:53 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-08 01:58:53 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-08 01:58:53 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-08 01:58:53 (9420) [INFO] yum --disablerepo= ... * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-08 01:58:53 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-08 01:58:53 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] yum-config-manager --disable * 2025-02-08 01:58:53 (9420) [INFO] or * 2025-02-08 01:58:53 (9420) [INFO] subscription-manager repos --disable= * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-08 01:58:53 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-08 01:58:53 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-08 01:58:53 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-08 01:58:53 (9420) [INFO] compromise: * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-02-08 01:58:53 (9420) [INFO] * 2025-02-08 01:58:53 (9420) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-02-08 01:58:53 (9437) [INFO] * 2025-02-08 01:58:53 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-08 01:58:53 (5895) [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 * 2025-02-08 01:58:54 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-08 01:58:54 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-08 01:58:54 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-08 01:58:54 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-08 01:58:54 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-08 01:59:02 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lj7mL7cBt9/ea_profile.json * 2025-02-08 02:01:18 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lj7mL7cBt9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-08 02:01:18 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-09 01:45:40 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-09 01:49:41 (10486) [INFO] Script is up to date. * 2025-02-09 01:53:44 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-09 01:53:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-09 01:53:45 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-09 01:53:45 (9407) [INFO] * 2025-02-09 01:53:48 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-09 01:53:48 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-09 01:53:48 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-09 01:53:48 (9407) [INFO] * 2025-02-09 01:54:23 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-09 01:54:23 (9407) [INFO] * 2025-02-09 01:54:23 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-09 01:54:24 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-09 01:54:55 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-09 01:54:55 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-09 01:54:55 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-09 01:54:55 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-09 01:56:39 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-09 01:56:39 (9420) [INFO] Trying other mirror. * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-09 01:56:39 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-09 01:56:39 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-09 01:56:39 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-09 01:56:39 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-09 01:56:39 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-09 01:56:39 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-09 01:56:39 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-09 01:56:39 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-09 01:56:39 (9420) [INFO] or * 2025-02-09 01:56:39 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-09 01:56:39 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-09 01:56:39 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-09 01:56:39 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-09 01:56:39 (9420) [INFO] compromise: * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-09 01:56:39 (9420) [INFO] * 2025-02-09 01:56:39 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-09 01:56:39 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-09 01:56:39 (9437) [INFO] * 2025-02-09 01:56:39 (5884) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM4NjcxNjI0OjE3Mzg5MzA4MjQ6PsnVUHr2i95RrGj7PqVLgyA_rxh8wGTGpfemUX9nkoR4IPT8kf9RQJMblkVM0rNA4_5sRn1NtLJtF_oDdK89kbCjJLEm4hhmmN7Di_CmSGCqjfdX_cuVKkFrNXD4-bTkDCGktnZl-H3MHYG_-dVIRLQjdvy46H1xmFsafllk1oFMSOjouwWbGrgGt0Jhhn_EGPP9zE4Tqj1OBJg0kSgA5bSzurPldvRGc7nnQryoOPHfUmmaKoYhfMnsfxBQoLGKWASSJFIo6EnZh8hmCXfm3CQ_hwEmZknmuw-7rh9fvPanDmbb3nGQfmEbqT5smKK5JqFX1EfNhdhV-q0iTIdVtTdKnrRwyyUYQ4OFntBORrRoZdna9mtExeCduGMsWi1hbWSqdcP4kEEV8oK6Dsm5hnNqx_XVf52D3OSSyUj4VBqiNrMSFBSzVWKa8OTvkFT6GQS-6T3PdLfzCK6R4hC59JUWuVP7J6ENTLxjoDjTwmLLRtkt5KAz4AQ2qKODZQZskyyOQfZULfeVvmIZk6RZ0Zq3FKd626gTQCa3nFcuaAJZEWskjkk5siVbcCcsfSfNjO2CZOnJeCF_Lo5hdCGWaf2-4BI5F70cpPiOeOKhVREOtrsAfUkIMAjzHOyeHM7A_k-krcImiKKD0E4ha_U_Wg2lIAn40uPQOuS-J4SifXs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-09 01:56:39 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-09 01:56:39 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-09 01:56:39 (9407) [INFO] * 2025-02-09 01:56:40 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-09 01:56:40 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-09 01:56:40 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-09 01:56:40 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-09 01:56:40 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-09 01:56:40 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-09 01:56:40 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-09 01:56:40 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-09 01:56:40 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-09 01:56:40 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-09 01:56:40 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-09 01:56:40 (9420) [INFO] Other repos take up 940 k of disk space (use --verbose for details) * 2025-02-09 01:56:40 (9437) [INFO] * 2025-02-09 01:56:40 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-09 01:56:40 (9407) [INFO] * 2025-02-09 01:56:41 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-09 01:56:41 (9420) [INFO] Determining fastest mirrors * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-02-09 01:57:12 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-09 01:57:12 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-09 01:57:12 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-09 01:57:12 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-09 01:57:12 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-09 01:57:12 (9420) [INFO] yum --disablerepo= ... * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-09 01:57:12 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-09 01:57:12 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] yum-config-manager --disable * 2025-02-09 01:57:12 (9420) [INFO] or * 2025-02-09 01:57:12 (9420) [INFO] subscription-manager repos --disable= * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-09 01:57:12 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-09 01:57:12 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-09 01:57:12 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-09 01:57:12 (9420) [INFO] compromise: * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-02-09 01:57:12 (9420) [INFO] * 2025-02-09 01:57:12 (9420) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-02-09 01:57:12 (9437) [INFO] * 2025-02-09 01:57:12 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-09 01:57:12 (5895) [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 * 2025-02-09 01:57:13 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-09 01:57:13 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-09 01:57:13 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-09 01:57:13 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-09 01:57:13 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-09 01:57:19 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/R2WewVRdDz/ea_profile.json * 2025-02-09 01:59:35 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/R2WewVRdDz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-09 01:59:35 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-10 01:53:51 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-10 01:57:52 (10486) [INFO] Script is up to date. * 2025-02-10 02:01:55 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-10 02:01:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-10 02:01:55 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-10 02:01:55 (9407) [INFO] * 2025-02-10 02:01:59 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-10 02:01:59 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-10 02:01:59 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-10 02:01:59 (9407) [INFO] * 2025-02-10 02:02:12 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-10 02:02:15 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-10 02:02:15 (9407) [INFO] * 2025-02-10 02:02:15 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-10 02:02:15 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-10 02:02:45 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-10 02:02:45 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-10 02:02:45 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-10 02:02:45 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-10 02:05:31 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:05:31 (9420) [INFO] Trying other mirror. * 2025-02-10 02:05:48 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:05:48 (9420) [INFO] Trying other mirror. * 2025-02-10 02:06:05 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-10 02:06:05 (9420) [INFO] Trying other mirror. * 2025-02-10 02:06:17 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-10 02:06:17 (9420) [INFO] Trying other mirror. * 2025-02-10 02:06:19 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:06:19 (9420) [INFO] Trying other mirror. * 2025-02-10 02:06:36 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-10 02:06:36 (9420) [INFO] Trying other mirror. * 2025-02-10 02:06:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:06:47 (9420) [INFO] Trying other mirror. * 2025-02-10 02:07:06 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-10 02:07:06 (9420) [INFO] Trying other mirror. * 2025-02-10 02:07:37 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-10 02:07:37 (9420) [INFO] Trying other mirror. * 2025-02-10 02:08:22 (9420) [INFO] Metadata Cache Created * 2025-02-10 02:08:22 (9437) [INFO] * 2025-02-10 02:08:22 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-02-10 02:08:22 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-10 02:08:22 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-10 02:08:22 (9407) [INFO] * 2025-02-10 02:08:22 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-10 02:08:22 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-10 02:08:22 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-10 02:08:22 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-10 02:08:22 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-10 02:08:22 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-10 02:08:22 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-10 02:08:22 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-10 02:08:22 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-10 02:08:22 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-10 02:08:23 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-10 02:08:23 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-10 02:08:23 (9437) [INFO] * 2025-02-10 02:08:23 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-10 02:08:23 (9407) [INFO] * 2025-02-10 02:08:24 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-10 02:08:24 (9420) [INFO] Determining fastest mirrors * 2025-02-10 02:08:56 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-10 02:08:56 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-10 02:08:56 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-10 02:08:56 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-10 02:09:43 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:09:43 (9420) [INFO] Trying other mirror. * 2025-02-10 02:10:13 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-10 02:10:13 (9420) [INFO] Trying other mirror. * 2025-02-10 02:13:00 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-10 02:13:00 (9420) [INFO] Trying other mirror. * 2025-02-10 02:13:00 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:13:00 (9420) [INFO] Trying other mirror. * 2025-02-10 02:13:31 (9420) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/0c95a97897fa76cfbe1800d1f92be4ebd1ea6b2712020c74973936b129dde073-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:13:31 (9420) [INFO] Trying other mirror. * 2025-02-10 02:13:31 (9420) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/3ec45c43c4fb83de83f4f4fb873288e7afdd17952f98f016094fce5c3b26ab1d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:13:31 (9420) [INFO] Trying other mirror. * 2025-02-10 02:13:48 (9420) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:13:48 (9420) [INFO] Trying other mirror. * 2025-02-10 02:14:03 (9420) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:14:03 (9420) [INFO] Trying other mirror. * 2025-02-10 02:14:19 (9420) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:14:19 (9420) [INFO] Trying other mirror. * 2025-02-10 02:14:35 (9420) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:14:35 (9420) [INFO] Trying other mirror. * 2025-02-10 02:14:50 (9420) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:14:50 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:06 (9420) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:06 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:07 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:07 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:08 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:08 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:08 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:08 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:35 (9420) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/30fbbe036ea57e7b61c5ab97b681de8b8a756f942967541ae3eb925327b45b2b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:35 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:39 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:15:39 (9420) [INFO] Trying other mirror. * 2025-02-10 02:15:51 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5MDkxMDk0OjE3MzkzNTAyOTQ6dpTeu72lOhE0dSwfOdTYdSCMa_x6c5Hb-MTnDqj-vem3zvU5KOroE7N9fZ6L8Np8-YPxLIkToDm3MZE4Er8V5XjJEgaVpaPHmiRzVUHIi2jJe9tNTcnREMe2Fas59-iFWMKOPp4SLIx56URUrzmNyddaY2FCSJRY9jTxQeAp2CCmcD1Yl8TxXvMvNrd8Ocnpgu10AqSx-pDTFSWMXy7X36XIY-HU8xdEAlNDYYSY8ayRj31zIf0Ikw5kufkqPVDet9SPcTf3s9aCW76Yv8IIRwHnu87sYXGgtU8Rr6sFrrEfIhQn_9bD6AzPPytRdvF18qzNzjIuNHpDVnpkd3rVCChnxedRUgKZXKhskSpBOENHmBI5OaLG92rMCDdOluqs8QYNIcwLVN-6na9l8LFb3U-X_oXrMnDtpw8PD_c4GlpfnyXFNylVjrtrbpnH36fPE-12x6-_gLfqCUoreDS66pqSDhnQP5cRUemA0sd5pSiIeHOIYDHEQQCnCNXj_sa8TDqLcsHG4YVArOXadN2fQq7kRb4_ciPJQIf8vEqr5wCTAPJlPNB_Tw72vw6vXuv_jRr32wxsVzemyursE59dbN9U4t-f7zJk8J_v0tpJe-ASh88hDiRcOLssxUdASvdqSy3ReBanLNsO5WewKYrS50bhsVhLzohqwBr3Ur-UQQk%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:15:51 (9420) [INFO] Trying other mirror. * 2025-02-10 02:16:06 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5MDkxMDk0OjE3MzkzNTAyOTQ6dpTeu72lOhE0dSwfOdTYdSCMa_x6c5Hb-MTnDqj-vem3zvU5KOroE7N9fZ6L8Np8-YPxLIkToDm3MZE4Er8V5XjJEgaVpaPHmiRzVUHIi2jJe9tNTcnREMe2Fas59-iFWMKOPp4SLIx56URUrzmNyddaY2FCSJRY9jTxQeAp2CCmcD1Yl8TxXvMvNrd8Ocnpgu10AqSx-pDTFSWMXy7X36XIY-HU8xdEAlNDYYSY8ayRj31zIf0Ikw5kufkqPVDet9SPcTf3s9aCW76Yv8IIRwHnu87sYXGgtU8Rr6sFrrEfIhQn_9bD6AzPPytRdvF18qzNzjIuNHpDVnpkd3rVCChnxedRUgKZXKhskSpBOENHmBI5OaLG92rMCDdOluqs8QYNIcwLVN-6na9l8LFb3U-X_oXrMnDtpw8PD_c4GlpfnyXFNylVjrtrbpnH36fPE-12x6-_gLfqCUoreDS66pqSDhnQP5cRUemA0sd5pSiIeHOIYDHEQQCnCNXj_sa8TDqLcsHG4YVArOXadN2fQq7kRb4_ciPJQIf8vEqr5wCTAPJlPNB_Tw72vw6vXuv_jRr32wxsVzemyursE59dbN9U4t-f7zJk8J_v0tpJe-ASh88hDiRcOLssxUdASvdqSy3ReBanLNsO5WewKYrS50bhsVhLzohqwBr3Ur-UQQk%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:16:06 (9420) [INFO] Trying other mirror. * 2025-02-10 02:16:22 (9420) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:16:22 (9420) [INFO] Trying other mirror. * 2025-02-10 02:16:38 (9420) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:16:38 (9420) [INFO] Trying other mirror. * 2025-02-10 02:16:53 (9420) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:16:53 (9420) [INFO] Trying other mirror. * 2025-02-10 02:17:09 (9420) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:17:09 (9420) [INFO] Trying other mirror. * 2025-02-10 02:17:25 (9420) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:17:25 (9420) [INFO] Trying other mirror. * 2025-02-10 02:17:40 (9420) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:17:40 (9420) [INFO] Trying other mirror. * 2025-02-10 02:17:56 (9420) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:17:56 (9420) [INFO] Trying other mirror. * 2025-02-10 02:18:12 (9420) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:18:12 (9420) [INFO] Trying other mirror. * 2025-02-10 02:18:42 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-10 02:18:42 (9420) [INFO] Trying other mirror. * 2025-02-10 02:18:43 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:18:43 (9420) [INFO] Trying other mirror. * 2025-02-10 02:18:58 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:18:58 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:13 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:19:13 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:14 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:19:14 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:14 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:19:14 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:14 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:19:14 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:30 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:19:30 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:44 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:19:44 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:44 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-10 02:19:44 (9420) [INFO] Trying other mirror. * 2025-02-10 02:19:45 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:19:45 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:02 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:20:02 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:14 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:20:14 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:16 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-10 02:20:16 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:16 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-10 02:20:16 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:16 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:20:16 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:32 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:20:32 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:32 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:20:32 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:32 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:20:32 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:33 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:20:33 (9420) [INFO] Trying other mirror. * 2025-02-10 02:20:46 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:20:46 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:02 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:21:02 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:02 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:02 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:02 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:02 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:17 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-10 02:21:17 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:17 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:17 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:18 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:18 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:33 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-10 02:21:33 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:33 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:33 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:47 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:21:47 (9420) [INFO] Trying other mirror. * 2025-02-10 02:21:47 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:21:47 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:03 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:03 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:17 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:17 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:17 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 12] Timeout on https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2025-02-10 02:22:17 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:18 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-02-10 02:22:18 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:18 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-10 02:22:18 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:18 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:18 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:19 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:19 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:33 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:33 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:33 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:33 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:34 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:34 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:35 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:35 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:49 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-10 02:22:49 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:51 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:51 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:51 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:51 (9420) [INFO] Trying other mirror. * 2025-02-10 02:22:51 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:22:51 (9420) [INFO] Trying other mirror. * 2025-02-10 02:23:06 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:23:06 (9420) [INFO] Trying other mirror. * 2025-02-10 02:23:07 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:23:07 (9420) [INFO] Trying other mirror. * 2025-02-10 02:23:20 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-10 02:23:20 (9420) [INFO] Trying other mirror. * 2025-02-10 02:23:38 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-10 02:23:38 (9420) [INFO] Trying other mirror. * 2025-02-11 01:53:51 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-11 01:57:52 (10486) [INFO] Script is up to date. * 2025-02-11 02:01:55 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-11 02:01:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-11 02:01:55 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-11 02:01:55 (9407) [INFO] * 2025-02-11 02:01:59 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-11 02:01:59 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-11 02:01:59 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-11 02:01:59 (9407) [INFO] * 2025-02-11 02:02:11 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-11 02:02:14 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-11 02:02:14 (9407) [INFO] * 2025-02-11 02:02:15 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-11 02:02:15 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-11 02:02:45 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-11 02:02:45 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-11 02:02:45 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-11 02:02:45 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-11 02:03:31 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') * 2025-02-11 02:03:31 (9420) [INFO] Trying other mirror. * 2025-02-11 02:06:02 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-11 02:06:02 (9420) [INFO] Trying other mirror. * 2025-02-11 02:06:19 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-11 02:06:19 (9420) [INFO] Trying other mirror. * 2025-02-11 02:06:35 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-11 02:06:35 (9420) [INFO] Trying other mirror. * 2025-02-11 02:06:48 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:06:48 (9420) [INFO] Trying other mirror. * 2025-02-11 02:06:49 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:06:49 (9420) [INFO] Trying other mirror. * 2025-02-11 02:07:06 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:07:06 (9420) [INFO] Trying other mirror. * 2025-02-11 02:07:36 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-11 02:07:36 (9420) [INFO] Trying other mirror. * 2025-02-11 02:08:06 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-02-11 02:08:06 (9420) [INFO] Trying other mirror. * 2025-02-11 02:08:48 (9420) [INFO] Metadata Cache Created * 2025-02-11 02:08:48 (9437) [INFO] * 2025-02-11 02:08:48 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. * 2025-02-11 02:08:48 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-11 02:08:48 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-11 02:08:48 (9407) [INFO] * 2025-02-11 02:08:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-11 02:08:49 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-11 02:08:49 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-11 02:08:49 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-11 02:08:49 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-11 02:08:49 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-11 02:08:49 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-11 02:08:49 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-11 02:08:49 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-11 02:08:49 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-11 02:08:50 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-11 02:08:50 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-11 02:08:50 (9437) [INFO] * 2025-02-11 02:08:50 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-11 02:08:50 (9407) [INFO] * 2025-02-11 02:08:50 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-11 02:08:51 (9420) [INFO] Determining fastest mirrors * 2025-02-11 02:09:22 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-11 02:09:22 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-11 02:09:22 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-11 02:09:22 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-11 02:10:08 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-11 02:10:08 (9420) [INFO] Trying other mirror. * 2025-02-11 02:10:39 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-11 02:10:39 (9420) [INFO] Trying other mirror. * 2025-02-11 02:11:10 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-11 02:11:10 (9420) [INFO] Trying other mirror. * 2025-02-11 02:13:40 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-11 02:13:40 (9420) [INFO] Trying other mirror. * 2025-02-11 02:13:40 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-11 02:13:40 (9420) [INFO] Trying other mirror. * 2025-02-11 02:14:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:14:11 (9420) [INFO] Trying other mirror. * 2025-02-11 02:14:59 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:14:59 (9420) [INFO] Trying other mirror. * 2025-02-11 02:14:59 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-11 02:14:59 (9420) [INFO] Trying other mirror. * 2025-02-11 02:15:48 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-11 02:15:48 (9420) [INFO] Trying other mirror. * 2025-02-11 02:16:03 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-11 02:16:03 (9420) [INFO] Trying other mirror. * 2025-02-11 02:16:18 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-11 02:16:18 (9420) [INFO] Trying other mirror. * 2025-02-11 02:16:48 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:16:48 (9420) [INFO] Trying other mirror. * 2025-02-11 02:17:19 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-11 02:17:19 (9420) [INFO] Trying other mirror. * 2025-02-11 02:17:19 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:17:19 (9420) [INFO] Trying other mirror. * 2025-02-11 02:18:52 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-11 02:18:52 (9420) [INFO] Trying other mirror. * 2025-02-11 02:19:23 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-11 02:19:23 (9420) [INFO] Trying other mirror. * 2025-02-11 02:19:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-11 02:19:54 (9420) [INFO] Trying other mirror. * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-02-11 02:20:24 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-11 02:20:24 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-11 02:20:24 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-11 02:20:24 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-11 02:20:24 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-11 02:20:24 (9420) [INFO] yum --disablerepo= ... * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-11 02:20:24 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-11 02:20:24 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] yum-config-manager --disable * 2025-02-11 02:20:24 (9420) [INFO] or * 2025-02-11 02:20:24 (9420) [INFO] subscription-manager repos --disable= * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-11 02:20:24 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-11 02:20:24 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-11 02:20:24 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-11 02:20:24 (9420) [INFO] compromise: * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-02-11 02:20:24 (9420) [INFO] * 2025-02-11 02:20:24 (9420) [INFO] extras: Check uncompressed DB failed * 2025-02-11 02:20:24 (9437) [INFO] * 2025-02-11 02:20:24 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-11 02:20:24 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') 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 extras: Check uncompressed DB failed * 2025-02-11 02:20:25 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-11 02:20:25 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-11 02:20:25 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-11 02:20:25 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-11 02:20:25 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-11 02:20:32 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Eur2zdme4O/ea_profile.json * 2025-02-12 01:55:46 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-12 01:59:47 (10486) [INFO] Script is up to date. * 2025-02-12 02:03:50 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-12 02:03:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-12 02:03:51 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-12 02:03:51 (9407) [INFO] * 2025-02-12 02:03:54 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-12 02:03:54 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-12 02:03:54 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-12 02:03:54 (9407) [INFO] * 2025-02-12 02:04:05 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-12 02:04:08 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-12 02:04:08 (9407) [INFO] * 2025-02-12 02:04:08 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-12 02:04:08 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-12 02:04:38 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-12 02:04:38 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-12 02:04:38 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-12 02:04:38 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-12 02:05:24 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-12 02:05:24 (9420) [INFO] Trying other mirror. * 2025-02-12 02:07:55 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-02-12 02:07:55 (9420) [INFO] Trying other mirror. * 2025-02-12 02:08:11 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:08:11 (9420) [INFO] Trying other mirror. * 2025-02-12 02:08:41 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:08:41 (9420) [INFO] Trying other mirror. * 2025-02-12 02:08:44 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-12 02:08:44 (9420) [INFO] Trying other mirror. * 2025-02-12 02:08:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:08:54 (9420) [INFO] Trying other mirror. * 2025-02-12 02:09:11 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-12 02:09:11 (9420) [INFO] Trying other mirror. * 2025-02-12 02:09:14 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:09:14 (9420) [INFO] Trying other mirror. * 2025-02-12 02:09:24 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-12 02:09:24 (9420) [INFO] Trying other mirror. * 2025-02-12 02:09:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:09:45 (9420) [INFO] Trying other mirror. * 2025-02-12 02:10:16 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:10:16 (9420) [INFO] Trying other mirror. * 2025-02-12 02:11:01 (9420) [INFO] Metadata Cache Created * 2025-02-12 02:11:01 (9437) [INFO] * 2025-02-12 02:11:01 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-02-12 02:11:01 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-12 02:11:01 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-12 02:11:01 (9407) [INFO] * 2025-02-12 02:11:02 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-12 02:11:02 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-12 02:11:02 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-12 02:11:02 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-12 02:11:02 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-12 02:11:02 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-12 02:11:02 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-12 02:11:02 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-12 02:11:02 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-12 02:11:02 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-12 02:11:03 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-12 02:11:03 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-12 02:11:03 (9437) [INFO] * 2025-02-12 02:11:03 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-12 02:11:03 (9407) [INFO] * 2025-02-12 02:11:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-12 02:11:04 (9420) [INFO] Determining fastest mirrors * 2025-02-12 02:11:35 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-12 02:11:35 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-12 02:11:35 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-12 02:11:35 (9420) [INFO] * epel: dl.fedoraproject.org * 2025-02-12 02:12:21 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30722 milliseconds') * 2025-02-12 02:12:21 (9420) [INFO] Trying other mirror. * 2025-02-12 02:15:09 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-12 02:15:09 (9420) [INFO] Trying other mirror. * 2025-02-12 02:15:09 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:15:09 (9420) [INFO] Trying other mirror. * 2025-02-12 02:15:39 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:15:39 (9420) [INFO] Trying other mirror. * 2025-02-12 02:16:10 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-12 02:16:10 (9420) [INFO] Trying other mirror. * 2025-02-12 02:17:48 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:17:48 (9420) [INFO] Trying other mirror. * 2025-02-12 02:17:49 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-12 02:17:49 (9420) [INFO] Trying other mirror. * 2025-02-12 02:18:18 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30024 milliseconds with 0 out of 0 bytes received') * 2025-02-12 02:18:18 (9420) [INFO] Trying other mirror. * 2025-02-12 02:21:07 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:21:07 (9420) [INFO] Trying other mirror. * 2025-02-12 02:22:10 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:22:10 (9420) [INFO] Trying other mirror. * 2025-02-12 02:22:41 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-12 02:22:41 (9420) [INFO] Trying other mirror. * 2025-02-12 02:23:11 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:23:11 (9420) [INFO] Trying other mirror. * 2025-02-12 02:23:12 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-12 02:23:12 (9420) [INFO] Trying other mirror. * 2025-02-12 02:23:42 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:23:42 (9420) [INFO] Trying other mirror. * 2025-02-12 02:24:13 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-12 02:24:13 (9420) [INFO] Trying other mirror. * 2025-02-12 02:24:43 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-12 02:24:44 (9420) [INFO] Trying other mirror. * 2025-02-12 02:25:14 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-12 02:25:14 (9420) [INFO] Trying other mirror. * 2025-02-13 01:52:13 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-13 01:56:14 (10486) [INFO] Script is up to date. * 2025-02-13 02:00:16 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-13 02:00:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-13 02:00:17 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-13 02:00:17 (9407) [INFO] * 2025-02-13 02:00:20 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-13 02:00:20 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-13 02:00:20 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-13 02:00:20 (9407) [INFO] * 2025-02-13 02:00:31 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-13 02:00:33 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-13 02:00:33 (9407) [INFO] * 2025-02-13 02:00:33 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-13 02:00:33 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-13 02:01:03 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-13 02:01:03 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-13 02:01:03 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-13 02:01:03 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-13 02:03:49 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:03:49 (9420) [INFO] Trying other mirror. * 2025-02-13 02:04:06 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-13 02:04:06 (9420) [INFO] Trying other mirror. * 2025-02-13 02:04:35 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-13 02:04:35 (9420) [INFO] Trying other mirror. * 2025-02-13 02:04:38 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:04:38 (9420) [INFO] Trying other mirror. * 2025-02-13 02:04:49 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-02-13 02:04:49 (9420) [INFO] Trying other mirror. * 2025-02-13 02:05:06 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-13 02:05:06 (9420) [INFO] Trying other mirror. * 2025-02-13 02:05:20 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:05:20 (9420) [INFO] Trying other mirror. * 2025-02-13 02:05:37 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-13 02:05:37 (9420) [INFO] Trying other mirror. * 2025-02-13 02:05:50 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-13 02:05:50 (9420) [INFO] Trying other mirror. * 2025-02-13 02:06:31 (9420) [INFO] Metadata Cache Created * 2025-02-13 02:06:31 (9437) [INFO] * 2025-02-13 02:06:31 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-02-13 02:06:31 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-13 02:06:31 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-13 02:06:31 (9407) [INFO] * 2025-02-13 02:06:32 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-13 02:06:32 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-13 02:06:32 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-13 02:06:32 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-13 02:06:32 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-13 02:06:32 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-13 02:06:32 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-13 02:06:32 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-13 02:06:32 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-13 02:06:32 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-13 02:06:33 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-13 02:06:33 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-13 02:06:33 (9437) [INFO] * 2025-02-13 02:06:33 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-13 02:06:33 (9407) [INFO] * 2025-02-13 02:06:33 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-13 02:06:34 (9420) [INFO] Determining fastest mirrors * 2025-02-13 02:07:05 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-13 02:07:05 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-13 02:07:05 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-13 02:07:05 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-13 02:10:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:10:11 (9420) [INFO] Trying other mirror. * 2025-02-13 02:10:12 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-13 02:10:12 (9420) [INFO] Trying other mirror. * 2025-02-13 02:10:42 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-13 02:10:42 (9420) [INFO] Trying other mirror. * 2025-02-13 02:10:43 (9420) [INFO] https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/3ec45c43c4fb83de83f4f4fb873288e7afdd17952f98f016094fce5c3b26ab1d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:10:43 (9420) [INFO] Trying other mirror. * 2025-02-13 02:10:59 (9420) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:10:59 (9420) [INFO] Trying other mirror. * 2025-02-13 02:11:14 (9420) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:11:14 (9420) [INFO] Trying other mirror. * 2025-02-13 02:11:30 (9420) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:11:30 (9420) [INFO] Trying other mirror. * 2025-02-13 02:11:46 (9420) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:11:46 (9420) [INFO] Trying other mirror. * 2025-02-13 02:12:01 (9420) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:12:01 (9420) [INFO] Trying other mirror. * 2025-02-13 02:12:17 (9420) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:12:17 (9420) [INFO] Trying other mirror. * 2025-02-13 02:12:19 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:12:19 (9420) [INFO] Trying other mirror. * 2025-02-13 02:12:46 (9420) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f4d562ca887427d73dba96a09b4e5dc40bf0560e0207afb00eede1d666015edf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:12:46 (9420) [INFO] Trying other mirror. * 2025-02-13 02:12:49 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:12:49 (9420) [INFO] Trying other mirror. * 2025-02-13 02:13:02 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5MzIwMTk4OjE3Mzk1NzkzOTg6KxdBOef00UZLPqU7empAEAa5Kh5jhCyk0lmHHAXQGxbnScUS-BPqf9BCK_ESpUzZRzxFZTJ4Tu-c1Co5Pqk7LsfjcUpgro8WQ5pXtfmOIiwugXqJDSR_FzWgBB95YXN2fakTOS344FyMkf2iyTw0qucRZAQrKIr6sjBHpLtqjsMS43IuCPy_IAokceoEywtqY3Ls5Dm1ZsGXS_Xl1OFtwhyTrQfCEhuiPKMUtc5U83ZCbHHNtQQQE1oNCayY27_lnj95qga1MZFrLaN7ixOjR-1Gc0zBptKwnrGixg5O_MaXoa4XQuFm_exjmD2NfmI9FQ7Qc5CmGyKHrwiOJSZN2DhSW70T0efF_MGq5q0sDRet8c0asxAkW86vrNZ9BxSZK1pNFNF4pLnXD5W_r6CvjkWnpC0OWPpEetWR2ECgy6xp2TDlZXmAgg59O0JI0Z5WO2Jl5ZmxZLJb9Sj19a3qvzWfPQXCvOBlQaNkAPbdOeFEYxNy3UoofIFBNQhuVqxzEH0YCB6OB9aYhBPgu4p19Z3rmGHWg3u2c613iACzaGKsegqtRJxo14sfw41CURx3s1YfqDaRhne8oD4nEeyA_lGfB7oqruvEL2Wddt-g8MMBCm4FUhLfodsRlrYvUaWPTz_6kw7Rx9bjbZV78F1rSpRbcxlwOuxijLUu45fa8_w%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:13:02 (9420) [INFO] Trying other mirror. * 2025-02-13 02:13:18 (9420) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:13:18 (9420) [INFO] Trying other mirror. * 2025-02-13 02:13:33 (9420) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:13:33 (9420) [INFO] Trying other mirror. * 2025-02-13 02:13:49 (9420) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:13:49 (9420) [INFO] Trying other mirror. * 2025-02-13 02:14:05 (9420) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:14:05 (9420) [INFO] Trying other mirror. * 2025-02-13 02:14:20 (9420) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:14:20 (9420) [INFO] Trying other mirror. * 2025-02-13 02:14:36 (9420) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:14:36 (9420) [INFO] Trying other mirror. * 2025-02-13 02:14:52 (9420) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:14:52 (9420) [INFO] Trying other mirror. * 2025-02-13 02:15:07 (9420) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:15:07 (9420) [INFO] Trying other mirror. * 2025-02-13 02:15:37 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:15:37 (9420) [INFO] Trying other mirror. * 2025-02-13 02:15:38 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-13 02:15:38 (9420) [INFO] Trying other mirror. * 2025-02-13 02:15:53 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:15:53 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:09 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:16:09 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:09 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:16:09 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:10 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:16:10 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:39 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:16:39 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:39 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:16:39 (9420) [INFO] Trying other mirror. * 2025-02-13 02:16:40 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:16:40 (9420) [INFO] Trying other mirror. * 2025-02-13 02:17:10 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:17:10 (9420) [INFO] Trying other mirror. * 2025-02-13 02:17:10 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-13 02:17:10 (9420) [INFO] Trying other mirror. * 2025-02-13 02:17:26 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:17:26 (9420) [INFO] Trying other mirror. * 2025-02-13 02:17:41 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30314 milliseconds') * 2025-02-13 02:17:41 (9420) [INFO] Trying other mirror. * 2025-02-13 02:17:42 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:17:42 (9420) [INFO] Trying other mirror. * 2025-02-13 02:18:11 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-13 02:18:11 (9420) [INFO] Trying other mirror. * 2025-02-13 02:18:12 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:18:12 (9420) [INFO] Trying other mirror. * 2025-02-13 02:18:28 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:18:28 (9420) [INFO] Trying other mirror. * 2025-02-13 02:18:41 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:18:41 (9420) [INFO] Trying other mirror. * 2025-02-13 02:18:58 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-02-13 02:18:58 (9420) [INFO] Trying other mirror. * 2025-02-13 02:19:15 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:19:15 (9420) [INFO] Trying other mirror. * 2025-02-13 02:19:32 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:19:32 (9420) [INFO] Trying other mirror. * 2025-02-13 02:19:48 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-13 02:19:48 (9420) [INFO] Trying other mirror. * 2025-02-13 02:20:25 (9420) [INFO] Metadata Cache Created * 2025-02-13 02:20:25 (9437) [INFO] * 2025-02-13 02:20:25 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-13 02:20:25 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/3ec45c43c4fb83de83f4f4fb873288e7afdd17952f98f016094fce5c3b26ab1d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f4d562ca887427d73dba96a09b4e5dc40bf0560e0207afb00eede1d666015edf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5MzIwMTk4OjE3Mzk1NzkzOTg6KxdBOef00UZLPqU7empAEAa5Kh5jhCyk0lmHHAXQGxbnScUS-BPqf9BCK_ESpUzZRzxFZTJ4Tu-c1Co5Pqk7LsfjcUpgro8WQ5pXtfmOIiwugXqJDSR_FzWgBB95YXN2fakTOS344FyMkf2iyTw0qucRZAQrKIr6sjBHpLtqjsMS43IuCPy_IAokceoEywtqY3Ls5Dm1ZsGXS_Xl1OFtwhyTrQfCEhuiPKMUtc5U83ZCbHHNtQQQE1oNCayY27_lnj95qga1MZFrLaN7ixOjR-1Gc0zBptKwnrGixg5O_MaXoa4XQuFm_exjmD2NfmI9FQ7Qc5CmGyKHrwiOJSZN2DhSW70T0efF_MGq5q0sDRet8c0asxAkW86vrNZ9BxSZK1pNFNF4pLnXD5W_r6CvjkWnpC0OWPpEetWR2ECgy6xp2TDlZXmAgg59O0JI0Z5WO2Jl5ZmxZLJb9Sj19a3qvzWfPQXCvOBlQaNkAPbdOeFEYxNy3UoofIFBNQhuVqxzEH0YCB6OB9aYhBPgu4p19Z3rmGHWg3u2c613iACzaGKsegqtRJxo14sfw41CURx3s1YfqDaRhne8oD4nEeyA_lGfB7oqruvEL2Wddt-g8MMBCm4FUhLfodsRlrYvUaWPTz_6kw7Rx9bjbZV78F1rSpRbcxlwOuxijLUu45fa8_w%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30314 milliseconds') Trying other mirror. https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-02-13 02:20:26 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-13 02:20:26 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-13 02:20:26 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-13 02:20:26 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-13 02:20:26 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-13 02:20:33 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/01RQkRAWOn/ea_profile.json * 2025-02-13 02:20:35 (8554) [INFO] Backed up EA4 profile to /tmp/01RQkRAWOn/ea_profile.json * 2025-02-13 02:20:36 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-13 02:20:39 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-13 02:21:10 (641) [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. * 2025-02-13 02:21:10 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-14 01:54:15 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-14 01:58:16 (10486) [INFO] Script is up to date. * 2025-02-14 02:02:19 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-14 02:02:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-14 02:02:19 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-14 02:02:19 (9407) [INFO] * 2025-02-14 02:02:23 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-14 02:02:23 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-14 02:02:23 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-14 02:02:23 (9407) [INFO] * 2025-02-14 02:02:35 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-14 02:02:38 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-14 02:02:38 (9407) [INFO] * 2025-02-14 02:02:38 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-14 02:02:39 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-14 02:03:08 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-14 02:03:08 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-14 02:03:08 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-14 02:03:08 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-14 02:05:55 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-14 02:05:55 (9420) [INFO] Trying other mirror. * 2025-02-14 02:06:12 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-14 02:06:12 (9420) [INFO] Trying other mirror. * 2025-02-14 02:06:41 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:06:41 (9420) [INFO] Trying other mirror. * 2025-02-14 02:06:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-14 02:06:45 (9420) [INFO] Trying other mirror. * 2025-02-14 02:06:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:06:54 (9420) [INFO] Trying other mirror. * 2025-02-14 02:07:16 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-14 02:07:16 (9420) [INFO] Trying other mirror. * 2025-02-14 02:07:25 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-14 02:07:25 (9420) [INFO] Trying other mirror. * 2025-02-14 02:07:46 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:07:46 (9420) [INFO] Trying other mirror. * 2025-02-14 02:08:33 (9420) [INFO] Metadata Cache Created * 2025-02-14 02:08:33 (9437) [INFO] * 2025-02-14 02:08:33 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-14 02:08:33 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-14 02:08:33 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-14 02:08:33 (9407) [INFO] * 2025-02-14 02:08:34 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-14 02:08:34 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-14 02:08:34 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-14 02:08:34 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-14 02:08:34 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-14 02:08:34 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-14 02:08:34 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-14 02:08:34 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-14 02:08:34 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-14 02:08:34 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-14 02:08:35 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-14 02:08:35 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-14 02:08:35 (9437) [INFO] * 2025-02-14 02:08:35 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-14 02:08:35 (9407) [INFO] * 2025-02-14 02:08:35 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-14 02:08:36 (9420) [INFO] Determining fastest mirrors * 2025-02-14 02:09:06 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-14 02:09:06 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-14 02:09:06 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-14 02:09:06 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-14 02:09:53 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-14 02:09:53 (9420) [INFO] Trying other mirror. * 2025-02-14 02:10:24 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-14 02:10:24 (9420) [INFO] Trying other mirror. * 2025-02-14 02:10:54 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-14 02:10:54 (9420) [INFO] Trying other mirror. * 2025-02-14 02:13:25 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-14 02:13:25 (9420) [INFO] Trying other mirror. * 2025-02-14 02:13:25 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:13:25 (9420) [INFO] Trying other mirror. * 2025-02-14 02:13:56 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-02-14 02:13:56 (9420) [INFO] Trying other mirror. * 2025-02-14 02:14:44 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:14:44 (9420) [INFO] Trying other mirror. * 2025-02-14 02:15:17 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-14 02:15:17 (9420) [INFO] Trying other mirror. * 2025-02-14 02:15:18 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-14 02:15:18 (9420) [INFO] Trying other mirror. * 2025-02-14 02:15:33 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-14 02:15:33 (9420) [INFO] Trying other mirror. * 2025-02-14 02:15:48 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-14 02:15:48 (9420) [INFO] Trying other mirror. * 2025-02-14 02:15:48 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-14 02:15:48 (9420) [INFO] Trying other mirror. * 2025-02-14 02:16:18 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-14 02:16:18 (9420) [INFO] Trying other mirror. * 2025-02-14 02:16:48 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:16:48 (9420) [INFO] Trying other mirror. * 2025-02-14 02:16:48 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:16:48 (9420) [INFO] Trying other mirror. * 2025-02-14 02:16:48 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-14 02:16:48 (9420) [INFO] Trying other mirror. * 2025-02-14 02:17:50 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') * 2025-02-14 02:17:50 (9420) [INFO] Trying other mirror. * 2025-02-14 02:18:20 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:18:20 (9420) [INFO] Trying other mirror. * 2025-02-14 02:18:50 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-14 02:18:50 (9420) [INFO] Trying other mirror. * 2025-02-14 02:19:47 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:19:47 (9420) [INFO] Trying other mirror. * 2025-02-14 02:19:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:19:47 (9420) [INFO] Trying other mirror. * 2025-02-14 02:19:47 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-14 02:19:47 (9420) [INFO] Trying other mirror. * 2025-02-14 02:20:17 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-14 02:20:17 (9420) [INFO] Trying other mirror. * 2025-02-14 02:20:18 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-14 02:20:18 (9420) [INFO] Trying other mirror. * 2025-02-14 02:20:49 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-14 02:20:49 (9420) [INFO] Trying other mirror. * 2025-02-14 02:21:19 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-02-14 02:21:19 (9420) [INFO] Trying other mirror. * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-02-14 02:21:51 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-14 02:21:51 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-14 02:21:51 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-14 02:21:51 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-14 02:21:51 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-14 02:21:51 (9420) [INFO] yum --disablerepo= ... * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-14 02:21:51 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-14 02:21:51 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] yum-config-manager --disable * 2025-02-14 02:21:51 (9420) [INFO] or * 2025-02-14 02:21:51 (9420) [INFO] subscription-manager repos --disable= * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-14 02:21:51 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-14 02:21:51 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-14 02:21:51 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-14 02:21:51 (9420) [INFO] compromise: * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-02-14 02:21:51 (9420) [INFO] * 2025-02-14 02:21:51 (9420) [INFO] extras: Check uncompressed DB failed * 2025-02-14 02:21:51 (9437) [INFO] * 2025-02-14 02:21:51 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-14 02:21:51 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') 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 extras: Check uncompressed DB failed * 2025-02-14 02:21:52 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-14 02:21:52 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-14 02:21:52 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-14 02:21:52 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-14 02:21:52 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-14 02:21:58 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ZZ3Zali2Sh/ea_profile.json * 2025-02-15 01:55:24 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-15 01:59:24 (10486) [INFO] Script is up to date. * 2025-02-15 02:03:27 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-15 02:03:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-15 02:03:27 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-15 02:03:27 (9407) [INFO] * 2025-02-15 02:03:31 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-15 02:03:31 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-15 02:03:31 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-15 02:03:31 (9407) [INFO] * 2025-02-15 02:03:45 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-15 02:03:48 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-15 02:03:48 (9407) [INFO] * 2025-02-15 02:03:49 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-15 02:03:49 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-15 02:04:19 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-15 02:04:19 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-15 02:04:19 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-15 02:04:19 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-15 02:07:05 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-15 02:07:05 (9420) [INFO] Trying other mirror. * 2025-02-15 02:07:21 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:07:21 (9420) [INFO] Trying other mirror. * 2025-02-15 02:07:39 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-15 02:07:39 (9420) [INFO] Trying other mirror. * 2025-02-15 02:07:51 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:07:51 (9420) [INFO] Trying other mirror. * 2025-02-15 02:08:09 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:08:09 (9420) [INFO] Trying other mirror. * 2025-02-15 02:08:53 (9420) [INFO] Metadata Cache Created * 2025-02-15 02:08:53 (9437) [INFO] * 2025-02-15 02:08:53 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-15 02:08:53 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-15 02:08:53 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-15 02:08:53 (9407) [INFO] * 2025-02-15 02:08:53 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-15 02:08:54 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-15 02:08:54 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-15 02:08:54 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-15 02:08:54 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-15 02:08:54 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-15 02:08:54 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-15 02:08:54 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-15 02:08:54 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-15 02:08:54 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-15 02:08:54 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-15 02:08:54 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-15 02:08:54 (9437) [INFO] * 2025-02-15 02:08:54 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-15 02:08:54 (9407) [INFO] * 2025-02-15 02:08:55 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-15 02:08:55 (9420) [INFO] Determining fastest mirrors * 2025-02-15 02:09:27 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-15 02:09:27 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-15 02:09:27 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-15 02:09:27 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-15 02:12:29 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-15 02:12:29 (9420) [INFO] Trying other mirror. * 2025-02-15 02:12:29 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:12:29 (9420) [INFO] Trying other mirror. * 2025-02-15 02:13:00 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-15 02:13:00 (9420) [INFO] Trying other mirror. * 2025-02-15 02:13:17 (9420) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:13:17 (9420) [INFO] Trying other mirror. * 2025-02-15 02:15:05 (9420) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f4d562ca887427d73dba96a09b4e5dc40bf0560e0207afb00eede1d666015edf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:15:05 (9420) [INFO] Trying other mirror. * 2025-02-15 02:15:09 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:15:09 (9420) [INFO] Trying other mirror. * 2025-02-15 02:15:21 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5NTQ3MTAxOjE3Mzk4MDYzMDE6hLzOdPAe1Hi25CNljwYgSX0DKaIiwpPXJKCOVB2sbmrU7ehMCq7Rz1jdfOjmONocXDh5AHV5sFh63T-bdBMRVBMhCWuSCePjX8YZtvDz2Tfl1GMiRcdDhx1QrL2iBYjdLvi21Wm90rVGXn66ruYHQpaTMUC4iyzzN_JnXomW7pL_OhNjEyUm196CITdd4KRNSIWGdWbqvXF9I_RupiB4_q65Exp3N1J8miG09UdH33VysqUy_7W_wCmf2sYQ9gRSJnbFcbL7PsjLQyGi8ibfGkDcLLrk3vsygCdCovRta9M8joyquDM2aJFcV7RxiEUfRImKKqaYMne0yRQrMtNevgMYHxc3p19lxI0ScJQ8lHXoD9Yh2--5qtldWp2Y_j9AEuebpNefqlPr8bVvxqTcPsc5UfoaanH10O6_Bvpekz3XHMOFSWa9lDOvwA4elgS_mDF3lt-sDE4HLNNChWlFCBRjhETThlUNfbsIFuZAM5SC2pNtM-06Al8vrgJcb7iSWafxbRkH_3VP9_OrejaKsDViRoEWMIyvJCkNvMLfXHNXXpwlnsfx5OcYpEO9f_9bRpGSvunCTYr33E4Jqs1RttneJrmgTwQRWsNp7k6i4k8CDT9u7clHmUYmGZnEQ_eyRhxu_uQP-TvQBSEUZDKFH1oMnet55sXvT0uirYiDfho%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:15:21 (9420) [INFO] Trying other mirror. * 2025-02-15 02:15:36 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5NTQ3MTAxOjE3Mzk4MDYzMDE6hLzOdPAe1Hi25CNljwYgSX0DKaIiwpPXJKCOVB2sbmrU7ehMCq7Rz1jdfOjmONocXDh5AHV5sFh63T-bdBMRVBMhCWuSCePjX8YZtvDz2Tfl1GMiRcdDhx1QrL2iBYjdLvi21Wm90rVGXn66ruYHQpaTMUC4iyzzN_JnXomW7pL_OhNjEyUm196CITdd4KRNSIWGdWbqvXF9I_RupiB4_q65Exp3N1J8miG09UdH33VysqUy_7W_wCmf2sYQ9gRSJnbFcbL7PsjLQyGi8ibfGkDcLLrk3vsygCdCovRta9M8joyquDM2aJFcV7RxiEUfRImKKqaYMne0yRQrMtNevgMYHxc3p19lxI0ScJQ8lHXoD9Yh2--5qtldWp2Y_j9AEuebpNefqlPr8bVvxqTcPsc5UfoaanH10O6_Bvpekz3XHMOFSWa9lDOvwA4elgS_mDF3lt-sDE4HLNNChWlFCBRjhETThlUNfbsIFuZAM5SC2pNtM-06Al8vrgJcb7iSWafxbRkH_3VP9_OrejaKsDViRoEWMIyvJCkNvMLfXHNXXpwlnsfx5OcYpEO9f_9bRpGSvunCTYr33E4Jqs1RttneJrmgTwQRWsNp7k6i4k8CDT9u7clHmUYmGZnEQ_eyRhxu_uQP-TvQBSEUZDKFH1oMnet55sXvT0uirYiDfho%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:15:36 (9420) [INFO] Trying other mirror. * 2025-02-15 02:15:52 (9420) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:15:52 (9420) [INFO] Trying other mirror. * 2025-02-15 02:16:08 (9420) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:16:08 (9420) [INFO] Trying other mirror. * 2025-02-15 02:16:23 (9420) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:16:23 (9420) [INFO] Trying other mirror. * 2025-02-15 02:16:39 (9420) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:16:39 (9420) [INFO] Trying other mirror. * 2025-02-15 02:16:55 (9420) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:16:55 (9420) [INFO] Trying other mirror. * 2025-02-15 02:17:10 (9420) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:17:10 (9420) [INFO] Trying other mirror. * 2025-02-15 02:17:26 (9420) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:17:26 (9420) [INFO] Trying other mirror. * 2025-02-15 02:17:42 (9420) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:17:42 (9420) [INFO] Trying other mirror. * 2025-02-15 02:18:12 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:18:12 (9420) [INFO] Trying other mirror. * 2025-02-15 02:18:28 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:18:28 (9420) [INFO] Trying other mirror. * 2025-02-15 02:18:43 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:18:43 (9420) [INFO] Trying other mirror. * 2025-02-15 02:18:43 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:18:43 (9420) [INFO] Trying other mirror. * 2025-02-15 02:19:14 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-02-15 02:19:14 (9420) [INFO] Trying other mirror. * 2025-02-15 02:19:44 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:19:44 (9420) [INFO] Trying other mirror. * 2025-02-15 02:19:44 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:19:44 (9420) [INFO] Trying other mirror. * 2025-02-15 02:19:44 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2025-02-15 02:19:44 (9420) [INFO] Trying other mirror. * 2025-02-15 02:20:15 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:20:15 (9420) [INFO] Trying other mirror. * 2025-02-15 02:20:15 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:20:15 (9420) [INFO] Trying other mirror. * 2025-02-15 02:20:15 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-15 02:20:15 (9420) [INFO] Trying other mirror. * 2025-02-15 02:20:45 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:20:45 (9420) [INFO] Trying other mirror. * 2025-02-15 02:20:46 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-15 02:20:46 (9420) [INFO] Trying other mirror. * 2025-02-15 02:21:15 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:21:15 (9420) [INFO] Trying other mirror. * 2025-02-15 02:21:16 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-15 02:21:16 (9420) [INFO] Trying other mirror. * 2025-02-15 02:21:47 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-15 02:21:47 (9420) [INFO] Trying other mirror. * 2025-02-15 02:22:17 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-02-15 02:22:17 (9420) [INFO] Trying other mirror. * 2025-02-15 02:22:46 (9420) [INFO] Metadata Cache Created * 2025-02-15 02:22:46 (9437) [INFO] * 2025-02-15 02:22:46 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-15 02:22:46 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f4d562ca887427d73dba96a09b4e5dc40bf0560e0207afb00eede1d666015edf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5NTQ3MTAxOjE3Mzk4MDYzMDE6hLzOdPAe1Hi25CNljwYgSX0DKaIiwpPXJKCOVB2sbmrU7ehMCq7Rz1jdfOjmONocXDh5AHV5sFh63T-bdBMRVBMhCWuSCePjX8YZtvDz2Tfl1GMiRcdDhx1QrL2iBYjdLvi21Wm90rVGXn66ruYHQpaTMUC4iyzzN_JnXomW7pL_OhNjEyUm196CITdd4KRNSIWGdWbqvXF9I_RupiB4_q65Exp3N1J8miG09UdH33VysqUy_7W_wCmf2sYQ9gRSJnbFcbL7PsjLQyGi8ibfGkDcLLrk3vsygCdCovRta9M8joyquDM2aJFcV7RxiEUfRImKKqaYMne0yRQrMtNevgMYHxc3p19lxI0ScJQ8lHXoD9Yh2--5qtldWp2Y_j9AEuebpNefqlPr8bVvxqTcPsc5UfoaanH10O6_Bvpekz3XHMOFSWa9lDOvwA4elgS_mDF3lt-sDE4HLNNChWlFCBRjhETThlUNfbsIFuZAM5SC2pNtM-06Al8vrgJcb7iSWafxbRkH_3VP9_OrejaKsDViRoEWMIyvJCkNvMLfXHNXXpwlnsfx5OcYpEO9f_9bRpGSvunCTYr33E4Jqs1RttneJrmgTwQRWsNp7k6i4k8CDT9u7clHmUYmGZnEQ_eyRhxu_uQP-TvQBSEUZDKFH1oMnet55sXvT0uirYiDfho%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5NTQ3MTAxOjE3Mzk4MDYzMDE6hLzOdPAe1Hi25CNljwYgSX0DKaIiwpPXJKCOVB2sbmrU7ehMCq7Rz1jdfOjmONocXDh5AHV5sFh63T-bdBMRVBMhCWuSCePjX8YZtvDz2Tfl1GMiRcdDhx1QrL2iBYjdLvi21Wm90rVGXn66ruYHQpaTMUC4iyzzN_JnXomW7pL_OhNjEyUm196CITdd4KRNSIWGdWbqvXF9I_RupiB4_q65Exp3N1J8miG09UdH33VysqUy_7W_wCmf2sYQ9gRSJnbFcbL7PsjLQyGi8ibfGkDcLLrk3vsygCdCovRta9M8joyquDM2aJFcV7RxiEUfRImKKqaYMne0yRQrMtNevgMYHxc3p19lxI0ScJQ8lHXoD9Yh2--5qtldWp2Y_j9AEuebpNefqlPr8bVvxqTcPsc5UfoaanH10O6_Bvpekz3XHMOFSWa9lDOvwA4elgS_mDF3lt-sDE4HLNNChWlFCBRjhETThlUNfbsIFuZAM5SC2pNtM-06Al8vrgJcb7iSWafxbRkH_3VP9_OrejaKsDViRoEWMIyvJCkNvMLfXHNXXpwlnsfx5OcYpEO9f_9bRpGSvunCTYr33E4Jqs1RttneJrmgTwQRWsNp7k6i4k8CDT9u7clHmUYmGZnEQ_eyRhxu_uQP-TvQBSEUZDKFH1oMnet55sXvT0uirYiDfho%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/wp-toolkit/repodata/f89ed153ea92cbdb90655fc3609b81671b34dcd9db53d928ed863513589abb4c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.4/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-02-15 02:22:46 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-15 02:22:46 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-15 02:22:46 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-15 02:22:46 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-15 02:22:46 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-15 02:22:52 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/s3knVXoecA/ea_profile.json * 2025-02-15 02:22:54 (8554) [INFO] Backed up EA4 profile to /tmp/s3knVXoecA/ea_profile.json * 2025-02-15 02:22:55 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-15 02:22:58 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-15 02:23:29 (641) [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. * 2025-02-15 02:23:29 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-16 01:57:22 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-16 02:01:23 (10486) [INFO] Script is up to date. * 2025-02-16 02:05:26 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-16 02:05:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-16 02:05:26 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-16 02:05:26 (9407) [INFO] * 2025-02-16 02:05:30 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-16 02:05:30 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-16 02:05:30 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-16 02:05:30 (9407) [INFO] * 2025-02-16 02:05:41 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-16 02:05:44 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-16 02:05:44 (9407) [INFO] * 2025-02-16 02:05:45 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-16 02:05:45 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-16 02:06:14 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-16 02:06:14 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-16 02:06:14 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-16 02:06:14 (9420) [INFO] * epel: mirror.math.princeton.edu * 2025-02-16 02:09:01 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:09:01 (9420) [INFO] Trying other mirror. * 2025-02-16 02:09:17 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:09:17 (9420) [INFO] Trying other mirror. * 2025-02-16 02:09:37 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:09:37 (9420) [INFO] Trying other mirror. * 2025-02-16 02:09:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:09:47 (9420) [INFO] Trying other mirror. * 2025-02-16 02:10:07 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:10:07 (9420) [INFO] Trying other mirror. * 2025-02-16 02:10:17 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:10:17 (9420) [INFO] Trying other mirror. * 2025-02-16 02:11:01 (9420) [INFO] Metadata Cache Created * 2025-02-16 02:11:01 (9437) [INFO] * 2025-02-16 02:11:01 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-16 02:11:01 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-16 02:11:01 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-16 02:11:01 (9407) [INFO] * 2025-02-16 02:11:01 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-16 02:11:01 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-16 02:11:01 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-16 02:11:01 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-16 02:11:01 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-16 02:11:01 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-16 02:11:01 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-16 02:11:01 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-16 02:11:01 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-16 02:11:01 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-16 02:11:02 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-16 02:11:02 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-16 02:11:02 (9437) [INFO] * 2025-02-16 02:11:02 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-16 02:11:02 (9407) [INFO] * 2025-02-16 02:11:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-16 02:11:03 (9420) [INFO] Determining fastest mirrors * 2025-02-16 02:11:36 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-16 02:11:36 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-16 02:11:36 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-16 02:11:36 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-16 02:12:22 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:12:22 (9420) [INFO] Trying other mirror. * 2025-02-16 02:12:53 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:12:53 (9420) [INFO] Trying other mirror. * 2025-02-16 02:15:41 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-16 02:15:41 (9420) [INFO] Trying other mirror. * 2025-02-16 02:15:41 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30599 milliseconds') * 2025-02-16 02:15:41 (9420) [INFO] Trying other mirror. * 2025-02-16 02:16:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:16:11 (9420) [INFO] Trying other mirror. * 2025-02-16 02:18:21 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-16 02:18:21 (9420) [INFO] Trying other mirror. * 2025-02-16 02:21:09 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:21:09 (9420) [INFO] Trying other mirror. * 2025-02-16 02:21:09 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-16 02:21:09 (9420) [INFO] Trying other mirror. * 2025-02-16 02:22:11 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:22:11 (9420) [INFO] Trying other mirror. * 2025-02-16 02:22:11 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-02-16 02:22:11 (9420) [INFO] Trying other mirror. * 2025-02-16 02:22:41 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-16 02:22:41 (9420) [INFO] Trying other mirror. * 2025-02-16 02:23:13 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-16 02:23:13 (9420) [INFO] Trying other mirror. * 2025-02-16 02:23:43 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-16 02:23:43 (9420) [INFO] Trying other mirror. * 2025-02-16 02:25:04 (9420) [INFO] Metadata Cache Created * 2025-02-16 02:25:05 (9437) [INFO] * 2025-02-16 02:25:05 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-16 02:25:05 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30599 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-02-16 02:25:05 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-16 02:25:05 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-16 02:25:05 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-16 02:25:05 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-16 02:25:05 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-16 02:25:13 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GUSR5pvD9r/ea_profile.json * 2025-02-16 02:25:16 (8554) [INFO] Backed up EA4 profile to /tmp/GUSR5pvD9r/ea_profile.json * 2025-02-16 02:25:16 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-16 02:25:20 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-16 02:25:51 (641) [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. * 2025-02-16 02:25:51 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-17 01:55:55 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-17 01:59:56 (10486) [INFO] Script is up to date. * 2025-02-17 02:03:58 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-17 02:03:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-17 02:03:58 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-17 02:03:58 (9407) [INFO] * 2025-02-17 02:04:03 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-17 02:04:03 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-17 02:04:03 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-17 02:04:03 (9407) [INFO] * 2025-02-17 02:04:14 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-17 02:04:18 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-17 02:04:18 (9407) [INFO] * 2025-02-17 02:04:18 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-17 02:04:18 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-17 02:04:48 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-17 02:04:48 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-17 02:04:48 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-17 02:04:48 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-17 02:05:34 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-02-17 02:05:34 (9420) [INFO] Trying other mirror. * 2025-02-17 02:06:05 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-17 02:06:05 (9420) [INFO] Trying other mirror. * 2025-02-17 02:08:35 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-17 02:08:35 (9420) [INFO] Trying other mirror. * 2025-02-17 02:08:51 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:08:51 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:08 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:09:08 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:22 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-17 02:09:22 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:22 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-17 02:09:22 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:38 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-17 02:09:38 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:52 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:09:52 (9420) [INFO] Trying other mirror. * 2025-02-17 02:09:53 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-17 02:09:53 (9420) [INFO] Trying other mirror. * 2025-02-17 02:10:24 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-17 02:10:24 (9420) [INFO] Trying other mirror. * 2025-02-17 02:10:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-17 02:10:54 (9420) [INFO] Trying other mirror. * 2025-02-17 02:11:38 (9420) [INFO] Metadata Cache Created * 2025-02-17 02:11:38 (9437) [INFO] * 2025-02-17 02:11:38 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-02-17 02:11:38 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-17 02:11:38 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-17 02:11:38 (9407) [INFO] * 2025-02-17 02:11:38 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-17 02:11:38 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-17 02:11:38 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-17 02:11:38 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-17 02:11:38 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-17 02:11:38 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-17 02:11:38 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-17 02:11:38 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-17 02:11:38 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-17 02:11:38 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-17 02:11:39 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-17 02:11:39 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-17 02:11:39 (9437) [INFO] * 2025-02-17 02:11:39 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-17 02:11:39 (9407) [INFO] * 2025-02-17 02:11:40 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-17 02:11:40 (9420) [INFO] Determining fastest mirrors * 2025-02-17 02:12:10 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-17 02:12:10 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-17 02:12:10 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-17 02:12:10 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-17 02:15:14 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-17 02:15:14 (9420) [INFO] Trying other mirror. * 2025-02-17 02:15:14 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-17 02:15:14 (9420) [INFO] Trying other mirror. * 2025-02-17 02:15:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-17 02:15:45 (9420) [INFO] Trying other mirror. * 2025-02-17 02:16:15 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:16:15 (9420) [INFO] Trying other mirror. * 2025-02-17 02:17:55 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-17 02:17:55 (9420) [INFO] Trying other mirror. * 2025-02-17 02:17:55 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-17 02:17:55 (9420) [INFO] Trying other mirror. * 2025-02-17 02:21:14 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-02-17 02:21:14 (9420) [INFO] Trying other mirror. * 2025-02-17 02:21:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-17 02:21:45 (9420) [INFO] Trying other mirror. * 2025-02-17 02:22:16 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-02-17 02:22:16 (9420) [INFO] Trying other mirror. * 2025-02-17 02:23:17 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:23:17 (9420) [INFO] Trying other mirror. * 2025-02-17 02:23:47 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:23:47 (9420) [INFO] Trying other mirror. * 2025-02-17 02:23:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-17 02:23:47 (9420) [INFO] Trying other mirror. * 2025-02-17 02:23:47 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-17 02:23:47 (9420) [INFO] Trying other mirror. * 2025-02-17 02:24:18 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-17 02:24:18 (9420) [INFO] Trying other mirror. * 2025-02-17 02:24:48 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:24:48 (9420) [INFO] Trying other mirror. * 2025-02-17 02:24:48 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-17 02:24:48 (9420) [INFO] Trying other mirror. * 2025-02-17 02:25:19 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-02-17 02:25:19 (9420) [INFO] Trying other mirror. * 2025-02-18 01:55:53 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-18 01:59:53 (10486) [INFO] Script is up to date. * 2025-02-18 02:03:56 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-18 02:03:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-18 02:03:56 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-18 02:03:56 (9407) [INFO] * 2025-02-18 02:04:00 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-18 02:04:00 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-18 02:04:00 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-18 02:04:00 (9407) [INFO] * 2025-02-18 02:04:09 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-18 02:04:11 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-18 02:04:11 (9407) [INFO] * 2025-02-18 02:04:11 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-18 02:04:11 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-18 02:04:41 (9420) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-02-18 02:04:41 (9420) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-02-18 02:04:41 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-18 02:04:41 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-18 02:04:41 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-18 02:04:41 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-18 02:07:27 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:07:27 (9420) [INFO] Trying other mirror. * 2025-02-18 02:07:43 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:07:43 (9420) [INFO] Trying other mirror. * 2025-02-18 02:08:27 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:08:27 (9420) [INFO] Trying other mirror. * 2025-02-18 02:08:29 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:08:29 (9420) [INFO] Trying other mirror. * 2025-02-18 02:08:58 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-18 02:08:58 (9420) [INFO] Trying other mirror. * 2025-02-18 02:08:59 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30028 milliseconds with 0 out of 0 bytes received') * 2025-02-18 02:08:59 (9420) [INFO] Trying other mirror. * 2025-02-18 02:09:30 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-18 02:09:30 (9420) [INFO] Trying other mirror. * 2025-02-18 02:10:19 (9420) [INFO] Metadata Cache Created * 2025-02-18 02:10:19 (9437) [INFO] * 2025-02-18 02:10:19 (5884) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30028 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-02-18 02:10:19 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-18 02:10:19 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-18 02:10:19 (9407) [INFO] * 2025-02-18 02:10:19 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-18 02:10:19 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-18 02:10:19 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-18 02:10:19 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-18 02:10:19 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-18 02:10:19 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-18 02:10:19 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-18 02:10:19 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-18 02:10:19 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-18 02:10:19 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-18 02:10:20 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-18 02:10:20 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-18 02:10:20 (9437) [INFO] * 2025-02-18 02:10:20 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-18 02:10:20 (9407) [INFO] * 2025-02-18 02:10:20 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-18 02:10:20 (9420) [INFO] Determining fastest mirrors * 2025-02-18 02:10:51 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-18 02:10:51 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-18 02:10:51 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-18 02:10:51 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-18 02:11:38 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-18 02:11:38 (9420) [INFO] Trying other mirror. * 2025-02-18 02:14:26 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-18 02:14:26 (9420) [INFO] Trying other mirror. * 2025-02-18 02:14:26 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-18 02:14:26 (9420) [INFO] Trying other mirror. * 2025-02-18 02:14:56 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:14:56 (9420) [INFO] Trying other mirror. * 2025-02-18 02:17:05 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:17:05 (9420) [INFO] Trying other mirror. * 2025-02-18 02:19:54 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-18 02:19:54 (9420) [INFO] Trying other mirror. * 2025-02-18 02:20:55 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-18 02:20:55 (9420) [INFO] Trying other mirror. * 2025-02-18 02:21:26 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-02-18 02:21:26 (9420) [INFO] Trying other mirror. * 2025-02-18 02:21:57 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:21:57 (9420) [INFO] Trying other mirror. * 2025-02-18 02:21:57 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:21:57 (9420) [INFO] Trying other mirror. * 2025-02-18 02:21:57 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-18 02:21:57 (9420) [INFO] Trying other mirror. * 2025-02-18 02:22:28 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-02-18 02:22:28 (9420) [INFO] Trying other mirror. * 2025-02-18 02:22:58 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:22:58 (9420) [INFO] Trying other mirror. * 2025-02-18 02:22:59 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-18 02:22:59 (9420) [INFO] Trying other mirror. * 2025-02-18 02:23:29 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:23:29 (9420) [INFO] Trying other mirror. * 2025-02-18 02:23:29 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-18 02:23:29 (9420) [INFO] Trying other mirror. * 2025-02-18 02:23:59 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-18 02:23:59 (9420) [INFO] Trying other mirror. * 2025-02-18 02:23:59 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-18 02:23:59 (9420) [INFO] Trying other mirror. * 2025-02-18 02:25:25 (9420) [INFO] Metadata Cache Created * 2025-02-18 02:25:26 (9437) [INFO] * 2025-02-18 02:25:26 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-18 02:25:26 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. * 2025-02-18 02:25:26 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-18 02:25:26 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-18 02:25:26 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-18 02:25:26 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-18 02:25:26 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-18 02:25:33 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/16uJpyQPBT/ea_profile.json * 2025-02-18 02:25:36 (8554) [INFO] Backed up EA4 profile to /tmp/16uJpyQPBT/ea_profile.json * 2025-02-18 02:25:36 (254) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-02-18 02:25:39 (605) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-02-19 01:59:06 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-19 02:03:06 (10486) [INFO] Script is up to date. * 2025-02-19 02:07:09 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-19 02:07:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-19 02:07:10 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-19 02:07:10 (9407) [INFO] * 2025-02-19 02:07:20 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-19 02:07:20 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-19 02:07:20 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-19 02:07:20 (9407) [INFO] * 2025-02-19 02:14:01 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-02-19 02:14:04 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-19 02:14:04 (9407) [INFO] * 2025-02-19 02:14:05 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-19 02:14:05 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-19 02:14:35 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-19 02:14:35 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-19 02:14:35 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-19 02:14:35 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-19 02:15:21 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-19 02:15:21 (9420) [INFO] Trying other mirror. * 2025-02-19 02:17:51 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-19 02:17:51 (9420) [INFO] Trying other mirror. * 2025-02-19 02:17:51 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:17:51 (9420) [INFO] Trying other mirror. * 2025-02-19 02:18:40 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:18:40 (9420) [INFO] Trying other mirror. * 2025-02-19 02:19:24 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-19 02:19:24 (9420) [INFO] Trying other mirror. * 2025-02-19 02:19:41 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-19 02:19:41 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:11 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:20:11 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:11 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:20:11 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:11 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-19 02:20:11 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:41 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-02-19 02:20:41 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:42 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:20:42 (9420) [INFO] Trying other mirror. * 2025-02-19 02:20:42 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-02-19 02:20:42 (9420) [INFO] Trying other mirror. * 2025-02-19 02:21:12 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-02-19 02:21:12 (9420) [INFO] Trying other mirror. * 2025-02-19 02:21:42 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:21:42 (9420) [INFO] Trying other mirror. * 2025-02-19 02:21:43 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-19 02:21:43 (9420) [INFO] Trying other mirror. * 2025-02-19 02:22:13 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:22:13 (9420) [INFO] Trying other mirror. * 2025-02-19 02:22:44 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-02-19 02:22:44 (9420) [INFO] Trying other mirror. * 2025-02-19 02:23:14 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-02-19 02:23:14 (9420) [INFO] Trying other mirror. * 2025-02-19 02:23:45 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-19 02:23:45 (9420) [INFO] Trying other mirror. * 2025-02-19 02:24:16 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-02-19 02:24:16 (9420) [INFO] Trying other mirror. * 2025-02-19 02:24:47 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-19 02:24:47 (9420) [INFO] Trying other mirror. * 2025-02-19 02:25:41 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-02-19 02:25:41 (9420) [INFO] Trying other mirror. * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-02-19 02:26:12 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-19 02:26:12 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-19 02:26:12 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-19 02:26:12 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-19 02:26:12 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-19 02:26:12 (9420) [INFO] yum --disablerepo= ... * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-19 02:26:12 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-19 02:26:12 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] yum-config-manager --disable * 2025-02-19 02:26:12 (9420) [INFO] or * 2025-02-19 02:26:12 (9420) [INFO] subscription-manager repos --disable= * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-19 02:26:12 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-19 02:26:12 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-19 02:26:12 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-19 02:26:12 (9420) [INFO] compromise: * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-02-19 02:26:12 (9420) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] updates: Check uncompressed DB failed * 2025-02-19 02:26:12 (9437) [INFO] * 2025-02-19 02:26:12 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') 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 updates: Check uncompressed DB failed * 2025-02-19 02:26:12 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-19 02:26:12 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-19 02:26:12 (9407) [INFO] * 2025-02-19 02:26:12 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-19 02:26:13 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-19 02:26:13 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-19 02:26:13 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-19 02:26:13 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-19 02:26:13 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-19 02:26:13 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-19 02:26:13 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-19 02:26:13 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-19 02:26:13 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-19 02:26:13 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-19 02:26:13 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-02-19 02:26:13 (9437) [INFO] * 2025-02-19 02:26:13 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-19 02:26:13 (9407) [INFO] * 2025-02-19 02:26:14 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-19 02:26:14 (9420) [INFO] Determining fastest mirrors * 2025-02-19 02:26:46 (9420) [INFO] * EA4: 208.74.123.61 * 2025-02-19 02:26:46 (9420) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-02-19 02:26:46 (9420) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-02-19 02:26:46 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-19 02:27:33 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-02-19 02:27:33 (9420) [INFO] Trying other mirror. * 2025-02-20 01:46:50 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-20 01:50:51 (10486) [INFO] Script is up to date. * 2025-02-20 01:54:54 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-20 01:54:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-20 01:54:54 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-20 01:54:54 (9407) [INFO] * 2025-02-20 01:54:58 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-20 01:54:58 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-20 01:54:58 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-20 01:54:58 (9407) [INFO] * 2025-02-20 01:55:20 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-20 01:55:20 (9407) [INFO] * 2025-02-20 01:55:20 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-20 01:55:21 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-20 01:55:51 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-20 01:55:51 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-20 01:55:51 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-20 01:55:51 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-20 01:56:38 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30887 milliseconds') * 2025-02-20 01:56:38 (9420) [INFO] Trying other mirror. * 2025-02-20 01:58:06 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 01:58:06 (9420) [INFO] Trying other mirror. * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-20 01:58:06 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-20 01:58:06 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-20 01:58:06 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-20 01:58:06 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-20 01:58:06 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-20 01:58:06 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-20 01:58:06 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-20 01:58:06 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-20 01:58:06 (9420) [INFO] or * 2025-02-20 01:58:06 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-20 01:58:06 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-20 01:58:06 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-20 01:58:06 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-20 01:58:06 (9420) [INFO] compromise: * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-20 01:58:06 (9420) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-20 01:58:06 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 01:58:06 (9437) [INFO] * 2025-02-20 01:58:06 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 01:58:06 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-20 01:58:06 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-20 01:58:06 (9407) [INFO] * 2025-02-20 01:58:06 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-20 01:58:06 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-20 01:58:06 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-20 01:58:06 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-20 01:58:06 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-20 01:58:06 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-20 01:58:06 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-20 01:58:06 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-20 01:58:06 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-20 01:58:06 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-20 01:58:07 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-20 01:58:07 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-20 01:58:07 (9437) [INFO] * 2025-02-20 01:58:07 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-20 01:58:07 (9407) [INFO] * 2025-02-20 01:58:07 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-20 01:58:07 (9420) [INFO] Determining fastest mirrors * 2025-02-20 01:58:39 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-20 01:58:39 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-20 01:58:39 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-20 01:58:39 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-20 01:59:26 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-20 01:59:26 (9420) [INFO] Trying other mirror. * 2025-02-20 01:59:56 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-02-20 01:59:56 (9420) [INFO] Trying other mirror. * 2025-02-20 02:00:26 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30027 milliseconds with 0 out of 0 bytes received') * 2025-02-20 02:00:26 (9420) [INFO] Trying other mirror. * 2025-02-20 02:01:55 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 02:01:55 (9420) [INFO] Trying other mirror. * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-20 02:01:55 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-20 02:01:55 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-20 02:01:55 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-20 02:01:55 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-20 02:01:55 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-20 02:01:55 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-20 02:01:55 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-20 02:01:55 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-20 02:01:55 (9420) [INFO] or * 2025-02-20 02:01:55 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-20 02:01:55 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-20 02:01:55 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-20 02:01:55 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-20 02:01:55 (9420) [INFO] compromise: * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-20 02:01:55 (9420) [INFO] * 2025-02-20 02:01:55 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-20 02:01:55 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 02:01:55 (9437) [INFO] * 2025-02-20 02:01:55 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-20 02:01:55 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30027 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-20 02:01:56 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-20 02:01:56 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-20 02:01:56 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-20 02:01:56 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-20 02:01:56 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-20 02:04:00 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XheQGe_PsR/ea_profile.json * 2025-02-20 02:07:48 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XheQGe_PsR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-20 02:07:48 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-21 01:49:46 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-21 01:53:46 (10486) [INFO] Script is up to date. * 2025-02-21 01:57:49 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-21 01:57:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-21 01:57:50 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-21 01:57:50 (9407) [INFO] * 2025-02-21 01:57:53 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-21 01:57:53 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-21 01:57:53 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-21 01:57:53 (9407) [INFO] * 2025-02-21 01:58:14 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-21 01:58:14 (9407) [INFO] * 2025-02-21 01:58:14 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-21 01:58:14 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-21 01:58:44 (9420) [INFO] * EA4: 208.74.123.61 * 2025-02-21 01:58:44 (9420) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-02-21 01:58:44 (9420) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-02-21 01:58:44 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-21 02:00:28 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:00:28 (9420) [INFO] Trying other mirror. * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-21 02:00:28 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-21 02:00:28 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-21 02:00:28 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-21 02:00:28 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-21 02:00:28 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-21 02:00:28 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-21 02:00:28 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-21 02:00:28 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-21 02:00:28 (9420) [INFO] or * 2025-02-21 02:00:28 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-21 02:00:28 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-21 02:00:28 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-21 02:00:28 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-21 02:00:28 (9420) [INFO] compromise: * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-21 02:00:28 (9420) [INFO] * 2025-02-21 02:00:28 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-21 02:00:28 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:00:28 (9437) [INFO] * 2025-02-21 02:00:28 (5884) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:00:28 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-21 02:00:28 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-21 02:00:28 (9407) [INFO] * 2025-02-21 02:00:29 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-21 02:00:29 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-21 02:00:29 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-21 02:00:29 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-21 02:00:29 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-21 02:00:29 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-21 02:00:29 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-21 02:00:29 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-21 02:00:29 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-21 02:00:29 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-21 02:00:29 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-21 02:00:29 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-21 02:00:29 (9437) [INFO] * 2025-02-21 02:00:29 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-21 02:00:29 (9407) [INFO] * 2025-02-21 02:00:30 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-21 02:00:30 (9420) [INFO] Determining fastest mirrors * 2025-02-21 02:01:01 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-21 02:01:01 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-21 02:01:01 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-21 02:01:01 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-21 02:02:45 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:02:45 (9420) [INFO] Trying other mirror. * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-21 02:02:45 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-21 02:02:45 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-21 02:02:45 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-21 02:02:45 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-21 02:02:45 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-21 02:02:45 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-21 02:02:45 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-21 02:02:45 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-21 02:02:45 (9420) [INFO] or * 2025-02-21 02:02:45 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-21 02:02:45 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-21 02:02:45 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-21 02:02:45 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-21 02:02:45 (9420) [INFO] compromise: * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-21 02:02:45 (9420) [INFO] * 2025-02-21 02:02:45 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-21 02:02:45 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:02:45 (9437) [INFO] * 2025-02-21 02:02:45 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-21 02:02:45 (5895) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-21 02:02:46 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-21 02:02:46 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-21 02:02:46 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-21 02:02:46 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-21 02:02:46 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-21 02:02:53 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c3Re8zJZh1/ea_profile.json * 2025-02-21 02:05:09 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c3Re8zJZh1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-21 02:05:09 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-22 01:51:17 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-22 01:55:18 (10486) [INFO] Script is up to date. * 2025-02-22 01:59:21 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-22 01:59:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-22 01:59:21 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-22 01:59:21 (9407) [INFO] * 2025-02-22 01:59:36 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-22 01:59:36 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-22 01:59:36 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-22 01:59:36 (9407) [INFO] * 2025-02-22 01:59:59 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-22 01:59:59 (9407) [INFO] * 2025-02-22 01:59:59 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-22 02:00:00 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-22 02:00:30 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-22 02:00:30 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-22 02:00:30 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-22 02:00:30 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-22 02:01:16 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30802 milliseconds') * 2025-02-22 02:01:16 (9420) [INFO] Trying other mirror. * 2025-02-22 02:01:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-02-22 02:01:47 (9420) [INFO] Trying other mirror. * 2025-02-22 02:03:15 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:03:15 (9420) [INFO] Trying other mirror. * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-22 02:03:15 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-22 02:03:15 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-22 02:03:15 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-22 02:03:15 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-22 02:03:15 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-22 02:03:15 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-22 02:03:15 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-22 02:03:15 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-22 02:03:15 (9420) [INFO] or * 2025-02-22 02:03:15 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-22 02:03:15 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-22 02:03:15 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-22 02:03:15 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-22 02:03:15 (9420) [INFO] compromise: * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-22 02:03:15 (9420) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-22 02:03:15 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:03:15 (9437) [INFO] * 2025-02-22 02:03:15 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30802 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:03:15 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-22 02:03:15 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-22 02:03:15 (9407) [INFO] * 2025-02-22 02:03:15 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-22 02:03:16 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-22 02:03:16 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-22 02:03:16 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-22 02:03:16 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-22 02:03:16 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-22 02:03:16 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-22 02:03:16 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-22 02:03:16 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-22 02:03:16 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-22 02:03:16 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-22 02:03:16 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-22 02:03:16 (9437) [INFO] * 2025-02-22 02:03:16 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-22 02:03:16 (9407) [INFO] * 2025-02-22 02:03:16 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-22 02:03:17 (9420) [INFO] Determining fastest mirrors * 2025-02-22 02:03:48 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-22 02:03:48 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-22 02:03:48 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-22 02:03:48 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-22 02:04:35 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-02-22 02:04:35 (9420) [INFO] Trying other mirror. * 2025-02-22 02:06:03 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:06:03 (9420) [INFO] Trying other mirror. * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-22 02:06:03 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-22 02:06:03 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-22 02:06:03 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-22 02:06:03 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-22 02:06:03 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-22 02:06:03 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-22 02:06:03 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-22 02:06:03 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-22 02:06:03 (9420) [INFO] or * 2025-02-22 02:06:03 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-22 02:06:03 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-22 02:06:03 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-22 02:06:03 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-22 02:06:03 (9420) [INFO] compromise: * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-22 02:06:03 (9420) [INFO] * 2025-02-22 02:06:03 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-22 02:06:03 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:06:03 (9437) [INFO] * 2025-02-22 02:06:03 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-22 02:06:03 (5895) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-22 02:06:04 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-22 02:06:04 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-22 02:06:04 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-22 02:06:04 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-22 02:06:04 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-22 02:06:11 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MNHq5yK6Ll/ea_profile.json * 2025-02-22 02:08:26 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MNHq5yK6Ll/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-22 02:08:26 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-23 01:47:29 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-23 01:51:30 (10486) [INFO] Script is up to date. * 2025-02-23 01:55:33 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-23 01:55:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-23 01:55:33 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-23 01:55:33 (9407) [INFO] * 2025-02-23 01:55:45 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-23 01:55:45 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-23 01:55:45 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-23 01:55:45 (9407) [INFO] * 2025-02-23 01:56:07 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-23 01:56:07 (9407) [INFO] * 2025-02-23 01:56:07 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-23 01:56:08 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-23 01:56:37 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-23 01:56:37 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-23 01:56:37 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-23 01:56:37 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-02-23 01:58:21 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 01:58:21 (9420) [INFO] Trying other mirror. * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-23 01:58:21 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-23 01:58:21 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-23 01:58:21 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-23 01:58:21 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-23 01:58:21 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-23 01:58:21 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-23 01:58:21 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-23 01:58:21 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-23 01:58:21 (9420) [INFO] or * 2025-02-23 01:58:21 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-23 01:58:21 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-23 01:58:21 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-23 01:58:21 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-23 01:58:21 (9420) [INFO] compromise: * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-23 01:58:21 (9420) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-23 01:58:21 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 01:58:21 (9437) [INFO] * 2025-02-23 01:58:21 (5884) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 01:58:21 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-23 01:58:21 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-23 01:58:21 (9407) [INFO] * 2025-02-23 01:58:21 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-23 01:58:22 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-23 01:58:22 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-23 01:58:22 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-23 01:58:22 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-23 01:58:22 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-23 01:58:22 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-23 01:58:22 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-23 01:58:22 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-23 01:58:22 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-23 01:58:22 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-23 01:58:22 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-23 01:58:22 (9437) [INFO] * 2025-02-23 01:58:22 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-23 01:58:22 (9407) [INFO] * 2025-02-23 01:58:22 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-23 01:58:23 (9420) [INFO] Determining fastest mirrors * 2025-02-23 01:58:53 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-23 01:58:53 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-23 01:58:53 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-23 01:58:53 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-23 02:00:37 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 02:00:37 (9420) [INFO] Trying other mirror. * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-23 02:00:37 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-23 02:00:37 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-23 02:00:37 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-23 02:00:37 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-23 02:00:37 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-23 02:00:37 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-23 02:00:37 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-23 02:00:37 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-23 02:00:37 (9420) [INFO] or * 2025-02-23 02:00:37 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-23 02:00:37 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-23 02:00:37 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-23 02:00:37 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-23 02:00:37 (9420) [INFO] compromise: * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-23 02:00:37 (9420) [INFO] * 2025-02-23 02:00:37 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-23 02:00:37 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 02:00:37 (9437) [INFO] * 2025-02-23 02:00:37 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-23 02:00:37 (5895) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-23 02:00:38 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-23 02:00:38 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-23 02:00:38 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-23 02:00:38 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-23 02:00:38 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-23 02:00:44 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kTBzVdd81i/ea_profile.json * 2025-02-23 02:03:00 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kTBzVdd81i/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-23 02:03:00 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-02-24 01:47:20 (10464) [INFO] Self-update of script version 61 requested. * 2025-02-24 01:51:21 (10486) [INFO] Script is up to date. * 2025-02-24 01:55:24 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-02-24 01:55:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-02-24 01:55:24 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-02-24 01:55:24 (9407) [INFO] * 2025-02-24 01:55:28 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-02-24 01:55:28 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-02-24 01:55:28 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-02-24 01:55:28 (9407) [INFO] * 2025-02-24 01:55:51 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-24 01:55:51 (9407) [INFO] * 2025-02-24 01:55:52 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-24 01:55:52 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-02-24 01:56:22 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-24 01:56:22 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-24 01:56:22 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-24 01:56:22 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-24 01:57:09 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-02-24 01:57:09 (9420) [INFO] Trying other mirror. * 2025-02-24 01:58:37 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 01:58:37 (9420) [INFO] Trying other mirror. * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-24 01:58:37 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-24 01:58:37 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-24 01:58:37 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-24 01:58:37 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-24 01:58:37 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-24 01:58:37 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-24 01:58:37 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-24 01:58:37 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-24 01:58:37 (9420) [INFO] or * 2025-02-24 01:58:37 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-24 01:58:37 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-24 01:58:37 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-24 01:58:37 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-24 01:58:37 (9420) [INFO] compromise: * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-24 01:58:37 (9420) [INFO] * 2025-02-24 01:58:37 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-24 01:58:37 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 01:58:37 (9437) [INFO] * 2025-02-24 01:58:37 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 01:58:37 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-02-24 01:58:37 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-02-24 01:58:37 (9407) [INFO] * 2025-02-24 01:58:38 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-24 01:58:38 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-02-24 01:58:38 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-02-24 01:58:38 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-02-24 01:58:38 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-02-24 01:58:38 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-02-24 01:58:38 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-02-24 01:58:38 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-02-24 01:58:38 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-02-24 01:58:38 (9420) [INFO] : wp-toolkit-thirdparties * 2025-02-24 01:58:38 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-02-24 01:58:38 (9420) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-02-24 01:58:38 (9437) [INFO] * 2025-02-24 01:58:38 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-02-24 01:58:38 (9407) [INFO] * 2025-02-24 01:58:39 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-02-24 01:58:39 (9420) [INFO] Determining fastest mirrors * 2025-02-24 01:59:16 (9420) [INFO] * EA4: 107.178.98.171 * 2025-02-24 01:59:16 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-02-24 01:59:16 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-02-24 01:59:16 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-02-24 02:01:00 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 02:01:00 (9420) [INFO] Trying other mirror. * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-02-24 02:01:00 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-02-24 02:01:00 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-02-24 02:01:00 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-02-24 02:01:00 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-02-24 02:01:00 (9420) [INFO] packages for the previous distribution release still work). * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-02-24 02:01:00 (9420) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-02-24 02:01:00 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-02-24 02:01:00 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-02-24 02:01:00 (9420) [INFO] or * 2025-02-24 02:01:00 (9420) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-02-24 02:01:00 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-02-24 02:01:00 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-02-24 02:01:00 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-02-24 02:01:00 (9420) [INFO] compromise: * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-02-24 02:01:00 (9420) [INFO] * 2025-02-24 02:01:00 (9420) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-02-24 02:01:00 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 02:01:00 (9437) [INFO] * 2025-02-24 02:01:00 (5894) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-02-24 02:01:00 (5895) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzM5Nzc0NDUxOjE3NDAwMzM2NTE6Fd8nnn1wO51SaeZcJHOeuKBlGddVY35xF6-l_3ADPkfU8YL3QrdlOFcpRvG0cctpM7jDvqC1jvq81spOvVJbxNQnexBi5r3XIPzwBCTKVt4SE0FwDx8IGuxYOWX4n-STgIM056E6pKcHVYpEGu2xXl7wJ3Hm8rJl3rfw_pDJcZeEttoEmlqKQmhvvTgWtfXKBm1h_Oc1r8-837rgu_na775NTEESwfAW2CSljzY5JkShHNikx7DhtQXk2SNVbX6nRKyboy3QaEr4dirvMQ0nCGfnH_9lUNDm8rOknyJgi2CPjJSEpBQBgcykvL-Rnsn5X61bx_X974AVylAEQSCxcb0fIOEqaMmKivWgTq6mBhIbqXX_lAPzOADBre9Mw59mh33yx1gv1hVVXjCoaBbjyMZndY8THvwUa-XSXJFqDm1rVpoPXAWFZ8VpcFYYFx1evUQC-6Z7Uk5moJ9QbmIYqe8VYbX4n5F5ogihZUnp7_EKDjGboySJo9-pfxd-UUbLT3wIB8BJLS7vVQneGq3p5wDX6bME13H6jPllsXAK_hdkoxfPHzW4pAuP0OePvF3ddBMBK8D_zspAeIesJCJCGqEMI47obgaJMcqZ7pAxSH3FgwbghFRy3otSWQuRPZzezvKCvqPPb-pEj4io4Zf1IBjKFP2QbYwt7b-H3_pOGlo=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-02-24 02:01:01 (3238) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-02-24 02:01:01 (254) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-02-24 02:01:01 (4270) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-02-24 02:01:01 (4276) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-02-24 02:01:01 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-02-24 02:01:08 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/p5FQRm1RV6/ea_profile.json * 2025-02-24 02:03:24 (490) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/p5FQRm1RV6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-02-24 02:03:24 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-10 02:03:53 (10464) [INFO] Self-update of script version 61 requested. * 2025-03-10 02:07:54 (10486) [INFO] Script is up to date. * 2025-03-10 02:11:57 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-10 02:11:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-10 02:11:58 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-10 02:11:58 (9407) [INFO] * 2025-03-10 02:12:02 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-10 02:12:02 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-10 02:12:02 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-03-10 02:12:02 (9407) [INFO] * 2025-03-10 02:16:13 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-10 02:16:16 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-10 02:16:16 (9407) [INFO] * 2025-03-10 02:16:17 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-10 02:16:17 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-03-10 02:16:46 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-10 02:16:46 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-10 02:16:46 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-10 02:16:46 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-10 02:19:32 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:19:32 (9420) [INFO] Trying other mirror. * 2025-03-10 02:19:32 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:19:32 (9420) [INFO] Trying other mirror. * 2025-03-10 02:19:53 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:19:53 (9420) [INFO] Trying other mirror. * 2025-03-10 02:20:39 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-10 02:20:39 (9420) [INFO] Trying other mirror. * 2025-03-10 02:21:09 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:21:09 (9420) [INFO] Trying other mirror. * 2025-03-10 02:22:15 (9420) [INFO] Metadata Cache Created * 2025-03-10 02:22:15 (9437) [INFO] * 2025-03-10 02:22:15 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-10 02:22:15 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-10 02:22:15 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-03-10 02:22:15 (9407) [INFO] * 2025-03-10 02:22:15 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-10 02:22:16 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-10 02:22:16 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-10 02:22:16 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-10 02:22:16 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-10 02:22:16 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-10 02:22:16 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-10 02:22:16 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-10 02:22:16 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-10 02:22:16 (9420) [INFO] : wp-toolkit-thirdparties * 2025-03-10 02:22:16 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-03-10 02:22:17 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-10 02:22:17 (9437) [INFO] * 2025-03-10 02:22:17 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-10 02:22:17 (9407) [INFO] * 2025-03-10 02:22:17 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-10 02:22:17 (9420) [INFO] Determining fastest mirrors * 2025-03-10 02:22:51 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-10 02:22:51 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-10 02:22:51 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-10 02:22:51 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-10 02:25:54 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-10 02:25:54 (9420) [INFO] Trying other mirror. * 2025-03-10 02:25:54 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:25:54 (9420) [INFO] Trying other mirror. * 2025-03-10 02:28:34 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:28:34 (9420) [INFO] Trying other mirror. * 2025-03-10 02:31:23 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:31:23 (9420) [INFO] Trying other mirror. * 2025-03-10 02:32:25 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:32:25 (9420) [INFO] Trying other mirror. * 2025-03-10 02:32:25 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-10 02:32:25 (9420) [INFO] Trying other mirror. * 2025-03-10 02:32:55 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-10 02:32:55 (9420) [INFO] Trying other mirror. * 2025-03-10 02:32:55 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-10 02:32:55 (9420) [INFO] Trying other mirror. * 2025-03-11 01:53:34 (10464) [INFO] Self-update of script version 61 requested. * 2025-03-11 01:57:35 (10486) [INFO] Script is up to date. * 2025-03-11 02:01:38 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-11 02:01:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-11 02:01:39 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-11 02:01:39 (9407) [INFO] * 2025-03-11 02:01:42 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-11 02:01:42 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-11 02:01:42 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-03-11 02:01:42 (9407) [INFO] * 2025-03-11 02:01:55 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-11 02:01:58 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-11 02:01:58 (9407) [INFO] * 2025-03-11 02:01:59 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-11 02:01:59 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-03-11 02:02:29 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-11 02:02:29 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-11 02:02:29 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-11 02:02:29 (9420) [INFO] * epel: mirror.math.princeton.edu * 2025-03-11 02:03:15 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2025-03-11 02:03:15 (9420) [INFO] Trying other mirror. * 2025-03-11 02:05:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:05:45 (9420) [INFO] Trying other mirror. * 2025-03-11 02:06:02 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:06:02 (9420) [INFO] Trying other mirror. * 2025-03-11 02:06:35 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-11 02:06:35 (9420) [INFO] Trying other mirror. * 2025-03-11 02:06:45 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-11 02:06:45 (9420) [INFO] Trying other mirror. * 2025-03-11 02:07:15 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:07:15 (9420) [INFO] Trying other mirror. * 2025-03-11 02:07:46 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-03-11 02:07:46 (9420) [INFO] Trying other mirror. * 2025-03-11 02:08:16 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-11 02:08:16 (9420) [INFO] Trying other mirror. * 2025-03-11 02:08:47 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-11 02:08:47 (9420) [INFO] Trying other mirror. * 2025-03-11 02:09:28 (9420) [INFO] Metadata Cache Created * 2025-03-11 02:09:29 (9437) [INFO] * 2025-03-11 02:09:29 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-03-11 02:09:29 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-11 02:09:29 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-03-11 02:09:29 (9407) [INFO] * 2025-03-11 02:09:29 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-11 02:09:29 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-11 02:09:29 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-11 02:09:29 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-11 02:09:29 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-11 02:09:29 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-11 02:09:29 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-11 02:09:29 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-11 02:09:29 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-11 02:09:29 (9420) [INFO] : wp-toolkit-thirdparties * 2025-03-11 02:09:30 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-03-11 02:09:30 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-11 02:09:30 (9437) [INFO] * 2025-03-11 02:09:30 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-11 02:09:30 (9407) [INFO] * 2025-03-11 02:09:30 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-11 02:09:30 (9420) [INFO] Determining fastest mirrors * 2025-03-11 02:10:02 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-11 02:10:02 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-11 02:10:02 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-11 02:10:02 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-11 02:13:05 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-11 02:13:05 (9420) [INFO] Trying other mirror. * 2025-03-11 02:13:05 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:13:05 (9420) [INFO] Trying other mirror. * 2025-03-11 02:13:36 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-11 02:13:36 (9420) [INFO] Trying other mirror. * 2025-03-11 02:14:06 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-03-11 02:14:06 (9420) [INFO] Trying other mirror. * 2025-03-11 02:15:44 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:15:44 (9420) [INFO] Trying other mirror. * 2025-03-11 02:15:45 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-11 02:15:45 (9420) [INFO] Trying other mirror. * 2025-03-11 02:16:15 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-11 02:16:15 (9420) [INFO] Trying other mirror. * 2025-03-11 02:19:04 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-11 02:19:04 (9420) [INFO] Trying other mirror. * 2025-03-11 02:19:04 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-03-11 02:19:04 (9420) [INFO] Trying other mirror. * 2025-03-11 02:19:34 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:19:34 (9420) [INFO] Trying other mirror. * 2025-03-11 02:20:06 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-11 02:20:06 (9420) [INFO] Trying other mirror. * 2025-03-11 02:21:07 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:21:07 (9420) [INFO] Trying other mirror. * 2025-03-11 02:22:08 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-11 02:22:08 (9420) [INFO] Trying other mirror. * 2025-03-11 02:22:38 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:22:38 (9420) [INFO] Trying other mirror. * 2025-03-11 02:23:08 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-11 02:23:08 (9420) [INFO] Trying other mirror. * 2025-03-11 02:23:08 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-11 02:23:08 (9420) [INFO] Trying other mirror. * 2025-03-12 01:53:03 (10464) [INFO] Self-update of script version 61 requested. * 2025-03-12 01:57:04 (10486) [INFO] Script is up to date. * 2025-03-12 02:01:07 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-12 02:01:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-12 02:01:07 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-12 02:01:07 (9407) [INFO] * 2025-03-12 02:01:11 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-12 02:01:11 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-12 02:01:11 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-03-12 02:01:11 (9407) [INFO] * 2025-03-12 02:01:21 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-12 02:01:24 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-12 02:01:24 (9407) [INFO] * 2025-03-12 02:01:25 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-12 02:01:25 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-03-12 02:01:55 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-12 02:01:55 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-12 02:01:55 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-12 02:01:55 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-12 02:02:42 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-03-12 02:02:42 (9420) [INFO] Trying other mirror. * 2025-03-12 02:03:12 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-12 02:03:12 (9420) [INFO] Trying other mirror. * 2025-03-12 02:05:43 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:05:43 (9420) [INFO] Trying other mirror. * 2025-03-12 02:06:00 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:06:00 (9420) [INFO] Trying other mirror. * 2025-03-12 02:06:17 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') * 2025-03-12 02:06:17 (9420) [INFO] Trying other mirror. * 2025-03-12 02:06:32 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:06:32 (9420) [INFO] Trying other mirror. * 2025-03-12 02:06:48 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-12 02:06:48 (9420) [INFO] Trying other mirror. * 2025-03-12 02:07:18 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-12 02:07:18 (9420) [INFO] Trying other mirror. * 2025-03-12 02:07:49 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-12 02:07:49 (9420) [INFO] Trying other mirror. * 2025-03-12 02:08:33 (9420) [INFO] Metadata Cache Created * 2025-03-12 02:08:33 (9437) [INFO] * 2025-03-12 02:08:33 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30064 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-03-12 02:08:33 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-12 02:08:33 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-03-12 02:08:33 (9407) [INFO] * 2025-03-12 02:08:34 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-12 02:08:34 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-12 02:08:34 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-12 02:08:34 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-12 02:08:34 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-12 02:08:34 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-12 02:08:34 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-12 02:08:34 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-12 02:08:34 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-12 02:08:34 (9420) [INFO] : wp-toolkit-thirdparties * 2025-03-12 02:08:35 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-03-12 02:08:35 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-12 02:08:35 (9437) [INFO] * 2025-03-12 02:08:35 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-12 02:08:35 (9407) [INFO] * 2025-03-12 02:08:36 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-12 02:08:36 (9420) [INFO] Determining fastest mirrors * 2025-03-12 02:09:07 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-12 02:09:07 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-12 02:09:07 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-12 02:09:07 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-12 02:09:53 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-12 02:09:53 (9420) [INFO] Trying other mirror. * 2025-03-12 02:12:09 (9420) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/d3015a50dedf4688560e482b1ffef18e40556f02f7f67675f98b4dedea8f0276-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-03-12 02:12:09 (9420) [INFO] Trying other mirror. * 2025-03-12 02:12:39 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-12 02:12:39 (9420) [INFO] Trying other mirror. * 2025-03-12 02:12:39 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:12:39 (9420) [INFO] Trying other mirror. * 2025-03-12 02:13:25 (9420) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:13:25 (9420) [INFO] Trying other mirror. * 2025-03-12 02:13:41 (9420) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:13:41 (9420) [INFO] Trying other mirror. * 2025-03-12 02:13:56 (9420) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:13:56 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:12 (9420) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:12 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:28 (9420) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:28 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:43 (9420) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:43 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:44 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:44 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:45 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:45 (9420) [INFO] Trying other mirror. * 2025-03-12 02:14:45 (9420) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:14:45 (9420) [INFO] Trying other mirror. * 2025-03-12 02:15:12 (9420) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/178baf42176799ed9d00e08830e756c032015631b7e9528e2ab1e0816778fe87-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:15:12 (9420) [INFO] Trying other mirror. * 2025-03-12 02:15:16 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-12 02:15:16 (9420) [INFO] Trying other mirror. * 2025-03-12 02:15:28 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:15:28 (9420) [INFO] Trying other mirror. * 2025-03-12 02:15:43 (9420) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/ad0f8c6243a36d68f3d2da38dcbb6c561d3a672e89734ebdced642a68c90b946-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:15:43 (9420) [INFO] Trying other mirror. * 2025-03-12 02:15:59 (9420) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:15:59 (9420) [INFO] Trying other mirror. * 2025-03-12 02:16:15 (9420) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:16:15 (9420) [INFO] Trying other mirror. * 2025-03-12 02:16:30 (9420) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:16:30 (9420) [INFO] Trying other mirror. * 2025-03-12 02:16:46 (9420) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:16:46 (9420) [INFO] Trying other mirror. * 2025-03-12 02:17:02 (9420) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:17:02 (9420) [INFO] Trying other mirror. * 2025-03-12 02:17:17 (9420) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:17:17 (9420) [INFO] Trying other mirror. * 2025-03-12 02:17:33 (9420) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:17:33 (9420) [INFO] Trying other mirror. * 2025-03-12 02:17:49 (9420) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:17:49 (9420) [INFO] Trying other mirror. * 2025-03-12 02:18:19 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:18:19 (9420) [INFO] Trying other mirror. * 2025-03-12 02:18:19 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:18:19 (9420) [INFO] Trying other mirror. * 2025-03-12 02:18:34 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/wp-toolkit/repodata/5ecfb1fdd5e26647ef83fb42dbcab9ba6b8f766c77e681ef556d215baf325065-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:18:34 (9420) [INFO] Trying other mirror. * 2025-03-12 02:18:49 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-12 02:18:49 (9420) [INFO] Trying other mirror. * 2025-03-12 02:18:50 (9420) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:18:50 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:20 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:19:20 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:20 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:19:20 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:21 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:19:21 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:36 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:19:36 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:50 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:19:50 (9420) [INFO] Trying other mirror. * 2025-03-12 02:19:50 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:19:50 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:21 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-12 02:20:21 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:37 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:20:37 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:37 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:20:37 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:38 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:20:38 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:52 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:20:52 (9420) [INFO] Trying other mirror. * 2025-03-12 02:20:52 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-12 02:20:52 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:08 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:08 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:09 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:09 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:22 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-12 02:21:22 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:23 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-12 02:21:23 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:38 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:38 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:38 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:38 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:53 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:53 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:53 (9420) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-03-12 02:21:53 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:53 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:53 (9420) [INFO] Trying other mirror. * 2025-03-12 02:21:54 (9420) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:21:54 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:07 (9420) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:07 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:09 (9420) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:09 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:09 (9420) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:09 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:22 (9420) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:22 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:24 (9420) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:24 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:26 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:26 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:26 (9420) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:26 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:42 (9420) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:42 (9420) [INFO] Trying other mirror. * 2025-03-12 02:22:42 (9420) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-12 02:22:42 (9420) [INFO] Trying other mirror. * 2025-03-13 01:56:15 (10464) [INFO] Self-update of script version 61 requested. * 2025-03-13 02:00:15 (10486) [INFO] Script is up to date. * 2025-03-13 02:04:18 (6316) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-13 02:04:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-13 02:04:19 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-13 02:04:19 (9407) [INFO] * 2025-03-13 02:04:22 (4054) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-13 02:04:22 (4061) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-13 02:04:23 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-03-13 02:04:23 (9407) [INFO] * 2025-03-13 02:04:33 (254) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-13 02:04:37 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-13 02:04:37 (9407) [INFO] * 2025-03-13 02:04:37 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-13 02:04:37 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-03-13 02:05:07 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-13 02:05:07 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-13 02:05:07 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-13 02:05:07 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-13 02:07:53 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:07:53 (9420) [INFO] Trying other mirror. * 2025-03-13 02:08:10 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:08:10 (9420) [INFO] Trying other mirror. * 2025-03-13 02:08:53 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:08:53 (9420) [INFO] Trying other mirror. * 2025-03-13 02:09:24 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-13 02:09:24 (9420) [INFO] Trying other mirror. * 2025-03-13 02:09:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-03-13 02:09:54 (9420) [INFO] Trying other mirror. * 2025-03-13 02:10:25 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-13 02:10:25 (9420) [INFO] Trying other mirror. * 2025-03-13 02:11:08 (9420) [INFO] Metadata Cache Created * 2025-03-13 02:11:08 (9437) [INFO] * 2025-03-13 02:11:08 (5884) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-03-13 02:11:08 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-13 02:11:08 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-03-13 02:11:08 (9407) [INFO] * 2025-03-13 02:11:09 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-13 02:11:09 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-13 02:11:09 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-13 02:11:09 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-13 02:11:09 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-13 02:11:09 (9420) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-13 02:11:09 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-13 02:11:09 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-13 02:11:09 (9420) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-13 02:11:09 (9420) [INFO] : wp-toolkit-thirdparties * 2025-03-13 02:11:10 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-03-13 02:11:10 (9420) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-13 02:11:10 (9437) [INFO] * 2025-03-13 02:11:10 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-13 02:11:10 (9407) [INFO] * 2025-03-13 02:11:10 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-13 02:11:11 (9420) [INFO] Determining fastest mirrors * 2025-03-13 02:11:42 (9420) [INFO] * EA4: 107.178.98.171 * 2025-03-13 02:11:42 (9420) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-13 02:11:42 (9420) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-13 02:11:42 (9420) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-13 02:14:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-13 02:14:45 (9420) [INFO] Trying other mirror. * 2025-03-13 02:14:45 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:14:45 (9420) [INFO] Trying other mirror. * 2025-03-13 02:15:16 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-03-13 02:15:16 (9420) [INFO] Trying other mirror. * 2025-03-13 02:15:47 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-13 02:15:47 (9420) [INFO] Trying other mirror. * 2025-03-13 02:17:29 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-13 02:17:29 (9420) [INFO] Trying other mirror. * 2025-03-13 02:17:29 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-03-13 02:17:29 (9420) [INFO] Trying other mirror. * 2025-03-13 02:18:00 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-13 02:18:00 (9420) [INFO] Trying other mirror. * 2025-03-13 02:20:49 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-13 02:20:49 (9420) [INFO] Trying other mirror. * 2025-03-13 02:21:50 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-13 02:21:50 (9420) [INFO] Trying other mirror. * 2025-03-13 02:22:21 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-13 02:22:21 (9420) [INFO] Trying other mirror. * 2025-03-13 02:23:21 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:23:21 (9420) [INFO] Trying other mirror. * 2025-03-13 02:23:52 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-03-13 02:23:52 (9420) [INFO] Trying other mirror. * 2025-03-13 02:24:22 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-13 02:24:22 (9420) [INFO] Trying other mirror. * 2025-03-13 02:24:22 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-13 02:24:22 (9420) [INFO] Trying other mirror. * 2025-03-13 02:24:53 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-13 02:24:53 (9420) [INFO] Trying other mirror. * 2025-03-13 02:24:53 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-13 02:24:53 (9420) [INFO] Trying other mirror. * 2025-03-13 02:25:23 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-13 02:25:23 (9420) [INFO] Trying other mirror. * 2025-03-13 02:25:24 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-03-13 02:25:24 (9420) [INFO] Trying other mirror. * 2025-03-13 02:25:24 (9420) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-13 02:25:24 (9420) [INFO] Trying other mirror. * 2025-03-13 02:25:54 (9420) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-03-13 02:25:54 (9420) [INFO] Trying other mirror. * 2025-03-13 02:25:54 (9420) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-13 02:25:54 (9420) [INFO] Trying other mirror. * 2025-03-14 02:37:37 (10464) [INFO] Self-update of script version 61 requested. * 2025-03-14 02:41:37 (10469) [INFO] Newer version of script found. Downloading. * 2025-03-14 02:45:39 (10478) [INFO] Script update to version 62 successful. * 2025-03-14 02:49:42 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-14 02:49:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-14 02:49:42 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-14 02:49:42 (9645) [INFO] * 2025-03-14 02:49:54 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-14 02:49:54 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-14 02:49:54 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-14 02:49:54 (9645) [INFO] * 2025-03-14 02:50:06 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-14 02:50:09 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-14 02:50:09 (9645) [INFO] * 2025-03-14 02:50:09 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-14 02:50:10 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-14 02:50:39 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-14 02:50:39 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-14 02:50:39 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-14 02:50:39 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-14 02:51:26 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30599 milliseconds') * 2025-03-14 02:51:26 (9658) [INFO] Trying other mirror. * 2025-03-14 02:51:56 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-03-14 02:51:56 (9658) [INFO] Trying other mirror. * 2025-03-14 02:54:27 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-14 02:54:27 (9658) [INFO] Trying other mirror. * 2025-03-14 02:54:44 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 02:54:44 (9658) [INFO] Trying other mirror. * 2025-03-14 02:55:00 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 02:55:00 (9658) [INFO] Trying other mirror. * 2025-03-14 02:55:13 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 02:55:13 (9658) [INFO] Trying other mirror. * 2025-03-14 02:55:56 (9658) [INFO] Metadata Cache Created * 2025-03-14 02:55:56 (9675) [INFO] * 2025-03-14 02:55:56 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30599 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-14 02:55:56 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-14 02:55:56 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-14 02:55:56 (9645) [INFO] * 2025-03-14 02:55:56 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-14 02:55:57 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-14 02:55:57 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-14 02:55:57 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-14 02:55:57 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-14 02:55:57 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-14 02:55:57 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-14 02:55:57 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-14 02:55:57 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-14 02:55:57 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-14 02:55:58 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-14 02:55:58 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-14 02:55:58 (9675) [INFO] * 2025-03-14 02:55:58 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-14 02:55:58 (9645) [INFO] * 2025-03-14 02:55:58 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-14 02:55:59 (9658) [INFO] Determining fastest mirrors * 2025-03-14 02:56:30 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-14 02:56:30 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-14 02:56:30 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-14 02:56:30 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-14 02:59:33 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-14 02:59:33 (9658) [INFO] Trying other mirror. * 2025-03-14 02:59:33 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 02:59:33 (9658) [INFO] Trying other mirror. * 2025-03-14 03:02:13 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-14 03:02:13 (9658) [INFO] Trying other mirror. * 2025-03-14 03:05:01 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 03:05:01 (9658) [INFO] Trying other mirror. * 2025-03-14 03:05:02 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-03-14 03:05:02 (9658) [INFO] Trying other mirror. * 2025-03-14 03:06:03 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-14 03:06:03 (9658) [INFO] Trying other mirror. * 2025-03-14 03:06:03 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30537 milliseconds') * 2025-03-14 03:06:03 (9658) [INFO] Trying other mirror. * 2025-03-14 03:06:34 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 03:06:34 (9658) [INFO] Trying other mirror. * 2025-03-14 03:06:34 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-14 03:06:34 (9658) [INFO] Trying other mirror. * 2025-03-15 02:01:32 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-15 02:05:32 (10727) [INFO] Script is up to date. * 2025-03-15 02:09:34 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-15 02:09:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-15 02:09:35 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-15 02:09:35 (9645) [INFO] * 2025-03-15 02:16:40 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-15 02:16:40 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-15 02:16:40 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-15 02:16:40 (9645) [INFO] * 2025-03-15 02:16:50 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-15 02:16:52 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-15 02:16:52 (9645) [INFO] * 2025-03-15 02:16:53 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-15 02:16:53 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-15 02:17:23 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-15 02:17:23 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-15 02:17:23 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-15 02:17:23 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-15 02:19:07 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:19:07 (9658) [INFO] Trying other mirror. * 2025-03-15 02:20:09 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-15 02:20:09 (9658) [INFO] Trying other mirror. * 2025-03-15 02:20:25 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-15 02:20:25 (9658) [INFO] Trying other mirror. * 2025-03-15 02:20:54 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-15 02:20:54 (9658) [INFO] Trying other mirror. * 2025-03-15 02:20:56 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-15 02:20:56 (9658) [INFO] Trying other mirror. * 2025-03-15 02:21:46 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:21:46 (9658) [INFO] Trying other mirror. * 2025-03-15 02:22:01 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:22:01 (9658) [INFO] Trying other mirror. * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-15 02:22:02 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-15 02:22:02 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-15 02:22:02 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-15 02:22:02 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-15 02:22:02 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-15 02:22:02 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-15 02:22:02 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-15 02:22:02 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-15 02:22:02 (9658) [INFO] or * 2025-03-15 02:22:02 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-15 02:22:02 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-15 02:22:02 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-15 02:22:02 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-15 02:22:02 (9658) [INFO] compromise: * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-15 02:22:02 (9658) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] failure: repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2 from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-15 02:22:02 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:22:02 (9675) [INFO] * 2025-03-15 02:22:02 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2 from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/4da3d8019c96d1ec70733f71be778884cfeed05683d66a764a0cc11d68eac20b-other.sqlite.bz2: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:22:02 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-15 02:22:02 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-15 02:22:02 (9645) [INFO] * 2025-03-15 02:22:02 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-15 02:22:02 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-15 02:22:02 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-15 02:22:02 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-15 02:22:02 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-15 02:22:02 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-15 02:22:02 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-15 02:22:02 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-15 02:22:02 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-15 02:22:02 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-15 02:22:03 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-15 02:22:03 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-15 02:22:03 (9675) [INFO] * 2025-03-15 02:22:03 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-15 02:22:03 (9645) [INFO] * 2025-03-15 02:22:03 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-15 02:22:04 (9658) [INFO] Determining fastest mirrors * 2025-03-15 02:22:35 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-15 02:22:35 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-15 02:22:35 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-15 02:22:35 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-15 02:24:19 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:24:19 (9658) [INFO] Trying other mirror. * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-15 02:24:19 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-15 02:24:19 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-15 02:24:19 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-15 02:24:19 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-15 02:24:19 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-15 02:24:19 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-15 02:24:19 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-15 02:24:19 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-15 02:24:19 (9658) [INFO] or * 2025-03-15 02:24:19 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-15 02:24:19 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-15 02:24:19 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-15 02:24:19 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-15 02:24:19 (9658) [INFO] compromise: * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-15 02:24:19 (9658) [INFO] * 2025-03-15 02:24:19 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-15 02:24:19 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:24:19 (9675) [INFO] * 2025-03-15 02:24:19 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-15 02:24:19 (6033) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-15 02:24:20 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-15 02:24:20 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-15 02:24:20 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-15 02:24:20 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-15 02:24:20 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-15 02:29:33 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uKmk2HNXTB/ea_profile.json * 2025-03-16 01:46:40 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-16 01:50:40 (10727) [INFO] Script is up to date. * 2025-03-16 01:54:44 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-16 01:54:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-16 01:54:44 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-16 01:54:44 (9645) [INFO] * 2025-03-16 01:54:47 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-16 01:54:47 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-16 01:54:47 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-16 01:54:47 (9645) [INFO] * 2025-03-16 01:55:09 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-16 01:55:09 (9645) [INFO] * 2025-03-16 01:55:09 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-16 01:55:10 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-16 01:55:40 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-16 01:55:40 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-16 01:55:40 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-16 01:55:40 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-16 01:57:24 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-16 01:57:24 (9658) [INFO] Trying other mirror. * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-16 01:57:24 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-16 01:57:24 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-16 01:57:24 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-16 01:57:24 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-16 01:57:24 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-16 01:57:24 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-16 01:57:24 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-16 01:57:24 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-16 01:57:24 (9658) [INFO] or * 2025-03-16 01:57:24 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-16 01:57:24 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-16 01:57:24 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-16 01:57:24 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-16 01:57:24 (9658) [INFO] compromise: * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-16 01:57:24 (9658) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-16 01:57:24 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-16 01:57:24 (9675) [INFO] * 2025-03-16 01:57:24 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQxNzY2MTk1OjE3NDIwMjUzOTU6QNoByRiY8NNeYUQs34JQVng2gxzXsZZ54YzK8YcwgdXL6_evvK9m54HTO3Gte0TVPE9uVhmvB3MY8Yr3Rdwaiiw-_YEpVLhgzCFwIq0UJG0iate_NSbWOg5T0vTlMy2BtUWU5KXrKAxTmI4yT3jFRpXoHTmvV0eNOy6Z8QMn6De5R0oL2wwIuFzfIvm0W7-HqXNCxMaBxPrkxfdi8inCKGMSGXvsnTETryO5EGQepGNxa61MrCVcdm9DpbqgFPt7FlLsLSiYGccBvZkCDY8-RyjHeNQu3yQeMakJCHByrr9D2ih6qk4pXX3NGpHR6hkHQ7BPrOPd3IByR5cNQ9D3ypjs_2utirQBT4RlL9ZK7jYN9jytoXavy6pvMbXR8_HGxDYdWuAEHc4pwIRo28_3l2hI1ZevSo0dk9pJRB9WQPsgEp8yv68zNaopqRV8fhueA-BJpbGeV3YqnXDpPoeT1cyH0OyOfEEwAjaQFwNtqJvNpAedkTUUdrbTvlVQvc7An08o5WqutmLI9HMqQmI3FJI65N5CwwYz5jlfBbtYCBAkZtYyjC1lk8UyGkTvNPszAMR3CFGk24N2VdRh4GjaneQy5fbIejiND4IHvm_UMv8P5Us5Lse_IM2U8M6566yz_l9DUorox3389E9Jso9fmy_18iwqparyigAz2yzgl4w=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-16 01:57:24 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-16 01:57:24 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-16 01:57:24 (9645) [INFO] * 2025-03-16 01:57:24 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-16 01:57:25 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-16 01:57:25 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-16 01:57:25 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-16 01:57:25 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-16 01:57:25 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-16 01:57:25 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-16 01:57:25 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-16 01:57:25 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-16 01:57:25 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-16 01:57:25 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-16 01:57:25 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-16 01:57:25 (9675) [INFO] * 2025-03-16 01:57:25 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-16 01:57:25 (9645) [INFO] * 2025-03-16 01:57:25 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-16 01:57:25 (9658) [INFO] Determining fastest mirrors * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-16 01:57:57 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-16 01:57:57 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-16 01:57:57 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-16 01:57:57 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-16 01:57:57 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-16 01:57:57 (9658) [INFO] yum --disablerepo= ... * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-16 01:57:57 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-16 01:57:57 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] yum-config-manager --disable * 2025-03-16 01:57:57 (9658) [INFO] or * 2025-03-16 01:57:57 (9658) [INFO] subscription-manager repos --disable= * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-16 01:57:57 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-16 01:57:57 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-16 01:57:57 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-16 01:57:57 (9658) [INFO] compromise: * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-16 01:57:57 (9658) [INFO] * 2025-03-16 01:57:57 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-16 01:57:57 (9675) [INFO] * 2025-03-16 01:57:57 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-16 01:57:57 (6033) [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 * 2025-03-16 01:57:59 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-16 01:57:59 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-16 01:57:59 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-16 01:57:59 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-16 01:57:59 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-16 01:58:06 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lhu0722Hm9/ea_profile.json * 2025-03-16 02:01:56 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lhu0722Hm9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-16 02:01:56 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-17 01:52:51 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-17 01:56:51 (10727) [INFO] Script is up to date. * 2025-03-17 02:00:54 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-17 02:00:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-17 02:00:54 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-17 02:00:54 (9645) [INFO] * 2025-03-17 02:01:08 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-17 02:01:08 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-17 02:01:08 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-17 02:01:08 (9645) [INFO] * 2025-03-17 02:01:20 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-17 02:01:24 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-17 02:01:24 (9645) [INFO] * 2025-03-17 02:01:24 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-17 02:01:25 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-17 02:01:55 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-17 02:01:55 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-17 02:01:55 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-17 02:01:55 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-17 02:04:41 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-17 02:04:41 (9658) [INFO] Trying other mirror. * 2025-03-17 02:04:56 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-17 02:04:56 (9658) [INFO] Trying other mirror. * 2025-03-17 02:05:30 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-17 02:05:30 (9658) [INFO] Trying other mirror. * 2025-03-17 02:05:39 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-17 02:05:39 (9658) [INFO] Trying other mirror. * 2025-03-17 02:06:00 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-17 02:06:00 (9658) [INFO] Trying other mirror. * 2025-03-17 02:06:44 (9658) [INFO] Metadata Cache Created * 2025-03-17 02:06:44 (9675) [INFO] * 2025-03-17 02:06:44 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-17 02:06:44 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-17 02:06:44 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-17 02:06:44 (9645) [INFO] * 2025-03-17 02:06:44 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-17 02:06:44 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-17 02:06:44 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-17 02:06:44 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-17 02:06:44 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-17 02:06:44 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-17 02:06:44 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-17 02:06:44 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-17 02:06:44 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-17 02:06:44 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-17 02:06:45 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-17 02:06:45 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-17 02:06:45 (9675) [INFO] * 2025-03-17 02:06:45 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-17 02:06:45 (9645) [INFO] * 2025-03-17 02:06:46 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-17 02:06:46 (9658) [INFO] Determining fastest mirrors * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-17 02:07:18 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-17 02:07:18 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-17 02:07:18 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-17 02:07:18 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-17 02:07:18 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-17 02:07:18 (9658) [INFO] yum --disablerepo= ... * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-17 02:07:18 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-17 02:07:18 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] yum-config-manager --disable * 2025-03-17 02:07:18 (9658) [INFO] or * 2025-03-17 02:07:18 (9658) [INFO] subscription-manager repos --disable= * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-17 02:07:18 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-17 02:07:18 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-17 02:07:18 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-17 02:07:18 (9658) [INFO] compromise: * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-17 02:07:18 (9658) [INFO] * 2025-03-17 02:07:18 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-17 02:07:18 (9675) [INFO] * 2025-03-17 02:07:18 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-17 02:07:18 (6033) [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 * 2025-03-17 02:07:19 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-17 02:07:19 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-17 02:07:19 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-17 02:07:19 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-17 02:07:19 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-17 02:07:25 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/93lX8JyXBU/ea_profile.json * 2025-03-17 02:15:21 (8792) [INFO] Backed up EA4 profile to /tmp/93lX8JyXBU/ea_profile.json * 2025-03-17 02:15:22 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-17 02:15:25 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-17 02:15:56 (681) [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. * 2025-03-17 02:15:56 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-18 01:54:51 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-18 01:58:51 (10727) [INFO] Script is up to date. * 2025-03-18 02:02:54 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-18 02:02:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-18 02:02:55 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-18 02:02:55 (9645) [INFO] * 2025-03-18 02:02:59 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-18 02:02:59 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-18 02:02:59 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-18 02:02:59 (9645) [INFO] * 2025-03-18 02:03:11 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-18 02:03:14 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-18 02:03:14 (9645) [INFO] * 2025-03-18 02:03:14 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-18 02:03:14 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-18 02:03:44 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-18 02:03:44 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-18 02:03:44 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-18 02:03:44 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-18 02:06:30 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-18 02:06:30 (9658) [INFO] Trying other mirror. * 2025-03-18 02:06:47 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:06:47 (9658) [INFO] Trying other mirror. * 2025-03-18 02:07:04 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:07:04 (9658) [INFO] Trying other mirror. * 2025-03-18 02:07:19 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:07:19 (9658) [INFO] Trying other mirror. * 2025-03-18 02:07:50 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-03-18 02:07:50 (9658) [INFO] Trying other mirror. * 2025-03-18 02:08:21 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-18 02:08:21 (9658) [INFO] Trying other mirror. * 2025-03-18 02:08:51 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-03-18 02:08:51 (9658) [INFO] Trying other mirror. * 2025-03-18 02:09:33 (9658) [INFO] Metadata Cache Created * 2025-03-18 02:09:33 (9675) [INFO] * 2025-03-18 02:09:33 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. * 2025-03-18 02:09:33 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-18 02:09:33 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-18 02:09:33 (9645) [INFO] * 2025-03-18 02:09:34 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-18 02:09:34 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-18 02:09:34 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-18 02:09:34 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-18 02:09:34 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-18 02:09:34 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-18 02:09:34 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-18 02:09:34 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-18 02:09:34 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-18 02:09:34 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-18 02:09:35 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-18 02:09:35 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-18 02:09:35 (9675) [INFO] * 2025-03-18 02:09:35 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-18 02:09:35 (9645) [INFO] * 2025-03-18 02:09:35 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-18 02:09:35 (9658) [INFO] Determining fastest mirrors * 2025-03-18 02:10:08 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-18 02:10:08 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-18 02:10:08 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-18 02:10:08 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-18 02:13:11 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-18 02:13:11 (9658) [INFO] Trying other mirror. * 2025-03-18 02:13:11 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:13:11 (9658) [INFO] Trying other mirror. * 2025-03-18 02:15:51 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-03-18 02:15:51 (9658) [INFO] Trying other mirror. * 2025-03-18 02:18:40 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-18 02:18:40 (9658) [INFO] Trying other mirror. * 2025-03-18 02:18:40 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-18 02:18:40 (9658) [INFO] Trying other mirror. * 2025-03-18 02:19:10 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:19:10 (9658) [INFO] Trying other mirror. * 2025-03-18 02:20:11 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:20:11 (9658) [INFO] Trying other mirror. * 2025-03-18 02:20:11 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:20:11 (9658) [INFO] Trying other mirror. * 2025-03-18 02:20:42 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-18 02:20:42 (9658) [INFO] Trying other mirror. * 2025-03-18 02:21:43 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-18 02:21:43 (9658) [INFO] Trying other mirror. * 2025-03-18 02:22:13 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-18 02:22:13 (9658) [INFO] Trying other mirror. * 2025-03-18 02:22:44 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-18 02:22:44 (9658) [INFO] Trying other mirror. * 2025-03-18 02:24:05 (9658) [INFO] Metadata Cache Created * 2025-03-18 02:24:05 (9675) [INFO] * 2025-03-18 02:24:05 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-18 02:24:05 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-03-18 02:24:07 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-18 02:24:07 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-18 02:24:07 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-18 02:24:07 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-18 02:24:07 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-18 02:24:22 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/K5l98t9mjx/ea_profile.json * 2025-03-18 02:24:24 (8792) [INFO] Backed up EA4 profile to /tmp/K5l98t9mjx/ea_profile.json * 2025-03-18 02:24:25 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-18 02:24:28 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-19 01:46:53 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-19 01:50:53 (10727) [INFO] Script is up to date. * 2025-03-19 01:54:56 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-19 01:54:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-19 01:54:56 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-19 01:54:56 (9645) [INFO] * 2025-03-19 01:55:09 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-19 01:55:09 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-19 01:55:09 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-19 01:55:09 (9645) [INFO] * 2025-03-19 01:55:21 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-19 01:55:24 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-19 01:55:24 (9645) [INFO] * 2025-03-19 01:55:25 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-19 01:55:25 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-19 01:55:55 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-19 01:55:55 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-19 01:55:55 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-19 01:55:55 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-19 01:56:41 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-03-19 01:56:41 (9658) [INFO] Trying other mirror. * 2025-03-19 01:57:12 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-19 01:57:12 (9658) [INFO] Trying other mirror. * 2025-03-19 01:59:42 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-19 01:59:42 (9658) [INFO] Trying other mirror. * 2025-03-19 01:59:43 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-19 01:59:43 (9658) [INFO] Trying other mirror. * 2025-03-19 02:00:03 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-19 02:00:03 (9658) [INFO] Trying other mirror. * 2025-03-19 02:01:12 (9658) [INFO] Metadata Cache Created * 2025-03-19 02:01:12 (9675) [INFO] * 2025-03-19 02:01:12 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-19 02:01:12 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-19 02:01:12 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-19 02:01:12 (9645) [INFO] * 2025-03-19 02:01:12 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-19 02:01:12 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-19 02:01:12 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-19 02:01:12 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-19 02:01:12 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-19 02:01:12 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-19 02:01:12 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-19 02:01:12 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-19 02:01:12 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-19 02:01:12 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-19 02:01:13 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-19 02:01:13 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-19 02:01:13 (9675) [INFO] * 2025-03-19 02:01:13 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-19 02:01:13 (9645) [INFO] * 2025-03-19 02:01:13 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-19 02:01:14 (9658) [INFO] Determining fastest mirrors * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-19 02:01:44 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-19 02:01:44 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-19 02:01:44 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-19 02:01:44 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-19 02:01:44 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-19 02:01:44 (9658) [INFO] yum --disablerepo= ... * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-19 02:01:44 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-19 02:01:44 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] yum-config-manager --disable * 2025-03-19 02:01:44 (9658) [INFO] or * 2025-03-19 02:01:44 (9658) [INFO] subscription-manager repos --disable= * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-19 02:01:44 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-19 02:01:44 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-19 02:01:44 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-19 02:01:44 (9658) [INFO] compromise: * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-19 02:01:44 (9658) [INFO] * 2025-03-19 02:01:44 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-19 02:01:44 (9675) [INFO] * 2025-03-19 02:01:44 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-19 02:01:44 (6033) [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 * 2025-03-19 02:01:46 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-19 02:01:46 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-19 02:01:46 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-19 02:01:46 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-19 02:01:46 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-19 02:01:52 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fCPI1_t0UP/ea_profile.json * 2025-03-19 02:09:02 (8792) [INFO] Backed up EA4 profile to /tmp/fCPI1_t0UP/ea_profile.json * 2025-03-19 02:09:02 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-19 02:09:06 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-19 02:09:37 (681) [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. * 2025-03-19 02:09:37 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-20 01:57:58 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-20 02:01:59 (10727) [INFO] Script is up to date. * 2025-03-20 02:06:01 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-20 02:06:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-20 02:06:01 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-20 02:06:01 (9645) [INFO] * 2025-03-20 02:06:14 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-20 02:06:14 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-20 02:06:14 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-20 02:06:14 (9645) [INFO] * 2025-03-20 02:06:34 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-20 02:06:34 (9645) [INFO] * 2025-03-20 02:06:35 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-20 02:06:35 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-20 02:07:06 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-20 02:07:06 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-20 02:07:06 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-20 02:07:06 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-20 02:08:50 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-20 02:08:50 (9658) [INFO] Trying other mirror. * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-20 02:08:50 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-20 02:08:50 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-20 02:08:50 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-20 02:08:50 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-20 02:08:50 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-20 02:08:50 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-20 02:08:50 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-20 02:08:50 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-20 02:08:50 (9658) [INFO] or * 2025-03-20 02:08:50 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-20 02:08:50 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-20 02:08:50 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-20 02:08:50 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-20 02:08:50 (9658) [INFO] compromise: * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-20 02:08:50 (9658) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-20 02:08:50 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-20 02:08:50 (9675) [INFO] * 2025-03-20 02:08:50 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-20 02:08:50 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-20 02:08:50 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-20 02:08:50 (9645) [INFO] * 2025-03-20 02:08:50 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-20 02:08:51 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-20 02:08:51 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-20 02:08:51 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-20 02:08:51 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-20 02:08:51 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-20 02:08:51 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-20 02:08:51 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-20 02:08:51 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-20 02:08:51 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-20 02:08:51 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-20 02:08:51 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-20 02:08:51 (9675) [INFO] * 2025-03-20 02:08:51 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-20 02:08:51 (9645) [INFO] * 2025-03-20 02:08:51 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-20 02:08:51 (9658) [INFO] Determining fastest mirrors * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-20 02:09:23 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-20 02:09:23 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-20 02:09:23 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-20 02:09:23 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-20 02:09:23 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-20 02:09:23 (9658) [INFO] yum --disablerepo= ... * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-20 02:09:23 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-20 02:09:23 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] yum-config-manager --disable * 2025-03-20 02:09:23 (9658) [INFO] or * 2025-03-20 02:09:23 (9658) [INFO] subscription-manager repos --disable= * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-20 02:09:23 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-20 02:09:23 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-20 02:09:23 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-20 02:09:23 (9658) [INFO] compromise: * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-20 02:09:23 (9658) [INFO] * 2025-03-20 02:09:23 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-20 02:09:23 (9675) [INFO] * 2025-03-20 02:09:23 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-20 02:09:23 (6033) [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 * 2025-03-20 02:09:25 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-20 02:09:25 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-20 02:09:25 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-20 02:09:25 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-20 02:09:25 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-20 02:09:31 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/msiiXAaMUq/ea_profile.json * 2025-03-20 02:10:36 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/msiiXAaMUq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-20 02:10:36 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-21 01:49:43 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-21 01:53:44 (10727) [INFO] Script is up to date. * 2025-03-21 01:57:46 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-21 01:57:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-21 01:57:47 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-21 01:57:47 (9645) [INFO] * 2025-03-21 01:58:01 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-21 01:58:01 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-21 01:58:01 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-21 01:58:01 (9645) [INFO] * 2025-03-21 01:58:22 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-21 01:58:22 (9645) [INFO] * 2025-03-21 01:58:22 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-21 01:58:23 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-21 01:58:53 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-21 01:58:53 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-21 01:58:53 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-21 01:58:53 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-21 02:00:37 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:00:37 (9658) [INFO] Trying other mirror. * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-21 02:00:37 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-21 02:00:37 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-21 02:00:37 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-21 02:00:37 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-21 02:00:37 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-21 02:00:37 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-21 02:00:37 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-21 02:00:37 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-21 02:00:37 (9658) [INFO] or * 2025-03-21 02:00:37 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-21 02:00:37 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-21 02:00:37 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-21 02:00:37 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-21 02:00:37 (9658) [INFO] compromise: * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-21 02:00:37 (9658) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-21 02:00:37 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:00:37 (9675) [INFO] * 2025-03-21 02:00:37 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:00:37 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-21 02:00:37 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-21 02:00:37 (9645) [INFO] * 2025-03-21 02:00:37 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-21 02:00:38 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-21 02:00:38 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-21 02:00:38 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-21 02:00:38 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-21 02:00:38 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-21 02:00:38 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-21 02:00:38 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-21 02:00:38 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-21 02:00:38 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-21 02:00:38 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-21 02:00:38 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-21 02:00:38 (9675) [INFO] * 2025-03-21 02:00:38 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-21 02:00:38 (9645) [INFO] * 2025-03-21 02:00:38 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-21 02:00:39 (9658) [INFO] Determining fastest mirrors * 2025-03-21 02:01:11 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-21 02:01:11 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-21 02:01:11 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-21 02:01:11 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-21 02:01:57 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-21 02:01:57 (9658) [INFO] Trying other mirror. * 2025-03-21 02:02:28 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-21 02:02:28 (9658) [INFO] Trying other mirror. * 2025-03-21 02:02:59 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-03-21 02:02:59 (9658) [INFO] Trying other mirror. * 2025-03-21 02:04:27 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:04:27 (9658) [INFO] Trying other mirror. * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-21 02:04:27 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-21 02:04:27 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-21 02:04:27 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-21 02:04:27 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-21 02:04:27 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-21 02:04:27 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-21 02:04:27 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-21 02:04:27 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-21 02:04:27 (9658) [INFO] or * 2025-03-21 02:04:27 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-21 02:04:27 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-21 02:04:27 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-21 02:04:27 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-21 02:04:27 (9658) [INFO] compromise: * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-21 02:04:27 (9658) [INFO] * 2025-03-21 02:04:27 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-21 02:04:27 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:04:27 (9675) [INFO] * 2025-03-21 02:04:27 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-21 02:04:27 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-21 02:04:28 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-21 02:04:28 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-21 02:04:28 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-21 02:04:28 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-21 02:04:28 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-21 02:04:35 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/U6BEJyNHFt/ea_profile.json * 2025-03-21 02:07:22 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/U6BEJyNHFt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-21 02:07:22 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-22 01:46:46 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-22 01:50:46 (10727) [INFO] Script is up to date. * 2025-03-22 01:54:50 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-22 01:54:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-22 01:54:50 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-22 01:54:50 (9645) [INFO] * 2025-03-22 01:55:03 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-22 01:55:03 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-22 01:55:03 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-22 01:55:03 (9645) [INFO] * 2025-03-22 01:55:26 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-22 01:55:26 (9645) [INFO] * 2025-03-22 01:55:26 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-22 01:55:26 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-22 01:55:57 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-22 01:55:57 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-22 01:55:57 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-22 01:55:57 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-22 01:56:44 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') * 2025-03-22 01:56:44 (9658) [INFO] Trying other mirror. * 2025-03-22 01:58:12 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 01:58:12 (9658) [INFO] Trying other mirror. * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-22 01:58:12 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-22 01:58:12 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-22 01:58:12 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-22 01:58:12 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-22 01:58:12 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-22 01:58:12 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-22 01:58:12 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-22 01:58:12 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-22 01:58:12 (9658) [INFO] or * 2025-03-22 01:58:12 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-22 01:58:12 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-22 01:58:12 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-22 01:58:12 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-22 01:58:12 (9658) [INFO] compromise: * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-22 01:58:12 (9658) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-22 01:58:12 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 01:58:12 (9675) [INFO] * 2025-03-22 01:58:12 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 01:58:12 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-22 01:58:12 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-22 01:58:12 (9645) [INFO] * 2025-03-22 01:58:12 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-22 01:58:13 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-22 01:58:13 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-22 01:58:13 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-22 01:58:13 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-22 01:58:13 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-22 01:58:13 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-22 01:58:13 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-22 01:58:13 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-22 01:58:13 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-22 01:58:13 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-22 01:58:13 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-22 01:58:13 (9675) [INFO] * 2025-03-22 01:58:13 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-22 01:58:13 (9645) [INFO] * 2025-03-22 01:58:13 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-22 01:58:14 (9658) [INFO] Determining fastest mirrors * 2025-03-22 01:58:45 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-22 01:58:45 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-22 01:58:45 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-22 01:58:45 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-22 02:00:29 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 02:00:29 (9658) [INFO] Trying other mirror. * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-22 02:00:29 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-22 02:00:29 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-22 02:00:29 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-22 02:00:29 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-22 02:00:29 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-22 02:00:29 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-22 02:00:29 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-22 02:00:29 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-22 02:00:29 (9658) [INFO] or * 2025-03-22 02:00:29 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-22 02:00:29 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-22 02:00:29 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-22 02:00:29 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-22 02:00:29 (9658) [INFO] compromise: * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-22 02:00:29 (9658) [INFO] * 2025-03-22 02:00:29 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-22 02:00:29 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 02:00:29 (9675) [INFO] * 2025-03-22 02:00:29 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-22 02:00:29 (6033) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-22 02:00:31 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-22 02:00:31 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-22 02:00:31 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-22 02:00:31 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-22 02:00:31 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-22 02:00:38 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hbky7ml9_m/ea_profile.json * 2025-03-22 02:02:54 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hbky7ml9_m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-22 02:02:54 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-23 01:46:08 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-23 01:50:08 (10727) [INFO] Script is up to date. * 2025-03-23 01:54:11 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-23 01:54:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-23 01:54:11 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-23 01:54:11 (9645) [INFO] * 2025-03-23 01:54:25 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-23 01:54:25 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-23 01:54:25 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-23 01:54:25 (9645) [INFO] * 2025-03-23 01:54:47 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-23 01:54:47 (9645) [INFO] * 2025-03-23 01:54:47 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-23 01:54:47 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-23 01:55:18 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-23 01:55:18 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-23 01:55:18 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-23 01:55:18 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-23 01:57:02 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:57:02 (9658) [INFO] Trying other mirror. * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-23 01:57:02 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-23 01:57:02 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-23 01:57:02 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-23 01:57:02 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-23 01:57:02 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-23 01:57:02 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-23 01:57:02 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-23 01:57:02 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-23 01:57:02 (9658) [INFO] or * 2025-03-23 01:57:02 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-23 01:57:02 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-23 01:57:02 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-23 01:57:02 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-23 01:57:02 (9658) [INFO] compromise: * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-23 01:57:02 (9658) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-23 01:57:02 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:57:02 (9675) [INFO] * 2025-03-23 01:57:02 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:57:02 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-23 01:57:02 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-23 01:57:02 (9645) [INFO] * 2025-03-23 01:57:02 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-23 01:57:03 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-23 01:57:03 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-23 01:57:03 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-23 01:57:03 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-23 01:57:03 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-23 01:57:03 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-23 01:57:03 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-23 01:57:03 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-23 01:57:03 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-23 01:57:03 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-23 01:57:03 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-23 01:57:03 (9675) [INFO] * 2025-03-23 01:57:03 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-23 01:57:03 (9645) [INFO] * 2025-03-23 01:57:03 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-23 01:57:04 (9658) [INFO] Determining fastest mirrors * 2025-03-23 01:57:35 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-23 01:57:35 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-23 01:57:35 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-23 01:57:35 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-23 01:59:18 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:59:18 (9658) [INFO] Trying other mirror. * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-23 01:59:18 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-23 01:59:18 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-23 01:59:18 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-23 01:59:18 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-23 01:59:18 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-23 01:59:18 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-23 01:59:18 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-23 01:59:18 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-23 01:59:18 (9658) [INFO] or * 2025-03-23 01:59:18 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-23 01:59:18 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-23 01:59:18 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-23 01:59:18 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-23 01:59:18 (9658) [INFO] compromise: * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-23 01:59:18 (9658) [INFO] * 2025-03-23 01:59:18 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-23 01:59:18 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:59:19 (9675) [INFO] * 2025-03-23 01:59:19 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-23 01:59:19 (6033) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-23 01:59:20 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-23 01:59:20 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-23 01:59:20 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-23 01:59:20 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-23 01:59:20 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-23 01:59:27 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AOkJ_hueI3/ea_profile.json * 2025-03-23 02:01:42 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AOkJ_hueI3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-23 02:01:42 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-24 01:47:15 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-24 01:51:15 (10727) [INFO] Script is up to date. * 2025-03-24 01:55:18 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-24 01:55:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-24 01:55:18 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-24 01:55:18 (9645) [INFO] * 2025-03-24 01:55:29 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-24 01:55:29 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-24 01:55:29 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-24 01:55:29 (9645) [INFO] * 2025-03-24 01:55:51 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-24 01:55:51 (9645) [INFO] * 2025-03-24 01:55:52 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-24 01:55:52 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-24 01:56:22 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-24 01:56:22 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-24 01:56:22 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-24 01:56:22 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-24 01:58:06 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 01:58:06 (9658) [INFO] Trying other mirror. * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-24 01:58:06 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-24 01:58:06 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-24 01:58:06 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-24 01:58:06 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-24 01:58:06 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-24 01:58:06 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-24 01:58:06 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-24 01:58:06 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-24 01:58:06 (9658) [INFO] or * 2025-03-24 01:58:06 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-24 01:58:06 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-24 01:58:06 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-24 01:58:06 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-24 01:58:06 (9658) [INFO] compromise: * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-24 01:58:06 (9658) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-24 01:58:06 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 01:58:06 (9675) [INFO] * 2025-03-24 01:58:06 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 01:58:06 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-24 01:58:06 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-24 01:58:06 (9645) [INFO] * 2025-03-24 01:58:06 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-24 01:58:07 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-24 01:58:07 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-24 01:58:07 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-24 01:58:07 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-24 01:58:07 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-24 01:58:07 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-24 01:58:07 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-24 01:58:07 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-24 01:58:07 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-24 01:58:07 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-24 01:58:07 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-24 01:58:07 (9675) [INFO] * 2025-03-24 01:58:07 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-24 01:58:07 (9645) [INFO] * 2025-03-24 01:58:07 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-24 01:58:08 (9658) [INFO] Determining fastest mirrors * 2025-03-24 01:58:39 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-24 01:58:39 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-24 01:58:39 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-24 01:58:39 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-24 01:59:25 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-24 01:59:25 (9658) [INFO] Trying other mirror. * 2025-03-24 02:00:54 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 02:00:54 (9658) [INFO] Trying other mirror. * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-24 02:00:54 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-24 02:00:54 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-24 02:00:54 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-24 02:00:54 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-24 02:00:54 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-24 02:00:54 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-24 02:00:54 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-24 02:00:54 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-24 02:00:54 (9658) [INFO] or * 2025-03-24 02:00:54 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-24 02:00:54 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-24 02:00:54 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-24 02:00:54 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-24 02:00:54 (9658) [INFO] compromise: * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-24 02:00:54 (9658) [INFO] * 2025-03-24 02:00:54 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-24 02:00:54 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 02:00:54 (9675) [INFO] * 2025-03-24 02:00:54 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-24 02:00:54 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-24 02:00:55 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-24 02:00:55 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-24 02:00:55 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-24 02:00:55 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-24 02:00:55 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-24 02:01:03 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9vCIPNF0Rq/ea_profile.json * 2025-03-24 02:03:18 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9vCIPNF0Rq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-24 02:03:18 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-25 01:45:34 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-25 01:49:34 (10727) [INFO] Script is up to date. * 2025-03-25 01:53:37 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-25 01:53:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-25 01:53:37 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-25 01:53:37 (9645) [INFO] * 2025-03-25 01:53:41 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-25 01:53:41 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-25 01:53:41 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-25 01:53:41 (9645) [INFO] * 2025-03-25 01:56:00 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-25 01:56:00 (9645) [INFO] * 2025-03-25 01:56:00 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-25 01:56:01 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-25 01:56:32 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-25 01:56:32 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-25 01:56:32 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-25 01:56:32 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-25 01:58:16 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 01:58:16 (9658) [INFO] Trying other mirror. * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-25 01:58:16 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-25 01:58:16 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-25 01:58:16 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-25 01:58:16 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-25 01:58:16 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-25 01:58:16 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-25 01:58:16 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-25 01:58:16 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-25 01:58:16 (9658) [INFO] or * 2025-03-25 01:58:16 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-25 01:58:16 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-25 01:58:16 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-25 01:58:16 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-25 01:58:16 (9658) [INFO] compromise: * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-25 01:58:16 (9658) [INFO] * 2025-03-25 01:58:16 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-25 01:58:16 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 01:58:16 (9675) [INFO] * 2025-03-25 01:58:16 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 01:58:16 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-25 01:58:16 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-25 01:58:16 (9645) [INFO] * 2025-03-25 01:58:17 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-25 01:58:17 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-25 01:58:17 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-25 01:58:17 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-25 01:58:17 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-25 01:58:17 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-25 01:58:17 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-25 01:58:17 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-25 01:58:17 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-25 01:58:17 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-25 01:58:17 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-25 01:58:17 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-25 01:58:17 (9675) [INFO] * 2025-03-25 01:58:17 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-25 01:58:17 (9645) [INFO] * 2025-03-25 01:58:18 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-25 01:58:18 (9658) [INFO] Determining fastest mirrors * 2025-03-25 01:58:49 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-25 01:58:49 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-25 01:58:49 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-25 01:58:49 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-25 01:59:36 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-25 01:59:36 (9658) [INFO] Trying other mirror. * 2025-03-25 02:01:04 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 02:01:04 (9658) [INFO] Trying other mirror. * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-25 02:01:04 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-25 02:01:04 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-25 02:01:04 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-25 02:01:04 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-25 02:01:04 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-25 02:01:04 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-25 02:01:04 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-25 02:01:04 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-25 02:01:04 (9658) [INFO] or * 2025-03-25 02:01:04 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-25 02:01:04 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-25 02:01:04 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-25 02:01:04 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-25 02:01:04 (9658) [INFO] compromise: * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-25 02:01:04 (9658) [INFO] * 2025-03-25 02:01:04 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-25 02:01:04 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 02:01:04 (9675) [INFO] * 2025-03-25 02:01:04 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-25 02:01:04 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-25 02:01:06 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-25 02:01:06 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-25 02:01:06 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-25 02:01:06 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-25 02:01:06 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-25 02:03:09 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bPuVsJg29l/ea_profile.json * 2025-03-25 02:06:28 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bPuVsJg29l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-25 02:06:28 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-26 01:46:19 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-26 01:50:19 (10727) [INFO] Script is up to date. * 2025-03-26 01:54:22 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-26 01:54:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-26 01:54:22 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-26 01:54:22 (9645) [INFO] * 2025-03-26 01:54:34 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-26 01:54:34 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-26 01:54:34 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-26 01:54:34 (9645) [INFO] * 2025-03-26 01:54:55 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-26 01:54:55 (9645) [INFO] * 2025-03-26 01:54:56 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-26 01:54:56 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-26 01:55:28 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-26 01:55:28 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-26 01:55:28 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-26 01:55:28 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-26 01:57:12 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-26 01:57:12 (9658) [INFO] Trying other mirror. * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-26 01:57:12 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-26 01:57:12 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-26 01:57:12 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-26 01:57:12 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-26 01:57:12 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-26 01:57:12 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-26 01:57:12 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-26 01:57:12 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-26 01:57:12 (9658) [INFO] or * 2025-03-26 01:57:12 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-26 01:57:12 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-26 01:57:12 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-26 01:57:12 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-26 01:57:12 (9658) [INFO] compromise: * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-26 01:57:12 (9658) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-26 01:57:12 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-26 01:57:12 (9675) [INFO] * 2025-03-26 01:57:12 (6022) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyMTE2NDA3OjE3NDIzNzU2MDc6Ecu--Mja6CsZ4uBevHRb-Y74nZn8WT4VABjRDjGZBmkQj6MXuAeLoaGMHuWJXBTNzwI-5obuWzs1j2lSw-bh9m8-E96_wm4QjEdUwEJZHQIs80y09Lay8RwbW1M9ldDCuSy59kD5PAIbsmSRaPPV6-HRR6zfNy24xSyBOQODRyY2OYxGLDrYTVDLL_zNlB3Qra25cRyAZ1c4JrTYoPGQsKN72zzLGbTHQ29Wzs5mTiXmkMnY6QRa5DxXxWLpIvC3bKMERkc5O0aRcFFBghCVC3Y3ptdCW3JyDacipTSNb1wycHyVekpaF_qQ9iYbKNix-n60iG1tni75_mpyJnWiUp4X-LV6W9-Mh5I-pfJagzmTq0xdr7YU2_YArhrah4i7T7eyRw00TiX2fVr8paXDpg7aGlfcDAR9_QvuR-r7Q_o69FpbfP_vEN0VHbDjThwkGvphiKlSzF6qOYA21W14b1i2kg_shZ4qfTNNagrKkOzvZL-wVxUwAi-kgKTnfqPkyz4wlSiswosC2I-ckFivM-b0lZJXcixu359LcXsd9AGsxRRxELzVoogvlVB3CJVit8wQWPWP8azr4hqcbXsNmDRdeLOJfhr4UYHA9b21ndCXFvKpcKsfV8Kpeuq0m4tW8uJXTdlgFOm7KvHdRCxnyCwEzVdsBl8CdW4wcLAZxtc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-26 01:57:12 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-26 01:57:12 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-26 01:57:12 (9645) [INFO] * 2025-03-26 01:57:12 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-26 01:57:13 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-26 01:57:13 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-26 01:57:13 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-26 01:57:13 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-26 01:57:13 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-26 01:57:13 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-26 01:57:13 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-26 01:57:13 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-26 01:57:13 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-26 01:57:13 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-26 01:57:13 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-26 01:57:13 (9675) [INFO] * 2025-03-26 01:57:13 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-26 01:57:13 (9645) [INFO] * 2025-03-26 01:57:13 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-26 01:57:13 (9658) [INFO] Determining fastest mirrors * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-26 01:57:45 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-26 01:57:45 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-26 01:57:45 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-26 01:57:45 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-26 01:57:45 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-26 01:57:45 (9658) [INFO] yum --disablerepo= ... * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-26 01:57:45 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-26 01:57:45 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] yum-config-manager --disable * 2025-03-26 01:57:45 (9658) [INFO] or * 2025-03-26 01:57:45 (9658) [INFO] subscription-manager repos --disable= * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-26 01:57:45 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-26 01:57:45 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-26 01:57:45 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-26 01:57:45 (9658) [INFO] compromise: * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-26 01:57:45 (9658) [INFO] * 2025-03-26 01:57:45 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-26 01:57:45 (9675) [INFO] * 2025-03-26 01:57:45 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-26 01:57:45 (6033) [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 * 2025-03-26 01:57:46 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-26 01:57:46 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-26 01:57:46 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-26 01:57:46 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-26 01:57:46 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-26 01:57:53 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Ku1r6g4OUX/ea_profile.json * 2025-03-26 02:00:41 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Ku1r6g4OUX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-26 02:00:41 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-27 02:16:49 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-27 02:20:50 (10727) [INFO] Script is up to date. * 2025-03-27 02:24:53 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-27 02:24:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-27 02:24:53 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-27 02:24:53 (9645) [INFO] * 2025-03-27 02:24:56 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-27 02:24:56 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-27 02:24:56 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-27 02:24:57 (9645) [INFO] * 2025-03-27 02:25:09 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-27 02:25:13 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-27 02:25:13 (9645) [INFO] * 2025-03-27 02:25:13 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-27 02:25:13 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-27 02:25:43 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-27 02:25:43 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-27 02:25:43 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-27 02:25:43 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-27 02:28:29 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-27 02:28:29 (9658) [INFO] Trying other mirror. * 2025-03-27 02:28:47 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-03-27 02:28:47 (9658) [INFO] Trying other mirror. * 2025-03-27 02:29:16 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-03-27 02:29:16 (9658) [INFO] Trying other mirror. * 2025-03-27 02:29:18 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-27 02:29:18 (9658) [INFO] Trying other mirror. * 2025-03-27 02:29:47 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-27 02:29:47 (9658) [INFO] Trying other mirror. * 2025-03-27 02:29:48 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-27 02:29:48 (9658) [INFO] Trying other mirror. * 2025-03-27 02:30:17 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-27 02:30:17 (9658) [INFO] Trying other mirror. * 2025-03-27 02:30:48 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-27 02:30:48 (9658) [INFO] Trying other mirror. * 2025-03-27 02:31:19 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-03-27 02:31:19 (9658) [INFO] Trying other mirror. * 2025-03-27 02:31:49 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-27 02:31:49 (9658) [INFO] Trying other mirror. * 2025-03-27 02:32:20 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-27 02:32:20 (9658) [INFO] Trying other mirror. * 2025-03-27 02:33:04 (9658) [INFO] Metadata Cache Created * 2025-03-27 02:33:04 (9675) [INFO] * 2025-03-27 02:33:04 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. * 2025-03-27 02:33:04 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-27 02:33:04 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-27 02:33:04 (9645) [INFO] * 2025-03-27 02:33:05 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-27 02:33:05 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-27 02:33:05 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-27 02:33:05 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-27 02:33:05 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-27 02:33:05 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-27 02:33:05 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-27 02:33:05 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-27 02:33:05 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-27 02:33:05 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-27 02:33:06 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-27 02:33:06 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-27 02:33:06 (9675) [INFO] * 2025-03-27 02:33:06 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-27 02:33:06 (9645) [INFO] * 2025-03-27 02:33:06 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-27 02:33:06 (9658) [INFO] Determining fastest mirrors * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-03-27 02:33:37 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-27 02:33:37 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-27 02:33:37 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-27 02:33:37 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-27 02:33:37 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-27 02:33:37 (9658) [INFO] yum --disablerepo= ... * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-27 02:33:37 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-27 02:33:37 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] yum-config-manager --disable * 2025-03-27 02:33:37 (9658) [INFO] or * 2025-03-27 02:33:37 (9658) [INFO] subscription-manager repos --disable= * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-27 02:33:37 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-27 02:33:37 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-27 02:33:37 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-27 02:33:37 (9658) [INFO] compromise: * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-27 02:33:37 (9658) [INFO] * 2025-03-27 02:33:37 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-03-27 02:33:37 (9675) [INFO] * 2025-03-27 02:33:37 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-27 02:33:37 (6033) [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 * 2025-03-27 02:33:39 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-27 02:33:39 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-27 02:33:39 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-27 02:33:39 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-27 02:33:39 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-27 02:33:54 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_F_8y9sRWD/ea_profile.json * 2025-03-27 02:40:48 (8792) [INFO] Backed up EA4 profile to /tmp/_F_8y9sRWD/ea_profile.json * 2025-03-27 02:40:48 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-27 02:40:51 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-27 02:41:22 (681) [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. * 2025-03-27 02:41:22 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-28 01:53:22 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-28 01:57:23 (10727) [INFO] Script is up to date. * 2025-03-28 02:01:25 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-28 02:01:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-28 02:01:25 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-28 02:01:25 (9645) [INFO] * 2025-03-28 02:01:30 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-28 02:01:30 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-28 02:01:30 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-28 02:01:30 (9645) [INFO] * 2025-03-28 02:01:46 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-28 02:01:50 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-28 02:01:50 (9645) [INFO] * 2025-03-28 02:01:50 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-28 02:01:50 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-28 02:02:21 (9658) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-03-28 02:02:21 (9658) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-28 02:02:21 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-28 02:02:21 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-28 02:02:21 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-28 02:02:21 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-28 02:03:07 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-28 02:03:07 (9658) [INFO] Trying other mirror. * 2025-03-28 02:03:38 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-28 02:03:38 (9658) [INFO] Trying other mirror. * 2025-03-28 02:06:07 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:06:07 (9658) [INFO] Trying other mirror. * 2025-03-28 02:06:24 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-28 02:06:24 (9658) [INFO] Trying other mirror. * 2025-03-28 02:06:41 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-28 02:06:41 (9658) [INFO] Trying other mirror. * 2025-03-28 02:06:54 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:06:54 (9658) [INFO] Trying other mirror. * 2025-03-28 02:06:56 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-28 02:06:56 (9658) [INFO] Trying other mirror. * 2025-03-28 02:07:27 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-03-28 02:07:27 (9658) [INFO] Trying other mirror. * 2025-03-28 02:07:57 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:07:57 (9658) [INFO] Trying other mirror. * 2025-03-28 02:08:28 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-28 02:08:28 (9658) [INFO] Trying other mirror. * 2025-03-28 02:09:18 (9658) [INFO] Metadata Cache Created * 2025-03-28 02:09:18 (9675) [INFO] * 2025-03-28 02:09:18 (6022) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30534 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-03-28 02:09:18 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-28 02:09:18 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-28 02:09:18 (9645) [INFO] * 2025-03-28 02:09:18 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-28 02:09:19 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-28 02:09:19 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-28 02:09:19 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-28 02:09:19 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-28 02:09:19 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-28 02:09:19 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-28 02:09:19 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-28 02:09:19 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-28 02:09:19 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-28 02:09:20 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-28 02:09:20 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-28 02:09:20 (9675) [INFO] * 2025-03-28 02:09:20 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-28 02:09:20 (9645) [INFO] * 2025-03-28 02:09:20 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-28 02:09:20 (9658) [INFO] Determining fastest mirrors * 2025-03-28 02:09:53 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-28 02:09:53 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-28 02:09:53 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-28 02:09:53 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-28 02:10:41 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30723 milliseconds') * 2025-03-28 02:10:41 (9658) [INFO] Trying other mirror. * 2025-03-28 02:13:28 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:13:28 (9658) [INFO] Trying other mirror. * 2025-03-28 02:13:28 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-28 02:13:28 (9658) [INFO] Trying other mirror. * 2025-03-28 02:16:08 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-28 02:16:08 (9658) [INFO] Trying other mirror. * 2025-03-28 02:18:56 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:18:56 (9658) [INFO] Trying other mirror. * 2025-03-28 02:18:56 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-03-28 02:18:56 (9658) [INFO] Trying other mirror. * 2025-03-28 02:19:58 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:19:58 (9658) [INFO] Trying other mirror. * 2025-03-28 02:19:58 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:19:58 (9658) [INFO] Trying other mirror. * 2025-03-28 02:20:28 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:20:28 (9658) [INFO] Trying other mirror. * 2025-03-28 02:20:59 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-28 02:20:59 (9658) [INFO] Trying other mirror. * 2025-03-28 02:22:27 (9658) [INFO] Metadata Cache Created * 2025-03-28 02:22:27 (9675) [INFO] * 2025-03-28 02:22:27 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-28 02:22:27 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30723 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-28 02:22:29 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-28 02:22:29 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-28 02:22:29 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-28 02:22:29 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-28 02:22:29 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-28 02:22:44 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fdg09m7WDZ/ea_profile.json * 2025-03-28 02:22:46 (8792) [INFO] Backed up EA4 profile to /tmp/fdg09m7WDZ/ea_profile.json * 2025-03-28 02:22:47 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-28 02:22:51 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-29 01:54:20 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-29 01:58:21 (10727) [INFO] Script is up to date. * 2025-03-29 02:02:24 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-29 02:02:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-29 02:02:24 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-29 02:02:24 (9645) [INFO] * 2025-03-29 02:02:38 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-29 02:02:38 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-29 02:02:38 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-29 02:02:38 (9645) [INFO] * 2025-03-29 02:02:52 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-29 02:02:55 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-29 02:02:55 (9645) [INFO] * 2025-03-29 02:02:55 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-29 02:02:55 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-29 02:03:25 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-29 02:03:25 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-29 02:03:25 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-29 02:03:25 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-29 02:06:12 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-29 02:06:12 (9658) [INFO] Trying other mirror. * 2025-03-29 02:06:28 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:06:28 (9658) [INFO] Trying other mirror. * 2025-03-29 02:06:44 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:06:44 (9658) [INFO] Trying other mirror. * 2025-03-29 02:06:58 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-29 02:06:58 (9658) [INFO] Trying other mirror. * 2025-03-29 02:07:28 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:07:28 (9658) [INFO] Trying other mirror. * 2025-03-29 02:08:13 (9658) [INFO] Metadata Cache Created * 2025-03-29 02:08:13 (9675) [INFO] * 2025-03-29 02:08:13 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-03-29 02:08:13 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-29 02:08:13 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-29 02:08:13 (9645) [INFO] * 2025-03-29 02:08:13 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-29 02:08:13 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-29 02:08:13 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-29 02:08:13 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-29 02:08:13 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-29 02:08:13 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-29 02:08:13 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-29 02:08:13 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-29 02:08:13 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-29 02:08:13 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-29 02:08:14 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-29 02:08:14 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-29 02:08:14 (9675) [INFO] * 2025-03-29 02:08:14 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-29 02:08:14 (9645) [INFO] * 2025-03-29 02:08:14 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-29 02:08:14 (9658) [INFO] Determining fastest mirrors * 2025-03-29 02:08:46 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-29 02:08:46 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-29 02:08:46 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-29 02:08:46 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-29 02:11:50 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-29 02:11:50 (9658) [INFO] Trying other mirror. * 2025-03-29 02:11:50 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-29 02:11:50 (9658) [INFO] Trying other mirror. * 2025-03-29 02:12:21 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-03-29 02:12:21 (9658) [INFO] Trying other mirror. * 2025-03-29 02:12:51 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:12:51 (9658) [INFO] Trying other mirror. * 2025-03-29 02:13:58 (9658) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:13:58 (9658) [INFO] Trying other mirror. * 2025-03-29 02:14:29 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:14:29 (9658) [INFO] Trying other mirror. * 2025-03-29 02:14:55 (9658) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/0bd1dc1f1e4d9eea51c84b624688218fc5a31d49cb1667fa6b2faeeeeed60343-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:14:55 (9658) [INFO] Trying other mirror. * 2025-03-29 02:15:11 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/1ca976fad73aad18e6ee33e10d76c5734802082e367c3d4a1979b35da5a35b43-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:15:11 (9658) [INFO] Trying other mirror. * 2025-03-29 02:15:27 (9658) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:15:27 (9658) [INFO] Trying other mirror. * 2025-03-29 02:15:42 (9658) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:15:42 (9658) [INFO] Trying other mirror. * 2025-03-29 02:15:58 (9658) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:15:58 (9658) [INFO] Trying other mirror. * 2025-03-29 02:16:14 (9658) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:16:14 (9658) [INFO] Trying other mirror. * 2025-03-29 02:16:29 (9658) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:16:29 (9658) [INFO] Trying other mirror. * 2025-03-29 02:16:45 (9658) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:16:45 (9658) [INFO] Trying other mirror. * 2025-03-29 02:17:01 (9658) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:17:01 (9658) [INFO] Trying other mirror. * 2025-03-29 02:17:16 (9658) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:17:16 (9658) [INFO] Trying other mirror. * 2025-03-29 02:17:47 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:17:47 (9658) [INFO] Trying other mirror. * 2025-03-29 02:18:02 (9658) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/wp-toolkit/repodata/5ecfb1fdd5e26647ef83fb42dbcab9ba6b8f766c77e681ef556d215baf325065-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:18:02 (9658) [INFO] Trying other mirror. * 2025-03-29 02:18:18 (9658) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:18:18 (9658) [INFO] Trying other mirror. * 2025-03-29 02:18:18 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:18:18 (9658) [INFO] Trying other mirror. * 2025-03-29 02:18:49 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-03-29 02:18:49 (9658) [INFO] Trying other mirror. * 2025-03-29 02:18:49 (9658) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:18:49 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:19 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:19:19 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:19 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:19:19 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:19 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-29 02:19:19 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:19 (9658) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:19:19 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:36 (9658) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:19:36 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:49 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:19:49 (9658) [INFO] Trying other mirror. * 2025-03-29 02:19:50 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-29 02:19:50 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:06 (9658) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-03-29 02:20:06 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:20 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-03-29 02:20:20 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:35 (9658) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:20:35 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:50 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:20:50 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:52 (9658) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 404 - Not Found * 2025-03-29 02:20:52 (9658) [INFO] Trying other mirror. * 2025-03-29 02:20:52 (9658) [INFO] To address this issue please refer to the below wiki article * 2025-03-29 02:20:52 (9658) [INFO] * 2025-03-29 02:20:52 (9658) [INFO] https://wiki.centos.org/yum-errors * 2025-03-29 02:20:52 (9658) [INFO] * 2025-03-29 02:20:52 (9658) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-03-29 02:20:52 (9658) [INFO] * 2025-03-29 02:21:08 (9658) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:21:08 (9658) [INFO] Trying other mirror. * 2025-03-29 02:21:24 (9658) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:21:24 (9658) [INFO] Trying other mirror. * 2025-03-29 02:21:41 (9658) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:21:41 (9658) [INFO] Trying other mirror. * 2025-03-29 02:21:57 (9658) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-29 02:21:57 (9658) [INFO] Trying other mirror. * 2025-03-29 02:22:32 (9658) [INFO] Metadata Cache Created * 2025-03-29 02:22:32 (9675) [INFO] * 2025-03-29 02:22:32 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-29 02:22:32 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/0bd1dc1f1e4d9eea51c84b624688218fc5a31d49cb1667fa6b2faeeeeed60343-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/1ca976fad73aad18e6ee33e10d76c5734802082e367c3d4a1979b35da5a35b43-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/wp-toolkit/repodata/5ecfb1fdd5e26647ef83fb42dbcab9ba6b8f766c77e681ef556d215baf325065-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable Trying other mirror. https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.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://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-03-29 02:22:33 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-29 02:22:33 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-29 02:22:33 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-29 02:22:33 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-29 02:22:33 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-29 02:22:50 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DLG_rB3Z5S/ea_profile.json * 2025-03-29 02:22:53 (8792) [INFO] Backed up EA4 profile to /tmp/DLG_rB3Z5S/ea_profile.json * 2025-03-29 02:22:54 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-29 02:22:57 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-29 02:23:28 (681) [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. * 2025-03-29 02:23:28 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-30 01:47:25 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-30 01:51:26 (10727) [INFO] Script is up to date. * 2025-03-30 01:55:29 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-30 01:55:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-30 01:55:29 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-30 01:55:29 (9645) [INFO] * 2025-03-30 02:00:58 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-30 02:00:58 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-30 02:00:58 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-30 02:00:58 (9645) [INFO] * 2025-03-30 02:01:20 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-30 02:01:20 (9645) [INFO] * 2025-03-30 02:01:20 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-30 02:01:20 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-30 02:01:51 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-30 02:01:51 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-30 02:01:51 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-30 02:01:51 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-30 02:02:13 (9658) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" * 2025-03-30 02:02:13 (9658) [INFO] Trying other mirror. * 2025-03-30 02:03:08 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30773 milliseconds') * 2025-03-30 02:03:08 (9658) [INFO] Trying other mirror. * 2025-03-30 02:03:39 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-30 02:03:39 (9658) [INFO] Trying other mirror. * 2025-03-30 02:05:06 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:05:06 (9658) [INFO] Trying other mirror. * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-30 02:05:06 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-30 02:05:06 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-30 02:05:06 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-30 02:05:06 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-30 02:05:06 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-30 02:05:06 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-30 02:05:06 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-30 02:05:06 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-30 02:05:06 (9658) [INFO] or * 2025-03-30 02:05:06 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-30 02:05:06 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-30 02:05:06 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-30 02:05:06 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-30 02:05:06 (9658) [INFO] compromise: * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-30 02:05:06 (9658) [INFO] * 2025-03-30 02:05:06 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-30 02:05:06 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:05:06 (9675) [INFO] * 2025-03-30 02:05:06 (6022) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Operation now in progress" Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30773 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:05:06 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-30 02:05:06 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-30 02:05:06 (9645) [INFO] * 2025-03-30 02:05:07 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-30 02:05:07 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-30 02:05:07 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-30 02:05:07 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-30 02:05:07 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-30 02:05:07 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-30 02:05:07 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-30 02:05:07 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-30 02:05:07 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-30 02:05:07 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-30 02:05:07 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-30 02:05:07 (9658) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-03-30 02:05:07 (9675) [INFO] * 2025-03-30 02:05:07 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-30 02:05:07 (9645) [INFO] * 2025-03-30 02:05:08 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-30 02:05:08 (9658) [INFO] Determining fastest mirrors * 2025-03-30 02:05:39 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-30 02:05:39 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-30 02:05:39 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-30 02:05:39 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-03-30 02:07:23 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:07:23 (9658) [INFO] Trying other mirror. * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-03-30 02:07:23 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-30 02:07:23 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-30 02:07:23 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-30 02:07:23 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-03-30 02:07:23 (9658) [INFO] packages for the previous distribution release still work). * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-30 02:07:23 (9658) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-30 02:07:23 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-30 02:07:23 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-03-30 02:07:23 (9658) [INFO] or * 2025-03-30 02:07:23 (9658) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-30 02:07:23 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-30 02:07:23 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-30 02:07:23 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-30 02:07:23 (9658) [INFO] compromise: * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-03-30 02:07:23 (9658) [INFO] * 2025-03-30 02:07:23 (9658) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-03-30 02:07:23 (9658) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:07:23 (9675) [INFO] * 2025-03-30 02:07:23 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-30 02:07:23 (6033) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQyOTk0MDk3OjE3NDMyNTMyOTc6j04-tvdFnGffEV6i-m0xQK16ArcDSkz03GOjfZR3IyF_JRUerPeVyhaaK_aknwCeaN73h-8A9ylb_e4mhL9gWX7I7CfTkK914Dz1d9XO634vBNjjzN9fjCcfDYPhA9AhWx-ldM8M1iBxN915unztRn6y4O7RGFr_6B_IE73EETDY6q06RluOaFUxdZNz9_fDtIXLPuxZgTMGIteXhNQ5mih0qJ8t9tlHy8VaZIgedjtpkgM9PNM8Rp8nQh0AEno39hUUmKmbQFWo49ieX0jFc2G6HADefuVZ8ItxEIkUEEAkDpi5dXzk-BpBz92W6oDqnNUGCd88L460MWfRTZ4IEC_bkfVbnx_lNWHtUGDScByzxZPNPQYOAcfNyoTwFHBAj-bGbIHW1-QOGr2WsejQjZa-4ouZKK05v6jbVsO_IKsZsUuO0vyAAqEdqIK-WWYajdGp532YQSB4ZJJ4ooWAu6RNVgZTkcE80rGTkEPqJav7qC_L5-jlJK9SGl0XA1uC2clvXb92gWeSkrE69oCfq85pxQDJft8ySlL92tU--NW8VBGnp0hUy4y5obPdv4YLo9NWyAxg2X_vx8NqvN4C41AfbkdtW-D0kvsQ06NPfXpeW7fmFBWzv_OZKBKHhx-FqQTh6OQzrCDraIOZ4nJb6OgaXBhQ5ximO2xYSVMymjw=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-03-30 02:07:25 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-30 02:07:25 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-30 02:07:25 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-30 02:07:25 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-30 02:07:25 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-30 02:07:32 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/negzCtgz8V/ea_profile.json * 2025-03-30 02:09:47 (530) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/negzCtgz8V/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8771. * 2025-03-30 02:09:47 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-31 01:52:57 (10705) [INFO] Self-update of script version 62 requested. * 2025-03-31 01:56:58 (10727) [INFO] Script is up to date. * 2025-03-31 02:01:00 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-03-31 02:01:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-03-31 02:01:01 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-31 02:01:01 (9645) [INFO] * 2025-03-31 02:01:13 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-03-31 02:01:13 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-31 02:01:14 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-03-31 02:01:14 (9645) [INFO] * 2025-03-31 02:01:25 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-03-31 02:01:29 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-31 02:01:29 (9645) [INFO] * 2025-03-31 02:01:30 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-31 02:01:30 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-03-31 02:02:00 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-31 02:02:00 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-31 02:02:00 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-31 02:02:00 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-31 02:04:46 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-31 02:04:46 (9658) [INFO] Trying other mirror. * 2025-03-31 02:05:03 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:05:03 (9658) [INFO] Trying other mirror. * 2025-03-31 02:05:32 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:05:32 (9658) [INFO] Trying other mirror. * 2025-03-31 02:05:46 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:05:46 (9658) [INFO] Trying other mirror. * 2025-03-31 02:06:03 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-03-31 02:06:03 (9658) [INFO] Trying other mirror. * 2025-03-31 02:06:17 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-03-31 02:06:17 (9658) [INFO] Trying other mirror. * 2025-03-31 02:06:47 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-31 02:06:47 (9658) [INFO] Trying other mirror. * 2025-03-31 02:07:32 (9658) [INFO] Metadata Cache Created * 2025-03-31 02:07:32 (9675) [INFO] * 2025-03-31 02:07:32 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-03-31 02:07:32 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-31 02:07:32 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-03-31 02:07:32 (9645) [INFO] * 2025-03-31 02:07:32 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-31 02:07:32 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-03-31 02:07:32 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-31 02:07:32 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-31 02:07:32 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-03-31 02:07:32 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-03-31 02:07:32 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-31 02:07:32 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-31 02:07:32 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-03-31 02:07:32 (9658) [INFO] : wp-toolkit-thirdparties * 2025-03-31 02:07:33 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-03-31 02:07:33 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-03-31 02:07:33 (9675) [INFO] * 2025-03-31 02:07:33 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-03-31 02:07:33 (9645) [INFO] * 2025-03-31 02:07:34 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-31 02:07:34 (9658) [INFO] Determining fastest mirrors * 2025-03-31 02:08:05 (9658) [INFO] * EA4: 107.178.98.171 * 2025-03-31 02:08:05 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-03-31 02:08:05 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-03-31 02:08:05 (9658) [INFO] * epel: dl.fedoraproject.org * 2025-03-31 02:08:52 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-03-31 02:08:52 (9658) [INFO] Trying other mirror. * 2025-03-31 02:11:39 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-03-31 02:11:39 (9658) [INFO] Trying other mirror. * 2025-03-31 02:11:39 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-03-31 02:11:39 (9658) [INFO] Trying other mirror. * 2025-03-31 02:14:14 (9658) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/0bd1dc1f1e4d9eea51c84b624688218fc5a31d49cb1667fa6b2faeeeeed60343-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-31 02:14:14 (9658) [INFO] Trying other mirror. * 2025-03-31 02:14:18 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:14:18 (9658) [INFO] Trying other mirror. * 2025-03-31 02:14:46 (9658) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-31 02:14:46 (9658) [INFO] Trying other mirror. * 2025-03-31 02:17:06 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:17:06 (9658) [INFO] Trying other mirror. * 2025-03-31 02:17:22 (9658) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/wp-toolkit/repodata/5ecfb1fdd5e26647ef83fb42dbcab9ba6b8f766c77e681ef556d215baf325065-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-31 02:17:22 (9658) [INFO] Trying other mirror. * 2025-03-31 02:17:37 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-03-31 02:17:37 (9658) [INFO] Trying other mirror. * 2025-03-31 02:18:07 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno -1] Metadata file does not match checksum * 2025-03-31 02:18:07 (9658) [INFO] Trying other mirror. * 2025-03-31 02:18:38 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:18:38 (9658) [INFO] Trying other mirror. * 2025-03-31 02:18:38 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-03-31 02:18:38 (9658) [INFO] Trying other mirror. * 2025-03-31 02:19:38 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-03-31 02:19:38 (9658) [INFO] Trying other mirror. * 2025-03-31 02:20:08 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-03-31 02:20:08 (9658) [INFO] Trying other mirror. * 2025-03-31 02:20:42 (9658) [INFO] Metadata Cache Created * 2025-03-31 02:20:43 (9675) [INFO] * 2025-03-31 02:20:43 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-31 02:20:43 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/0bd1dc1f1e4d9eea51c84b624688218fc5a31d49cb1667fa6b2faeeeeed60343-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.5/wp-toolkit/repodata/5ecfb1fdd5e26647ef83fb42dbcab9ba6b8f766c77e681ef556d215baf325065-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-03-31 02:20:44 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-03-31 02:20:44 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-03-31 02:20:44 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-03-31 02:20:44 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-03-31 02:20:44 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-31 02:21:01 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XqjjzAzxst/ea_profile.json * 2025-03-31 02:21:04 (8792) [INFO] Backed up EA4 profile to /tmp/XqjjzAzxst/ea_profile.json * 2025-03-31 02:21:05 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-03-31 02:21:08 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-03-31 02:21:38 (681) [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. * 2025-03-31 02:21:38 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-01 01:54:25 (10705) [INFO] Self-update of script version 62 requested. * 2025-04-01 01:58:26 (10727) [INFO] Script is up to date. * 2025-04-01 02:02:30 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-01 02:02:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-01 02:02:30 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-01 02:02:30 (9645) [INFO] * 2025-04-01 02:02:43 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-01 02:02:43 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-01 02:02:43 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-04-01 02:02:43 (9645) [INFO] * 2025-04-01 02:02:55 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-01 02:02:59 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-04-01 02:02:59 (9645) [INFO] * 2025-04-01 02:02:59 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-01 02:02:59 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-04-01 02:03:29 (9658) [INFO] * EA4: 107.178.98.171 * 2025-04-01 02:03:29 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-01 02:03:29 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-01 02:03:29 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-01 02:04:15 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') * 2025-04-01 02:04:15 (9658) [INFO] Trying other mirror. * 2025-04-01 02:06:45 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-01 02:06:45 (9658) [INFO] Trying other mirror. * 2025-04-01 02:07:02 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-01 02:07:02 (9658) [INFO] Trying other mirror. * 2025-04-01 02:07:31 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-01 02:07:31 (9658) [INFO] Trying other mirror. * 2025-04-01 02:08:14 (9658) [INFO] Metadata Cache Created * 2025-04-01 02:08:14 (9675) [INFO] * 2025-04-01 02:08:14 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-01 02:08:14 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-01 02:08:14 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-04-01 02:08:14 (9645) [INFO] * 2025-04-01 02:08:15 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-01 02:08:15 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-01 02:08:15 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-01 02:08:15 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-01 02:08:15 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-01 02:08:15 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-01 02:08:15 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-01 02:08:15 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-01 02:08:15 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-01 02:08:15 (9658) [INFO] : wp-toolkit-thirdparties * 2025-04-01 02:08:16 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-04-01 02:08:16 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-01 02:08:16 (9675) [INFO] * 2025-04-01 02:08:16 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-04-01 02:08:16 (9645) [INFO] * 2025-04-01 02:08:17 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-01 02:08:17 (9658) [INFO] Determining fastest mirrors * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] One of the configured repositories failed (Unknown), * 2025-04-01 02:08:49 (9658) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-01 02:08:49 (9658) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-01 02:08:49 (9658) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-01 02:08:49 (9658) [INFO] distribution release than is supported by the repository (and the * 2025-04-01 02:08:49 (9658) [INFO] packages for the previous distribution release still work). * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-01 02:08:49 (9658) [INFO] yum --disablerepo= ... * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-01 02:08:49 (9658) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-01 02:08:49 (9658) [INFO] again or use --enablerepo for temporary usage: * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] yum-config-manager --disable * 2025-04-01 02:08:49 (9658) [INFO] or * 2025-04-01 02:08:49 (9658) [INFO] subscription-manager repos --disable= * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-01 02:08:49 (9658) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-01 02:08:49 (9658) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-01 02:08:49 (9658) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-01 02:08:49 (9658) [INFO] compromise: * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-01 02:08:49 (9658) [INFO] * 2025-04-01 02:08:49 (9658) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-01 02:08:49 (9675) [INFO] * 2025-04-01 02:08:49 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-01 02:08:49 (6033) [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 * 2025-04-01 02:08:50 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-01 02:08:50 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-01 02:08:50 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-01 02:08:50 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-01 02:08:50 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-01 02:08:57 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/44URNAOtgl/ea_profile.json * 2025-04-01 02:16:25 (8792) [INFO] Backed up EA4 profile to /tmp/44URNAOtgl/ea_profile.json * 2025-04-01 02:16:26 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-04-01 02:16:30 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-04-01 02:17:00 (681) [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. * 2025-04-01 02:17:00 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-02 01:55:27 (10705) [INFO] Self-update of script version 62 requested. * 2025-04-02 01:59:28 (10727) [INFO] Script is up to date. * 2025-04-02 02:03:31 (6456) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-02 02:03:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-02 02:03:32 (9644) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-02 02:03:32 (9645) [INFO] * 2025-04-02 02:03:46 (4136) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-02 02:03:46 (4143) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-02 02:03:46 (9644) [INFO] Running: /usr/bin/yum list extras * 2025-04-02 02:03:46 (9645) [INFO] * 2025-04-02 02:03:58 (256) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-02 02:04:01 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-04-02 02:04:01 (9645) [INFO] * 2025-04-02 02:04:02 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-02 02:04:02 (9658) [INFO] Loading mirror speeds from cached hostfile * 2025-04-02 02:04:32 (9658) [INFO] * EA4: 107.178.98.171 * 2025-04-02 02:04:32 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-02 02:04:32 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-02 02:04:32 (9658) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-02 02:07:18 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-02 02:07:18 (9658) [INFO] Trying other mirror. * 2025-04-02 02:07:35 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:07:35 (9658) [INFO] Trying other mirror. * 2025-04-02 02:07:52 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-02 02:07:52 (9658) [INFO] Trying other mirror. * 2025-04-02 02:08:05 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-02 02:08:05 (9658) [INFO] Trying other mirror. * 2025-04-02 02:08:22 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:08:22 (9658) [INFO] Trying other mirror. * 2025-04-02 02:08:36 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-02 02:08:36 (9658) [INFO] Trying other mirror. * 2025-04-02 02:08:53 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-04-02 02:08:53 (9658) [INFO] Trying other mirror. * 2025-04-02 02:09:06 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:09:06 (9658) [INFO] Trying other mirror. * 2025-04-02 02:09:49 (9658) [INFO] Metadata Cache Created * 2025-04-02 02:09:49 (9675) [INFO] * 2025-04-02 02:09:49 (6022) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-02 02:09:49 (6023) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-02 02:09:49 (9644) [INFO] Running: /usr/bin/yum clean all * 2025-04-02 02:09:49 (9645) [INFO] * 2025-04-02 02:09:49 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-02 02:09:50 (9658) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-02 02:09:50 (9658) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-02 02:09:50 (9658) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-02 02:09:50 (9658) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-02 02:09:50 (9658) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-02 02:09:50 (9658) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-02 02:09:50 (9658) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-02 02:09:50 (9658) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-02 02:09:50 (9658) [INFO] : wp-toolkit-thirdparties * 2025-04-02 02:09:50 (9658) [INFO] Cleaning up list of fastest mirrors * 2025-04-02 02:09:50 (9658) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-02 02:09:50 (9675) [INFO] * 2025-04-02 02:09:50 (9644) [INFO] Running: /usr/bin/yum makecache * 2025-04-02 02:09:50 (9645) [INFO] * 2025-04-02 02:09:51 (9658) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-02 02:09:51 (9658) [INFO] Determining fastest mirrors * 2025-04-02 02:10:22 (9658) [INFO] * EA4: 107.178.98.171 * 2025-04-02 02:10:22 (9658) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-02 02:10:22 (9658) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-02 02:10:22 (9658) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-02 02:13:25 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:13:25 (9658) [INFO] Trying other mirror. * 2025-04-02 02:13:25 (9658) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-04-02 02:13:25 (9658) [INFO] Trying other mirror. * 2025-04-02 02:16:04 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:16:04 (9658) [INFO] Trying other mirror. * 2025-04-02 02:18:53 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:18:53 (9658) [INFO] Trying other mirror. * 2025-04-02 02:19:23 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-02 02:19:23 (9658) [INFO] Trying other mirror. * 2025-04-02 02:20:24 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:20:24 (9658) [INFO] Trying other mirror. * 2025-04-02 02:20:24 (9658) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:20:24 (9658) [INFO] Trying other mirror. * 2025-04-02 02:20:55 (9658) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-02 02:20:55 (9658) [INFO] Trying other mirror. * 2025-04-02 02:22:18 (9658) [INFO] Metadata Cache Created * 2025-04-02 02:22:18 (9675) [INFO] * 2025-04-02 02:22:18 (6032) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-02 02:22:18 (6033) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-02 02:22:20 (3318) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-02 02:22:20 (256) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-02 02:22:20 (4384) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-02 02:22:20 (4390) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-02 02:22:20 (2052) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-02 02:22:34 (8769) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tMPWwfIqKY/ea_profile.json * 2025-04-02 02:22:37 (8792) [INFO] Backed up EA4 profile to /tmp/tMPWwfIqKY/ea_profile.json * 2025-04-02 02:22:38 (256) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-04-02 02:22:41 (645) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-04-02 02:23:11 (681) [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. * 2025-04-02 02:23:11 (471) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-03 01:46:08 (10705) [INFO] Self-update of script version 62 requested. * 2025-04-03 01:50:08 (10710) [INFO] Newer version of script found. Downloading. * 2025-04-03 01:54:10 (10719) [INFO] Script update to version 63 successful. * 2025-04-03 01:58:14 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-03 01:58:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-03 01:58:14 (9921) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-03 01:58:14 (9922) [INFO] * 2025-04-03 01:58:27 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-03 01:58:27 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-03 01:58:27 (9921) [INFO] Running: /usr/bin/yum list extras * 2025-04-03 01:58:27 (9922) [INFO] * 2025-04-03 01:58:49 (9921) [INFO] Running: /usr/bin/yum makecache * 2025-04-03 01:58:49 (9922) [INFO] * 2025-04-03 01:58:50 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-03 01:58:50 (9935) [INFO] Loading mirror speeds from cached hostfile * 2025-04-03 01:59:21 (9935) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-03 01:59:21 (9935) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-03 01:59:21 (9935) [INFO] * EA4: 107.178.98.171 * 2025-04-03 01:59:21 (9935) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-03 01:59:21 (9935) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-03 01:59:21 (9935) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-03 02:01:05 (9935) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:01:05 (9935) [INFO] Trying other mirror. * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-03 02:01:05 (9935) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-03 02:01:05 (9935) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-03 02:01:05 (9935) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-03 02:01:05 (9935) [INFO] distribution release than is supported by the repository (and the * 2025-04-03 02:01:05 (9935) [INFO] packages for the previous distribution release still work). * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-03 02:01:05 (9935) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-03 02:01:05 (9935) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-03 02:01:05 (9935) [INFO] again or use --enablerepo for temporary usage: * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-03 02:01:05 (9935) [INFO] or * 2025-04-03 02:01:05 (9935) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-03 02:01:05 (9935) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-03 02:01:05 (9935) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-03 02:01:05 (9935) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-03 02:01:05 (9935) [INFO] compromise: * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-03 02:01:05 (9935) [INFO] * 2025-04-03 02:01:05 (9935) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-03 02:01:05 (9935) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:01:05 (9952) [INFO] * 2025-04-03 02:01:05 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30536 milliseconds') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:01:05 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-03 02:01:05 (9921) [INFO] Running: /usr/bin/yum clean all * 2025-04-03 02:01:05 (9922) [INFO] * 2025-04-03 02:01:06 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-03 02:01:06 (9935) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-03 02:01:06 (9935) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-03 02:01:06 (9935) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-03 02:01:06 (9935) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-03 02:01:06 (9935) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-03 02:01:06 (9935) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-03 02:01:06 (9935) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-03 02:01:06 (9935) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-03 02:01:06 (9935) [INFO] : wp-toolkit-thirdparties * 2025-04-03 02:01:06 (9935) [INFO] Cleaning up list of fastest mirrors * 2025-04-03 02:01:06 (9935) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2025-04-03 02:01:06 (9952) [INFO] * 2025-04-03 02:01:06 (9921) [INFO] Running: /usr/bin/yum makecache * 2025-04-03 02:01:06 (9922) [INFO] * 2025-04-03 02:01:07 (9935) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-03 02:01:07 (9935) [INFO] Determining fastest mirrors * 2025-04-03 02:01:39 (9935) [INFO] * EA4: 107.178.98.171 * 2025-04-03 02:01:39 (9935) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-03 02:01:39 (9935) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-03 02:01:39 (9935) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-03 02:03:24 (9935) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:03:24 (9935) [INFO] Trying other mirror. * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-03 02:03:24 (9935) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-03 02:03:24 (9935) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-03 02:03:24 (9935) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-03 02:03:24 (9935) [INFO] distribution release than is supported by the repository (and the * 2025-04-03 02:03:24 (9935) [INFO] packages for the previous distribution release still work). * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-03 02:03:24 (9935) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-03 02:03:24 (9935) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-03 02:03:24 (9935) [INFO] again or use --enablerepo for temporary usage: * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-03 02:03:24 (9935) [INFO] or * 2025-04-03 02:03:24 (9935) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-03 02:03:24 (9935) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-03 02:03:24 (9935) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-03 02:03:24 (9935) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-03 02:03:24 (9935) [INFO] compromise: * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-03 02:03:24 (9935) [INFO] * 2025-04-03 02:03:24 (9935) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-03 02:03:24 (9935) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:03:24 (9952) [INFO] * 2025-04-03 02:03:24 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-03 02:03:24 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-03 02:03:25 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-03 02:03:25 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-03 02:03:25 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-03 02:03:25 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-03 02:03:25 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-03 02:03:32 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QyOH_rzkLx/ea_profile.json * 2025-04-03 02:05:48 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QyOH_rzkLx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-03 02:05:48 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-04 01:45:14 (10983) [INFO] Self-update of script version 63 requested. * 2025-04-04 01:49:15 (10988) [INFO] Newer version of script found. Downloading. * 2025-04-04 01:53:17 (10997) [INFO] Script update to version 64 successful. * 2025-04-04 01:57:19 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-04 01:57:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-04 01:57:20 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-04 01:57:20 (9926) [INFO] * 2025-04-04 01:57:32 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-04 01:57:32 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-04 01:57:32 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-04 01:57:32 (9926) [INFO] * 2025-04-04 01:57:53 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-04 01:57:53 (9926) [INFO] * 2025-04-04 01:57:54 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-04 01:57:54 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-04 01:58:25 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-04 01:58:25 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-04 01:58:25 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-04 01:58:25 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-04 01:59:12 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-04 01:59:12 (9939) [INFO] Trying other mirror. * 2025-04-04 02:00:40 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:00:40 (9939) [INFO] Trying other mirror. * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-04 02:00:40 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-04 02:00:40 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-04 02:00:40 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-04 02:00:40 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-04 02:00:40 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-04 02:00:40 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-04 02:00:40 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-04 02:00:40 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-04 02:00:40 (9939) [INFO] or * 2025-04-04 02:00:40 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-04 02:00:40 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-04 02:00:40 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-04 02:00:40 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-04 02:00:40 (9939) [INFO] compromise: * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-04 02:00:40 (9939) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-04 02:00:40 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:00:40 (9956) [INFO] * 2025-04-04 02:00:40 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:00:40 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-04 02:00:40 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-04 02:00:40 (9926) [INFO] * 2025-04-04 02:00:40 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-04 02:00:41 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-04 02:00:41 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-04 02:00:41 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-04 02:00:41 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-04 02:00:41 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-04 02:00:41 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-04 02:00:41 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-04 02:00:41 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-04 02:00:41 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-04 02:00:41 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-04 02:00:41 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-04 02:00:41 (9956) [INFO] * 2025-04-04 02:00:41 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-04 02:00:41 (9926) [INFO] * 2025-04-04 02:00:41 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-04 02:00:41 (9939) [INFO] Determining fastest mirrors * 2025-04-04 02:01:14 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-04 02:01:14 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-04 02:01:14 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-04 02:01:14 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-04 02:02:58 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:02:58 (9939) [INFO] Trying other mirror. * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-04 02:02:58 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-04 02:02:58 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-04 02:02:58 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-04 02:02:58 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-04 02:02:58 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-04 02:02:58 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-04 02:02:58 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-04 02:02:58 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-04 02:02:58 (9939) [INFO] or * 2025-04-04 02:02:58 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-04 02:02:58 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-04 02:02:58 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-04 02:02:58 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-04 02:02:58 (9939) [INFO] compromise: * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-04 02:02:58 (9939) [INFO] * 2025-04-04 02:02:58 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-04 02:02:58 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:02:58 (9956) [INFO] * 2025-04-04 02:02:58 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-04 02:02:58 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-04 02:03:00 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-04 02:03:00 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-04 02:03:00 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-04 02:03:00 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-04 02:03:00 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-04 02:03:07 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2RI4caHjNT/ea_profile.json * 2025-04-04 02:05:23 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2RI4caHjNT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-04 02:05:23 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-05 01:51:03 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-05 01:55:04 (11009) [INFO] Script is up to date. * 2025-04-05 01:59:07 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-05 01:59:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-05 01:59:07 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-05 01:59:07 (9926) [INFO] * 2025-04-05 01:59:20 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-05 01:59:20 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-05 01:59:20 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-05 01:59:20 (9926) [INFO] * 2025-04-05 01:59:41 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-05 01:59:41 (9926) [INFO] * 2025-04-05 01:59:41 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-05 01:59:42 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-05 02:00:12 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-05 02:00:12 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-05 02:00:12 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-05 02:00:12 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-05 02:00:58 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-05 02:00:58 (9939) [INFO] Trying other mirror. * 2025-04-05 02:02:26 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:02:26 (9939) [INFO] Trying other mirror. * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-05 02:02:26 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-05 02:02:26 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-05 02:02:26 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-05 02:02:26 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-05 02:02:26 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-05 02:02:26 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-05 02:02:26 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-05 02:02:26 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-05 02:02:26 (9939) [INFO] or * 2025-04-05 02:02:26 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-05 02:02:26 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-05 02:02:26 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-05 02:02:26 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-05 02:02:26 (9939) [INFO] compromise: * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-05 02:02:26 (9939) [INFO] * 2025-04-05 02:02:26 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-05 02:02:26 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:02:26 (9956) [INFO] * 2025-04-05 02:02:26 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:02:26 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-05 02:02:26 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-05 02:02:26 (9926) [INFO] * 2025-04-05 02:02:27 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-05 02:02:27 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-05 02:02:27 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-05 02:02:27 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-05 02:02:27 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-05 02:02:27 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-05 02:02:27 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-05 02:02:27 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-05 02:02:27 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-05 02:02:27 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-05 02:02:27 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-05 02:02:27 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-05 02:02:27 (9956) [INFO] * 2025-04-05 02:02:27 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-05 02:02:27 (9926) [INFO] * 2025-04-05 02:02:27 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-05 02:02:28 (9939) [INFO] Determining fastest mirrors * 2025-04-05 02:02:59 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-05 02:02:59 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-05 02:02:59 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-05 02:02:59 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-05 02:03:46 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-05 02:03:46 (9939) [INFO] Trying other mirror. * 2025-04-05 02:04:16 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-05 02:04:16 (9939) [INFO] Trying other mirror. * 2025-04-05 02:04:47 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-05 02:04:47 (9939) [INFO] Trying other mirror. * 2025-04-05 02:05:18 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-05 02:05:18 (9939) [INFO] Trying other mirror. * 2025-04-05 02:05:49 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-05 02:05:49 (9939) [INFO] Trying other mirror. * 2025-04-05 02:07:17 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:07:17 (9939) [INFO] Trying other mirror. * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-05 02:07:17 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-05 02:07:17 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-05 02:07:17 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-05 02:07:17 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-05 02:07:17 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-05 02:07:17 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-05 02:07:17 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-05 02:07:17 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-05 02:07:17 (9939) [INFO] or * 2025-04-05 02:07:17 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-05 02:07:17 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-05 02:07:17 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-05 02:07:17 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-05 02:07:17 (9939) [INFO] compromise: * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-05 02:07:17 (9939) [INFO] * 2025-04-05 02:07:17 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-05 02:07:17 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:07:17 (9956) [INFO] * 2025-04-05 02:07:17 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-05 02:07:17 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-05 02:07:19 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-05 02:07:19 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-05 02:07:19 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-05 02:07:19 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-05 02:07:19 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-05 02:12:14 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/seDPwfczBu/ea_profile.json * 2025-04-05 02:12:31 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/seDPwfczBu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-05 02:12:31 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-06 01:46:00 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-06 01:50:00 (11009) [INFO] Script is up to date. * 2025-04-06 01:54:04 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-06 01:54:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-06 01:54:04 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-06 01:54:04 (9926) [INFO] * 2025-04-06 01:54:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-06 01:54:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-06 01:54:18 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-06 01:54:18 (9926) [INFO] * 2025-04-06 01:56:06 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-06 01:56:06 (9926) [INFO] * 2025-04-06 01:56:07 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-06 01:56:07 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-06 01:56:38 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-06 01:56:38 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-06 01:56:38 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-06 01:56:38 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-06 01:57:24 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-06 01:57:24 (9939) [INFO] Trying other mirror. * 2025-04-06 01:58:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 01:58:52 (9939) [INFO] Trying other mirror. * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-06 01:58:52 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-06 01:58:52 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-06 01:58:52 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-06 01:58:52 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-06 01:58:52 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-06 01:58:52 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-06 01:58:52 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-06 01:58:52 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-06 01:58:52 (9939) [INFO] or * 2025-04-06 01:58:52 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-06 01:58:52 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-06 01:58:52 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-06 01:58:52 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-06 01:58:52 (9939) [INFO] compromise: * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-06 01:58:52 (9939) [INFO] * 2025-04-06 01:58:52 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-06 01:58:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 01:58:52 (9956) [INFO] * 2025-04-06 01:58:52 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 01:58:52 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-06 01:58:52 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-06 01:58:52 (9926) [INFO] * 2025-04-06 01:58:53 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-06 01:58:53 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-06 01:58:53 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-06 01:58:53 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-06 01:58:53 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-06 01:58:53 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-06 01:58:53 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-06 01:58:53 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-06 01:58:53 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-06 01:58:53 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-06 01:58:53 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-06 01:58:53 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-06 01:58:53 (9956) [INFO] * 2025-04-06 01:58:53 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-06 01:58:53 (9926) [INFO] * 2025-04-06 01:58:54 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-06 01:58:54 (9939) [INFO] Determining fastest mirrors * 2025-04-06 01:59:25 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-06 01:59:25 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-06 01:59:25 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-06 01:59:25 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-06 02:01:09 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 02:01:09 (9939) [INFO] Trying other mirror. * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-06 02:01:09 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-06 02:01:09 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-06 02:01:09 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-06 02:01:09 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-06 02:01:09 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-06 02:01:09 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-06 02:01:09 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-06 02:01:09 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-06 02:01:09 (9939) [INFO] or * 2025-04-06 02:01:09 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-06 02:01:09 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-06 02:01:09 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-06 02:01:09 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-06 02:01:09 (9939) [INFO] compromise: * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-06 02:01:09 (9939) [INFO] * 2025-04-06 02:01:09 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-06 02:01:09 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 02:01:09 (9956) [INFO] * 2025-04-06 02:01:09 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-06 02:01:09 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-06 02:01:11 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-06 02:01:11 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-06 02:01:11 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-06 02:01:11 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-06 02:01:11 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-06 02:07:06 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oXAaRMDkpI/ea_profile.json * 2025-04-06 02:09:53 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oXAaRMDkpI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-06 02:09:53 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-07 01:45:30 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-07 01:49:31 (11009) [INFO] Script is up to date. * 2025-04-07 01:53:34 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-07 01:53:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-07 01:53:34 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-07 01:53:34 (9926) [INFO] * 2025-04-07 01:53:46 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-07 01:53:46 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-07 01:53:46 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-07 01:53:46 (9926) [INFO] * 2025-04-07 01:54:07 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-07 01:54:07 (9926) [INFO] * 2025-04-07 01:54:08 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-07 01:54:08 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-07 01:54:38 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-07 01:54:38 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-07 01:54:38 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-07 01:54:38 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-07 01:56:22 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:56:22 (9939) [INFO] Trying other mirror. * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-07 01:56:22 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-07 01:56:22 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-07 01:56:22 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-07 01:56:22 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-07 01:56:22 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-07 01:56:22 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-07 01:56:22 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-07 01:56:22 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-07 01:56:22 (9939) [INFO] or * 2025-04-07 01:56:22 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-07 01:56:22 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-07 01:56:22 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-07 01:56:22 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-07 01:56:22 (9939) [INFO] compromise: * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-07 01:56:22 (9939) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-07 01:56:22 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:56:22 (9956) [INFO] * 2025-04-07 01:56:22 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:56:22 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-07 01:56:22 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-07 01:56:22 (9926) [INFO] * 2025-04-07 01:56:22 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-07 01:56:22 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-07 01:56:22 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-07 01:56:22 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-07 01:56:22 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-07 01:56:22 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-07 01:56:22 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-07 01:56:22 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-07 01:56:22 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-07 01:56:22 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-07 01:56:22 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-07 01:56:22 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-07 01:56:22 (9956) [INFO] * 2025-04-07 01:56:22 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-07 01:56:22 (9926) [INFO] * 2025-04-07 01:56:23 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-07 01:56:23 (9939) [INFO] Determining fastest mirrors * 2025-04-07 01:56:55 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-07 01:56:55 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-07 01:56:55 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-07 01:56:55 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-07 01:58:39 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:58:39 (9939) [INFO] Trying other mirror. * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-07 01:58:39 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-07 01:58:39 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-07 01:58:39 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-07 01:58:39 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-07 01:58:39 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-07 01:58:39 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-07 01:58:39 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-07 01:58:39 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-07 01:58:39 (9939) [INFO] or * 2025-04-07 01:58:39 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-07 01:58:39 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-07 01:58:39 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-07 01:58:39 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-07 01:58:39 (9939) [INFO] compromise: * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-07 01:58:39 (9939) [INFO] * 2025-04-07 01:58:39 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-07 01:58:39 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:58:39 (9956) [INFO] * 2025-04-07 01:58:39 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-07 01:58:39 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-07 01:58:41 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-07 01:58:41 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-07 01:58:41 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-07 01:58:41 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-07 01:58:41 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-07 01:58:47 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Bl40pESCHZ/ea_profile.json * 2025-04-07 02:01:33 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Bl40pESCHZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-07 02:01:33 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-08 01:47:50 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-08 01:51:50 (11009) [INFO] Script is up to date. * 2025-04-08 01:55:52 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-08 01:55:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-08 01:55:53 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-08 01:55:53 (9926) [INFO] * 2025-04-08 01:56:06 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-08 01:56:06 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-08 01:56:06 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-08 01:56:06 (9926) [INFO] * 2025-04-08 01:56:28 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-08 01:56:28 (9926) [INFO] * 2025-04-08 01:56:29 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-08 01:56:29 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-08 01:56:59 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-08 01:56:59 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-08 01:56:59 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-08 01:56:59 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-08 01:58:43 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 01:58:43 (9939) [INFO] Trying other mirror. * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-08 01:58:43 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-08 01:58:43 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-08 01:58:43 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-08 01:58:43 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-08 01:58:43 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-08 01:58:43 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-08 01:58:43 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-08 01:58:43 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-08 01:58:43 (9939) [INFO] or * 2025-04-08 01:58:43 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-08 01:58:43 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-08 01:58:43 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-08 01:58:43 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-08 01:58:43 (9939) [INFO] compromise: * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-08 01:58:43 (9939) [INFO] * 2025-04-08 01:58:43 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-08 01:58:43 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 01:58:43 (9956) [INFO] * 2025-04-08 01:58:43 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 01:58:43 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-08 01:58:43 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-08 01:58:43 (9926) [INFO] * 2025-04-08 01:58:44 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-08 01:58:44 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-08 01:58:44 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-08 01:58:44 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-08 01:58:44 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-08 01:58:44 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-08 01:58:44 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-08 01:58:44 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-08 01:58:44 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-08 01:58:44 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-08 01:58:44 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-08 01:58:44 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-08 01:58:44 (9956) [INFO] * 2025-04-08 01:58:44 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-08 01:58:44 (9926) [INFO] * 2025-04-08 01:58:45 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-08 01:58:45 (9939) [INFO] Determining fastest mirrors * 2025-04-08 01:59:16 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-08 01:59:16 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-08 01:59:16 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-08 01:59:16 (9939) [INFO] * epel: dl.fedoraproject.org * 2025-04-08 02:00:02 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30037 milliseconds with 0 out of 0 bytes received') * 2025-04-08 02:00:02 (9939) [INFO] Trying other mirror. * 2025-04-08 02:00:33 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-08 02:00:33 (9939) [INFO] Trying other mirror. * 2025-04-08 02:02:01 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 02:02:01 (9939) [INFO] Trying other mirror. * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-08 02:02:01 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-08 02:02:01 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-08 02:02:01 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-08 02:02:01 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-08 02:02:01 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-08 02:02:01 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-08 02:02:01 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-08 02:02:01 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-08 02:02:01 (9939) [INFO] or * 2025-04-08 02:02:01 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-08 02:02:01 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-08 02:02:01 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-08 02:02:01 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-08 02:02:01 (9939) [INFO] compromise: * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-08 02:02:01 (9939) [INFO] * 2025-04-08 02:02:01 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-08 02:02:01 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 02:02:01 (9956) [INFO] * 2025-04-08 02:02:01 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-08 02:02:01 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30037 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-08 02:02:03 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-08 02:02:03 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-08 02:02:03 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-08 02:02:03 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-08 02:02:03 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-08 02:02:10 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SOHun5cftL/ea_profile.json * 2025-04-08 02:04:56 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SOHun5cftL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-08 02:04:56 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-09 01:52:47 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-09 01:56:47 (11009) [INFO] Script is up to date. * 2025-04-09 02:00:51 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-09 02:00:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-09 02:00:51 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-09 02:00:51 (9926) [INFO] * 2025-04-09 02:01:04 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-09 02:01:04 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-09 02:01:04 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-09 02:01:04 (9926) [INFO] * 2025-04-09 02:01:26 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-09 02:01:26 (9926) [INFO] * 2025-04-09 02:01:26 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-09 02:01:27 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-09 02:01:57 (9939) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-09 02:01:57 (9939) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30599 milliseconds') * 2025-04-09 02:01:57 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-09 02:01:57 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-09 02:01:57 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-09 02:01:57 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-09 02:02:44 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-09 02:02:44 (9939) [INFO] Trying other mirror. * 2025-04-09 02:03:15 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-09 02:03:15 (9939) [INFO] Trying other mirror. * 2025-04-09 02:04:43 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-09 02:04:43 (9939) [INFO] Trying other mirror. * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-09 02:04:43 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-09 02:04:43 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-09 02:04:43 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-09 02:04:43 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-09 02:04:43 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-09 02:04:43 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-09 02:04:43 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-09 02:04:43 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-09 02:04:43 (9939) [INFO] or * 2025-04-09 02:04:43 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-09 02:04:43 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-09 02:04:43 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-09 02:04:43 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-09 02:04:43 (9939) [INFO] compromise: * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-09 02:04:43 (9939) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-09 02:04:43 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-09 02:04:43 (9956) [INFO] * 2025-04-09 02:04:43 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30599 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-09 02:04:43 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-09 02:04:43 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-09 02:04:43 (9926) [INFO] * 2025-04-09 02:04:43 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-09 02:04:44 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-09 02:04:44 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-09 02:04:44 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-09 02:04:44 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-09 02:04:44 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-09 02:04:44 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-09 02:04:44 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-09 02:04:44 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-09 02:04:44 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-09 02:04:44 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-09 02:04:44 (9939) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2025-04-09 02:04:44 (9956) [INFO] * 2025-04-09 02:04:44 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-09 02:04:44 (9926) [INFO] * 2025-04-09 02:04:44 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-09 02:04:45 (9939) [INFO] Determining fastest mirrors * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] One of the configured repositories failed (Unknown), * 2025-04-09 02:05:16 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-09 02:05:16 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-09 02:05:16 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-09 02:05:16 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-09 02:05:16 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-09 02:05:16 (9939) [INFO] yum --disablerepo= ... * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-09 02:05:16 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-09 02:05:16 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] yum-config-manager --disable * 2025-04-09 02:05:16 (9939) [INFO] or * 2025-04-09 02:05:16 (9939) [INFO] subscription-manager repos --disable= * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-09 02:05:16 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-09 02:05:16 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-09 02:05:16 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-09 02:05:16 (9939) [INFO] compromise: * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-09 02:05:16 (9939) [INFO] * 2025-04-09 02:05:16 (9939) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-09 02:05:16 (9956) [INFO] * 2025-04-09 02:05:16 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-09 02:05:16 (6278) [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 * 2025-04-09 02:05:18 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-09 02:05:18 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-09 02:05:18 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-09 02:05:18 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-09 02:05:18 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-09 02:05:25 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/znG2xczI9d/ea_profile.json * 2025-04-09 02:08:13 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/znG2xczI9d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-09 02:08:13 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-10 01:51:00 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-10 01:55:00 (11009) [INFO] Script is up to date. * 2025-04-10 01:59:03 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-10 01:59:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-10 01:59:03 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-10 01:59:03 (9926) [INFO] * 2025-04-10 01:59:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-10 01:59:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-10 01:59:18 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-10 01:59:18 (9926) [INFO] * 2025-04-10 01:59:41 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-10 01:59:41 (9926) [INFO] * 2025-04-10 01:59:41 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-10 01:59:42 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-10 02:00:12 (9939) [INFO] * EA4: 107.178.98.171 * 2025-04-10 02:00:12 (9939) [INFO] * cpanel-addons-production-feed: 107.178.98.171 * 2025-04-10 02:00:12 (9939) [INFO] * cpanel-plugins: 107.178.98.171 * 2025-04-10 02:00:12 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-10 02:01:56 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-10 02:01:56 (9939) [INFO] Trying other mirror. * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-10 02:01:56 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-10 02:01:56 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-10 02:01:56 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-10 02:01:56 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-10 02:01:56 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-10 02:01:56 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-10 02:01:56 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-10 02:01:56 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-10 02:01:56 (9939) [INFO] or * 2025-04-10 02:01:56 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-10 02:01:56 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-10 02:01:56 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-10 02:01:56 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-10 02:01:56 (9939) [INFO] compromise: * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-10 02:01:56 (9939) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-10 02:01:56 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-10 02:01:56 (9956) [INFO] * 2025-04-10 02:01:56 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-10 02:01:56 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-10 02:01:56 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-10 02:01:56 (9926) [INFO] * 2025-04-10 02:01:56 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-10 02:01:57 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-10 02:01:57 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-10 02:01:57 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-10 02:01:57 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-10 02:01:57 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-10 02:01:57 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-10 02:01:57 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-10 02:01:57 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-10 02:01:57 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-10 02:01:57 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-10 02:01:57 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-10 02:01:57 (9956) [INFO] * 2025-04-10 02:01:57 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-10 02:01:57 (9926) [INFO] * 2025-04-10 02:01:57 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-10 02:01:58 (9939) [INFO] Determining fastest mirrors * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] One of the configured repositories failed (Unknown), * 2025-04-10 02:02:29 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-10 02:02:29 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-10 02:02:29 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-10 02:02:29 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-10 02:02:29 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-10 02:02:29 (9939) [INFO] yum --disablerepo= ... * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-10 02:02:29 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-10 02:02:29 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] yum-config-manager --disable * 2025-04-10 02:02:29 (9939) [INFO] or * 2025-04-10 02:02:29 (9939) [INFO] subscription-manager repos --disable= * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-10 02:02:29 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-10 02:02:29 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-10 02:02:29 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-10 02:02:29 (9939) [INFO] compromise: * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-10 02:02:29 (9939) [INFO] * 2025-04-10 02:02:29 (9939) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-10 02:02:29 (9956) [INFO] * 2025-04-10 02:02:29 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-10 02:02:29 (6278) [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 * 2025-04-10 02:02:31 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-10 02:02:31 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-10 02:02:31 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-10 02:02:31 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-10 02:02:31 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-10 02:02:37 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8q6MxtmX7F/ea_profile.json * 2025-04-10 02:04:12 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8q6MxtmX7F/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-10 02:04:12 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-11 01:44:37 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-11 01:48:37 (11009) [INFO] Script is up to date. * 2025-04-11 01:52:40 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-11 01:52:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-11 01:52:41 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-11 01:52:41 (9926) [INFO] * 2025-04-11 01:52:54 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-11 01:52:54 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-11 01:52:54 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-11 01:52:54 (9926) [INFO] * 2025-04-11 01:53:16 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-11 01:53:16 (9926) [INFO] * 2025-04-11 01:53:16 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-11 01:53:17 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-11 01:53:48 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-11 01:53:48 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-11 01:53:48 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-11 01:53:48 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-11 01:55:31 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-11 01:55:31 (9939) [INFO] Trying other mirror. * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-11 01:55:31 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-11 01:55:31 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-11 01:55:31 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-11 01:55:31 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-11 01:55:31 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-11 01:55:31 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-11 01:55:31 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-11 01:55:31 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-11 01:55:31 (9939) [INFO] or * 2025-04-11 01:55:31 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-11 01:55:31 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-11 01:55:31 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-11 01:55:31 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-11 01:55:31 (9939) [INFO] compromise: * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-11 01:55:31 (9939) [INFO] * 2025-04-11 01:55:31 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-11 01:55:31 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-11 01:55:31 (9956) [INFO] * 2025-04-11 01:55:31 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-11 01:55:31 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-11 01:55:31 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-11 01:55:31 (9926) [INFO] * 2025-04-11 01:55:32 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-11 01:55:32 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-11 01:55:32 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-11 01:55:32 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-11 01:55:32 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-11 01:55:32 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-11 01:55:32 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-11 01:55:32 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-11 01:55:32 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-11 01:55:32 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-11 01:55:32 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-11 01:55:32 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-11 01:55:32 (9956) [INFO] * 2025-04-11 01:55:32 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-11 01:55:32 (9926) [INFO] * 2025-04-11 01:55:33 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-11 01:55:33 (9939) [INFO] Determining fastest mirrors * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] One of the configured repositories failed (Unknown), * 2025-04-11 01:56:04 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-11 01:56:04 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-11 01:56:04 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-11 01:56:04 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-11 01:56:04 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-11 01:56:04 (9939) [INFO] yum --disablerepo= ... * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-11 01:56:04 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-11 01:56:04 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] yum-config-manager --disable * 2025-04-11 01:56:04 (9939) [INFO] or * 2025-04-11 01:56:04 (9939) [INFO] subscription-manager repos --disable= * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-11 01:56:04 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-11 01:56:04 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-11 01:56:04 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-11 01:56:04 (9939) [INFO] compromise: * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-11 01:56:04 (9939) [INFO] * 2025-04-11 01:56:04 (9939) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-11 01:56:04 (9956) [INFO] * 2025-04-11 01:56:04 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-11 01:56:04 (6278) [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 * 2025-04-11 01:56:05 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-11 01:56:05 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-11 01:56:05 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-11 01:56:05 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-11 01:56:05 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-11 01:56:11 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xp9Uia1KUo/ea_profile.json * 2025-04-11 01:58:47 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xp9Uia1KUo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-11 01:58:47 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-12 01:51:44 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-12 01:55:44 (11009) [INFO] Script is up to date. * 2025-04-12 01:59:48 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-12 01:59:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-12 01:59:48 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-12 01:59:48 (9926) [INFO] * 2025-04-12 01:59:52 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-12 01:59:52 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-12 01:59:52 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-12 01:59:52 (9926) [INFO] * 2025-04-12 02:00:15 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-12 02:00:15 (9926) [INFO] * 2025-04-12 02:00:15 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-12 02:00:15 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-12 02:00:47 (9939) [INFO] * EA4: 208.74.123.62 * 2025-04-12 02:00:47 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-04-12 02:00:47 (9939) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-04-12 02:00:47 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-12 02:02:33 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:02:33 (9939) [INFO] Trying other mirror. * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-12 02:02:33 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-12 02:02:33 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-12 02:02:33 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-12 02:02:33 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-12 02:02:33 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-12 02:02:33 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-12 02:02:33 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-12 02:02:33 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-12 02:02:33 (9939) [INFO] or * 2025-04-12 02:02:33 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-12 02:02:33 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-12 02:02:33 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-12 02:02:33 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-12 02:02:33 (9939) [INFO] compromise: * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-12 02:02:33 (9939) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-12 02:02:33 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:02:33 (9956) [INFO] * 2025-04-12 02:02:33 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:02:33 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-12 02:02:33 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-12 02:02:33 (9926) [INFO] * 2025-04-12 02:02:33 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-12 02:02:34 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-12 02:02:34 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-12 02:02:34 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-12 02:02:34 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-12 02:02:34 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-12 02:02:34 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-12 02:02:34 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-12 02:02:34 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-12 02:02:34 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-12 02:02:34 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-12 02:02:34 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-12 02:02:34 (9956) [INFO] * 2025-04-12 02:02:34 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-12 02:02:34 (9926) [INFO] * 2025-04-12 02:02:34 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-12 02:02:34 (9939) [INFO] Determining fastest mirrors * 2025-04-12 02:03:06 (9939) [INFO] * EA4: 184.94.196.92 * 2025-04-12 02:03:06 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-04-12 02:03:06 (9939) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-04-12 02:03:06 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-12 02:03:53 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-12 02:03:53 (9939) [INFO] Trying other mirror. * 2025-04-12 02:04:24 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30846 milliseconds') * 2025-04-12 02:04:24 (9939) [INFO] Trying other mirror. * 2025-04-12 02:05:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:05:52 (9939) [INFO] Trying other mirror. * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-12 02:05:52 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-12 02:05:52 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-12 02:05:52 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-12 02:05:52 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-12 02:05:52 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-12 02:05:52 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-12 02:05:52 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-12 02:05:52 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-12 02:05:52 (9939) [INFO] or * 2025-04-12 02:05:52 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-12 02:05:52 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-12 02:05:52 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-12 02:05:52 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-12 02:05:52 (9939) [INFO] compromise: * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-12 02:05:52 (9939) [INFO] * 2025-04-12 02:05:52 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-12 02:05:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:05:52 (9956) [INFO] * 2025-04-12 02:05:52 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-12 02:05:52 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30846 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-12 02:05:54 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-12 02:05:54 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-12 02:05:54 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-12 02:05:54 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-12 02:05:54 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-12 02:06:02 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ojVLMuKmCk/ea_profile.json * 2025-04-12 02:09:34 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ojVLMuKmCk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-12 02:09:34 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-13 01:46:46 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-13 01:50:47 (11009) [INFO] Script is up to date. * 2025-04-13 01:54:49 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-13 01:54:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-13 01:54:50 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-13 01:54:50 (9926) [INFO] * 2025-04-13 01:54:53 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-13 01:54:53 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-13 01:54:53 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-13 01:54:53 (9926) [INFO] * 2025-04-13 01:55:16 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-13 01:55:16 (9926) [INFO] * 2025-04-13 01:55:16 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-13 01:55:17 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-13 01:55:47 (9939) [INFO] * EA4: 184.94.196.92 * 2025-04-13 01:55:47 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-04-13 01:55:47 (9939) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-04-13 01:55:47 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-13 01:56:34 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-13 01:56:34 (9939) [INFO] Trying other mirror. * 2025-04-13 01:58:02 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 01:58:02 (9939) [INFO] Trying other mirror. * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-13 01:58:02 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-13 01:58:02 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-13 01:58:02 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-13 01:58:02 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-13 01:58:02 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-13 01:58:02 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-13 01:58:02 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-13 01:58:02 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-13 01:58:02 (9939) [INFO] or * 2025-04-13 01:58:02 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-13 01:58:02 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-13 01:58:02 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-13 01:58:02 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-13 01:58:02 (9939) [INFO] compromise: * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-13 01:58:02 (9939) [INFO] * 2025-04-13 01:58:02 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-13 01:58:02 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 01:58:02 (9956) [INFO] * 2025-04-13 01:58:02 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 01:58:02 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-13 01:58:02 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-13 01:58:02 (9926) [INFO] * 2025-04-13 01:58:03 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-13 01:58:03 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-13 01:58:03 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-13 01:58:03 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-13 01:58:03 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-13 01:58:03 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-13 01:58:03 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-13 01:58:03 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-13 01:58:03 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-13 01:58:03 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-13 01:58:03 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-13 01:58:03 (9939) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-13 01:58:03 (9956) [INFO] * 2025-04-13 01:58:03 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-13 01:58:03 (9926) [INFO] * 2025-04-13 01:58:03 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-13 01:58:04 (9939) [INFO] Determining fastest mirrors * 2025-04-13 01:58:37 (9939) [INFO] * EA4: 184.94.196.92 * 2025-04-13 01:58:37 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-04-13 01:58:37 (9939) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-04-13 01:58:37 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-13 01:59:24 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-13 01:59:24 (9939) [INFO] Trying other mirror. * 2025-04-13 02:00:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 02:00:52 (9939) [INFO] Trying other mirror. * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-13 02:00:52 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-13 02:00:52 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-13 02:00:52 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-13 02:00:52 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-13 02:00:52 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-13 02:00:52 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-13 02:00:52 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-13 02:00:52 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-13 02:00:52 (9939) [INFO] or * 2025-04-13 02:00:52 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-13 02:00:52 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-13 02:00:52 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-13 02:00:52 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-13 02:00:52 (9939) [INFO] compromise: * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-13 02:00:52 (9939) [INFO] * 2025-04-13 02:00:52 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-13 02:00:52 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 02:00:52 (9956) [INFO] * 2025-04-13 02:00:52 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-13 02:00:52 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-13 02:00:54 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-13 02:00:54 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-13 02:00:54 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-13 02:00:54 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-13 02:00:54 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-13 02:01:02 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4SVQ3NcmDe/ea_profile.json * 2025-04-13 02:04:28 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4SVQ3NcmDe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9043. * 2025-04-13 02:04:28 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-14 01:52:33 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-14 01:56:33 (11009) [INFO] Script is up to date. * 2025-04-14 02:00:36 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-14 02:00:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-14 02:00:37 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-14 02:00:37 (9926) [INFO] * 2025-04-14 02:00:41 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-14 02:00:41 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-14 02:00:41 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-14 02:00:41 (9926) [INFO] * 2025-04-14 02:01:04 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-14 02:01:04 (9926) [INFO] * 2025-04-14 02:01:04 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-14 02:01:04 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-14 02:01:35 (9939) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-14 02:01:35 (9939) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2025-04-14 02:01:35 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-14 02:01:35 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-14 02:01:35 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-14 02:01:35 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-14 02:02:22 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-14 02:02:22 (9939) [INFO] Trying other mirror. * 2025-04-14 02:03:50 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:03:50 (9939) [INFO] Trying other mirror. * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-14 02:03:50 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-14 02:03:50 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-14 02:03:50 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-14 02:03:50 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-14 02:03:50 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-14 02:03:50 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-14 02:03:50 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-14 02:03:50 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-14 02:03:50 (9939) [INFO] or * 2025-04-14 02:03:50 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-14 02:03:50 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-14 02:03:50 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-14 02:03:50 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-14 02:03:50 (9939) [INFO] compromise: * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-14 02:03:50 (9939) [INFO] * 2025-04-14 02:03:50 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-14 02:03:50 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:03:50 (9956) [INFO] * 2025-04-14 02:03:50 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:03:50 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-14 02:03:50 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-14 02:03:50 (9926) [INFO] * 2025-04-14 02:03:51 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-14 02:03:51 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-14 02:03:51 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-14 02:03:51 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-14 02:03:51 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-14 02:03:51 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-14 02:03:51 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-14 02:03:51 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-14 02:03:51 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-14 02:03:51 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-14 02:03:51 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-14 02:03:51 (9939) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2025-04-14 02:03:51 (9956) [INFO] * 2025-04-14 02:03:51 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-14 02:03:51 (9926) [INFO] * 2025-04-14 02:03:52 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-14 02:03:52 (9939) [INFO] Determining fastest mirrors * 2025-04-14 02:04:23 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-14 02:04:23 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-14 02:04:23 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-14 02:04:23 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-14 02:06:09 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:06:09 (9939) [INFO] Trying other mirror. * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-14 02:06:09 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-14 02:06:09 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-14 02:06:09 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-14 02:06:09 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-14 02:06:09 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-14 02:06:09 (9939) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-14 02:06:09 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-14 02:06:09 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-14 02:06:09 (9939) [INFO] or * 2025-04-14 02:06:09 (9939) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-14 02:06:09 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-14 02:06:09 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-14 02:06:09 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-14 02:06:09 (9939) [INFO] compromise: * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-14 02:06:09 (9939) [INFO] * 2025-04-14 02:06:09 (9939) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-14 02:06:09 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:06:09 (9956) [INFO] * 2025-04-14 02:06:09 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-14 02:06:09 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQzMzQyOTk3OjE3NDM2MDIxOTc6AT4w85qeI2QcO4Mb33QZsVD4hKRwQW2QArAj2qfL4dIVEBiD-K3ynsGIUGg9LXHt3zBzu-0Kv27kbCsLWPsQRj728FBjZ-ZQw2dBV7-W4CmX4A8BGfFtEa1GwXZkkTwYz1TOi-uSiX-UiVwJ584erniFTWOKsDYagWAKIttJNILxDy574gemoPPaDlhhtzarLZ8LORovuy5uoC6o05AhcJF3VIBQd7EkBegOJ-RDwhilBQ8ZX-lva468fGlIsPSxTG7mYPaoqz73i2N8crrY4if4dmLW40bwNaAy1zpwcPUdlmWjJfeJoTjAN5ZtRrex3sVuXONfCgJGwvpmLnXNa-WU8ehCjc3ZzrWWeubJsEOzLChD0dXUmfXrCWkpx_p-9QhU_lrIeYJoN55Xru48_P7Nrij4J4c5A4VVtXaHuiiV5eLgyzkbZmUNMN87Y5NvOr5Hk5hlVQC1DxzIaZdG9fa_nGT-imhcyqlrs6BdptUKfU-wTKhc_GHcqw0sqXkWHQeyfOmi8WYBqSHvSD4Yw5hzo8L5iln4zm-PLaDSH9-KdSfF48aKzw8Wd0J4y4KNTOdRDl-qdlZyfnRvVyAAe4lRGUX5A4FiHzjSy2mD5zZOjogqkDL1B6BGczDRZ0220mHXg4MeXaIotk_8l0uPLllaXCEAtv6n-s93UQ9zSvc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-14 02:06:10 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-14 02:06:10 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-14 02:06:10 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-14 02:06:10 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-14 02:06:10 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-14 02:06:18 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iDDz3PBykD/ea_profile.json * 2025-04-14 02:13:43 (9064) [INFO] Backed up EA4 profile to /tmp/iDDz3PBykD/ea_profile.json * 2025-04-14 02:13:44 (259) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-04-14 02:13:48 (650) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-04-14 02:14:18 (686) [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. * 2025-04-14 02:14:18 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-15 02:05:10 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-15 02:09:10 (11009) [INFO] Script is up to date. * 2025-04-15 02:13:14 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-15 02:13:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-15 02:13:14 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-15 02:13:14 (9926) [INFO] * 2025-04-15 02:13:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-15 02:13:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-15 02:13:18 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-15 02:13:18 (9926) [INFO] * 2025-04-15 02:13:29 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-15 02:13:31 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-15 02:13:31 (9926) [INFO] * 2025-04-15 02:13:32 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-15 02:13:32 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-15 02:14:02 (9939) [INFO] * EA4: 184.94.196.94 * 2025-04-15 02:14:02 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 2025-04-15 02:14:02 (9939) [INFO] * cpanel-plugins: 184.94.196.94 * 2025-04-15 02:14:02 (9939) [INFO] * epel: mirror.math.princeton.edu * 2025-04-15 02:16:48 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:16:48 (9939) [INFO] Trying other mirror. * 2025-04-15 02:17:05 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:17:05 (9939) [INFO] Trying other mirror. * 2025-04-15 02:17:48 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-15 02:17:48 (9939) [INFO] Trying other mirror. * 2025-04-15 02:18:18 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:18:18 (9939) [INFO] Trying other mirror. * 2025-04-15 02:18:49 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-15 02:18:49 (9939) [INFO] Trying other mirror. * 2025-04-15 02:19:20 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-15 02:19:20 (9939) [INFO] Trying other mirror. * 2025-04-15 02:20:02 (9939) [INFO] Metadata Cache Created * 2025-04-15 02:20:02 (9956) [INFO] * 2025-04-15 02:20:02 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-04-15 02:20:02 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-15 02:20:02 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-15 02:20:02 (9926) [INFO] * 2025-04-15 02:20:03 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-15 02:20:03 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-15 02:20:03 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-15 02:20:03 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-15 02:20:03 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-15 02:20:03 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-15 02:20:03 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-15 02:20:03 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-15 02:20:03 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-15 02:20:03 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-15 02:20:03 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-15 02:20:03 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-15 02:20:03 (9956) [INFO] * 2025-04-15 02:20:03 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-15 02:20:03 (9926) [INFO] * 2025-04-15 02:20:04 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-15 02:20:04 (9939) [INFO] Determining fastest mirrors * 2025-04-15 02:20:37 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-15 02:20:37 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-15 02:20:37 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-15 02:20:37 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-15 02:23:42 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-04-15 02:23:42 (9939) [INFO] Trying other mirror. * 2025-04-15 02:23:42 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:23:42 (9939) [INFO] Trying other mirror. * 2025-04-15 02:24:13 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-04-15 02:24:13 (9939) [INFO] Trying other mirror. * 2025-04-15 02:26:22 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:26:22 (9939) [INFO] Trying other mirror. * 2025-04-15 02:29:11 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:29:11 (9939) [INFO] Trying other mirror. * 2025-04-15 02:29:12 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-15 02:29:12 (9939) [INFO] Trying other mirror. * 2025-04-15 02:29:42 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-15 02:29:42 (9939) [INFO] Trying other mirror. * 2025-04-15 02:30:43 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:30:43 (9939) [INFO] Trying other mirror. * 2025-04-15 02:30:43 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:30:43 (9939) [INFO] Trying other mirror. * 2025-04-15 02:31:14 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-15 02:31:14 (9939) [INFO] Trying other mirror. * 2025-04-15 02:31:44 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:31:44 (9939) [INFO] Trying other mirror. * 2025-04-15 02:32:15 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-15 02:32:15 (9939) [INFO] Trying other mirror. * 2025-04-15 02:33:40 (9939) [INFO] Metadata Cache Created * 2025-04-15 02:33:40 (9956) [INFO] * 2025-04-15 02:33:40 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-15 02:33:40 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-15 02:33:42 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-15 02:33:42 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-15 02:33:42 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-15 02:33:42 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-15 02:33:42 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-15 02:33:48 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8WCD8OeE8y/ea_profile.json * 2025-04-15 02:33:50 (9064) [INFO] Backed up EA4 profile to /tmp/8WCD8OeE8y/ea_profile.json * 2025-04-15 02:33:50 (259) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-04-15 02:33:53 (650) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-04-15 02:34:24 (686) [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. * 2025-04-15 02:34:24 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-16 01:54:23 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-16 01:58:24 (11009) [INFO] Script is up to date. * 2025-04-16 02:02:27 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-16 02:02:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-16 02:02:27 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-16 02:02:27 (9926) [INFO] * 2025-04-16 02:02:31 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-16 02:02:31 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-16 02:02:31 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-16 02:02:31 (9926) [INFO] * 2025-04-16 02:02:43 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-16 02:02:46 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-16 02:02:46 (9926) [INFO] * 2025-04-16 02:02:47 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-16 02:02:47 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-16 02:03:17 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-16 02:03:17 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-16 02:03:17 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-16 02:03:17 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-16 02:04:04 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-04-16 02:04:04 (9939) [INFO] Trying other mirror. * 2025-04-16 02:06:34 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:06:34 (9939) [INFO] Trying other mirror. * 2025-04-16 02:06:51 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:06:51 (9939) [INFO] Trying other mirror. * 2025-04-16 02:07:24 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-16 02:07:24 (9939) [INFO] Trying other mirror. * 2025-04-16 02:07:34 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:07:34 (9939) [INFO] Trying other mirror. * 2025-04-16 02:07:55 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-04-16 02:07:55 (9939) [INFO] Trying other mirror. * 2025-04-16 02:08:42 (9939) [INFO] Metadata Cache Created * 2025-04-16 02:08:42 (9956) [INFO] * 2025-04-16 02:08:42 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-04-16 02:08:42 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-16 02:08:42 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-16 02:08:42 (9926) [INFO] * 2025-04-16 02:08:43 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-16 02:08:43 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-16 02:08:43 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-16 02:08:43 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-16 02:08:43 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-16 02:08:43 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-16 02:08:43 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-16 02:08:43 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-16 02:08:43 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-16 02:08:43 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-16 02:08:44 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-16 02:08:44 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-16 02:08:44 (9956) [INFO] * 2025-04-16 02:08:44 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-16 02:08:44 (9926) [INFO] * 2025-04-16 02:08:44 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-16 02:08:45 (9939) [INFO] Determining fastest mirrors * 2025-04-16 02:09:16 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-16 02:09:16 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-16 02:09:16 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-16 02:09:16 (9939) [INFO] * epel: dl.fedoraproject.org * 2025-04-16 02:12:20 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-04-16 02:12:20 (9939) [INFO] Trying other mirror. * 2025-04-16 02:12:20 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:12:20 (9939) [INFO] Trying other mirror. * 2025-04-16 02:12:51 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30783 milliseconds') * 2025-04-16 02:12:51 (9939) [INFO] Trying other mirror. * 2025-04-16 02:15:00 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-16 02:15:00 (9939) [INFO] Trying other mirror. * 2025-04-16 02:15:44 (9939) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-04-16 02:15:44 (9939) [INFO] Trying other mirror. * 2025-04-16 02:16:00 (9939) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:16:00 (9939) [INFO] Trying other mirror. * 2025-04-16 02:16:16 (9939) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:16:16 (9939) [INFO] Trying other mirror. * 2025-04-16 02:16:31 (9939) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:16:31 (9939) [INFO] Trying other mirror. * 2025-04-16 02:16:47 (9939) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:16:47 (9939) [INFO] Trying other mirror. * 2025-04-16 02:17:03 (9939) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:17:03 (9939) [INFO] Trying other mirror. * 2025-04-16 02:17:18 (9939) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:17:18 (9939) [INFO] Trying other mirror. * 2025-04-16 02:17:48 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:17:48 (9939) [INFO] Trying other mirror. * 2025-04-16 02:17:49 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-16 02:17:49 (9939) [INFO] Trying other mirror. * 2025-04-16 02:18:04 (9939) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/wp-toolkit/repodata/25d21152519417eb0ea58dc783e9203b7a2e31478bec0375f7e028a8c5c61d5b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:18:04 (9939) [INFO] Trying other mirror. * 2025-04-16 02:18:19 (9939) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:18:19 (9939) [INFO] Trying other mirror. * 2025-04-16 02:18:19 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:18:19 (9939) [INFO] Trying other mirror. * 2025-04-16 02:18:50 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-16 02:18:50 (9939) [INFO] Trying other mirror. * 2025-04-16 02:19:20 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:19:20 (9939) [INFO] Trying other mirror. * 2025-04-16 02:19:21 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-16 02:19:21 (9939) [INFO] Trying other mirror. * 2025-04-16 02:19:21 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-16 02:19:21 (9939) [INFO] Trying other mirror. * 2025-04-16 02:19:51 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-16 02:19:51 (9939) [INFO] Trying other mirror. * 2025-04-16 02:19:51 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:19:51 (9939) [INFO] Trying other mirror. * 2025-04-16 02:20:21 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:20:21 (9939) [INFO] Trying other mirror. * 2025-04-16 02:20:22 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:20:22 (9939) [INFO] Trying other mirror. * 2025-04-16 02:20:52 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-16 02:20:52 (9939) [INFO] Trying other mirror. * 2025-04-16 02:21:23 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-16 02:21:23 (9939) [INFO] Trying other mirror. * 2025-04-16 02:21:53 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-16 02:21:53 (9939) [INFO] Trying other mirror. * 2025-04-16 02:22:46 (9939) [INFO] Metadata Cache Created * 2025-04-16 02:22:46 (9956) [INFO] * 2025-04-16 02:22:46 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-16 02:22:46 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30783 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/wp-toolkit/repodata/25d21152519417eb0ea58dc783e9203b7a2e31478bec0375f7e028a8c5c61d5b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-04-16 02:22:48 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-16 02:22:48 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-16 02:22:48 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-16 02:22:48 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-16 02:22:48 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-16 02:22:55 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2j4ncL8_O5/ea_profile.json * 2025-04-16 02:23:13 (9064) [INFO] Backed up EA4 profile to /tmp/2j4ncL8_O5/ea_profile.json * 2025-04-16 02:23:14 (259) [WARN] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-04-16 02:23:17 (650) [WARN] Symlinks with absolute paths were found in /: This can cause problems during the upgrade, and the script will correct them to relative symlinks before elevation. * 2025-04-16 02:23:48 (686) [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. * 2025-04-16 02:23:48 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-17 02:20:48 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-17 02:24:48 (11009) [INFO] Script is up to date. * 2025-04-17 02:28:51 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-17 02:28:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-17 02:28:52 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-17 02:28:52 (9926) [INFO] * 2025-04-17 02:41:11 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-17 02:41:11 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-17 02:41:11 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-17 02:41:11 (9926) [INFO] * 2025-04-17 02:41:24 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-17 02:41:27 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-17 02:41:27 (9926) [INFO] * 2025-04-17 02:41:28 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-17 02:41:28 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-17 02:41:58 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-17 02:41:58 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-17 02:41:58 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-17 02:41:58 (9939) [INFO] * epel: mirror.math.princeton.edu * 2025-04-17 02:42:45 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-17 02:42:45 (9939) [INFO] Trying other mirror. * 2025-04-17 02:43:16 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-17 02:43:16 (9939) [INFO] Trying other mirror. * 2025-04-17 02:43:47 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-17 02:43:47 (9939) [INFO] Trying other mirror. * 2025-04-17 02:44:17 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30015 milliseconds with 0 out of 0 bytes received') * 2025-04-17 02:44:17 (9939) [INFO] Trying other mirror. * 2025-04-17 02:44:48 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-04-17 02:44:48 (9939) [INFO] Trying other mirror. * 2025-04-17 02:47:21 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-17 02:47:21 (9939) [INFO] Trying other mirror. * 2025-04-17 02:47:38 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-04-17 02:47:38 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:07 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-17 02:48:08 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:12 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-04-17 02:48:12 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:21 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30538 milliseconds') * 2025-04-17 02:48:21 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:38 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-17 02:48:38 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:42 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-04-17 02:48:42 (9939) [INFO] Trying other mirror. * 2025-04-17 02:48:52 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-17 02:48:52 (9939) [INFO] Trying other mirror. * 2025-04-17 02:49:13 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-17 02:49:13 (9939) [INFO] Trying other mirror. * 2025-04-17 02:49:22 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-17 02:49:22 (9939) [INFO] Trying other mirror. * 2025-04-17 02:49:44 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-17 02:49:44 (9939) [INFO] Trying other mirror. * 2025-04-17 02:49:52 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Operation timed out after 30011 milliseconds with 0 out of 0 bytes received') * 2025-04-17 02:49:52 (9939) [INFO] Trying other mirror. * 2025-04-17 02:50:14 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-17 02:50:14 (9939) [INFO] Trying other mirror. * 2025-04-18 02:06:38 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-18 02:10:39 (11009) [INFO] Script is up to date. * 2025-04-18 02:14:42 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-18 02:14:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-18 02:14:43 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-18 02:14:43 (9926) [INFO] * 2025-04-18 02:35:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-18 02:35:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-18 02:35:18 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-18 02:35:18 (9926) [INFO] * 2025-04-18 02:35:30 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-18 02:35:33 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-18 02:35:33 (9926) [INFO] * 2025-04-18 02:35:33 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-18 02:35:34 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-18 02:36:04 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-18 02:36:04 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-18 02:36:04 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-18 02:36:04 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-19 01:56:01 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-19 02:00:02 (11009) [INFO] Script is up to date. * 2025-04-19 02:04:05 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-19 02:04:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-19 02:04:06 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-19 02:04:06 (9926) [INFO] * 2025-04-19 02:11:05 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-19 02:11:05 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-19 02:11:05 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-19 02:11:05 (9926) [INFO] * 2025-04-19 02:11:18 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-19 02:11:21 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-19 02:11:21 (9926) [INFO] * 2025-04-19 02:11:21 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-19 02:11:22 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-19 02:11:52 (9939) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-19 02:11:52 (9939) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30538 milliseconds') * 2025-04-19 02:11:52 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-19 02:11:52 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-19 02:11:52 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-19 02:11:52 (9939) [INFO] * epel: mirror.math.princeton.edu * 2025-04-19 02:12:39 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-19 02:12:39 (9939) [INFO] Trying other mirror. * 2025-04-19 02:15:09 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-19 02:15:09 (9939) [INFO] Trying other mirror. * 2025-04-19 02:15:25 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-19 02:15:25 (9939) [INFO] Trying other mirror. * 2025-04-19 02:15:58 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-19 02:15:58 (9939) [INFO] Trying other mirror. * 2025-04-19 02:16:08 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-19 02:16:08 (9939) [INFO] Trying other mirror. * 2025-04-19 02:16:39 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-04-19 02:16:39 (9939) [INFO] Trying other mirror. * 2025-04-19 02:17:23 (9939) [INFO] Metadata Cache Created * 2025-04-19 02:17:23 (9956) [INFO] * 2025-04-19 02:17:23 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30538 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. * 2025-04-19 02:17:23 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-19 02:17:23 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-19 02:17:23 (9926) [INFO] * 2025-04-19 02:17:24 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-19 02:17:24 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-19 02:17:24 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-19 02:17:24 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-19 02:17:24 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-19 02:17:24 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-19 02:17:24 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-19 02:17:24 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-19 02:17:24 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-19 02:17:24 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-19 02:17:25 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-19 02:17:25 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-19 02:17:25 (9956) [INFO] * 2025-04-19 02:17:25 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-19 02:17:25 (9926) [INFO] * 2025-04-19 02:17:25 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-19 02:17:26 (9939) [INFO] Determining fastest mirrors * 2025-04-19 02:17:57 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-19 02:17:57 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-19 02:17:57 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-19 02:17:57 (9939) [INFO] * epel: dl.fedoraproject.org * 2025-04-19 02:18:44 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-04-19 02:18:44 (9939) [INFO] Trying other mirror. * 2025-04-19 02:22:46 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-19 02:22:46 (9939) [INFO] Trying other mirror. * 2025-04-19 02:22:47 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-19 02:22:47 (9939) [INFO] Trying other mirror. * 2025-04-19 02:25:25 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-19 02:25:25 (9939) [INFO] Trying other mirror. * 2025-04-20 01:54:25 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-20 01:58:26 (11009) [INFO] Script is up to date. * 2025-04-20 02:02:29 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-20 02:02:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-20 02:02:30 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-20 02:02:30 (9926) [INFO] * 2025-04-20 02:07:02 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-20 02:07:02 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-20 02:07:02 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-20 02:07:02 (9926) [INFO] * 2025-04-20 02:07:15 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-20 02:07:19 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-20 02:07:19 (9926) [INFO] * 2025-04-20 02:07:19 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-20 02:07:20 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-20 02:07:50 (9939) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-20 02:07:50 (9939) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30048 milliseconds with 0 out of 0 bytes received') * 2025-04-20 02:07:50 (9939) [INFO] * EA4: 184.94.196.93 * 2025-04-20 02:07:50 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 2025-04-20 02:07:50 (9939) [INFO] * cpanel-plugins: 184.94.196.93 * 2025-04-20 02:07:50 (9939) [INFO] * epel: mirror.math.princeton.edu * 2025-04-20 02:10:37 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-20 02:10:37 (9939) [INFO] Trying other mirror. * 2025-04-20 02:10:53 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-20 02:10:53 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:10 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-20 02:11:10 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:23 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-20 02:11:23 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:24 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-20 02:11:24 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:40 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-20 02:11:40 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:53 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-20 02:11:53 (9939) [INFO] Trying other mirror. * 2025-04-20 02:11:54 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-20 02:11:54 (9939) [INFO] Trying other mirror. * 2025-04-20 02:12:10 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-20 02:12:10 (9939) [INFO] Trying other mirror. * 2025-04-20 02:12:58 (9939) [INFO] Metadata Cache Created * 2025-04-20 02:12:58 (9956) [INFO] * 2025-04-20 02:12:58 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30048 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-04-20 02:12:58 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-20 02:12:58 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-20 02:12:58 (9926) [INFO] * 2025-04-20 02:12:59 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-20 02:12:59 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-20 02:12:59 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-20 02:12:59 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-20 02:12:59 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-20 02:12:59 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-20 02:12:59 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-20 02:12:59 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-20 02:12:59 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-20 02:12:59 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-20 02:13:00 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-20 02:13:00 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-20 02:13:00 (9956) [INFO] * 2025-04-20 02:13:00 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-20 02:13:00 (9926) [INFO] * 2025-04-20 02:13:00 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-20 02:13:01 (9939) [INFO] Determining fastest mirrors * 2025-04-20 02:13:33 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-20 02:13:33 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-20 02:13:33 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-20 02:13:33 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-20 02:14:20 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30595 milliseconds') * 2025-04-20 02:14:20 (9939) [INFO] Trying other mirror. * 2025-04-20 02:14:51 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30831 milliseconds') * 2025-04-20 02:14:51 (9939) [INFO] Trying other mirror. * 2025-04-20 02:15:22 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30846 milliseconds') * 2025-04-20 02:15:22 (9939) [INFO] Trying other mirror. * 2025-04-20 02:18:09 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-20 02:18:09 (9939) [INFO] Trying other mirror. * 2025-04-20 02:18:09 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-20 02:18:09 (9939) [INFO] Trying other mirror. * 2025-04-20 02:18:39 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-04-20 02:18:39 (9939) [INFO] Trying other mirror. * 2025-04-20 02:20:49 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-20 02:20:49 (9939) [INFO] Trying other mirror. * 2025-04-20 02:23:37 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-20 02:23:37 (9939) [INFO] Trying other mirror. * 2025-04-20 02:23:38 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-20 02:23:38 (9939) [INFO] Trying other mirror. * 2025-04-20 02:24:08 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-20 02:24:08 (9939) [INFO] Trying other mirror. * 2025-04-21 01:53:29 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-21 01:57:29 (11009) [INFO] Script is up to date. * 2025-04-21 02:01:32 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-21 02:01:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-21 02:01:33 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-21 02:01:33 (9926) [INFO] * 2025-04-21 02:01:36 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-21 02:01:36 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-21 02:01:36 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-21 02:01:36 (9926) [INFO] * 2025-04-21 02:01:50 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-21 02:01:54 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-21 02:01:54 (9926) [INFO] * 2025-04-21 02:01:55 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-21 02:01:55 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-21 02:02:26 (9939) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-21 02:02:26 (9939) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') * 2025-04-21 02:02:26 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-21 02:02:26 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-21 02:02:26 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-21 02:02:26 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-21 02:05:11 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:05:11 (9939) [INFO] Trying other mirror. * 2025-04-21 02:05:27 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:05:27 (9939) [INFO] Trying other mirror. * 2025-04-21 02:06:11 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-21 02:06:11 (9939) [INFO] Trying other mirror. * 2025-04-21 02:06:41 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:06:41 (9939) [INFO] Trying other mirror. * 2025-04-21 02:07:24 (9939) [INFO] Metadata Cache Created * 2025-04-21 02:07:24 (9956) [INFO] * 2025-04-21 02:07:24 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-21 02:07:24 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-21 02:07:24 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-21 02:07:24 (9926) [INFO] * 2025-04-21 02:07:24 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-21 02:07:24 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-21 02:07:24 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-21 02:07:24 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-21 02:07:24 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-21 02:07:24 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-21 02:07:24 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-21 02:07:24 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-21 02:07:24 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-21 02:07:24 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-21 02:07:25 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-21 02:07:25 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-21 02:07:25 (9956) [INFO] * 2025-04-21 02:07:25 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-21 02:07:25 (9926) [INFO] * 2025-04-21 02:07:26 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-21 02:07:26 (9939) [INFO] Determining fastest mirrors * 2025-04-21 02:07:59 (9939) [INFO] * EA4: 208.74.123.61 * 2025-04-21 02:07:59 (9939) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-21 02:07:59 (9939) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-21 02:07:59 (9939) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-21 02:08:46 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-21 02:08:46 (9939) [INFO] Trying other mirror. * 2025-04-21 02:09:17 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-21 02:09:17 (9939) [INFO] Trying other mirror. * 2025-04-21 02:09:47 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-21 02:09:47 (9939) [INFO] Trying other mirror. * 2025-04-21 02:10:18 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30597 milliseconds') * 2025-04-21 02:10:18 (9939) [INFO] Trying other mirror. * 2025-04-21 02:13:04 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:13:04 (9939) [INFO] Trying other mirror. * 2025-04-21 02:13:05 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-21 02:13:05 (9939) [INFO] Trying other mirror. * 2025-04-21 02:13:35 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-04-21 02:13:35 (9939) [INFO] Trying other mirror. * 2025-04-21 02:13:51 (9939) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:13:51 (9939) [INFO] Trying other mirror. * 2025-04-21 02:14:06 (9939) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:14:06 (9939) [INFO] Trying other mirror. * 2025-04-21 02:14:22 (9939) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:14:22 (9939) [INFO] Trying other mirror. * 2025-04-21 02:14:38 (9939) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:14:38 (9939) [INFO] Trying other mirror. * 2025-04-21 02:14:53 (9939) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:14:53 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:09 (9939) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:09 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:10 (9939) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:10 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:11 (9939) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:11 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:11 (9939) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:11 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:38 (9939) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5cdf58657e317d96d214fa0459cb417ec04f46336ea7e1da8f3d371391288bfe-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:38 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:42 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:15:42 (9939) [INFO] Trying other mirror. * 2025-04-21 02:15:54 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MTM5ODAxOjE3NDUzOTkwMDE6jKIDBxAC8cOFxPkk7wB9ScwY326AhB5eSapA7_2886XbQdSH4WBB5d6QBDY_Rqm_hlWgPtS8GRWIUZhgSkNbxVtJh7MspOhfaV6c8RGJZYBMk-Ai9ZYvXyBrCX_hb5v2eMqHDMsXROIvcokwi88_DFqCrQirs_ZhXz2J53NROPkbOPqNj2r4SY-kHtz2rqnjHr8ufgSCyRPsi9mC9KUbZ6CpiL6atG4y5JYAhrxP_VkO9Z9Qs4uFeKrsw86CKCiu28_bVBYM7hZZXx5wtMPvSDtRwl5sXeTqPiXq4uKIb4YR2CSizUiGhBSbDZq2Cc0c-OBoH97HQRuhcXBssCRlN1cjyMRRYaIwnkwQsLiC8DWKHl-uk5vrKn2tB3mbykMAUZ-AVTSHRfk_REcHqJY05i4La9b320BpJUJDrlC0Og1koSYVI12nOB0ua3yev5TRo1aCd7xhbDhgf3kExtthoox5KZ6AxG8dAURwm0eFvNIryBEdVvdBdZOVGqvzOGjvTGTabZ7EyZfvHm1mL803aHyunZZ-pTYLNqMhlC9ydVkoWovxpLQjSTo4NJeVY12Tzzt9kdyFPe6k6qjgmOB1ghoMgXFyajOYptRpuEePci0tKuDZNTYRvYluEX9323b1OgwrBmS296aTljScnhs3hftKpjshHaNfnH7_Srsnsf8%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:15:54 (9939) [INFO] Trying other mirror. * 2025-04-21 02:16:09 (9939) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MTM5ODAxOjE3NDUzOTkwMDE6jKIDBxAC8cOFxPkk7wB9ScwY326AhB5eSapA7_2886XbQdSH4WBB5d6QBDY_Rqm_hlWgPtS8GRWIUZhgSkNbxVtJh7MspOhfaV6c8RGJZYBMk-Ai9ZYvXyBrCX_hb5v2eMqHDMsXROIvcokwi88_DFqCrQirs_ZhXz2J53NROPkbOPqNj2r4SY-kHtz2rqnjHr8ufgSCyRPsi9mC9KUbZ6CpiL6atG4y5JYAhrxP_VkO9Z9Qs4uFeKrsw86CKCiu28_bVBYM7hZZXx5wtMPvSDtRwl5sXeTqPiXq4uKIb4YR2CSizUiGhBSbDZq2Cc0c-OBoH97HQRuhcXBssCRlN1cjyMRRYaIwnkwQsLiC8DWKHl-uk5vrKn2tB3mbykMAUZ-AVTSHRfk_REcHqJY05i4La9b320BpJUJDrlC0Og1koSYVI12nOB0ua3yev5TRo1aCd7xhbDhgf3kExtthoox5KZ6AxG8dAURwm0eFvNIryBEdVvdBdZOVGqvzOGjvTGTabZ7EyZfvHm1mL803aHyunZZ-pTYLNqMhlC9ydVkoWovxpLQjSTo4NJeVY12Tzzt9kdyFPe6k6qjgmOB1ghoMgXFyajOYptRpuEePci0tKuDZNTYRvYluEX9323b1OgwrBmS296aTljScnhs3hftKpjshHaNfnH7_Srsnsf8%3D/ea-php/7/updates/x86_64/repodata/edad1be4209e565219273305d4bf46dd93f73814121f0ce24ef4ab0d02ad6acc-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:16:09 (9939) [INFO] Trying other mirror. * 2025-04-21 02:16:25 (9939) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:16:25 (9939) [INFO] Trying other mirror. * 2025-04-21 02:16:41 (9939) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:16:41 (9939) [INFO] Trying other mirror. * 2025-04-21 02:16:56 (9939) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:16:56 (9939) [INFO] Trying other mirror. * 2025-04-21 02:17:12 (9939) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:17:12 (9939) [INFO] Trying other mirror. * 2025-04-21 02:17:28 (9939) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:17:28 (9939) [INFO] Trying other mirror. * 2025-04-21 02:17:43 (9939) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:17:43 (9939) [INFO] Trying other mirror. * 2025-04-21 02:17:59 (9939) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:17:59 (9939) [INFO] Trying other mirror. * 2025-04-21 02:18:15 (9939) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:18:15 (9939) [INFO] Trying other mirror. * 2025-04-21 02:18:45 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:18:45 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:01 (9939) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/wp-toolkit/repodata/25d21152519417eb0ea58dc783e9203b7a2e31478bec0375f7e028a8c5c61d5b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:01 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:16 (9939) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:16 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:16 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:16 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:17 (9939) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:17 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:32 (9939) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:32 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:33 (9939) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:33 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:34 (9939) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:47 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-04-21 02:19:47 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:47 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-21 02:19:47 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:48 (9939) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:48 (9939) [INFO] Trying other mirror. * 2025-04-21 02:19:49 (9939) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:19:49 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:04 (9939) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'timed out before SSL handshake') * 2025-04-21 02:20:04 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:04 (9939) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:04 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:05 (9939) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2025-04-21 02:20:05 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:05 (9939) [INFO] To address this issue please refer to the below wiki article * 2025-04-21 02:20:05 (9939) [INFO] * 2025-04-21 02:20:05 (9939) [INFO] https://wiki.centos.org/yum-errors * 2025-04-21 02:20:05 (9939) [INFO] * 2025-04-21 02:20:05 (9939) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-04-21 02:20:05 (9939) [INFO] * 2025-04-21 02:20:17 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:17 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:18 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-21 02:20:18 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:21 (9939) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 404 - Not Found * 2025-04-21 02:20:21 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:34 (9939) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 12] Timeout on https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: (28, 'Connection timed out after 30004 milliseconds') * 2025-04-21 02:20:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:34 (9939) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:35 (9939) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:35 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:50 (9939) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:50 (9939) [INFO] Trying other mirror. * 2025-04-21 02:20:50 (9939) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:20:50 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:03 (9939) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:03 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:05 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-21 02:21:05 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:06 (9939) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:06 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:06 (9939) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:06 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:21 (9939) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:21 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:34 (9939) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 12] Timeout on https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-21 02:21:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:34 (9939) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:34 (9939) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:34 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:35 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:35 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:50 (9939) [INFO] https://mirrors.hostiserver.com/fedora/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 404 - Not Found * 2025-04-21 02:21:50 (9939) [INFO] Trying other mirror. * 2025-04-21 02:21:50 (9939) [INFO] https://repo.jing.rocks/fedora-buffet/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:21:50 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:04 (9939) [INFO] https://d2lzkl7pfhq30w.cloudfront.net/pub/archive/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:04 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:05 (9939) [INFO] https://mirror.2degrees.nz/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:05 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:06 (9939) [INFO] https://fedora-archive.mirror.liquidtelecom.com/archive/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:06 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:22 (9939) [INFO] https://fedora-archive.ip-connect.info/epel/7/x86_64/repodata/ee7ce72544e0fca006120c613404d937cc3da9d09c7d80aea269df31639f310c-updateinfo.xml.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:22 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:33 (9939) [INFO] https://fedora-archive.ip-connect.vn.ua/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:33 (9939) [INFO] Trying other mirror. * 2025-04-21 02:22:48 (9939) [INFO] https://ftp-stud.hs-esslingen.de/pub/Mirrors/archive.fedoraproject.org/epel/7/x86_64/repodata/9cfdefede5c3cf769a448c2a7d0a6441d6dbd7ba215833153a284c50c76faa56-comps-Everything.x86_64.xml: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-21 02:22:48 (9939) [INFO] Trying other mirror. * 2025-04-22 01:52:27 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-22 01:56:27 (11009) [INFO] Script is up to date. * 2025-04-22 02:00:31 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-22 02:00:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-22 02:00:31 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-22 02:00:31 (9926) [INFO] * 2025-04-22 02:07:30 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-22 02:07:30 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-22 02:07:30 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-22 02:07:30 (9926) [INFO] * 2025-04-22 02:07:44 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-22 02:07:48 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-22 02:07:48 (9926) [INFO] * 2025-04-22 02:07:49 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-22 02:07:49 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-22 02:08:19 (9939) [INFO] * EA4: 63.247.64.58 * 2025-04-22 02:08:19 (9939) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-22 02:08:19 (9939) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-22 02:08:19 (9939) [INFO] * epel: mirror.math.princeton.edu * 2025-04-22 02:09:05 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:09:05 (9939) [INFO] Trying other mirror. * 2025-04-22 02:09:36 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-22 02:09:36 (9939) [INFO] Trying other mirror. * 2025-04-22 02:10:06 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30005 milliseconds') * 2025-04-22 02:10:06 (9939) [INFO] Trying other mirror. * 2025-04-22 02:10:37 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-22 02:10:37 (9939) [INFO] Trying other mirror. * 2025-04-22 02:11:07 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:11:07 (9939) [INFO] Trying other mirror. * 2025-04-22 02:11:37 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:11:37 (9939) [INFO] Trying other mirror. * 2025-04-22 02:12:07 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-22 02:12:07 (9939) [INFO] Trying other mirror. * 2025-04-22 02:12:37 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:12:37 (9939) [INFO] Trying other mirror. * 2025-04-22 02:13:07 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:13:07 (9939) [INFO] Trying other mirror. * 2025-04-22 02:13:37 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:13:37 (9939) [INFO] Trying other mirror. * 2025-04-22 02:14:24 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-22 02:14:24 (9939) [INFO] Trying other mirror. * 2025-04-22 02:14:54 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30034 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:14:54 (9939) [INFO] Trying other mirror. * 2025-04-22 02:15:24 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:15:24 (9939) [INFO] Trying other mirror. * 2025-04-22 02:15:54 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:15:54 (9939) [INFO] Trying other mirror. * 2025-04-22 02:16:25 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-22 02:16:25 (9939) [INFO] Trying other mirror. * 2025-04-22 02:16:55 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30005 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:16:55 (9939) [INFO] Trying other mirror. * 2025-04-22 02:17:26 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-22 02:17:26 (9939) [INFO] Trying other mirror. * 2025-04-22 02:17:56 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:17:56 (9939) [INFO] Trying other mirror. * 2025-04-22 02:18:26 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:18:26 (9939) [INFO] Trying other mirror. * 2025-04-22 02:18:56 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:18:56 (9939) [INFO] Trying other mirror. * 2025-04-22 02:20:23 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:20:23 (9939) [INFO] Trying other mirror. * 2025-04-22 02:20:53 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-22 02:20:53 (9939) [INFO] Trying other mirror. * 2025-04-22 02:21:24 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') * 2025-04-22 02:21:24 (9939) [INFO] Trying other mirror. * 2025-04-22 02:21:55 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-04-22 02:21:55 (9939) [INFO] Trying other mirror. * 2025-04-23 01:57:58 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-23 02:01:59 (11009) [INFO] Script is up to date. * 2025-04-23 02:06:02 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-23 02:06:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-23 02:06:03 (9925) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-23 02:06:03 (9926) [INFO] * 2025-04-23 02:07:01 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-23 02:07:01 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-23 02:07:01 (9925) [INFO] Running: /usr/bin/yum list extras * 2025-04-23 02:07:01 (9926) [INFO] * 2025-04-23 02:07:14 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-23 02:07:17 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-23 02:07:17 (9926) [INFO] * 2025-04-23 02:07:17 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-23 02:07:18 (9939) [INFO] Loading mirror speeds from cached hostfile * 2025-04-23 02:07:48 (9939) [INFO] * EA4: 184.94.196.92 * 2025-04-23 02:07:48 (9939) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-04-23 02:07:48 (9939) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-04-23 02:07:48 (9939) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-23 02:10:36 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-23 02:10:36 (9939) [INFO] Trying other mirror. * 2025-04-23 02:10:53 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-23 02:10:53 (9939) [INFO] Trying other mirror. * 2025-04-23 02:11:22 (9939) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-23 02:11:22 (9939) [INFO] Trying other mirror. * 2025-04-23 02:11:28 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-23 02:11:28 (9939) [INFO] Trying other mirror. * 2025-04-23 02:11:37 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-23 02:11:37 (9939) [INFO] Trying other mirror. * 2025-04-23 02:11:59 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-04-23 02:11:59 (9939) [INFO] Trying other mirror. * 2025-04-23 02:12:08 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-23 02:12:08 (9939) [INFO] Trying other mirror. * 2025-04-23 02:12:30 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-23 02:12:30 (9939) [INFO] Trying other mirror. * 2025-04-23 02:12:38 (9939) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-23 02:12:38 (9939) [INFO] Trying other mirror. * 2025-04-23 02:13:00 (9939) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-23 02:13:00 (9939) [INFO] Trying other mirror. * 2025-04-23 02:13:44 (9939) [INFO] Metadata Cache Created * 2025-04-23 02:13:44 (9956) [INFO] * 2025-04-23 02:13:44 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-23 02:13:44 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-23 02:13:44 (9925) [INFO] Running: /usr/bin/yum clean all * 2025-04-23 02:13:44 (9926) [INFO] * 2025-04-23 02:13:44 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-23 02:13:45 (9939) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-23 02:13:45 (9939) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-23 02:13:45 (9939) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-23 02:13:45 (9939) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-23 02:13:45 (9939) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-23 02:13:45 (9939) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-23 02:13:45 (9939) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-23 02:13:45 (9939) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-23 02:13:45 (9939) [INFO] : wp-toolkit-thirdparties * 2025-04-23 02:13:45 (9939) [INFO] Cleaning up list of fastest mirrors * 2025-04-23 02:13:45 (9939) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-23 02:13:45 (9956) [INFO] * 2025-04-23 02:13:45 (9925) [INFO] Running: /usr/bin/yum makecache * 2025-04-23 02:13:45 (9926) [INFO] * 2025-04-23 02:13:46 (9939) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-23 02:13:46 (9939) [INFO] Determining fastest mirrors * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] One of the configured repositories failed (Unknown), * 2025-04-23 02:14:17 (9939) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-23 02:14:17 (9939) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-23 02:14:17 (9939) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-23 02:14:17 (9939) [INFO] distribution release than is supported by the repository (and the * 2025-04-23 02:14:17 (9939) [INFO] packages for the previous distribution release still work). * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-23 02:14:17 (9939) [INFO] yum --disablerepo= ... * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-23 02:14:17 (9939) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-23 02:14:17 (9939) [INFO] again or use --enablerepo for temporary usage: * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] yum-config-manager --disable * 2025-04-23 02:14:17 (9939) [INFO] or * 2025-04-23 02:14:17 (9939) [INFO] subscription-manager repos --disable= * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-23 02:14:17 (9939) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-23 02:14:17 (9939) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-23 02:14:17 (9939) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-23 02:14:17 (9939) [INFO] compromise: * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-23 02:14:17 (9939) [INFO] * 2025-04-23 02:14:17 (9939) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-23 02:14:17 (9956) [INFO] * 2025-04-23 02:14:17 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-23 02:14:17 (6278) [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 * 2025-04-23 02:14:19 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-23 02:14:19 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-23 02:14:19 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-23 02:14:19 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-23 02:14:19 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-23 02:26:59 (9041) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/TjO7PbWtRG/ea_profile.json * 2025-04-24 02:00:29 (10987) [INFO] Self-update of script version 64 requested. * 2025-04-24 02:04:30 (10992) [INFO] Newer version of script found. Downloading. * 2025-04-24 02:08:32 (11001) [INFO] Script update to version 65 successful. * 2025-04-24 02:12:34 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-24 02:12:34 (10030) [INFO] * 2025-04-24 02:14:05 (10060) [INFO] * 2025-04-24 02:14:05 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-24 02:14:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-24 02:14:05 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-24 02:14:05 (10030) [INFO] * 2025-04-24 02:14:09 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-24 02:14:09 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-24 02:14:09 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-24 02:14:09 (10030) [INFO] * 2025-04-24 02:14:21 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-24 02:14:24 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-24 02:14:24 (10030) [INFO] * 2025-04-24 02:14:25 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-24 02:14:25 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-24 02:14:55 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-24 02:14:55 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-24 02:14:55 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-24 02:14:55 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-24 02:14:55 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-24 02:14:55 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-24 02:17:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-24 02:17:41 (10043) [INFO] Trying other mirror. * 2025-04-24 02:17:57 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-24 02:17:57 (10043) [INFO] Trying other mirror. * 2025-04-24 02:18:27 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30008 milliseconds with 0 out of 0 bytes received') * 2025-04-24 02:18:27 (10043) [INFO] Trying other mirror. * 2025-04-24 02:18:30 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-24 02:18:30 (10043) [INFO] Trying other mirror. * 2025-04-24 02:18:40 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-24 02:18:40 (10043) [INFO] Trying other mirror. * 2025-04-24 02:18:57 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-24 02:18:57 (10043) [INFO] Trying other mirror. * 2025-04-24 02:19:01 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-24 02:19:01 (10043) [INFO] Trying other mirror. * 2025-04-24 02:19:10 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-24 02:19:10 (10043) [INFO] Trying other mirror. * 2025-04-24 02:19:28 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-04-24 02:19:28 (10043) [INFO] Trying other mirror. * 2025-04-24 02:19:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-24 02:19:41 (10043) [INFO] Trying other mirror. * 2025-04-24 02:20:27 (10043) [INFO] Metadata Cache Created * 2025-04-24 02:20:27 (10060) [INFO] * 2025-04-24 02:20:27 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30008 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-04-24 02:20:27 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-24 02:20:27 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-24 02:20:27 (10030) [INFO] * 2025-04-24 02:20:27 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-24 02:20:28 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-24 02:20:28 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-24 02:20:28 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-24 02:20:28 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-24 02:20:28 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-24 02:20:28 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-24 02:20:28 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-24 02:20:28 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-24 02:20:28 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-24 02:20:29 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-24 02:20:29 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-24 02:20:29 (10060) [INFO] * 2025-04-24 02:20:29 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-24 02:20:29 (10030) [INFO] * 2025-04-24 02:20:29 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-24 02:20:30 (10043) [INFO] Determining fastest mirrors * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-04-24 02:21:02 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-24 02:21:02 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-24 02:21:02 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-24 02:21:02 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-24 02:21:02 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-24 02:21:02 (10043) [INFO] yum --disablerepo= ... * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-24 02:21:02 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-24 02:21:02 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] yum-config-manager --disable * 2025-04-24 02:21:02 (10043) [INFO] or * 2025-04-24 02:21:02 (10043) [INFO] subscription-manager repos --disable= * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-24 02:21:02 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-24 02:21:02 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-24 02:21:02 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-24 02:21:02 (10043) [INFO] compromise: * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-24 02:21:02 (10043) [INFO] * 2025-04-24 02:21:02 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-24 02:21:02 (10060) [INFO] * 2025-04-24 02:21:02 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-24 02:21:02 (6278) [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 * 2025-04-24 02:21:04 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-24 02:21:04 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-24 02:21:04 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-24 02:21:04 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-24 02:21:04 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-24 02:25:32 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0t0lXOXNB3/ea_profile.json * 2025-04-25 01:54:34 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-25 01:58:34 (11113) [INFO] Script is up to date. * 2025-04-25 02:02:37 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-25 02:02:37 (10030) [INFO] * 2025-04-25 02:04:02 (10060) [INFO] * 2025-04-25 02:04:02 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-25 02:04:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-25 02:04:02 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-25 02:04:02 (10030) [INFO] * 2025-04-25 02:11:02 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-25 02:11:02 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-25 02:11:02 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-25 02:11:02 (10030) [INFO] * 2025-04-25 02:11:14 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-25 02:11:18 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-25 02:11:18 (10030) [INFO] * 2025-04-25 02:11:19 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-25 02:11:19 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-25 02:11:49 (10043) [INFO] * EA4: 184.94.196.92 * 2025-04-25 02:11:49 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-04-25 02:11:49 (10043) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-04-25 02:11:49 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-25 02:14:35 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-25 02:14:35 (10043) [INFO] Trying other mirror. * 2025-04-25 02:14:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-04-25 02:14:53 (10043) [INFO] Trying other mirror. * 2025-04-25 02:15:22 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-25 02:15:22 (10043) [INFO] Trying other mirror. * 2025-04-25 02:15:27 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-04-25 02:15:27 (10043) [INFO] Trying other mirror. * 2025-04-25 02:15:35 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-25 02:15:35 (10043) [INFO] Trying other mirror. * 2025-04-25 02:15:53 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-04-25 02:15:53 (10043) [INFO] Trying other mirror. * 2025-04-25 02:15:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-25 02:15:57 (10043) [INFO] Trying other mirror. * 2025-04-25 02:16:06 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-25 02:16:06 (10043) [INFO] Trying other mirror. * 2025-04-25 02:16:24 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-04-25 02:16:24 (10043) [INFO] Trying other mirror. * 2025-04-25 02:16:28 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-25 02:16:28 (10043) [INFO] Trying other mirror. * 2025-04-25 02:16:54 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-25 02:16:54 (10043) [INFO] Trying other mirror. * 2025-04-25 02:17:39 (10043) [INFO] Metadata Cache Created * 2025-04-25 02:17:39 (10060) [INFO] * 2025-04-25 02:17:39 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-25 02:17:39 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-25 02:17:39 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-25 02:17:39 (10030) [INFO] * 2025-04-25 02:17:40 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-25 02:17:40 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-25 02:17:40 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-25 02:17:40 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-25 02:17:40 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-25 02:17:40 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-25 02:17:40 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-25 02:17:40 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-25 02:17:40 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-25 02:17:40 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-25 02:17:41 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-25 02:17:41 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-25 02:17:41 (10060) [INFO] * 2025-04-25 02:17:41 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-25 02:17:41 (10030) [INFO] * 2025-04-25 02:17:42 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-25 02:17:42 (10043) [INFO] Determining fastest mirrors * 2025-04-25 02:18:17 (10043) [INFO] * EA4: 63.247.64.58 * 2025-04-25 02:18:17 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-25 02:18:17 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-25 02:18:17 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-25 02:21:21 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-25 02:21:21 (10043) [INFO] Trying other mirror. * 2025-04-25 02:21:21 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-25 02:21:21 (10043) [INFO] Trying other mirror. * 2025-04-25 02:21:52 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-25 02:21:52 (10043) [INFO] Trying other mirror. * 2025-04-25 02:24:00 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-25 02:24:00 (10043) [INFO] Trying other mirror. * 2025-04-26 01:47:35 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-26 01:51:36 (11113) [INFO] Script is up to date. * 2025-04-26 01:55:39 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-26 01:55:39 (10030) [INFO] * 2025-04-26 01:56:46 (10060) [INFO] * 2025-04-26 01:56:47 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-26 01:56:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-26 01:56:47 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-26 01:56:47 (10030) [INFO] * 2025-04-26 02:03:47 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-26 02:03:47 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-26 02:03:47 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-26 02:03:47 (10030) [INFO] * 2025-04-26 02:04:08 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-26 02:04:08 (10030) [INFO] * 2025-04-26 02:04:09 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-26 02:04:09 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-26 02:04:39 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-26 02:04:39 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-26 02:04:39 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-26 02:04:39 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-26 02:05:26 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-26 02:05:26 (10043) [INFO] Trying other mirror. * 2025-04-26 02:06:54 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:06:54 (10043) [INFO] Trying other mirror. * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-26 02:06:54 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-26 02:06:54 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-26 02:06:54 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-26 02:06:54 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-26 02:06:54 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-26 02:06:54 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-26 02:06:54 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-26 02:06:54 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-26 02:06:54 (10043) [INFO] or * 2025-04-26 02:06:54 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-26 02:06:54 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-26 02:06:54 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-26 02:06:54 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-26 02:06:54 (10043) [INFO] compromise: * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-26 02:06:54 (10043) [INFO] * 2025-04-26 02:06:54 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-26 02:06:54 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:06:54 (10060) [INFO] * 2025-04-26 02:06:54 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:06:54 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-26 02:06:54 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-26 02:06:54 (10030) [INFO] * 2025-04-26 02:06:55 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-26 02:06:55 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-26 02:06:55 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-26 02:06:55 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-26 02:06:55 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-26 02:06:55 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-26 02:06:55 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-26 02:06:55 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-26 02:06:55 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-26 02:06:55 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-26 02:06:55 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-26 02:06:55 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-04-26 02:06:55 (10060) [INFO] * 2025-04-26 02:06:55 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-26 02:06:55 (10030) [INFO] * 2025-04-26 02:06:56 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-26 02:06:56 (10043) [INFO] Determining fastest mirrors * 2025-04-26 02:07:28 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-26 02:07:28 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-26 02:07:28 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-26 02:07:28 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-26 02:08:14 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-26 02:08:14 (10043) [INFO] Trying other mirror. * 2025-04-26 02:08:45 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-26 02:08:45 (10043) [INFO] Trying other mirror. * 2025-04-26 02:10:14 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:10:14 (10043) [INFO] Trying other mirror. * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-26 02:10:14 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-26 02:10:14 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-26 02:10:14 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-26 02:10:14 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-26 02:10:14 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-26 02:10:14 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-26 02:10:14 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-26 02:10:14 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-26 02:10:14 (10043) [INFO] or * 2025-04-26 02:10:14 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-26 02:10:14 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-26 02:10:14 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-26 02:10:14 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-26 02:10:14 (10043) [INFO] compromise: * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-26 02:10:14 (10043) [INFO] * 2025-04-26 02:10:14 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-26 02:10:14 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:10:14 (10060) [INFO] * 2025-04-26 02:10:14 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-26 02:10:14 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-26 02:10:16 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-26 02:10:16 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-26 02:10:16 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-26 02:10:16 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-26 02:10:16 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-27 01:46:12 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-27 01:50:13 (11113) [INFO] Script is up to date. * 2025-04-27 01:54:16 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-27 01:54:16 (10030) [INFO] * 2025-04-27 01:55:18 (10060) [INFO] * 2025-04-27 01:55:18 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-27 01:55:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-27 01:55:18 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-27 01:55:18 (10030) [INFO] * 2025-04-27 02:02:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-27 02:02:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-27 02:02:18 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-27 02:02:18 (10030) [INFO] * 2025-04-27 02:02:40 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-27 02:02:40 (10030) [INFO] * 2025-04-27 02:02:40 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-27 02:02:40 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-27 02:03:11 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-27 02:03:11 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-27 02:03:11 (10043) [INFO] * EA4: 184.94.196.93 * 2025-04-27 02:03:11 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 2025-04-27 02:03:11 (10043) [INFO] * cpanel-plugins: 184.94.196.93 * 2025-04-27 02:03:11 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-27 02:04:55 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:04:55 (10043) [INFO] Trying other mirror. * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-27 02:04:55 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-27 02:04:55 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-27 02:04:55 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-27 02:04:55 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-27 02:04:55 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-27 02:04:55 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-27 02:04:55 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-27 02:04:55 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-27 02:04:55 (10043) [INFO] or * 2025-04-27 02:04:55 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-27 02:04:55 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-27 02:04:55 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-27 02:04:55 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-27 02:04:55 (10043) [INFO] compromise: * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-27 02:04:55 (10043) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-27 02:04:55 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:04:55 (10060) [INFO] * 2025-04-27 02:04:55 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:04:55 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-27 02:04:55 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-27 02:04:55 (10030) [INFO] * 2025-04-27 02:04:55 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-27 02:04:56 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-27 02:04:56 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-27 02:04:56 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-27 02:04:56 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-27 02:04:56 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-27 02:04:56 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-27 02:04:56 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-27 02:04:56 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-27 02:04:56 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-27 02:04:56 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-27 02:04:56 (10043) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2025-04-27 02:04:56 (10060) [INFO] * 2025-04-27 02:04:56 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-27 02:04:56 (10030) [INFO] * 2025-04-27 02:04:56 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-27 02:04:57 (10043) [INFO] Determining fastest mirrors * 2025-04-27 02:05:29 (10043) [INFO] * EA4: 208.74.123.62 * 2025-04-27 02:05:29 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-04-27 02:05:29 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-04-27 02:05:29 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-27 02:06:15 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30658 milliseconds') * 2025-04-27 02:06:15 (10043) [INFO] Trying other mirror. * 2025-04-27 02:07:44 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:07:44 (10043) [INFO] Trying other mirror. * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-04-27 02:07:44 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-27 02:07:44 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-27 02:07:44 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-27 02:07:44 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-27 02:07:44 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-27 02:07:44 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-27 02:07:44 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-27 02:07:44 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-04-27 02:07:44 (10043) [INFO] or * 2025-04-27 02:07:44 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-27 02:07:44 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-27 02:07:44 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-27 02:07:44 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-27 02:07:44 (10043) [INFO] compromise: * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-04-27 02:07:44 (10043) [INFO] * 2025-04-27 02:07:44 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-04-27 02:07:44 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:07:44 (10060) [INFO] * 2025-04-27 02:07:44 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-27 02:07:44 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30658 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1MzIxMDAyOjE3NDU1ODAyMDI6r_I4JPf9ClXvRcsn69bYHddNrG0ifTNRi2o56KuQono9FxuQA2zUVd8AGnuwskvcOiFfSGfpspg-7-nazIWuEanOLUfujvVdDQCU_1DwlpvwfohjzNG1CTsk6wXTtHRe3eUBKDacSI_gTwKh_zyZHDYqDT6SysU5KJNvrwdWo4Ls1ZIskzuZzwVxX5Sk4zTH3lasPMkccejaJEx9f3I2Z8R0YW9LUhDoo36mfbZf93LM0nHYeDmauiyo3pPkNkiAaCogkP_Q0w0gq2pdovlDUv_Zvqfiu96uD-suZzOOpOkjadM30urSe4ALG-lyM8Gas6DKHwRUuBA8dI_cJ9z8Ouaiwfh7PETFe2Y4A7H8VE9xkcfJWsb-BXqgaV1ZcA0TuGdI20FaQq76rWTTjBzIDni3GcVgqGADKrL2M-yxKlSfTW98_sa3ZyDSESAofG6ZOLa5aIHXxXc3T0PlhSyvnqPy01IEENfwx7YwgJV2QScmUfrWLJqUjlGrqbem0YjCbtkzqbug7Hd-LWGWJxCQulv0Md0bCeIrVfKg7rALvOpFfkbG5X8vy-L9a1Pxn_SJVM6KWnRR5xIMqB6M-nnCXRebhjxyX-7zFvBTM27FQTpa5flwBkTAvG3E_u0jZXUuak3YXjRVd3DgtgyHSHZWHCoe4geKhg5dO7Zxzt5ityc=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-04-27 02:07:45 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-27 02:07:45 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-27 02:07:46 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-27 02:07:46 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-27 02:07:46 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-27 02:07:53 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rxIe1K65KL/ea_profile.json * 2025-04-27 02:10:09 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rxIe1K65KL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-04-27 02:10:09 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-04-28 01:52:30 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-28 01:56:30 (11113) [INFO] Script is up to date. * 2025-04-28 02:00:33 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-28 02:00:33 (10030) [INFO] * 2025-04-28 02:02:03 (10060) [INFO] * 2025-04-28 02:02:03 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-28 02:02:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-28 02:02:03 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-28 02:02:03 (10030) [INFO] * 2025-04-28 02:09:01 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-28 02:09:01 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-28 02:09:01 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-28 02:09:01 (10030) [INFO] * 2025-04-28 02:09:15 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-28 02:09:20 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-28 02:09:20 (10030) [INFO] * 2025-04-28 02:09:20 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-28 02:09:20 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-28 02:09:50 (10043) [INFO] * EA4: 63.247.64.58 * 2025-04-28 02:09:50 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-04-28 02:09:50 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-04-28 02:09:50 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-28 02:12:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-28 02:12:36 (10043) [INFO] Trying other mirror. * 2025-04-28 02:12:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-04-28 02:12:53 (10043) [INFO] Trying other mirror. * 2025-04-28 02:13:36 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-28 02:13:36 (10043) [INFO] Trying other mirror. * 2025-04-28 02:13:52 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-28 02:13:52 (10043) [INFO] Trying other mirror. * 2025-04-28 02:13:52 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-28 02:13:52 (10043) [INFO] Trying other mirror. * 2025-04-28 02:14:22 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-28 02:14:22 (10043) [INFO] Trying other mirror. * 2025-04-28 02:14:23 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-28 02:14:23 (10043) [INFO] Trying other mirror. * 2025-04-28 02:15:10 (10043) [INFO] Metadata Cache Created * 2025-04-28 02:15:10 (10060) [INFO] * 2025-04-28 02:15:10 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-28 02:15:10 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-28 02:15:10 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-28 02:15:10 (10030) [INFO] * 2025-04-28 02:15:11 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-28 02:15:11 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-28 02:15:11 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-28 02:15:11 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-28 02:15:11 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-28 02:15:11 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-28 02:15:11 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-28 02:15:11 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-28 02:15:11 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-28 02:15:11 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-28 02:15:12 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-28 02:15:12 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-28 02:15:12 (10060) [INFO] * 2025-04-28 02:15:12 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-28 02:15:12 (10030) [INFO] * 2025-04-28 02:15:12 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-28 02:15:13 (10043) [INFO] Determining fastest mirrors * 2025-04-28 02:15:44 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-28 02:15:44 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-28 02:15:44 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-28 02:15:44 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-28 02:18:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30007 milliseconds') * 2025-04-28 02:18:47 (10043) [INFO] Trying other mirror. * 2025-04-28 02:18:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-28 02:18:47 (10043) [INFO] Trying other mirror. * 2025-04-28 02:19:17 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-28 02:19:17 (10043) [INFO] Trying other mirror. * 2025-04-28 02:19:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-28 02:19:47 (10043) [INFO] Trying other mirror. * 2025-04-28 02:21:26 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-04-28 02:21:26 (10043) [INFO] Trying other mirror. * 2025-04-28 02:21:26 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-28 02:21:26 (10043) [INFO] Trying other mirror. * 2025-04-29 02:16:23 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-29 02:20:24 (11113) [INFO] Script is up to date. * 2025-04-29 02:24:27 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-29 02:24:27 (10030) [INFO] * 2025-04-29 02:25:53 (10060) [INFO] * 2025-04-29 02:25:53 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-29 02:25:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-29 02:25:53 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-29 02:25:53 (10030) [INFO] * 2025-04-29 02:25:57 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-29 02:25:57 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-29 02:25:58 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-29 02:25:58 (10030) [INFO] * 2025-04-29 02:26:12 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-29 02:26:15 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-29 02:26:15 (10030) [INFO] * 2025-04-29 02:26:16 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-29 02:26:16 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-29 02:26:46 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-29 02:26:46 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-04-29 02:26:46 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-29 02:26:46 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-29 02:26:46 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-29 02:26:46 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-29 02:27:33 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30603 milliseconds') * 2025-04-29 02:27:33 (10043) [INFO] Trying other mirror. * 2025-04-29 02:30:03 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:30:03 (10043) [INFO] Trying other mirror. * 2025-04-29 02:30:19 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:30:19 (10043) [INFO] Trying other mirror. * 2025-04-29 02:30:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-29 02:30:53 (10043) [INFO] Trying other mirror. * 2025-04-29 02:31:02 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:31:02 (10043) [INFO] Trying other mirror. * 2025-04-29 02:31:24 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-29 02:31:24 (10043) [INFO] Trying other mirror. * 2025-04-29 02:31:33 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-29 02:31:33 (10043) [INFO] Trying other mirror. * 2025-04-29 02:32:17 (10043) [INFO] Metadata Cache Created * 2025-04-29 02:32:17 (10060) [INFO] * 2025-04-29 02:32:17 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30603 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-04-29 02:32:17 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-29 02:32:17 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-29 02:32:17 (10030) [INFO] * 2025-04-29 02:32:17 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-29 02:32:18 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-29 02:32:18 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-29 02:32:18 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-29 02:32:18 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-29 02:32:18 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-29 02:32:18 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-29 02:32:18 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-29 02:32:18 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-29 02:32:18 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-29 02:32:19 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-29 02:32:19 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-29 02:32:19 (10060) [INFO] * 2025-04-29 02:32:19 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-29 02:32:19 (10030) [INFO] * 2025-04-29 02:32:19 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-29 02:32:20 (10043) [INFO] Determining fastest mirrors * 2025-04-29 02:32:52 (10043) [INFO] * EA4: 208.74.123.61 * 2025-04-29 02:32:52 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-04-29 02:32:52 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-04-29 02:32:52 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-04-29 02:35:56 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-04-29 02:35:56 (10043) [INFO] Trying other mirror. * 2025-04-29 02:35:56 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:35:56 (10043) [INFO] Trying other mirror. * 2025-04-29 02:36:27 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-29 02:36:27 (10043) [INFO] Trying other mirror. * 2025-04-29 02:38:36 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:38:36 (10043) [INFO] Trying other mirror. * 2025-04-29 02:39:37 (10043) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-04-29 02:39:37 (10043) [INFO] Trying other mirror. * 2025-04-29 02:39:52 (10043) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:39:52 (10043) [INFO] Trying other mirror. * 2025-04-29 02:40:08 (10043) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:40:08 (10043) [INFO] Trying other mirror. * 2025-04-29 02:40:24 (10043) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:40:24 (10043) [INFO] Trying other mirror. * 2025-04-29 02:40:39 (10043) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:40:39 (10043) [INFO] Trying other mirror. * 2025-04-29 02:40:55 (10043) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:40:55 (10043) [INFO] Trying other mirror. * 2025-04-29 02:41:25 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:41:25 (10043) [INFO] Trying other mirror. * 2025-04-29 02:41:41 (10043) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/wp-toolkit/repodata/25d21152519417eb0ea58dc783e9203b7a2e31478bec0375f7e028a8c5c61d5b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:41:41 (10043) [INFO] Trying other mirror. * 2025-04-29 02:41:56 (10043) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:41:56 (10043) [INFO] Trying other mirror. * 2025-04-29 02:41:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:41:57 (10043) [INFO] Trying other mirror. * 2025-04-29 02:42:27 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:42:27 (10043) [INFO] Trying other mirror. * 2025-04-29 02:42:28 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-04-29 02:42:28 (10043) [INFO] Trying other mirror. * 2025-04-29 02:42:57 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:42:57 (10043) [INFO] Trying other mirror. * 2025-04-29 02:42:58 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-29 02:42:58 (10043) [INFO] Trying other mirror. * 2025-04-29 02:43:29 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-29 02:43:29 (10043) [INFO] Trying other mirror. * 2025-04-29 02:43:59 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-04-29 02:43:59 (10043) [INFO] Trying other mirror. * 2025-04-29 02:44:47 (10043) [INFO] Metadata Cache Created * 2025-04-29 02:44:47 (10060) [INFO] * 2025-04-29 02:44:47 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-29 02:44:47 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/wp-toolkit/repodata/25d21152519417eb0ea58dc783e9203b7a2e31478bec0375f7e028a8c5c61d5b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.6.7/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror. * 2025-04-29 02:44:49 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-29 02:44:49 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-29 02:44:49 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-29 02:44:49 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-29 02:44:49 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-04-30 02:01:27 (11091) [INFO] Self-update of script version 65 requested. * 2025-04-30 02:05:27 (11113) [INFO] Script is up to date. * 2025-04-30 02:09:31 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-04-30 02:09:31 (10030) [INFO] * 2025-04-30 02:11:04 (10060) [INFO] * 2025-04-30 02:11:04 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-04-30 02:11:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-04-30 02:11:04 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-04-30 02:11:04 (10030) [INFO] * 2025-04-30 02:18:06 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-04-30 02:18:06 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-04-30 02:18:06 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-04-30 02:18:06 (10030) [INFO] * 2025-04-30 02:18:16 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-04-30 02:18:20 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-30 02:18:20 (10030) [INFO] * 2025-04-30 02:18:20 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-30 02:18:20 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-04-30 02:18:51 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-04-30 02:18:51 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30729 milliseconds') * 2025-04-30 02:18:51 (10043) [INFO] * EA4: 184.94.196.97 * 2025-04-30 02:18:51 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 2025-04-30 02:18:51 (10043) [INFO] * cpanel-plugins: 184.94.196.97 * 2025-04-30 02:18:51 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-04-30 02:21:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-30 02:21:37 (10043) [INFO] Trying other mirror. * 2025-04-30 02:21:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-30 02:21:53 (10043) [INFO] Trying other mirror. * 2025-04-30 02:22:23 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-30 02:22:23 (10043) [INFO] Trying other mirror. * 2025-04-30 02:22:39 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-04-30 02:22:39 (10043) [INFO] Trying other mirror. * 2025-04-30 02:23:10 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30660 milliseconds') * 2025-04-30 02:23:10 (10043) [INFO] Trying other mirror. * 2025-04-30 02:23:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-04-30 02:23:41 (10043) [INFO] Trying other mirror. * 2025-04-30 02:24:11 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-04-30 02:24:11 (10043) [INFO] Trying other mirror. * 2025-04-30 02:24:57 (10043) [INFO] Metadata Cache Created * 2025-04-30 02:24:57 (10060) [INFO] * 2025-04-30 02:24:57 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30729 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30660 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-04-30 02:24:57 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-04-30 02:24:57 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-04-30 02:24:57 (10030) [INFO] * 2025-04-30 02:24:57 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-30 02:24:58 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-04-30 02:24:58 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-04-30 02:24:58 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-04-30 02:24:58 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-04-30 02:24:58 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-04-30 02:24:58 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-04-30 02:24:58 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-04-30 02:24:58 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-04-30 02:24:58 (10043) [INFO] : wp-toolkit-thirdparties * 2025-04-30 02:24:59 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-04-30 02:24:59 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-04-30 02:24:59 (10060) [INFO] * 2025-04-30 02:24:59 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-04-30 02:24:59 (10030) [INFO] * 2025-04-30 02:24:59 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-04-30 02:25:00 (10043) [INFO] Determining fastest mirrors * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-04-30 02:25:31 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-04-30 02:25:31 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-04-30 02:25:31 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-04-30 02:25:31 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-04-30 02:25:31 (10043) [INFO] packages for the previous distribution release still work). * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-04-30 02:25:31 (10043) [INFO] yum --disablerepo= ... * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-04-30 02:25:31 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-04-30 02:25:31 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] yum-config-manager --disable * 2025-04-30 02:25:31 (10043) [INFO] or * 2025-04-30 02:25:31 (10043) [INFO] subscription-manager repos --disable= * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-04-30 02:25:31 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-04-30 02:25:31 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-04-30 02:25:31 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-04-30 02:25:31 (10043) [INFO] compromise: * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-04-30 02:25:31 (10043) [INFO] * 2025-04-30 02:25:31 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-04-30 02:25:31 (10060) [INFO] * 2025-04-30 02:25:31 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-04-30 02:25:31 (6278) [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 * 2025-04-30 02:25:32 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-04-30 02:25:33 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-04-30 02:25:33 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-04-30 02:25:33 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-04-30 02:25:33 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-01 01:54:49 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-01 01:58:49 (11113) [INFO] Script is up to date. * 2025-05-01 02:02:53 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-01 02:02:53 (10030) [INFO] * 2025-05-01 02:04:29 (10060) [INFO] * 2025-05-01 02:04:29 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-01 02:04:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-01 02:04:30 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-01 02:04:30 (10030) [INFO] * 2025-05-01 02:11:29 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-01 02:11:29 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-01 02:11:29 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-01 02:11:29 (10030) [INFO] * 2025-05-01 02:11:45 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-01 02:11:48 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-01 02:11:48 (10030) [INFO] * 2025-05-01 02:11:48 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-01 02:11:48 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-01 02:12:19 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-01 02:12:19 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-01 02:12:19 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-01 02:12:19 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-01 02:13:05 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30540 milliseconds') * 2025-05-01 02:13:05 (10043) [INFO] Trying other mirror. * 2025-05-01 02:13:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-01 02:13:36 (10043) [INFO] Trying other mirror. * 2025-05-01 02:16:06 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-01 02:16:06 (10043) [INFO] Trying other mirror. * 2025-05-01 02:16:23 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-01 02:16:23 (10043) [INFO] Trying other mirror. * 2025-05-01 02:16:54 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-01 02:16:54 (10043) [INFO] Trying other mirror. * 2025-05-01 02:17:06 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-01 02:17:06 (10043) [INFO] Trying other mirror. * 2025-05-01 02:17:53 (10043) [INFO] Metadata Cache Created * 2025-05-01 02:17:54 (10060) [INFO] * 2025-05-01 02:17:54 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30540 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-01 02:17:54 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-01 02:17:54 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-01 02:17:54 (10030) [INFO] * 2025-05-01 02:17:54 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-01 02:17:54 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-01 02:17:54 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-01 02:17:54 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-01 02:17:54 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-01 02:17:54 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-01 02:17:54 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-01 02:17:54 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-01 02:17:54 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-01 02:17:54 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-01 02:17:55 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-01 02:17:55 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-01 02:17:56 (10060) [INFO] * 2025-05-01 02:17:56 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-01 02:17:56 (10030) [INFO] * 2025-05-01 02:17:56 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-01 02:17:56 (10043) [INFO] Determining fastest mirrors * 2025-05-01 02:18:29 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-01 02:18:29 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-01 02:18:29 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-01 02:18:29 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-01 02:21:34 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-01 02:21:34 (10043) [INFO] Trying other mirror. * 2025-05-01 02:21:35 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-01 02:21:35 (10043) [INFO] Trying other mirror. * 2025-05-01 02:24:14 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-01 02:24:14 (10043) [INFO] Trying other mirror. * 2025-05-02 02:09:26 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-02 02:13:26 (11113) [INFO] Script is up to date. * 2025-05-02 02:17:29 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-02 02:17:29 (10030) [INFO] * 2025-05-02 02:19:01 (10060) [INFO] * 2025-05-02 02:19:01 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-02 02:19:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-02 02:19:02 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-02 02:19:02 (10030) [INFO] * 2025-05-02 02:31:37 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-02 02:31:37 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-02 02:31:37 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-02 02:31:37 (10030) [INFO] * 2025-05-02 02:31:48 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-02 02:31:53 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-02 02:31:53 (10030) [INFO] * 2025-05-02 02:31:53 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-02 02:31:54 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-02 02:32:24 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-02 02:32:24 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-02 02:32:24 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-02 02:32:24 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-02 02:33:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-05-02 02:33:10 (10043) [INFO] Trying other mirror. * 2025-05-02 02:34:38 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-02 02:34:38 (10043) [INFO] Trying other mirror. * 2025-05-02 02:35:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-02 02:35:41 (10043) [INFO] Trying other mirror. * 2025-05-02 02:35:58 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-02 02:35:58 (10043) [INFO] Trying other mirror. * 2025-05-02 02:36:15 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-02 02:36:15 (10043) [INFO] Trying other mirror. * 2025-05-02 02:36:28 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-02 02:36:28 (10043) [INFO] Trying other mirror. * 2025-05-02 02:36:28 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-02 02:36:28 (10043) [INFO] Trying other mirror. * 2025-05-02 02:36:46 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-02 02:36:46 (10043) [INFO] Trying other mirror. * 2025-05-02 02:36:59 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-02 02:36:59 (10043) [INFO] Trying other mirror. * 2025-05-02 02:37:16 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-02 02:37:16 (10043) [INFO] Trying other mirror. * 2025-05-02 02:37:29 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-02 02:37:29 (10043) [INFO] Trying other mirror. * 2025-05-02 02:37:47 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-02 02:37:47 (10043) [INFO] Trying other mirror. * 2025-05-02 02:38:18 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-02 02:38:18 (10043) [INFO] Trying other mirror. * 2025-05-02 02:38:48 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-02 02:38:48 (10043) [INFO] Trying other mirror. * 2025-05-03 01:49:31 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-03 01:53:31 (11113) [INFO] Script is up to date. * 2025-05-03 01:57:35 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-03 01:57:35 (10030) [INFO] * 2025-05-03 01:58:45 (10060) [INFO] * 2025-05-03 01:58:45 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-03 01:58:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-03 01:58:45 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-03 01:58:45 (10030) [INFO] * 2025-05-03 02:05:46 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-03 02:05:46 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-03 02:05:46 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-03 02:05:46 (10030) [INFO] * 2025-05-03 02:06:09 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-03 02:06:09 (10030) [INFO] * 2025-05-03 02:06:09 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-03 02:06:09 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-03 02:06:40 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-03 02:06:40 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-03 02:06:40 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-03 02:06:40 (10043) [INFO] * epel: mirror.math.princeton.edu * 2025-05-03 02:08:24 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:08:24 (10043) [INFO] Trying other mirror. * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-03 02:08:24 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-03 02:08:24 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-03 02:08:24 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-03 02:08:24 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-03 02:08:24 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-03 02:08:24 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-03 02:08:24 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-03 02:08:24 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-03 02:08:24 (10043) [INFO] or * 2025-05-03 02:08:24 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-03 02:08:24 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-03 02:08:24 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-03 02:08:24 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-03 02:08:24 (10043) [INFO] compromise: * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-03 02:08:24 (10043) [INFO] * 2025-05-03 02:08:24 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-03 02:08:24 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:08:24 (10060) [INFO] * 2025-05-03 02:08:24 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:08:24 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-03 02:08:24 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-03 02:08:24 (10030) [INFO] * 2025-05-03 02:08:25 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-03 02:08:25 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-03 02:08:25 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-03 02:08:25 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-03 02:08:25 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-03 02:08:25 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-03 02:08:25 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-03 02:08:25 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-03 02:08:25 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-03 02:08:25 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-03 02:08:25 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-03 02:08:25 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-03 02:08:25 (10060) [INFO] * 2025-05-03 02:08:25 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-03 02:08:25 (10030) [INFO] * 2025-05-03 02:08:26 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-03 02:08:26 (10043) [INFO] Determining fastest mirrors * 2025-05-03 02:08:59 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-03 02:08:59 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-03 02:08:59 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-03 02:08:59 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-03 02:10:44 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:10:44 (10043) [INFO] Trying other mirror. * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-03 02:10:44 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-03 02:10:44 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-03 02:10:44 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-03 02:10:44 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-03 02:10:44 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-03 02:10:44 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-03 02:10:44 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-03 02:10:44 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-03 02:10:44 (10043) [INFO] or * 2025-05-03 02:10:44 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-03 02:10:44 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-03 02:10:44 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-03 02:10:44 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-03 02:10:44 (10043) [INFO] compromise: * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-03 02:10:44 (10043) [INFO] * 2025-05-03 02:10:44 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-03 02:10:44 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:10:44 (10060) [INFO] * 2025-05-03 02:10:44 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-03 02:10:44 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ1OTE1MzAwOjE3NDYxNzQ1MDA6ClQxKkL3Umysoq7wsmRt_6vOH3fPM5N0dgFR_amvE7T6mco5MKcr5KA1w4_oOTxGZZDj3xTDBGScL-WK4Vz8cvRhEnL-tYVjPaWL6qFmx3dGmD9gG6vTkAXXEWaB-whsZDLD-2YhNB1BBhKG23QCxPBjwM470_ZG7PteNpqi1QPSgnkCgNZWo3eTSas94ny0O-3-WQcIzXDKTgVTIKbtZXU4ujVvg4JqMgYPpOaUrGGLBLRFYahDU4kJxOAyFYa_iXvkbmo_cd0hIyvVKORXxqJMoy3U6blByGwyam98y8LUNH6CpEhgzddQeOmx8r03Un5IEHS6HeqziI8AFYJRXrClxhULgaHclAavr1oU91eEm_diFqS3dwjr8Jw4_NmGQZqJ8L9NusDSa8AxJkqBDBuOxrxK8JVRRpQJOrxbchHrKnB53lJBsnfXogsMYj0KSBNq6UMBaNX6dvIa0LA_m0PACptcaMxPWSunylHhg0-2ilwNfmS6U2AOgG_EhhT9NWhVbRomqIPodXc32P3p_u_i6s5u4ucRCH2AjnlnVTMvTz9YHXW2eLXsOpRmkygaATe3EMlUGj6KK5kd-Vev9sb1MS_fj6OMqaiPvKLk8uLdxac1wZ89jh8uMWduN0R_nvMstbMEu7woy8AMZPawCbXauzccWyY3VerUkVdG3eE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-03 02:10:46 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-03 02:10:46 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-03 02:10:46 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-03 02:10:46 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-03 02:10:46 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-03 02:10:54 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fVQ_w8yCPQ/ea_profile.json * 2025-05-03 02:13:11 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fVQ_w8yCPQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-05-03 02:13:11 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-05-04 01:57:46 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-04 02:01:47 (11113) [INFO] Script is up to date. * 2025-05-04 02:05:50 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-04 02:05:50 (10030) [INFO] * 2025-05-04 02:07:02 (10060) [INFO] * 2025-05-04 02:07:02 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-04 02:07:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-04 02:07:02 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-04 02:07:02 (10030) [INFO] * 2025-05-04 02:14:03 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-04 02:14:03 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-04 02:14:03 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-04 02:14:03 (10030) [INFO] * 2025-05-04 02:14:14 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-04 02:14:18 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-04 02:14:18 (10030) [INFO] * 2025-05-04 02:14:18 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-04 02:14:19 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-04 02:14:49 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-04 02:14:49 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-04 02:14:49 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-04 02:14:49 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-04 02:17:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-04 02:17:36 (10043) [INFO] Trying other mirror. * 2025-05-04 02:17:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-04 02:17:53 (10043) [INFO] Trying other mirror. * 2025-05-04 02:18:22 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-04 02:18:22 (10043) [INFO] Trying other mirror. * 2025-05-04 02:18:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-04 02:18:36 (10043) [INFO] Trying other mirror. * 2025-05-04 02:18:38 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-04 02:18:38 (10043) [INFO] Trying other mirror. * 2025-05-04 02:19:09 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-04 02:19:09 (10043) [INFO] Trying other mirror. * 2025-05-04 02:19:54 (10043) [INFO] Metadata Cache Created * 2025-05-04 02:19:54 (10060) [INFO] * 2025-05-04 02:19:54 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-04 02:19:54 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-04 02:19:54 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-04 02:19:54 (10030) [INFO] * 2025-05-04 02:19:54 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-04 02:19:55 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-04 02:19:55 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-04 02:19:55 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-04 02:19:55 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-04 02:19:55 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-04 02:19:55 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-04 02:19:55 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-04 02:19:55 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-04 02:19:55 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-04 02:19:56 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-04 02:19:56 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-04 02:19:56 (10060) [INFO] * 2025-05-04 02:19:56 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-04 02:19:56 (10030) [INFO] * 2025-05-04 02:19:56 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-04 02:19:57 (10043) [INFO] Determining fastest mirrors * 2025-05-04 02:20:29 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-04 02:20:29 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-04 02:20:29 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-04 02:20:29 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-04 02:23:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-04 02:23:36 (10043) [INFO] Trying other mirror. * 2025-05-04 02:23:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-04 02:23:36 (10043) [INFO] Trying other mirror. * 2025-05-04 02:24:24 (10043) [INFO] http://103.163.138.20/cpanelsync/repos/CentOS/7/EA4/repodata/3d9092d46dd8ee91c18f027dccc09cd7015abd33f01cbdedbdd19fffe52a8461-other.sqlite.bz2: [Errno 14] curl#18 - "transfer closed with 629927 bytes remaining to read" * 2025-05-04 02:24:24 (10043) [INFO] Trying other mirror. * 2025-05-04 02:26:15 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-04 02:26:15 (10043) [INFO] Trying other mirror. * 2025-05-05 01:55:22 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-05 01:59:23 (11113) [INFO] Script is up to date. * 2025-05-05 02:03:26 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-05 02:03:26 (10030) [INFO] * 2025-05-05 02:05:04 (10060) [INFO] * 2025-05-05 02:05:04 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-05 02:05:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-05 02:05:04 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-05 02:05:04 (10030) [INFO] * 2025-05-05 02:12:02 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-05 02:12:02 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-05 02:12:02 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-05 02:12:02 (10030) [INFO] * 2025-05-05 02:12:16 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-05 02:12:21 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-05 02:12:21 (10030) [INFO] * 2025-05-05 02:12:21 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-05 02:12:21 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-05 02:12:51 (10043) [INFO] * EA4: 184.94.196.92 * 2025-05-05 02:12:51 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.92 * 2025-05-05 02:12:51 (10043) [INFO] * cpanel-plugins: 184.94.196.92 * 2025-05-05 02:12:51 (10043) [INFO] * epel: mirror.math.princeton.edu * 2025-05-05 02:15:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-05 02:15:37 (10043) [INFO] Trying other mirror. * 2025-05-05 02:15:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-05 02:15:55 (10043) [INFO] Trying other mirror. * 2025-05-05 02:16:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-05 02:16:53 (10043) [INFO] Trying other mirror. * 2025-05-05 02:16:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-05 02:16:53 (10043) [INFO] Trying other mirror. * 2025-05-05 02:17:24 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-05 02:17:24 (10043) [INFO] Trying other mirror. * 2025-05-05 02:17:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-05 02:17:55 (10043) [INFO] Trying other mirror. * 2025-05-05 02:18:43 (10043) [INFO] Metadata Cache Created * 2025-05-05 02:18:44 (10060) [INFO] * 2025-05-05 02:18:44 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-05-05 02:18:44 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-05 02:18:44 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-05 02:18:44 (10030) [INFO] * 2025-05-05 02:18:44 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-05 02:18:44 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-05 02:18:44 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-05 02:18:44 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-05 02:18:44 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-05 02:18:44 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-05 02:18:44 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-05 02:18:44 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-05 02:18:44 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-05 02:18:44 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-05 02:18:45 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-05 02:18:45 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-05 02:18:45 (10060) [INFO] * 2025-05-05 02:18:45 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-05 02:18:45 (10030) [INFO] * 2025-05-05 02:18:46 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-05 02:18:46 (10043) [INFO] Determining fastest mirrors * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-05-05 02:19:17 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-05 02:19:17 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-05 02:19:17 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-05 02:19:17 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-05 02:19:17 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-05 02:19:17 (10043) [INFO] yum --disablerepo= ... * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-05 02:19:17 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-05 02:19:17 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] yum-config-manager --disable * 2025-05-05 02:19:17 (10043) [INFO] or * 2025-05-05 02:19:17 (10043) [INFO] subscription-manager repos --disable= * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-05 02:19:17 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-05 02:19:17 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-05 02:19:17 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-05 02:19:17 (10043) [INFO] compromise: * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-05-05 02:19:17 (10043) [INFO] * 2025-05-05 02:19:17 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-05-05 02:19:17 (10060) [INFO] * 2025-05-05 02:19:17 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-05 02:19:17 (6278) [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 * 2025-05-05 02:19:19 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-05 02:19:19 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-05 02:19:19 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-05 02:19:19 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-05 02:19:19 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-06 01:53:47 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-06 01:57:48 (11113) [INFO] Script is up to date. * 2025-05-06 02:01:51 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-06 02:01:51 (10030) [INFO] * 2025-05-06 02:03:14 (10060) [INFO] * 2025-05-06 02:03:14 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-06 02:03:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-06 02:03:14 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-06 02:03:14 (10030) [INFO] * 2025-05-06 02:16:37 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-06 02:16:37 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-06 02:16:37 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-06 02:16:37 (10030) [INFO] * 2025-05-06 02:16:48 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-06 02:16:52 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-06 02:16:52 (10030) [INFO] * 2025-05-06 02:16:53 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-06 02:16:53 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-06 02:17:24 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-05-06 02:17:24 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') * 2025-05-06 02:17:24 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-06 02:17:24 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-06 02:17:24 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-06 02:17:24 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-06 02:18:11 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-06 02:18:11 (10043) [INFO] Trying other mirror. * 2025-05-06 02:20:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-06 02:20:41 (10043) [INFO] Trying other mirror. * 2025-05-06 02:21:00 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-06 02:21:00 (10043) [INFO] Trying other mirror. * 2025-05-06 02:21:29 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-06 02:21:29 (10043) [INFO] Trying other mirror. * 2025-05-06 02:21:46 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-06 02:21:46 (10043) [INFO] Trying other mirror. * 2025-05-06 02:22:30 (10043) [INFO] Metadata Cache Created * 2025-05-06 02:22:30 (10060) [INFO] * 2025-05-06 02:22:30 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30596 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-06 02:22:30 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-06 02:22:30 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-06 02:22:30 (10030) [INFO] * 2025-05-06 02:22:31 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-06 02:22:31 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-06 02:22:31 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-06 02:22:31 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-06 02:22:31 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-06 02:22:31 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-06 02:22:31 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-06 02:22:31 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-06 02:22:31 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-06 02:22:31 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-06 02:22:32 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-06 02:22:32 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-06 02:22:32 (10060) [INFO] * 2025-05-06 02:22:32 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-06 02:22:32 (10030) [INFO] * 2025-05-06 02:22:32 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-06 02:22:32 (10043) [INFO] Determining fastest mirrors * 2025-05-06 02:23:04 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-06 02:23:04 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-06 02:23:04 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-06 02:23:04 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-07 01:55:05 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-07 01:59:05 (11113) [INFO] Script is up to date. * 2025-05-07 02:03:08 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-07 02:03:08 (10030) [INFO] * 2025-05-07 02:04:38 (10060) [INFO] * 2025-05-07 02:04:38 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-07 02:04:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-07 02:04:39 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-07 02:04:39 (10030) [INFO] * 2025-05-07 02:07:00 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-07 02:07:00 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-07 02:07:00 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-07 02:07:00 (10030) [INFO] * 2025-05-07 02:07:14 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-07 02:07:18 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-07 02:07:18 (10030) [INFO] * 2025-05-07 02:07:18 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-07 02:07:18 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-07 02:07:48 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-07 02:07:48 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-07 02:07:48 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-07 02:07:48 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-07 02:08:35 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-07 02:08:35 (10043) [INFO] Trying other mirror. * 2025-05-07 02:09:06 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30887 milliseconds') * 2025-05-07 02:09:06 (10043) [INFO] Trying other mirror. * 2025-05-07 02:11:38 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-07 02:11:38 (10043) [INFO] Trying other mirror. * 2025-05-07 02:11:56 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-07 02:11:56 (10043) [INFO] Trying other mirror. * 2025-05-07 02:12:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-07 02:12:38 (10043) [INFO] Trying other mirror. * 2025-05-07 02:12:40 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-07 02:12:40 (10043) [INFO] Trying other mirror. * 2025-05-07 02:12:42 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-07 02:12:42 (10043) [INFO] Trying other mirror. * 2025-05-07 02:13:09 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-07 02:13:09 (10043) [INFO] Trying other mirror. * 2025-05-07 02:13:12 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-07 02:13:12 (10043) [INFO] Trying other mirror. * 2025-05-07 02:13:43 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-07 02:13:43 (10043) [INFO] Trying other mirror. * 2025-05-07 02:14:32 (10043) [INFO] Metadata Cache Created * 2025-05-07 02:14:32 (10060) [INFO] * 2025-05-07 02:14:32 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30887 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-07 02:14:32 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-07 02:14:32 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-07 02:14:32 (10030) [INFO] * 2025-05-07 02:14:32 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-07 02:14:32 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-07 02:14:32 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-07 02:14:32 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-07 02:14:32 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-07 02:14:32 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-07 02:14:32 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-07 02:14:32 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-07 02:14:32 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-07 02:14:32 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-07 02:14:33 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-07 02:14:33 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-07 02:14:33 (10060) [INFO] * 2025-05-07 02:14:33 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-07 02:14:33 (10030) [INFO] * 2025-05-07 02:14:34 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-07 02:14:34 (10043) [INFO] Determining fastest mirrors * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-05-07 02:15:06 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-07 02:15:06 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-07 02:15:06 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-07 02:15:06 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-07 02:15:06 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-07 02:15:06 (10043) [INFO] yum --disablerepo= ... * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-07 02:15:06 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-07 02:15:06 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] yum-config-manager --disable * 2025-05-07 02:15:06 (10043) [INFO] or * 2025-05-07 02:15:06 (10043) [INFO] subscription-manager repos --disable= * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-07 02:15:06 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-07 02:15:06 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-07 02:15:06 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-07 02:15:06 (10043) [INFO] compromise: * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-05-07 02:15:06 (10043) [INFO] * 2025-05-07 02:15:06 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-05-07 02:15:06 (10060) [INFO] * 2025-05-07 02:15:06 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-07 02:15:06 (6278) [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 * 2025-05-07 02:15:08 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-07 02:15:08 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-07 02:15:08 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-07 02:15:08 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-07 02:15:08 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-08 01:56:22 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-08 02:00:23 (11113) [INFO] Script is up to date. * 2025-05-08 02:04:26 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-08 02:04:26 (10030) [INFO] * 2025-05-08 02:05:56 (10060) [INFO] * 2025-05-08 02:05:56 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-08 02:05:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-08 02:05:57 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-08 02:05:57 (10030) [INFO] * 2025-05-08 02:12:57 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-08 02:12:57 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-08 02:12:57 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-08 02:12:57 (10030) [INFO] * 2025-05-08 02:13:11 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-08 02:13:14 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-08 02:13:14 (10030) [INFO] * 2025-05-08 02:13:15 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-08 02:13:15 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-08 02:13:45 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-08 02:13:45 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-08 02:13:45 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-08 02:13:45 (10043) [INFO] * epel: mirror.math.princeton.edu * 2025-05-08 02:14:31 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-05-08 02:14:31 (10043) [INFO] Trying other mirror. * 2025-05-08 02:17:01 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-08 02:17:01 (10043) [INFO] Trying other mirror. * 2025-05-08 02:17:17 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-08 02:17:17 (10043) [INFO] Trying other mirror. * 2025-05-08 02:17:47 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-08 02:17:47 (10043) [INFO] Trying other mirror. * 2025-05-08 02:18:01 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-08 02:18:01 (10043) [INFO] Trying other mirror. * 2025-05-08 02:18:18 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-08 02:18:18 (10043) [INFO] Trying other mirror. * 2025-05-08 02:18:31 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-08 02:18:31 (10043) [INFO] Trying other mirror. * 2025-05-08 02:18:48 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-08 02:18:48 (10043) [INFO] Trying other mirror. * 2025-05-08 02:19:30 (10043) [INFO] Metadata Cache Created * 2025-05-08 02:19:30 (10060) [INFO] * 2025-05-08 02:19:30 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-08 02:19:30 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-08 02:19:30 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-08 02:19:30 (10030) [INFO] * 2025-05-08 02:19:31 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-08 02:19:31 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-08 02:19:31 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-08 02:19:31 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-08 02:19:31 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-08 02:19:31 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-08 02:19:31 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-08 02:19:31 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-08 02:19:31 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-08 02:19:31 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-08 02:19:32 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-08 02:19:32 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-08 02:19:32 (10060) [INFO] * 2025-05-08 02:19:32 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-08 02:19:32 (10030) [INFO] * 2025-05-08 02:19:32 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-08 02:19:33 (10043) [INFO] Determining fastest mirrors * 2025-05-08 02:20:05 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-08 02:20:05 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-08 02:20:05 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-08 02:20:05 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-08 02:23:09 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30721 milliseconds') * 2025-05-08 02:23:09 (10043) [INFO] Trying other mirror. * 2025-05-08 02:23:09 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-08 02:23:09 (10043) [INFO] Trying other mirror. * 2025-05-08 02:23:40 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-08 02:23:40 (10043) [INFO] Trying other mirror. * 2025-05-08 02:24:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-08 02:24:10 (10043) [INFO] Trying other mirror. * 2025-05-08 02:25:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-08 02:25:49 (10043) [INFO] Trying other mirror. * 2025-05-08 02:25:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-08 02:25:49 (10043) [INFO] Trying other mirror. * 2025-05-09 01:57:47 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-09 02:01:47 (11113) [INFO] Script is up to date. * 2025-05-09 02:05:51 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-09 02:05:51 (10030) [INFO] * 2025-05-09 02:07:23 (10060) [INFO] * 2025-05-09 02:07:23 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-09 02:07:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-09 02:07:24 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-09 02:07:24 (10030) [INFO] * 2025-05-09 02:14:23 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-09 02:14:23 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-09 02:14:24 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-09 02:14:24 (10030) [INFO] * 2025-05-09 02:14:37 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-09 02:14:41 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-09 02:14:41 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-09 02:14:41 (10030) [INFO] * 2025-05-09 02:14:41 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-09 02:14:42 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-09 02:15:12 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-05-09 02:15:12 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-05-09 02:15:12 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-09 02:15:12 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-09 02:15:12 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-09 02:15:12 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-09 02:15:58 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') * 2025-05-09 02:15:58 (10043) [INFO] Trying other mirror. * 2025-05-09 02:16:29 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-09 02:16:29 (10043) [INFO] Trying other mirror. * 2025-05-09 02:19:21 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-09 02:19:21 (10043) [INFO] Trying other mirror. * 2025-05-09 02:19:39 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-09 02:19:39 (10043) [INFO] Trying other mirror. * 2025-05-09 02:20:09 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-09 02:20:09 (10043) [INFO] Trying other mirror. * 2025-05-09 02:20:23 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-09 02:20:23 (10043) [INFO] Trying other mirror. * 2025-05-09 02:20:24 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-09 02:20:24 (10043) [INFO] Trying other mirror. * 2025-05-09 02:20:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-09 02:20:53 (10043) [INFO] Trying other mirror. * 2025-05-09 02:21:42 (10043) [INFO] Metadata Cache Created * 2025-05-09 02:21:42 (10060) [INFO] * 2025-05-09 02:21:42 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-09 02:21:42 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-09 02:21:42 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-09 02:21:42 (10030) [INFO] * 2025-05-09 02:21:43 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-09 02:21:43 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-09 02:21:43 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-09 02:21:43 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-09 02:21:43 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-09 02:21:43 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-09 02:21:43 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-09 02:21:43 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-09 02:21:43 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-09 02:21:43 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-09 02:21:44 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-09 02:21:44 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-09 02:21:44 (10060) [INFO] * 2025-05-09 02:21:44 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-09 02:21:44 (10030) [INFO] * 2025-05-09 02:21:45 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-09 02:21:45 (10043) [INFO] Determining fastest mirrors * 2025-05-09 02:22:18 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-09 02:22:18 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-09 02:22:18 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-09 02:22:18 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-09 02:23:04 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30536 milliseconds') * 2025-05-09 02:23:04 (10043) [INFO] Trying other mirror. * 2025-05-09 02:26:15 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-09 02:26:15 (10043) [INFO] Trying other mirror. * 2025-05-09 02:26:15 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30887 milliseconds') * 2025-05-09 02:26:15 (10043) [INFO] Trying other mirror. * 2025-05-09 02:26:45 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-09 02:26:45 (10043) [INFO] Trying other mirror. * 2025-05-09 02:27:16 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-09 02:27:16 (10043) [INFO] Trying other mirror. * 2025-05-10 02:04:17 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-10 02:08:18 (11113) [INFO] Script is up to date. * 2025-05-10 02:12:21 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-10 02:12:21 (10030) [INFO] * 2025-05-10 02:13:30 (10060) [INFO] * 2025-05-10 02:13:30 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-10 02:13:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-10 02:13:30 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-10 02:13:30 (10030) [INFO] * 2025-05-10 02:13:34 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-10 02:13:34 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-10 02:13:34 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-10 02:13:34 (10030) [INFO] * 2025-05-10 02:13:48 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-10 02:13:50 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-10 02:13:50 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-10 02:13:50 (10030) [INFO] * 2025-05-10 02:13:51 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-10 02:13:51 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-10 02:14:21 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-10 02:14:21 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-10 02:14:21 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-10 02:14:21 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-10 02:17:30 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-05-10 02:17:30 (10043) [INFO] Trying other mirror. * 2025-05-10 02:17:47 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:17:47 (10043) [INFO] Trying other mirror. * 2025-05-10 02:18:16 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:18:16 (10043) [INFO] Trying other mirror. * 2025-05-10 02:18:26 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:18:26 (10043) [INFO] Trying other mirror. * 2025-05-10 02:18:30 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-10 02:18:30 (10043) [INFO] Trying other mirror. * 2025-05-10 02:18:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-10 02:18:57 (10043) [INFO] Trying other mirror. * 2025-05-10 02:19:01 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:19:01 (10043) [INFO] Trying other mirror. * 2025-05-10 02:19:27 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:19:27 (10043) [INFO] Trying other mirror. * 2025-05-10 02:19:31 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:19:31 (10043) [INFO] Trying other mirror. * 2025-05-10 02:20:14 (10043) [INFO] Metadata Cache Created * 2025-05-10 02:20:14 (10060) [INFO] * 2025-05-10 02:20:14 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-10 02:20:14 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-10 02:20:14 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-10 02:20:14 (10030) [INFO] * 2025-05-10 02:20:14 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-10 02:20:15 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-10 02:20:15 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-10 02:20:15 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-10 02:20:15 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-10 02:20:15 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-10 02:20:15 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-10 02:20:15 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-10 02:20:15 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-10 02:20:15 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-10 02:20:15 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-10 02:20:15 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-10 02:20:15 (10060) [INFO] * 2025-05-10 02:20:15 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-10 02:20:15 (10030) [INFO] * 2025-05-10 02:20:16 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-10 02:20:16 (10043) [INFO] Determining fastest mirrors * 2025-05-10 02:20:48 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-10 02:20:48 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-10 02:20:48 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-10 02:20:48 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-10 02:24:15 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-10 02:24:15 (10043) [INFO] Trying other mirror. * 2025-05-10 02:24:16 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:24:16 (10043) [INFO] Trying other mirror. * 2025-05-10 02:24:46 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-10 02:24:46 (10043) [INFO] Trying other mirror. * 2025-05-10 02:25:17 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:25:17 (10043) [INFO] Trying other mirror. * 2025-05-10 02:27:18 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-10 02:27:18 (10043) [INFO] Trying other mirror. * 2025-05-10 02:27:18 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-10 02:27:18 (10043) [INFO] Trying other mirror. * 2025-05-10 02:27:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-05-10 02:27:49 (10043) [INFO] Trying other mirror. * 2025-05-10 02:30:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-10 02:30:38 (10043) [INFO] Trying other mirror. * 2025-05-10 02:30:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:30:38 (10043) [INFO] Trying other mirror. * 2025-05-10 02:31:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-10 02:31:41 (10043) [INFO] Trying other mirror. * 2025-05-10 02:32:11 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:32:11 (10043) [INFO] Trying other mirror. * 2025-05-10 02:32:42 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-10 02:32:42 (10043) [INFO] Trying other mirror. * 2025-05-10 02:33:12 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:33:12 (10043) [INFO] Trying other mirror. * 2025-05-10 02:33:12 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-10 02:33:12 (10043) [INFO] Trying other mirror. * 2025-05-10 02:33:43 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-10 02:33:43 (10043) [INFO] Trying other mirror. * 2025-05-11 01:48:51 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-11 01:52:51 (11113) [INFO] Script is up to date. * 2025-05-11 01:56:55 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-11 01:56:55 (10030) [INFO] * 2025-05-11 01:58:06 (10060) [INFO] * 2025-05-11 01:58:06 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-11 01:58:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-11 01:58:06 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-11 01:58:06 (10030) [INFO] * 2025-05-11 02:05:07 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-11 02:05:07 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-11 02:05:07 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-11 02:05:07 (10030) [INFO] * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-11 02:05:28 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-11 02:05:28 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-11 02:05:28 (10030) [INFO] * 2025-05-11 02:05:29 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-11 02:05:29 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-11 02:05:59 (10043) [INFO] * EA4: 184.94.196.97 * 2025-05-11 02:05:59 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 2025-05-11 02:05:59 (10043) [INFO] * cpanel-plugins: 184.94.196.97 * 2025-05-11 02:05:59 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-11 02:06:46 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-11 02:06:46 (10043) [INFO] Trying other mirror. * 2025-05-11 02:08:36 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:08:36 (10043) [INFO] Trying other mirror. * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-11 02:08:36 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-11 02:08:36 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-11 02:08:36 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-11 02:08:36 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-11 02:08:36 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-11 02:08:36 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-11 02:08:36 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-11 02:08:36 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-11 02:08:36 (10043) [INFO] or * 2025-05-11 02:08:36 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-11 02:08:36 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-11 02:08:36 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-11 02:08:36 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-11 02:08:36 (10043) [INFO] compromise: * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-11 02:08:36 (10043) [INFO] * 2025-05-11 02:08:36 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-11 02:08:36 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:08:36 (10060) [INFO] * 2025-05-11 02:08:36 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:08:36 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-11 02:08:36 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-11 02:08:36 (10030) [INFO] * 2025-05-11 02:08:37 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-11 02:08:37 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-11 02:08:37 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-11 02:08:37 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-11 02:08:37 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-11 02:08:37 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-11 02:08:37 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-11 02:08:37 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-11 02:08:37 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-11 02:08:37 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-11 02:08:37 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-11 02:08:37 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-11 02:08:37 (10060) [INFO] * 2025-05-11 02:08:37 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-11 02:08:37 (10030) [INFO] * 2025-05-11 02:08:38 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-11 02:08:38 (10043) [INFO] Determining fastest mirrors * 2025-05-11 02:09:10 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-11 02:09:10 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-11 02:09:10 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-11 02:09:10 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-11 02:09:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') * 2025-05-11 02:09:57 (10043) [INFO] Trying other mirror. * 2025-05-11 02:11:49 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:11:49 (10043) [INFO] Trying other mirror. * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-11 02:11:49 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-11 02:11:49 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-11 02:11:49 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-11 02:11:49 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-11 02:11:49 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-11 02:11:49 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-11 02:11:49 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-11 02:11:49 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-11 02:11:49 (10043) [INFO] or * 2025-05-11 02:11:49 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-11 02:11:49 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-11 02:11:49 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-11 02:11:49 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-11 02:11:49 (10043) [INFO] compromise: * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-11 02:11:49 (10043) [INFO] * 2025-05-11 02:11:49 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-11 02:11:49 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:11:49 (10060) [INFO] * 2025-05-11 02:11:49 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-11 02:11:49 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-11 02:11:51 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-11 02:11:51 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-11 02:11:51 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-11 02:11:51 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-11 02:11:51 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-12 01:47:35 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-12 01:51:36 (11113) [INFO] Script is up to date. * 2025-05-12 01:55:39 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-12 01:55:39 (10030) [INFO] * 2025-05-12 01:57:14 (10060) [INFO] * 2025-05-12 01:57:14 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-12 01:57:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-12 01:57:15 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-12 01:57:15 (10030) [INFO] * 2025-05-12 01:57:19 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-12 01:57:19 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-12 01:57:19 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-12 01:57:19 (10030) [INFO] * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-12 01:57:41 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-12 01:57:41 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-12 01:57:41 (10030) [INFO] * 2025-05-12 01:57:41 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-12 01:57:41 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-12 01:58:13 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-12 01:58:13 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-12 01:58:13 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-12 01:58:13 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-12 02:00:19 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:00:19 (10043) [INFO] Trying other mirror. * 2025-05-12 02:00:19 (10043) [INFO] * 2025-05-12 02:00:19 (10043) [INFO] * 2025-05-12 02:00:19 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-12 02:00:19 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-12 02:00:20 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-12 02:00:20 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-12 02:00:20 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-12 02:00:20 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-12 02:00:20 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-12 02:00:20 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-12 02:00:20 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-12 02:00:20 (10043) [INFO] or * 2025-05-12 02:00:20 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-12 02:00:20 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-12 02:00:20 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-12 02:00:20 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-12 02:00:20 (10043) [INFO] compromise: * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-12 02:00:20 (10043) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-12 02:00:20 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:00:20 (10060) [INFO] * 2025-05-12 02:00:20 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:00:20 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-12 02:00:20 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-12 02:00:20 (10030) [INFO] * 2025-05-12 02:00:20 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-12 02:00:20 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-12 02:00:20 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-12 02:00:20 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-12 02:00:20 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-12 02:00:20 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-12 02:00:20 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-12 02:00:20 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-12 02:00:20 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-12 02:00:20 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-12 02:00:21 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-12 02:00:21 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-12 02:00:21 (10060) [INFO] * 2025-05-12 02:00:21 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-12 02:00:21 (10030) [INFO] * 2025-05-12 02:00:21 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-12 02:00:21 (10043) [INFO] Determining fastest mirrors * 2025-05-12 02:00:53 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-12 02:00:53 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-12 02:00:53 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-12 02:00:53 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-12 02:01:39 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-12 02:01:39 (10043) [INFO] Trying other mirror. * 2025-05-12 02:02:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-12 02:02:10 (10043) [INFO] Trying other mirror. * 2025-05-12 02:04:01 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:04:01 (10043) [INFO] Trying other mirror. * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-12 02:04:01 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-12 02:04:01 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-12 02:04:01 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-12 02:04:01 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-12 02:04:01 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-12 02:04:01 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-12 02:04:01 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-12 02:04:01 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-12 02:04:01 (10043) [INFO] or * 2025-05-12 02:04:01 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-12 02:04:01 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-12 02:04:01 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-12 02:04:01 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-12 02:04:01 (10043) [INFO] compromise: * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-12 02:04:01 (10043) [INFO] * 2025-05-12 02:04:01 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-12 02:04:01 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:04:01 (10060) [INFO] * 2025-05-12 02:04:01 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-12 02:04:01 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-12 02:04:03 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-12 02:04:03 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-12 02:04:03 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-12 02:04:03 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-12 02:04:03 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-12 02:04:11 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/s5ZJxJWgI7/ea_profile.json * 2025-05-12 02:07:22 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/s5ZJxJWgI7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-05-12 02:07:22 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-05-13 01:46:29 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-13 01:50:29 (11113) [INFO] Script is up to date. * 2025-05-13 01:54:33 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-13 01:54:33 (10030) [INFO] * 2025-05-13 01:56:13 (10060) [INFO] * 2025-05-13 01:56:13 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-13 01:56:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-13 01:56:13 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-13 01:56:13 (10030) [INFO] * 2025-05-13 01:56:18 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-13 01:56:18 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-13 01:56:18 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-13 01:56:18 (10030) [INFO] * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-13 01:56:40 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-13 01:56:40 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-13 01:56:40 (10030) [INFO] * 2025-05-13 01:56:40 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-13 01:56:41 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-13 01:57:11 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-13 01:57:11 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-13 01:57:11 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-13 01:57:11 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-13 01:59:18 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 01:59:18 (10043) [INFO] Trying other mirror. * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-13 01:59:18 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-13 01:59:18 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-13 01:59:18 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-13 01:59:18 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-13 01:59:18 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-13 01:59:18 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-13 01:59:18 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-13 01:59:18 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-13 01:59:18 (10043) [INFO] or * 2025-05-13 01:59:18 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-13 01:59:18 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-13 01:59:18 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-13 01:59:18 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-13 01:59:18 (10043) [INFO] compromise: * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-13 01:59:18 (10043) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-13 01:59:18 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 01:59:18 (10060) [INFO] * 2025-05-13 01:59:18 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 01:59:18 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-13 01:59:18 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-13 01:59:18 (10030) [INFO] * 2025-05-13 01:59:18 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-13 01:59:19 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-13 01:59:19 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-13 01:59:19 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-13 01:59:19 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-13 01:59:19 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-13 01:59:19 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-13 01:59:19 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-13 01:59:19 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-13 01:59:19 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-13 01:59:19 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-13 01:59:19 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-13 01:59:19 (10060) [INFO] * 2025-05-13 01:59:19 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-13 01:59:19 (10030) [INFO] * 2025-05-13 01:59:19 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-13 01:59:20 (10043) [INFO] Determining fastest mirrors * 2025-05-13 01:59:52 (10043) [INFO] * EA4: 184.94.196.94 * 2025-05-13 01:59:52 (10043) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 2025-05-13 01:59:52 (10043) [INFO] * cpanel-plugins: 184.94.196.94 * 2025-05-13 01:59:52 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-13 02:00:39 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-13 02:00:39 (10043) [INFO] Trying other mirror. * 2025-05-13 02:01:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-13 02:01:10 (10043) [INFO] Trying other mirror. * 2025-05-13 02:01:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-13 02:01:41 (10043) [INFO] Trying other mirror. * 2025-05-13 02:02:12 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-05-13 02:02:12 (10043) [INFO] Trying other mirror. * 2025-05-13 02:04:03 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 02:04:03 (10043) [INFO] Trying other mirror. * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-13 02:04:03 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-13 02:04:03 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-13 02:04:03 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-13 02:04:03 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-13 02:04:03 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-13 02:04:03 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-13 02:04:03 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-13 02:04:03 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-13 02:04:03 (10043) [INFO] or * 2025-05-13 02:04:03 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-13 02:04:03 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-13 02:04:03 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-13 02:04:03 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-13 02:04:03 (10043) [INFO] compromise: * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-13 02:04:03 (10043) [INFO] * 2025-05-13 02:04:03 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-13 02:04:03 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 02:04:03 (10060) [INFO] * 2025-05-13 02:04:03 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-13 02:04:03 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-13 02:04:05 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-13 02:04:05 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-13 02:04:05 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-13 02:04:05 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-13 02:04:05 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-13 02:04:13 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yXqXylk9e9/ea_profile.json * 2025-05-13 02:06:54 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yXqXylk9e9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-05-13 02:06:54 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-05-14 01:45:47 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-14 01:49:47 (11113) [INFO] Script is up to date. * 2025-05-14 01:53:51 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-14 01:53:51 (10030) [INFO] * 2025-05-14 01:55:30 (10060) [INFO] * 2025-05-14 01:55:30 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-14 01:55:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-14 01:55:30 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-14 01:55:30 (10030) [INFO] * 2025-05-14 01:55:35 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-14 01:55:35 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-14 01:55:35 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-14 01:55:35 (10030) [INFO] * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-14 01:55:57 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-14 01:55:57 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-14 01:55:57 (10030) [INFO] * 2025-05-14 01:55:57 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-14 01:55:58 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-14 01:56:28 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-05-14 01:56:28 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-05-14 01:56:28 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-14 01:56:28 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-14 01:56:28 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-14 01:56:28 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-14 01:58:34 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 01:58:34 (10043) [INFO] Trying other mirror. * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-14 01:58:34 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-14 01:58:34 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-14 01:58:34 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-14 01:58:34 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-14 01:58:34 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-14 01:58:34 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-14 01:58:34 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-14 01:58:34 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-14 01:58:34 (10043) [INFO] or * 2025-05-14 01:58:34 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-14 01:58:34 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-14 01:58:34 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-14 01:58:34 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-14 01:58:34 (10043) [INFO] compromise: * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-14 01:58:34 (10043) [INFO] * 2025-05-14 01:58:34 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-14 01:58:34 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 01:58:34 (10060) [INFO] * 2025-05-14 01:58:34 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 01:58:34 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-14 01:58:34 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-14 01:58:34 (10030) [INFO] * 2025-05-14 01:58:35 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-14 01:58:35 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-14 01:58:35 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-14 01:58:35 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-14 01:58:35 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-14 01:58:35 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-14 01:58:35 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-14 01:58:35 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-14 01:58:35 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-14 01:58:35 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-14 01:58:35 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-14 01:58:35 (10043) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2025-05-14 01:58:35 (10060) [INFO] * 2025-05-14 01:58:35 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-14 01:58:35 (10030) [INFO] * 2025-05-14 01:58:36 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-14 01:58:36 (10043) [INFO] Determining fastest mirrors * 2025-05-14 01:59:10 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-14 01:59:10 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-14 01:59:10 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-14 01:59:11 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-14 02:01:17 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 02:01:17 (10043) [INFO] Trying other mirror. * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-14 02:01:17 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-14 02:01:17 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-14 02:01:17 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-14 02:01:17 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-14 02:01:17 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-14 02:01:17 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-14 02:01:17 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-14 02:01:17 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-14 02:01:17 (10043) [INFO] or * 2025-05-14 02:01:17 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-14 02:01:17 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-14 02:01:17 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-14 02:01:17 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-14 02:01:17 (10043) [INFO] compromise: * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-14 02:01:17 (10043) [INFO] * 2025-05-14 02:01:17 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-14 02:01:17 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 02:01:17 (10060) [INFO] * 2025-05-14 02:01:17 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-14 02:01:17 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ2NjE2MzM2OjE3NDY4NzU1MzY6WVeVq6I8Cq1P9MGq8zFSZAPURIoBi2-qf3w-ZfVVyT2VP52yKIggUnKvWBePA_oGddm24ZiQREnkUiEIwNKoiakQd5C5f5oxmfEWWqTeZ_SR-v0-Ws8STcDc98ZCAesKbuFXIHlYpSJ-Erwjm7j77_EIVPswIIIUSTJ9qV5yGCqwOCUtG9dzYMRivPGm0IRuyRQnqDAVsmA04xHPoCG_OlMpV4kYxc_nTWPdqTasQ4xwVxWoyUxmdz5nhn1Pui4002luSeuhwVlgjVp_0TXtpy8zaF0ontSQLcUzdNkEOhbVBVyhaLBpdOuy9enuQBzGfi1uIv_9fhRed55TTKNfW3KOJY3uL-Binvk8FuVRiUkTCvFiBvV0BPNi6YK6EM5r4kCYhGp0O5ph-SqYxg0xn28Unl6f2R2pju93sDMdc9tZxGv1q_Dy8zuQ4Lc43P6YrOu29jflKRDV7XOSQCXbkp2GIYChJaLzfE0osKP-V2Bqegl0i1bgCUmLUNap69s3G2AU-g4vDK7B84yVEoT6xT0dYtp4081dg4BxQvA5RKtDROy2WEgDFJw1yVkIGFJ22D9MNq3Z1wW6Sz3NoMe4C7q7VwFN9p2r59L1IZ6xASUARZVBWxI0izx9VsMuP89WIy0yPyt66q1SY7MtVO3AFPFnTrFRddaD2sj5ExG7BWE=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-14 02:01:19 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-14 02:01:19 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-14 02:01:19 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-14 02:01:19 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-14 02:01:19 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-14 02:01:27 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SZmTcX5smK/ea_profile.json * 2025-05-14 02:04:05 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SZmTcX5smK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-05-14 02:04:05 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-05-15 02:33:19 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-15 02:37:19 (11113) [INFO] Script is up to date. * 2025-05-15 02:41:23 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-15 02:41:23 (10030) [INFO] * 2025-05-15 02:43:05 (10060) [INFO] * 2025-05-15 02:43:05 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-15 02:43:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-15 02:43:06 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-15 02:43:06 (10030) [INFO] * 2025-05-15 02:50:06 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-15 02:50:06 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-15 02:50:06 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-15 02:50:06 (10030) [INFO] * 2025-05-15 02:50:20 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-15 02:50:24 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-15 02:50:24 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-15 02:50:24 (10030) [INFO] * 2025-05-15 02:50:24 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-15 02:50:25 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-15 02:50:54 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-15 02:50:54 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-15 02:50:54 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-15 02:50:54 (10043) [INFO] * epel: dl.fedoraproject.org * 2025-05-15 02:54:03 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:54:03 (10043) [INFO] Trying other mirror. * 2025-05-15 02:54:04 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:54:04 (10043) [INFO] Trying other mirror. * 2025-05-15 02:55:15 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:55:15 (10043) [INFO] Trying other mirror. * 2025-05-15 02:55:50 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:55:50 (10043) [INFO] Trying other mirror. * 2025-05-15 02:55:53 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:55:53 (10043) [INFO] Trying other mirror. * 2025-05-15 02:56:14 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:56:14 (10043) [INFO] Trying other mirror. * 2025-05-15 02:56:44 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:56:44 (10043) [INFO] Trying other mirror. * 2025-05-15 02:56:44 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:56:44 (10043) [INFO] Trying other mirror. * 2025-05-15 02:57:15 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:57:15 (10043) [INFO] Trying other mirror. * 2025-05-15 02:57:15 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-15 02:57:15 (10043) [INFO] Trying other mirror. * 2025-05-15 02:57:46 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-15 02:57:46 (10043) [INFO] Trying other mirror. * 2025-05-15 02:58:16 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:58:16 (10043) [INFO] Trying other mirror. * 2025-05-15 02:58:16 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-15 02:58:16 (10043) [INFO] Trying other mirror. * 2025-05-15 02:58:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-15 02:58:47 (10043) [INFO] Trying other mirror. * 2025-05-15 02:59:17 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-15 02:59:17 (10043) [INFO] Trying other mirror. * 2025-05-15 02:59:48 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-15 02:59:48 (10043) [INFO] Trying other mirror. * 2025-05-15 03:00:19 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-15 03:00:19 (10043) [INFO] Trying other mirror. * 2025-05-15 03:00:49 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-15 03:00:49 (10043) [INFO] Trying other mirror. * 2025-05-15 03:02:08 (10043) [INFO] Metadata Cache Created * 2025-05-15 03:02:08 (10060) [INFO] * 2025-05-15 03:02:08 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-05-15 03:02:08 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-15 03:02:08 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-15 03:02:08 (10030) [INFO] * 2025-05-15 03:02:08 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-15 03:02:09 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-15 03:02:09 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-15 03:02:09 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-15 03:02:09 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-15 03:02:09 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-15 03:02:09 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-15 03:02:09 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-15 03:02:09 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-15 03:02:09 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-15 03:02:10 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-15 03:02:10 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-15 03:02:10 (10060) [INFO] * 2025-05-15 03:02:10 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-15 03:02:10 (10030) [INFO] * 2025-05-15 03:02:10 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-15 03:02:10 (10043) [INFO] Determining fastest mirrors * 2025-05-15 03:02:44 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-15 03:02:44 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-15 03:02:44 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-15 03:02:44 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-15 03:02:59 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:02:59 (10043) [INFO] Trying other mirror. * 2025-05-15 03:02:59 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:02:59 (10043) [INFO] Trying other mirror. * 2025-05-15 03:02:59 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:02:59 (10043) [INFO] Trying other mirror. * 2025-05-15 03:02:59 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:02:59 (10043) [INFO] Trying other mirror. * 2025-05-15 03:02:59 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:02:59 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:00 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:00 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:01 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:01 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:01 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:01 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:02 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:02 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] Trying other mirror. * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] One of the configured repositories failed (MariaDB100), * 2025-05-15 03:03:03 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-15 03:03:03 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-15 03:03:03 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-15 03:03:03 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-15 03:03:03 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-15 03:03:03 (10043) [INFO] yum --disablerepo=MariaDB100 ... * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-15 03:03:03 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-15 03:03:03 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] yum-config-manager --disable MariaDB100 * 2025-05-15 03:03:03 (10043) [INFO] or * 2025-05-15 03:03:03 (10043) [INFO] subscription-manager repos --disable=MariaDB100 * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-15 03:03:03 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-15 03:03:03 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-15 03:03:03 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-15 03:03:03 (10043) [INFO] compromise: * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true * 2025-05-15 03:03:03 (10043) [INFO] * 2025-05-15 03:03:03 (10043) [INFO] failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10043) [INFO] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:03 (10060) [INFO] * 2025-05-15 03:03:03 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-15 03:03:03 (6278) [ERROR] https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" Trying other mirror. One of the configured repositories failed (MariaDB100), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=MariaDB100 ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable MariaDB100 or subscription-manager repos --disable=MariaDB100 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=MariaDB100.skip_if_unavailable=true failure: repodata/repomd.xml from MariaDB100: [Errno 256] No more mirrors to try. https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" https://archive.mariadb.org/mariadb-10.0/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to archive.mariadb.org:443; Network is unreachable" * 2025-05-15 03:03:05 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-15 03:03:05 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-15 03:03:05 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-15 03:03:05 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-15 03:03:05 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-16 01:46:52 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-16 01:50:52 (11113) [INFO] Script is up to date. * 2025-05-16 01:54:56 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-16 01:54:56 (10030) [INFO] * 2025-05-16 01:56:41 (10060) [INFO] * 2025-05-16 01:56:41 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-16 01:56:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-16 01:56:41 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-16 01:56:41 (10030) [INFO] * 2025-05-17 01:47:28 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-17 01:51:28 (11113) [INFO] Script is up to date. * 2025-05-17 01:55:32 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-17 01:55:32 (10030) [INFO] * 2025-05-17 01:56:45 (10060) [INFO] * 2025-05-17 01:56:45 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-17 01:56:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-17 01:56:46 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-17 01:56:46 (10030) [INFO] * 2025-05-17 02:03:47 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-17 02:03:47 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-17 02:03:47 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-17 02:03:47 (10030) [INFO] * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-17 02:06:06 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-17 02:06:06 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-17 02:06:06 (10030) [INFO] * 2025-05-17 02:06:06 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-17 02:06:06 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-17 02:06:36 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-17 02:06:36 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-17 02:06:36 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-17 02:06:36 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-17 02:08:43 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:08:43 (10043) [INFO] Trying other mirror. * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-17 02:08:43 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-17 02:08:43 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-17 02:08:43 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-17 02:08:43 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-17 02:08:43 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-17 02:08:43 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-17 02:08:43 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-17 02:08:43 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-17 02:08:43 (10043) [INFO] or * 2025-05-17 02:08:43 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-17 02:08:43 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-17 02:08:43 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-17 02:08:43 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-17 02:08:43 (10043) [INFO] compromise: * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-17 02:08:43 (10043) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-17 02:08:43 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:08:43 (10060) [INFO] * 2025-05-17 02:08:43 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:08:43 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-17 02:08:43 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-17 02:08:43 (10030) [INFO] * 2025-05-17 02:08:43 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-17 02:08:44 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-17 02:08:44 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-17 02:08:44 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-17 02:08:44 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-17 02:08:44 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-17 02:08:44 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-17 02:08:44 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-17 02:08:44 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-17 02:08:44 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-17 02:08:44 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-17 02:08:44 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-17 02:08:44 (10060) [INFO] * 2025-05-17 02:08:44 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-17 02:08:44 (10030) [INFO] * 2025-05-17 02:08:44 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-17 02:08:45 (10043) [INFO] Determining fastest mirrors * 2025-05-17 02:09:16 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-17 02:09:16 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-17 02:09:16 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-17 02:09:16 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-17 02:10:02 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30040 milliseconds with 0 out of 0 bytes received') * 2025-05-17 02:10:02 (10043) [INFO] Trying other mirror. * 2025-05-17 02:11:53 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:11:53 (10043) [INFO] Trying other mirror. * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-17 02:11:53 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-17 02:11:53 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-17 02:11:53 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-17 02:11:53 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-17 02:11:53 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-17 02:11:53 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-17 02:11:53 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-17 02:11:53 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-17 02:11:53 (10043) [INFO] or * 2025-05-17 02:11:53 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-17 02:11:53 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-17 02:11:53 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-17 02:11:53 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-17 02:11:53 (10043) [INFO] compromise: * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-17 02:11:53 (10043) [INFO] * 2025-05-17 02:11:53 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-17 02:11:53 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:11:53 (10060) [INFO] * 2025-05-17 02:11:53 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-17 02:11:53 (6278) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30040 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-17 02:11:55 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-17 02:11:55 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-17 02:11:55 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-17 02:11:55 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-17 02:11:55 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-18 01:48:42 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-18 01:52:42 (11113) [INFO] Script is up to date. * 2025-05-18 01:56:46 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-18 01:56:46 (10030) [INFO] * 2025-05-18 01:58:03 (10060) [INFO] * 2025-05-18 01:58:03 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-18 01:58:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-18 01:58:03 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-18 01:58:03 (10030) [INFO] * 2025-05-18 02:05:05 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-18 02:05:05 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-18 02:05:05 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-18 02:05:05 (10030) [INFO] * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-18 02:05:29 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-18 02:05:29 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-18 02:05:29 (10030) [INFO] * 2025-05-18 02:05:29 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-18 02:05:30 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-18 02:06:00 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-18 02:06:00 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-18 02:06:00 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-18 02:06:00 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-18 02:08:06 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:08:06 (10043) [INFO] Trying other mirror. * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-18 02:08:06 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-18 02:08:06 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-18 02:08:06 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-18 02:08:06 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-18 02:08:06 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-18 02:08:06 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-18 02:08:06 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-18 02:08:06 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-18 02:08:06 (10043) [INFO] or * 2025-05-18 02:08:06 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-18 02:08:06 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-18 02:08:06 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-18 02:08:06 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-18 02:08:06 (10043) [INFO] compromise: * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-18 02:08:06 (10043) [INFO] * 2025-05-18 02:08:06 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-18 02:08:06 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:08:06 (10060) [INFO] * 2025-05-18 02:08:06 (6267) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:08:06 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-18 02:08:06 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-18 02:08:06 (10030) [INFO] * 2025-05-18 02:08:07 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-18 02:08:07 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-18 02:08:07 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-18 02:08:07 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-18 02:08:07 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-18 02:08:07 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-18 02:08:07 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-18 02:08:07 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-18 02:08:07 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-18 02:08:07 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-18 02:08:07 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-18 02:08:07 (10043) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-05-18 02:08:07 (10060) [INFO] * 2025-05-18 02:08:07 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-18 02:08:07 (10030) [INFO] * 2025-05-18 02:08:08 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-18 02:08:08 (10043) [INFO] Determining fastest mirrors * 2025-05-18 02:08:41 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-18 02:08:41 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-18 02:08:41 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-18 02:08:41 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-18 02:10:47 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:10:47 (10043) [INFO] Trying other mirror. * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-05-18 02:10:47 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-18 02:10:47 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-18 02:10:47 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-18 02:10:47 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-18 02:10:47 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-18 02:10:47 (10043) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-18 02:10:47 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-18 02:10:47 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-05-18 02:10:47 (10043) [INFO] or * 2025-05-18 02:10:47 (10043) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-18 02:10:47 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-18 02:10:47 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-18 02:10:47 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-18 02:10:47 (10043) [INFO] compromise: * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-05-18 02:10:47 (10043) [INFO] * 2025-05-18 02:10:47 (10043) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-05-18 02:10:47 (10043) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:10:47 (10060) [INFO] * 2025-05-18 02:10:47 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-18 02:10:47 (6278) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ3MjA5MjAzOjE3NDc0Njg0MDM6gSfd8OaIFhKndeZhE2kwAF63IGuOtQilBWWYuAx0IFkmMZ0ZpiNWXlkl4EAyCRixPeztCEUxZhdAFMNcGR8BhnIwDTgRTkJ9n_iPH-sauv_zOLDzOVxKz109IXOOtI4HxHDQ5dBjeZ-LBALX2oSRU61gYy-D6ZxRvR4oYHa_jDVeFPrN3TE2BzYLPcbiTLdL3ZOMh3yIjAlwCmDsCTW-XKH2hrCzRSBP9rK3EAabc4RMdd5lvE8UJtpamK2IsZWSj9GoSpvFjE7v3U3ZX7bTKBwwMpumdcnB5HndX_N9o1TlrPQUrAOXddqa5-PLB6pVOtxfATYE24eUE2eyB4MNp5u0r64A1pEtGbc6RumBRkLutnY4RbNLfY7sfUGY_MzrxSuvK_6XKFB35wnO5e0FTftjSGTO-IvsRXQalGVUX6gfJL8j9xjZlurrRiZFHxqsOzxEAXA0VBWJ3TvYARh3hnCFd2q20LBR4q0Kd0iNsHXIz5AaDuKV-QaJkx-QtRAUH4w-QI1sbfTgMZEKFrhdQySFIGUQlLYoKXhquho_k_O3PNNoKWdNjVhlVXj3gyN5FqavX183LfB61i9N8eCyiQBj5vTkk1Jvo6Jk6FB3RDfbsoaHzzNcqWu-1KOyBfuTXq-WYirh_aMwJwxC5X2MM_KHY0OpV-BA7Zpb02lj1Pk=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-05-18 02:10:49 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-18 02:10:49 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-18 02:10:49 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-18 02:10:49 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-18 02:10:49 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-18 02:10:58 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pO67vtSQh4/ea_profile.json * 2025-05-18 02:13:36 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pO67vtSQh4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9151. * 2025-05-18 02:13:36 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-05-19 01:55:49 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-19 01:59:50 (11113) [INFO] Script is up to date. * 2025-05-19 02:03:53 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-19 02:03:53 (10030) [INFO] * 2025-05-19 02:05:39 (10060) [INFO] * 2025-05-19 02:05:39 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-19 02:05:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-19 02:05:39 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-19 02:05:39 (10030) [INFO] * 2025-05-19 02:05:43 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-19 02:05:43 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-19 02:05:43 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-19 02:05:43 (10030) [INFO] * 2025-05-19 02:05:56 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-19 02:06:01 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-19 02:06:01 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-19 02:06:01 (10030) [INFO] * 2025-05-19 02:06:01 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-19 02:06:01 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-19 02:06:32 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-19 02:06:32 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-19 02:06:32 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-19 02:06:32 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-19 02:07:18 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-19 02:07:18 (10043) [INFO] Trying other mirror. * 2025-05-19 02:07:49 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-19 02:07:49 (10043) [INFO] Trying other mirror. * 2025-05-19 02:10:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:10:41 (10043) [INFO] Trying other mirror. * 2025-05-19 02:10:58 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:10:58 (10043) [INFO] Trying other mirror. * 2025-05-19 02:11:38 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2025-05-19 02:11:38 (10043) [INFO] Trying other mirror. * 2025-05-19 02:11:43 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:11:43 (10043) [INFO] Trying other mirror. * 2025-05-19 02:12:09 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-19 02:12:09 (10043) [INFO] Trying other mirror. * 2025-05-19 02:12:40 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-19 02:12:40 (10043) [INFO] Trying other mirror. * 2025-05-19 02:13:26 (10043) [INFO] Metadata Cache Created * 2025-05-19 02:13:26 (10060) [INFO] * 2025-05-19 02:13:26 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-19 02:13:26 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-19 02:13:26 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-19 02:13:26 (10030) [INFO] * 2025-05-19 02:13:26 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-19 02:13:27 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-19 02:13:27 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-19 02:13:27 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-19 02:13:27 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-19 02:13:27 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-19 02:13:27 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-19 02:13:27 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-19 02:13:27 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-19 02:13:27 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-19 02:13:28 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-19 02:13:28 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-19 02:13:28 (10060) [INFO] * 2025-05-19 02:13:28 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-19 02:13:28 (10030) [INFO] * 2025-05-19 02:13:28 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-19 02:13:28 (10043) [INFO] Determining fastest mirrors * 2025-05-19 02:14:01 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-19 02:14:01 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-19 02:14:01 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-19 02:14:01 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-19 02:17:26 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-19 02:17:26 (10043) [INFO] Trying other mirror. * 2025-05-19 02:17:27 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30901 milliseconds') * 2025-05-19 02:17:27 (10043) [INFO] Trying other mirror. * 2025-05-19 02:17:56 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-19 02:17:56 (10043) [INFO] Trying other mirror. * 2025-05-19 02:18:27 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-19 02:18:27 (10043) [INFO] Trying other mirror. * 2025-05-19 02:20:29 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-05-19 02:20:29 (10043) [INFO] Trying other mirror. * 2025-05-19 02:23:47 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:23:47 (10043) [INFO] Trying other mirror. * 2025-05-19 02:23:47 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:23:47 (10043) [INFO] Trying other mirror. * 2025-05-19 02:24:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:24:49 (10043) [INFO] Trying other mirror. * 2025-05-19 02:24:49 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-19 02:24:49 (10043) [INFO] Trying other mirror. * 2025-05-19 02:25:20 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-19 02:25:20 (10043) [INFO] Trying other mirror. * 2025-05-19 02:25:20 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-19 02:25:20 (10043) [INFO] Trying other mirror. * 2025-05-20 02:02:31 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-20 02:06:31 (11113) [INFO] Script is up to date. * 2025-05-20 02:10:34 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-20 02:10:34 (10030) [INFO] * 2025-05-20 02:12:16 (10060) [INFO] * 2025-05-20 02:12:16 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-20 02:12:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-20 02:12:17 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-20 02:12:17 (10030) [INFO] * 2025-05-20 02:12:21 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-20 02:12:21 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-20 02:12:21 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-20 02:12:21 (10030) [INFO] * 2025-05-20 02:12:34 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-20 02:12:38 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-20 02:12:38 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-20 02:12:38 (10030) [INFO] * 2025-05-20 02:12:38 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-20 02:12:38 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-20 02:13:08 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-20 02:13:08 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-20 02:13:08 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-20 02:13:08 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-20 02:13:55 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-20 02:13:55 (10043) [INFO] Trying other mirror. * 2025-05-20 02:16:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:16:47 (10043) [INFO] Trying other mirror. * 2025-05-20 02:17:04 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:17:04 (10043) [INFO] Trying other mirror. * 2025-05-20 02:17:44 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-20 02:17:44 (10043) [INFO] Trying other mirror. * 2025-05-20 02:17:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-20 02:17:49 (10043) [INFO] Trying other mirror. * 2025-05-20 02:18:19 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:18:19 (10043) [INFO] Trying other mirror. * 2025-05-20 02:18:50 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-20 02:18:50 (10043) [INFO] Trying other mirror. * 2025-05-20 02:19:36 (10043) [INFO] Metadata Cache Created * 2025-05-20 02:19:36 (10060) [INFO] * 2025-05-20 02:19:36 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-20 02:19:36 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-20 02:19:36 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-20 02:19:36 (10030) [INFO] * 2025-05-20 02:19:36 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-20 02:19:37 (10043) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 5208. * 2025-05-20 02:19:37 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:37 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:37 (10043) [INFO] Memory : 71 M RSS (398 MB VSZ) * 2025-05-20 02:19:37 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:31 ago * 2025-05-20 02:19:37 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:39 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:39 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:39 (10043) [INFO] Memory : 81 M RSS (408 MB VSZ) * 2025-05-20 02:19:39 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:33 ago * 2025-05-20 02:19:39 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:41 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:41 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:41 (10043) [INFO] Memory : 85 M RSS (412 MB VSZ) * 2025-05-20 02:19:41 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:35 ago * 2025-05-20 02:19:41 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:43 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:43 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:43 (10043) [INFO] Memory : 89 M RSS (416 MB VSZ) * 2025-05-20 02:19:43 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:37 ago * 2025-05-20 02:19:43 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:45 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:45 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:45 (10043) [INFO] Memory : 93 M RSS (420 MB VSZ) * 2025-05-20 02:19:45 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:39 ago * 2025-05-20 02:19:45 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:47 (10043) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-05-20 02:19:47 (10043) [INFO] The other application is: yum * 2025-05-20 02:19:47 (10043) [INFO] Memory : 100 M RSS (427 MB VSZ) * 2025-05-20 02:19:47 (10043) [INFO] Started: Tue May 20 02:17:06 2025 - 02:41 ago * 2025-05-20 02:19:47 (10043) [INFO] State : Running, pid: 5208 * 2025-05-20 02:19:49 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-20 02:19:49 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-20 02:19:49 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-20 02:19:49 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-20 02:19:49 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-20 02:19:49 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-20 02:19:49 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-20 02:19:49 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-20 02:19:49 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-20 02:19:50 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-20 02:19:50 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-20 02:19:50 (10060) [INFO] * 2025-05-20 02:19:50 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-20 02:19:50 (10030) [INFO] * 2025-05-20 02:19:50 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-20 02:19:51 (10043) [INFO] Determining fastest mirrors * 2025-05-20 02:20:22 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-20 02:20:22 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-20 02:20:22 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-20 02:20:22 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-20 02:21:09 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-05-20 02:21:09 (10043) [INFO] Trying other mirror. * 2025-05-20 02:21:40 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-20 02:21:40 (10043) [INFO] Trying other mirror. * 2025-05-20 02:22:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30066 milliseconds') * 2025-05-20 02:22:10 (10043) [INFO] Trying other mirror. * 2025-05-20 02:22:40 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-20 02:22:40 (10043) [INFO] Trying other mirror. * 2025-05-20 02:25:52 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-20 02:25:52 (10043) [INFO] Trying other mirror. * 2025-05-20 02:25:52 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-20 02:25:52 (10043) [INFO] Trying other mirror. * 2025-05-20 02:26:22 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:26:22 (10043) [INFO] Trying other mirror. * 2025-05-20 02:26:52 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-20 02:26:52 (10043) [INFO] Trying other mirror. * 2025-05-20 02:28:54 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-05-20 02:28:54 (10043) [INFO] Trying other mirror. * 2025-05-20 02:32:12 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:32:12 (10043) [INFO] Trying other mirror. * 2025-05-20 02:32:13 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-20 02:32:13 (10043) [INFO] Trying other mirror. * 2025-05-21 02:42:46 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-21 02:46:47 (11113) [INFO] Script is up to date. * 2025-05-21 02:50:50 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-21 02:50:50 (10030) [INFO] * 2025-05-21 02:52:22 (10060) [INFO] * 2025-05-21 02:52:22 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-21 02:52:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-21 02:52:23 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-21 02:52:23 (10030) [INFO] * 2025-05-21 02:59:25 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-21 02:59:25 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-21 02:59:25 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-21 02:59:25 (10030) [INFO] * 2025-05-21 02:59:37 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-21 02:59:41 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-21 02:59:41 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-21 02:59:41 (10030) [INFO] * 2025-05-21 02:59:41 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-21 02:59:42 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-21 03:00:12 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-21 03:00:12 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-21 03:00:12 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-21 03:00:12 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-21 03:03:39 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-21 03:03:39 (10043) [INFO] Trying other mirror. * 2025-05-21 03:04:05 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-21 03:04:05 (10043) [INFO] Trying other mirror. * 2025-05-21 03:04:43 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-21 03:04:43 (10043) [INFO] Trying other mirror. * 2025-05-21 03:04:59 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-21 03:04:59 (10043) [INFO] Trying other mirror. * 2025-05-21 03:05:00 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-21 03:05:00 (10043) [INFO] Trying other mirror. * 2025-05-21 03:05:13 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-21 03:05:13 (10043) [INFO] Trying other mirror. * 2025-05-21 03:05:30 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-21 03:05:30 (10043) [INFO] Trying other mirror. * 2025-05-21 03:06:17 (10043) [INFO] Metadata Cache Created * 2025-05-21 03:06:17 (10060) [INFO] * 2025-05-21 03:06:17 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-21 03:06:17 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-21 03:06:17 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-21 03:06:17 (10030) [INFO] * 2025-05-21 03:06:18 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-21 03:06:18 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-21 03:06:18 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-21 03:06:18 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-21 03:06:18 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-21 03:06:18 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-21 03:06:18 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-21 03:06:18 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-21 03:06:18 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-21 03:06:18 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-21 03:06:19 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-21 03:06:19 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-21 03:06:19 (10060) [INFO] * 2025-05-21 03:06:19 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-21 03:06:19 (10030) [INFO] * 2025-05-21 03:06:19 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-21 03:06:20 (10043) [INFO] Determining fastest mirrors * 2025-05-21 03:06:51 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-21 03:06:51 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-21 03:06:51 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-21 03:06:51 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-21 03:10:35 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-21 03:10:35 (10043) [INFO] Trying other mirror. * 2025-05-21 03:10:36 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-21 03:10:36 (10043) [INFO] Trying other mirror. * 2025-05-21 03:11:29 (10043) [INFO] https://repo.tuxcare.com/centos7-els//updates/x86_64/repodata/c64d00c794b30e4da9dcd133437b1808fbf96b3ced4edb22ea68fbe496eb11b6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-05-21 03:11:29 (10043) [INFO] Trying other mirror. * 2025-05-21 03:11:53 (10043) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-05-21 03:11:53 (10043) [INFO] Trying other mirror. * 2025-05-21 03:12:16 (10043) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-05-21 03:12:16 (10043) [INFO] Trying other mirror. * 2025-05-22 01:55:30 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-22 01:59:31 (11113) [INFO] Script is up to date. * 2025-05-22 02:03:34 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-22 02:03:34 (10030) [INFO] * 2025-05-22 02:05:19 (10060) [INFO] * 2025-05-22 02:05:19 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-22 02:05:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-22 02:05:19 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-22 02:05:19 (10030) [INFO] * 2025-05-22 02:07:06 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-22 02:07:06 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-22 02:07:06 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-22 02:07:06 (10030) [INFO] * 2025-05-22 02:07:21 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-22 02:07:25 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-22 02:07:25 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-22 02:07:25 (10030) [INFO] * 2025-05-22 02:07:25 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-22 02:07:26 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-22 02:07:56 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-22 02:07:56 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-22 02:07:56 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-22 02:07:56 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-22 02:11:03 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-22 02:11:03 (10043) [INFO] Trying other mirror. * 2025-05-22 02:11:21 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-22 02:11:21 (10043) [INFO] Trying other mirror. * 2025-05-22 02:12:00 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-22 02:12:00 (10043) [INFO] Trying other mirror. * 2025-05-22 02:12:04 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-22 02:12:04 (10043) [INFO] Trying other mirror. * 2025-05-22 02:12:31 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-22 02:12:31 (10043) [INFO] Trying other mirror. * 2025-05-22 02:13:02 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-22 02:13:02 (10043) [INFO] Trying other mirror. * 2025-05-22 02:13:32 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30317 milliseconds') * 2025-05-22 02:13:32 (10043) [INFO] Trying other mirror. * 2025-05-22 02:14:02 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-22 02:14:02 (10043) [INFO] Trying other mirror. * 2025-05-22 02:14:48 (10043) [INFO] Metadata Cache Created * 2025-05-22 02:14:48 (10060) [INFO] * 2025-05-22 02:14:48 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30317 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-05-22 02:14:48 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-22 02:14:48 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-22 02:14:48 (10030) [INFO] * 2025-05-22 02:14:49 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-22 02:14:49 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-22 02:14:49 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-22 02:14:49 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-22 02:14:49 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-22 02:14:49 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-22 02:14:49 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-22 02:14:49 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-22 02:14:49 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-22 02:14:49 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-22 02:14:50 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-22 02:14:50 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-22 02:14:50 (10060) [INFO] * 2025-05-22 02:14:50 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-22 02:14:50 (10030) [INFO] * 2025-05-22 02:14:51 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-22 02:14:51 (10043) [INFO] Determining fastest mirrors * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-05-22 02:15:23 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-22 02:15:23 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-22 02:15:23 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-22 02:15:23 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-22 02:15:23 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-22 02:15:23 (10043) [INFO] yum --disablerepo= ... * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-22 02:15:23 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-22 02:15:23 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] yum-config-manager --disable * 2025-05-22 02:15:23 (10043) [INFO] or * 2025-05-22 02:15:23 (10043) [INFO] subscription-manager repos --disable= * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-22 02:15:23 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-22 02:15:23 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-22 02:15:23 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-22 02:15:23 (10043) [INFO] compromise: * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-05-22 02:15:23 (10043) [INFO] * 2025-05-22 02:15:23 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-05-22 02:15:23 (10060) [INFO] * 2025-05-22 02:15:23 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-22 02:15:23 (6278) [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 * 2025-05-22 02:15:24 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-22 02:15:24 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-22 02:15:24 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-22 02:15:24 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-22 02:15:24 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-23 02:00:38 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-23 02:04:39 (11113) [INFO] Script is up to date. * 2025-05-23 02:08:42 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-23 02:08:42 (10030) [INFO] * 2025-05-23 02:10:21 (10060) [INFO] * 2025-05-23 02:10:21 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-23 02:10:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-23 02:10:21 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-23 02:10:21 (10030) [INFO] * 2025-05-23 02:10:26 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-23 02:10:26 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-23 02:10:26 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-23 02:10:26 (10030) [INFO] * 2025-05-23 02:10:40 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-23 02:10:44 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-23 02:10:44 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-23 02:10:44 (10030) [INFO] * 2025-05-23 02:10:44 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-23 02:10:45 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-23 02:11:15 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-23 02:11:15 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-23 02:11:15 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-23 02:11:15 (10043) [INFO] * epel: mirror.math.princeton.edu * 2025-05-23 02:12:02 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:12:02 (10043) [INFO] Trying other mirror. * 2025-05-23 02:12:32 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:12:32 (10043) [INFO] Trying other mirror. * 2025-05-23 02:15:25 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-23 02:15:25 (10043) [INFO] Trying other mirror. * 2025-05-23 02:15:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-23 02:15:41 (10043) [INFO] Trying other mirror. * 2025-05-23 02:16:11 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-23 02:16:11 (10043) [INFO] Trying other mirror. * 2025-05-23 02:16:25 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:16:25 (10043) [INFO] Trying other mirror. * 2025-05-23 02:16:42 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-23 02:16:42 (10043) [INFO] Trying other mirror. * 2025-05-23 02:16:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-23 02:16:55 (10043) [INFO] Trying other mirror. * 2025-05-23 02:17:12 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:17:12 (10043) [INFO] Trying other mirror. * 2025-05-23 02:17:26 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:17:26 (10043) [INFO] Trying other mirror. * 2025-05-23 02:17:57 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-23 02:17:57 (10043) [INFO] Trying other mirror. * 2025-05-23 02:18:43 (10043) [INFO] Metadata Cache Created * 2025-05-23 02:18:43 (10060) [INFO] * 2025-05-23 02:18:43 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-05-23 02:18:43 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-23 02:18:43 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-23 02:18:43 (10030) [INFO] * 2025-05-23 02:18:44 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-23 02:18:44 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-23 02:18:44 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-23 02:18:44 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-23 02:18:44 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-23 02:18:44 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-23 02:18:44 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-23 02:18:44 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-23 02:18:44 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-23 02:18:44 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-23 02:18:45 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-23 02:18:45 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-23 02:18:45 (10060) [INFO] * 2025-05-23 02:18:45 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-23 02:18:45 (10030) [INFO] * 2025-05-23 02:18:45 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-23 02:18:46 (10043) [INFO] Determining fastest mirrors * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-05-23 02:19:17 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-23 02:19:17 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-23 02:19:17 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-23 02:19:17 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-23 02:19:17 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-23 02:19:17 (10043) [INFO] yum --disablerepo= ... * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-23 02:19:17 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-23 02:19:17 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] yum-config-manager --disable * 2025-05-23 02:19:17 (10043) [INFO] or * 2025-05-23 02:19:17 (10043) [INFO] subscription-manager repos --disable= * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-23 02:19:17 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-23 02:19:17 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-23 02:19:17 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-23 02:19:17 (10043) [INFO] compromise: * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-05-23 02:19:17 (10043) [INFO] * 2025-05-23 02:19:17 (10043) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-05-23 02:19:17 (10060) [INFO] * 2025-05-23 02:19:17 (6277) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-05-23 02:19:17 (6278) [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 * 2025-05-23 02:19:18 (3563) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-05-23 02:19:18 (259) [WARN] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-05-23 02:19:18 (4629) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-05-23 02:19:18 (4635) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-05-23 02:19:18 (2294) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-05-23 02:26:45 (9149) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/F6i81qWc1g/ea_profile.json * 2025-05-24 01:57:25 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-24 02:01:25 (11113) [INFO] Script is up to date. * 2025-05-24 02:05:28 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-24 02:05:28 (10030) [INFO] * 2025-05-24 02:06:34 (10060) [INFO] * 2025-05-24 02:06:34 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-24 02:06:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-24 02:06:35 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-24 02:06:35 (10030) [INFO] * 2025-05-24 02:07:05 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-24 02:07:05 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-24 02:07:05 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-24 02:07:05 (10030) [INFO] * 2025-05-24 02:07:19 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-24 02:07:23 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-24 02:07:23 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-24 02:07:23 (10030) [INFO] * 2025-05-24 02:07:23 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-24 02:07:24 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-24 02:07:54 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-24 02:07:54 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-24 02:07:54 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-24 02:07:54 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-24 02:11:02 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:11:02 (10043) [INFO] Trying other mirror. * 2025-05-24 02:11:19 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:11:19 (10043) [INFO] Trying other mirror. * 2025-05-24 02:12:02 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') * 2025-05-24 02:12:02 (10043) [INFO] Trying other mirror. * 2025-05-24 02:12:33 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-24 02:12:33 (10043) [INFO] Trying other mirror. * 2025-05-24 02:13:04 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-24 02:13:04 (10043) [INFO] Trying other mirror. * 2025-05-24 02:13:35 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-24 02:13:35 (10043) [INFO] Trying other mirror. * 2025-05-24 02:14:06 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-24 02:14:06 (10043) [INFO] Trying other mirror. * 2025-05-24 02:14:36 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-24 02:14:36 (10043) [INFO] Trying other mirror. * 2025-05-24 02:15:07 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-24 02:15:07 (10043) [INFO] Trying other mirror. * 2025-05-24 02:15:37 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:15:37 (10043) [INFO] Trying other mirror. * 2025-05-24 02:16:08 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-24 02:16:08 (10043) [INFO] Trying other mirror. * 2025-05-24 02:16:54 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-24 02:16:54 (10043) [INFO] Trying other mirror. * 2025-05-24 02:17:24 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:17:24 (10043) [INFO] Trying other mirror. * 2025-05-24 02:17:55 (10043) [INFO] Metadata Cache Created * 2025-05-24 02:17:55 (10060) [INFO] * 2025-05-24 02:17:55 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-24 02:17:55 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-24 02:17:55 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-24 02:17:55 (10030) [INFO] * 2025-05-24 02:17:55 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-24 02:17:56 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-24 02:17:56 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-24 02:17:56 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-24 02:17:56 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-24 02:17:56 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-24 02:17:56 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-24 02:17:56 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-24 02:17:56 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-24 02:17:56 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-24 02:17:57 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-24 02:17:57 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-24 02:17:57 (10060) [INFO] * 2025-05-24 02:17:57 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-24 02:17:57 (10030) [INFO] * 2025-05-24 02:17:57 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-24 02:17:58 (10043) [INFO] Determining fastest mirrors * 2025-05-24 02:18:30 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-24 02:18:30 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-24 02:18:30 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-24 02:18:30 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-24 02:21:56 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-24 02:21:56 (10043) [INFO] Trying other mirror. * 2025-05-24 02:21:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:21:57 (10043) [INFO] Trying other mirror. * 2025-05-24 02:24:58 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-24 02:24:58 (10043) [INFO] Trying other mirror. * 2025-05-25 02:00:14 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-25 02:04:14 (11113) [INFO] Script is up to date. * 2025-05-25 02:08:18 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-25 02:08:18 (10030) [INFO] * 2025-05-25 02:09:30 (10060) [INFO] * 2025-05-25 02:09:30 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-25 02:09:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-25 02:09:30 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-25 02:09:30 (10030) [INFO] * 2025-05-25 02:09:34 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-25 02:09:34 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-25 02:09:34 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-25 02:09:34 (10030) [INFO] * 2025-05-25 02:09:46 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-25 02:09:50 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-25 02:09:50 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-25 02:09:50 (10030) [INFO] * 2025-05-25 02:09:50 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-25 02:09:50 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-25 02:10:21 (10043) [INFO] * EA4: 208.74.123.61 * 2025-05-25 02:10:21 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-25 02:10:21 (10043) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-25 02:10:21 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-25 02:11:07 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-25 02:11:07 (10043) [INFO] Trying other mirror. * 2025-05-25 02:11:38 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-25 02:11:38 (10043) [INFO] Trying other mirror. * 2025-05-25 02:14:30 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:14:30 (10043) [INFO] Trying other mirror. * 2025-05-25 02:14:47 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:14:47 (10043) [INFO] Trying other mirror. * 2025-05-25 02:15:17 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-05-25 02:15:17 (10043) [INFO] Trying other mirror. * 2025-05-25 02:15:31 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:15:31 (10043) [INFO] Trying other mirror. * 2025-05-25 02:16:17 (10043) [INFO] Metadata Cache Created * 2025-05-25 02:16:17 (10060) [INFO] * 2025-05-25 02:16:17 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-25 02:16:17 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-25 02:16:17 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-25 02:16:17 (10030) [INFO] * 2025-05-25 02:16:17 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-25 02:16:18 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-25 02:16:18 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-25 02:16:18 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-25 02:16:18 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-25 02:16:18 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-25 02:16:18 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-25 02:16:18 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-25 02:16:18 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-25 02:16:18 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-25 02:16:18 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-25 02:16:18 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-25 02:16:18 (10060) [INFO] * 2025-05-25 02:16:18 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-25 02:16:18 (10030) [INFO] * 2025-05-25 02:16:19 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-25 02:16:19 (10043) [INFO] Determining fastest mirrors * 2025-05-25 02:16:51 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-25 02:16:51 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-25 02:16:51 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-25 02:16:51 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-25 02:17:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-25 02:17:37 (10043) [INFO] Trying other mirror. * 2025-05-25 02:20:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-25 02:20:47 (10043) [INFO] Trying other mirror. * 2025-05-25 02:20:47 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:20:47 (10043) [INFO] Trying other mirror. * 2025-05-25 02:23:49 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:23:49 (10043) [INFO] Trying other mirror. * 2025-05-25 02:26:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Operation timed out after 30026 milliseconds with 0 out of 0 bytes received') * 2025-05-25 02:26:38 (10043) [INFO] Trying other mirror. * 2025-05-25 02:26:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:26:38 (10043) [INFO] Trying other mirror. * 2025-05-25 02:27:08 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-25 02:27:08 (10043) [INFO] Trying other mirror. * 2025-05-25 02:27:39 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-25 02:27:39 (10043) [INFO] Trying other mirror. * 2025-05-25 02:28:10 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:28:10 (10043) [INFO] Trying other mirror. * 2025-05-25 02:28:10 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:28:10 (10043) [INFO] Trying other mirror. * 2025-05-25 02:28:40 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-25 02:28:40 (10043) [INFO] Trying other mirror. * 2025-05-25 02:29:11 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:29:11 (10043) [INFO] Trying other mirror. * 2025-05-25 02:29:11 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-25 02:29:11 (10043) [INFO] Trying other mirror. * 2025-05-25 02:29:42 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-25 02:29:42 (10043) [INFO] Trying other mirror. * 2025-05-25 02:29:42 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-25 02:29:42 (10043) [INFO] Trying other mirror. * 2025-05-26 01:53:07 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-26 01:57:08 (11113) [INFO] Script is up to date. * 2025-05-26 02:01:11 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-26 02:01:11 (10030) [INFO] * 2025-05-26 02:02:53 (10060) [INFO] * 2025-05-26 02:02:53 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-26 02:02:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-26 02:02:54 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-26 02:02:54 (10030) [INFO] * 2025-05-26 02:02:58 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-26 02:02:58 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-26 02:02:58 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-26 02:02:58 (10030) [INFO] * 2025-05-26 02:03:12 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-26 02:03:17 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-26 02:03:17 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-26 02:03:17 (10030) [INFO] * 2025-05-26 02:03:17 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-26 02:03:18 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-26 02:03:48 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-05-26 02:03:48 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') * 2025-05-26 02:03:48 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-26 02:03:48 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-26 02:03:48 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-26 02:03:48 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-26 02:06:57 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-26 02:06:57 (10043) [INFO] Trying other mirror. * 2025-05-26 02:07:13 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-26 02:07:13 (10043) [INFO] Trying other mirror. * 2025-05-26 02:07:43 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-26 02:07:43 (10043) [INFO] Trying other mirror. * 2025-05-26 02:07:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30439 milliseconds') * 2025-05-26 02:07:53 (10043) [INFO] Trying other mirror. * 2025-05-26 02:07:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-26 02:07:55 (10043) [INFO] Trying other mirror. * 2025-05-26 02:08:24 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-26 02:08:24 (10043) [INFO] Trying other mirror. * 2025-05-26 02:08:55 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-26 02:08:55 (10043) [INFO] Trying other mirror. * 2025-05-26 02:09:26 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30690 milliseconds') * 2025-05-26 02:09:26 (10043) [INFO] Trying other mirror. * 2025-05-26 02:09:56 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-26 02:09:56 (10043) [INFO] Trying other mirror. * 2025-05-26 02:10:41 (10043) [INFO] Metadata Cache Created * 2025-05-26 02:10:41 (10060) [INFO] * 2025-05-26 02:10:41 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30439 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30690 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-05-26 02:10:41 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-26 02:10:41 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-26 02:10:41 (10030) [INFO] * 2025-05-26 02:10:42 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-26 02:10:42 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-26 02:10:42 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-26 02:10:42 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-26 02:10:42 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-26 02:10:42 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-26 02:10:42 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-26 02:10:42 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-26 02:10:42 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-26 02:10:42 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-26 02:10:43 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-26 02:10:43 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-26 02:10:43 (10060) [INFO] * 2025-05-26 02:10:43 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-26 02:10:43 (10030) [INFO] * 2025-05-26 02:10:44 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-26 02:10:44 (10043) [INFO] Determining fastest mirrors * 2025-05-26 02:11:16 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-26 02:11:16 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-26 02:11:16 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-26 02:11:16 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-26 02:14:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-26 02:14:41 (10043) [INFO] Trying other mirror. * 2025-05-26 02:14:42 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30596 milliseconds') * 2025-05-26 02:14:42 (10043) [INFO] Trying other mirror. * 2025-05-26 02:15:12 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-05-26 02:15:12 (10043) [INFO] Trying other mirror. * 2025-05-26 02:15:42 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-26 02:15:42 (10043) [INFO] Trying other mirror. * 2025-05-26 02:17:45 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-05-26 02:17:45 (10043) [INFO] Trying other mirror. * 2025-05-26 02:17:45 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-26 02:17:45 (10043) [INFO] Trying other mirror. * 2025-05-26 02:18:16 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-26 02:18:16 (10043) [INFO] Trying other mirror. * 2025-05-26 02:21:05 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-26 02:21:05 (10043) [INFO] Trying other mirror. * 2025-05-26 02:21:05 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-05-26 02:21:05 (10043) [INFO] Trying other mirror. * 2025-05-26 02:21:35 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-05-26 02:21:35 (10043) [INFO] Trying other mirror. * 2025-05-26 02:22:06 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-26 02:22:06 (10043) [INFO] Trying other mirror. * 2025-05-26 02:22:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-26 02:22:37 (10043) [INFO] Trying other mirror. * 2025-05-27 02:02:55 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-27 02:06:56 (11113) [INFO] Script is up to date. * 2025-05-27 02:10:59 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-27 02:10:59 (10030) [INFO] * 2025-05-27 02:12:39 (10060) [INFO] * 2025-05-27 02:12:39 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-27 02:12:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-27 02:12:40 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-27 02:12:40 (10030) [INFO] * 2025-05-27 02:12:44 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-27 02:12:44 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-27 02:12:44 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-27 02:12:44 (10030) [INFO] * 2025-05-27 02:12:55 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-27 02:12:58 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-27 02:12:59 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-27 02:12:59 (10030) [INFO] * 2025-05-27 02:12:59 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-27 02:12:59 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-27 02:13:29 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-27 02:13:29 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-27 02:13:29 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-27 02:13:29 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-27 02:16:38 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:16:38 (10043) [INFO] Trying other mirror. * 2025-05-27 02:16:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:16:55 (10043) [INFO] Trying other mirror. * 2025-05-27 02:17:18 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-27 02:17:18 (10043) [INFO] Trying other mirror. * 2025-05-27 02:17:26 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:17:26 (10043) [INFO] Trying other mirror. * 2025-05-27 02:17:29 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:17:29 (10043) [INFO] Trying other mirror. * 2025-05-27 02:17:49 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-27 02:17:49 (10043) [INFO] Trying other mirror. * 2025-05-27 02:18:00 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-27 02:18:00 (10043) [INFO] Trying other mirror. * 2025-05-27 02:18:46 (10043) [INFO] Metadata Cache Created * 2025-05-27 02:18:46 (10060) [INFO] * 2025-05-27 02:18:46 (6267) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-05-27 02:18:46 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-27 02:18:46 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-27 02:18:46 (10030) [INFO] * 2025-05-27 02:18:46 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-27 02:18:47 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-27 02:18:47 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-27 02:18:47 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-27 02:18:47 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-27 02:18:47 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-27 02:18:47 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-27 02:18:47 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-27 02:18:47 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-27 02:18:47 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-27 02:18:48 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-27 02:18:48 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-27 02:18:48 (10060) [INFO] * 2025-05-27 02:18:48 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-27 02:18:48 (10030) [INFO] * 2025-05-27 02:18:48 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-27 02:18:49 (10043) [INFO] Determining fastest mirrors * 2025-05-27 02:19:21 (10043) [INFO] * EA4: 63.247.64.58 * 2025-05-27 02:19:21 (10043) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-27 02:19:21 (10043) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-27 02:19:21 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-27 02:20:08 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:20:08 (10043) [INFO] Trying other mirror. * 2025-05-27 02:20:39 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-27 02:20:39 (10043) [INFO] Trying other mirror. * 2025-05-27 02:23:48 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-27 02:23:48 (10043) [INFO] Trying other mirror. * 2025-05-27 02:23:49 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-05-27 02:23:49 (10043) [INFO] Trying other mirror. * 2025-05-27 02:26:51 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:26:51 (10043) [INFO] Trying other mirror. * 2025-05-27 02:29:39 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:29:39 (10043) [INFO] Trying other mirror. * 2025-05-27 02:29:39 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:29:39 (10043) [INFO] Trying other mirror. * 2025-05-27 02:30:41 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:30:41 (10043) [INFO] Trying other mirror. * 2025-05-27 02:30:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-27 02:30:41 (10043) [INFO] Trying other mirror. * 2025-05-27 02:31:11 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:31:11 (10043) [INFO] Trying other mirror. * 2025-05-27 02:31:42 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:31:42 (10043) [INFO] Trying other mirror. * 2025-05-27 02:31:42 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-27 02:31:42 (10043) [INFO] Trying other mirror. * 2025-05-27 02:32:44 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-27 02:32:44 (10043) [INFO] Trying other mirror. * 2025-05-28 01:51:31 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-28 01:55:32 (11113) [INFO] Script is up to date. * 2025-05-28 01:59:35 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-28 01:59:35 (10030) [INFO] * 2025-05-28 02:01:11 (10060) [INFO] * 2025-05-28 02:01:11 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-28 02:01:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-28 02:01:11 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-28 02:01:11 (10030) [INFO] * 2025-05-28 02:01:15 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-28 02:01:15 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-28 02:01:15 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-28 02:01:15 (10030) [INFO] * 2025-05-28 02:08:10 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-28 02:08:13 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-28 02:08:13 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-28 02:08:13 (10030) [INFO] * 2025-05-28 02:08:14 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-28 02:08:14 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-28 02:08:44 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-28 02:08:44 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-28 02:08:44 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-28 02:08:44 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-28 02:11:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:11:53 (10043) [INFO] Trying other mirror. * 2025-05-28 02:11:53 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-28 02:11:53 (10043) [INFO] Trying other mirror. * 2025-05-28 02:12:24 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-05-28 02:12:24 (10043) [INFO] Trying other mirror. * 2025-05-28 02:13:04 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:13:04 (10043) [INFO] Trying other mirror. * 2025-05-28 02:13:04 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:13:04 (10043) [INFO] Trying other mirror. * 2025-05-28 02:13:44 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:13:44 (10043) [INFO] Trying other mirror. * 2025-05-28 02:13:48 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-28 02:13:48 (10043) [INFO] Trying other mirror. * 2025-05-28 02:14:04 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:14:04 (10043) [INFO] Trying other mirror. * 2025-05-28 02:14:34 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-28 02:14:34 (10043) [INFO] Trying other mirror. * 2025-05-28 02:15:05 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:15:05 (10043) [INFO] Trying other mirror. * 2025-05-28 02:15:05 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:15:05 (10043) [INFO] Trying other mirror. * 2025-05-28 02:15:36 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-05-28 02:15:36 (10043) [INFO] Trying other mirror. * 2025-05-28 02:15:36 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30766 milliseconds') * 2025-05-28 02:15:36 (10043) [INFO] Trying other mirror. * 2025-05-28 02:16:06 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:16:06 (10043) [INFO] Trying other mirror. * 2025-05-28 02:16:06 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-28 02:16:06 (10043) [INFO] Trying other mirror. * 2025-05-28 02:17:07 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:17:07 (10043) [INFO] Trying other mirror. * 2025-05-28 02:17:37 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:17:37 (10043) [INFO] Trying other mirror. * 2025-05-28 02:17:38 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-05-28 02:17:38 (10043) [INFO] Trying other mirror. * 2025-05-28 02:18:08 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:18:08 (10043) [INFO] Trying other mirror. * 2025-05-28 02:18:08 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:18:08 (10043) [INFO] Trying other mirror. * 2025-05-28 02:18:08 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-28 02:18:08 (10043) [INFO] Trying other mirror. * 2025-05-28 02:18:39 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:18:39 (10043) [INFO] Trying other mirror. * 2025-05-28 02:18:39 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-28 02:18:39 (10043) [INFO] Trying other mirror. * 2025-05-28 02:19:10 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:19:10 (10043) [INFO] Trying other mirror. * 2025-05-28 02:19:10 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-28 02:19:10 (10043) [INFO] Trying other mirror. * 2025-05-28 02:19:10 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-28 02:19:10 (10043) [INFO] Trying other mirror. * 2025-05-28 02:19:40 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-28 02:19:40 (10043) [INFO] Trying other mirror. * 2025-05-28 02:20:11 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-28 02:20:11 (10043) [INFO] Trying other mirror. * 2025-05-28 02:20:11 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-05-28 02:20:11 (10043) [INFO] Trying other mirror. * 2025-05-28 02:20:41 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-28 02:20:41 (10043) [INFO] Trying other mirror. * 2025-05-28 02:21:12 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-28 02:21:12 (10043) [INFO] Trying other mirror. * 2025-05-29 01:46:42 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-29 01:50:42 (11113) [INFO] Script is up to date. * 2025-05-29 01:54:46 (10029) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-29 01:54:46 (10030) [INFO] * 2025-05-29 01:56:21 (10060) [INFO] * 2025-05-29 01:56:21 (6701) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-29 01:56:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-29 01:56:21 (10029) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-29 01:56:21 (10030) [INFO] * 2025-05-29 01:56:25 (4381) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-29 01:56:25 (4388) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-29 01:56:25 (10029) [INFO] Running: /usr/bin/yum list extras * 2025-05-29 01:56:25 (10030) [INFO] * 2025-05-29 01:56:38 (259) [WARN] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-29 01:56:42 (6418) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-29 01:56:42 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-29 01:56:42 (10030) [INFO] * 2025-05-29 01:56:43 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-29 01:56:43 (10043) [INFO] Loading mirror speeds from cached hostfile * 2025-05-29 01:57:13 (10043) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-05-29 01:57:13 (10043) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30542 milliseconds') * 2025-05-29 01:57:14 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-29 01:57:14 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-29 01:57:14 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-29 01:57:14 (10043) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-29 02:00:22 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:00:22 (10043) [INFO] Trying other mirror. * 2025-05-29 02:00:23 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-29 02:00:23 (10043) [INFO] Trying other mirror. * 2025-05-29 02:01:03 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-29 02:01:03 (10043) [INFO] Trying other mirror. * 2025-05-29 02:01:03 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-29 02:01:03 (10043) [INFO] Trying other mirror. * 2025-05-29 02:01:50 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:01:50 (10043) [INFO] Trying other mirror. * 2025-05-29 02:01:50 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:01:50 (10043) [INFO] Trying other mirror. * 2025-05-29 02:02:06 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-29 02:02:06 (10043) [INFO] Trying other mirror. * 2025-05-29 02:02:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:02:37 (10043) [INFO] Trying other mirror. * 2025-05-29 02:02:37 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:02:37 (10043) [INFO] Trying other mirror. * 2025-05-29 02:03:07 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:03:07 (10043) [INFO] Trying other mirror. * 2025-05-29 02:03:37 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:03:37 (10043) [INFO] Trying other mirror. * 2025-05-29 02:04:08 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:04:08 (10043) [INFO] Trying other mirror. * 2025-05-29 02:04:08 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:04:08 (10043) [INFO] Trying other mirror. * 2025-05-29 02:04:08 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-29 02:04:08 (10043) [INFO] Trying other mirror. * 2025-05-29 02:04:38 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:04:38 (10043) [INFO] Trying other mirror. * 2025-05-29 02:04:39 (10043) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:04:39 (10043) [INFO] Trying other mirror. * 2025-05-29 02:05:09 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-29 02:05:09 (10043) [INFO] Trying other mirror. * 2025-05-29 02:05:39 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:05:39 (10043) [INFO] Trying other mirror. * 2025-05-29 02:06:10 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-29 02:06:10 (10043) [INFO] Trying other mirror. * 2025-05-29 02:06:41 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-05-29 02:06:41 (10043) [INFO] Trying other mirror. * 2025-05-29 02:07:12 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-05-29 02:07:12 (10043) [INFO] Trying other mirror. * 2025-05-29 02:07:42 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-29 02:07:42 (10043) [INFO] Trying other mirror. * 2025-05-29 02:08:53 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:08:53 (10043) [INFO] Trying other mirror. * 2025-05-29 02:09:24 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-05-29 02:09:24 (10043) [INFO] Trying other mirror. * 2025-05-29 02:09:55 (10043) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-05-29 02:09:55 (10043) [INFO] Trying other mirror. * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] One of the configured repositories failed (Unknown), * 2025-05-29 02:10:28 (10043) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-05-29 02:10:28 (10043) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-05-29 02:10:28 (10043) [INFO] upstream. This is most often useful if you are using a newer * 2025-05-29 02:10:28 (10043) [INFO] distribution release than is supported by the repository (and the * 2025-05-29 02:10:28 (10043) [INFO] packages for the previous distribution release still work). * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] 3. Run the command with the repository temporarily disabled * 2025-05-29 02:10:28 (10043) [INFO] yum --disablerepo= ... * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-05-29 02:10:28 (10043) [INFO] will then just ignore the repository until you permanently enable it * 2025-05-29 02:10:28 (10043) [INFO] again or use --enablerepo for temporary usage: * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] yum-config-manager --disable * 2025-05-29 02:10:28 (10043) [INFO] or * 2025-05-29 02:10:28 (10043) [INFO] subscription-manager repos --disable= * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-05-29 02:10:28 (10043) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-05-29 02:10:28 (10043) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-05-29 02:10:28 (10043) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-05-29 02:10:28 (10043) [INFO] compromise: * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-05-29 02:10:28 (10043) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] extras: Check uncompressed DB failed * 2025-05-29 02:10:28 (10060) [INFO] * 2025-05-29 02:10:28 (6267) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30542 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') 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 extras: Check uncompressed DB failed * 2025-05-29 02:10:28 (6268) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-29 02:10:28 (10029) [INFO] Running: /usr/bin/yum clean all * 2025-05-29 02:10:28 (10030) [INFO] * 2025-05-29 02:10:28 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-29 02:10:29 (10043) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-29 02:10:29 (10043) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-29 02:10:29 (10043) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-29 02:10:29 (10043) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-29 02:10:29 (10043) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-29 02:10:29 (10043) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-29 02:10:29 (10043) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-29 02:10:29 (10043) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-29 02:10:29 (10043) [INFO] : wp-toolkit-thirdparties * 2025-05-29 02:10:30 (10043) [INFO] Cleaning up list of fastest mirrors * 2025-05-29 02:10:30 (10043) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-29 02:10:30 (10060) [INFO] * 2025-05-29 02:10:30 (10029) [INFO] Running: /usr/bin/yum makecache * 2025-05-29 02:10:30 (10030) [INFO] * 2025-05-29 02:10:30 (10043) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-29 02:10:31 (10043) [INFO] Determining fastest mirrors * 2025-05-29 02:11:05 (10043) [INFO] * EA4: 208.74.123.62 * 2025-05-29 02:11:05 (10043) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-05-29 02:11:05 (10043) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-05-29 02:11:05 (10043) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-29 02:14:30 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-29 02:14:30 (10043) [INFO] Trying other mirror. * 2025-05-29 02:14:31 (10043) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2025-05-29 02:14:31 (10043) [INFO] Trying other mirror. * 2025-05-30 01:56:24 (11091) [INFO] Self-update of script version 65 requested. * 2025-05-30 02:00:25 (11096) [INFO] Newer version of script found. Downloading. * 2025-05-30 02:04:26 (11105) [INFO] Script update to version 66 successful. * 2025-05-30 02:08:29 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-30 02:08:29 (10169) [INFO] * 2025-05-30 02:10:08 (10199) [INFO] * 2025-05-30 02:10:08 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-30 02:10:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-30 02:10:08 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-30 02:10:08 (10169) [INFO] * 2025-05-30 02:10:12 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-30 02:10:12 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-30 02:10:12 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-05-30 02:10:12 (10169) [INFO] * 2025-05-30 02:10:26 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-30 02:10:30 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-30 02:10:30 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-05-30 02:10:30 (10169) [INFO] * 2025-05-30 02:10:30 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-30 02:10:31 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-05-30 02:11:01 (10182) [INFO] * EA4: 63.247.64.58 * 2025-05-30 02:11:01 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-30 02:11:01 (10182) [INFO] * cpanel-plugins: 209.133.199.70 * 2025-05-30 02:11:01 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-05-30 02:11:47 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-30 02:11:47 (10182) [INFO] Trying other mirror. * 2025-05-30 02:12:18 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-30 02:12:18 (10182) [INFO] Trying other mirror. * 2025-05-30 02:12:49 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-30 02:12:49 (10182) [INFO] Trying other mirror. * 2025-05-30 02:13:20 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-30 02:13:20 (10182) [INFO] Trying other mirror. * 2025-05-30 02:16:13 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-30 02:16:13 (10182) [INFO] Trying other mirror. * 2025-05-30 02:16:30 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-30 02:16:30 (10182) [INFO] Trying other mirror. * 2025-05-30 02:17:00 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-30 02:17:00 (10182) [INFO] Trying other mirror. * 2025-05-30 02:17:09 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-05-30 02:17:09 (10182) [INFO] Trying other mirror. * 2025-05-30 02:17:13 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-30 02:17:13 (10182) [INFO] Trying other mirror. * 2025-05-30 02:17:30 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-30 02:17:30 (10182) [INFO] Trying other mirror. * 2025-05-30 02:17:44 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-30 02:17:44 (10182) [INFO] Trying other mirror. * 2025-05-30 02:18:01 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-30 02:18:01 (10182) [INFO] Trying other mirror. * 2025-05-30 02:18:15 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-05-30 02:18:15 (10182) [INFO] Trying other mirror. * 2025-05-30 02:18:31 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30010 milliseconds with 0 out of 0 bytes received') * 2025-05-30 02:18:31 (10182) [INFO] Trying other mirror. * 2025-05-30 02:19:16 (10182) [INFO] Metadata Cache Created * 2025-05-30 02:19:16 (10199) [INFO] * 2025-05-30 02:19:16 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30010 milliseconds with 0 out of 0 bytes received') Trying other mirror. * 2025-05-30 02:19:16 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-30 02:19:16 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-05-30 02:19:16 (10169) [INFO] * 2025-05-30 02:19:17 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-30 02:19:17 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-30 02:19:17 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-30 02:19:17 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-30 02:19:17 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-30 02:19:17 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-30 02:19:17 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-30 02:19:17 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-30 02:19:17 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-30 02:19:17 (10182) [INFO] : wp-toolkit-thirdparties * 2025-05-30 02:19:18 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-05-30 02:19:18 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-30 02:19:18 (10199) [INFO] * 2025-05-30 02:19:18 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-05-30 02:19:18 (10169) [INFO] * 2025-05-30 02:19:19 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-30 02:19:19 (10182) [INFO] Determining fastest mirrors * 2025-05-30 02:19:52 (10182) [INFO] * EA4: 63.247.64.58 * 2025-05-30 02:19:52 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-30 02:19:52 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-30 02:19:52 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-30 02:20:40 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-30 02:20:40 (10182) [INFO] Trying other mirror. * 2025-05-30 02:23:49 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-30 02:23:49 (10182) [INFO] Trying other mirror. * 2025-05-30 02:23:50 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-30 02:23:50 (10182) [INFO] Trying other mirror. * 2025-05-31 02:01:06 (11230) [INFO] Self-update of script version 66 requested. * 2025-05-31 02:05:06 (11252) [INFO] Script is up to date. * 2025-05-31 02:09:09 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-05-31 02:09:09 (10169) [INFO] * 2025-05-31 02:10:16 (10199) [INFO] * 2025-05-31 02:10:16 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-05-31 02:10:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-05-31 02:10:17 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-05-31 02:10:17 (10169) [INFO] * 2025-05-31 02:10:21 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-05-31 02:10:21 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-05-31 02:10:21 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-05-31 02:10:21 (10169) [INFO] * 2025-05-31 02:10:36 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-05-31 02:10:39 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-05-31 02:10:39 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-05-31 02:10:39 (10169) [INFO] * 2025-05-31 02:10:39 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-31 02:10:40 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-05-31 02:11:10 (10182) [INFO] * EA4: 208.74.123.61 * 2025-05-31 02:11:10 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-05-31 02:11:10 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-05-31 02:11:10 (10182) [INFO] * epel: mirror.math.princeton.edu * 2025-05-31 02:11:57 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-05-31 02:11:57 (10182) [INFO] Trying other mirror. * 2025-05-31 02:12:27 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-31 02:12:27 (10182) [INFO] Trying other mirror. * 2025-05-31 02:15:19 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:15:19 (10182) [INFO] Trying other mirror. * 2025-05-31 02:15:36 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:15:36 (10182) [INFO] Trying other mirror. * 2025-05-31 02:16:20 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:16:20 (10182) [INFO] Trying other mirror. * 2025-05-31 02:16:50 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-31 02:16:50 (10182) [INFO] Trying other mirror. * 2025-05-31 02:17:21 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-31 02:17:21 (10182) [INFO] Trying other mirror. * 2025-05-31 02:18:09 (10182) [INFO] Metadata Cache Created * 2025-05-31 02:18:09 (10199) [INFO] * 2025-05-31 02:18:09 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-05-31 02:18:09 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-05-31 02:18:09 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-05-31 02:18:09 (10169) [INFO] * 2025-05-31 02:18:10 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-31 02:18:10 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-05-31 02:18:10 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-05-31 02:18:10 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-05-31 02:18:10 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-05-31 02:18:10 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-05-31 02:18:10 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-05-31 02:18:10 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-05-31 02:18:10 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-05-31 02:18:10 (10182) [INFO] : wp-toolkit-thirdparties * 2025-05-31 02:18:11 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-05-31 02:18:11 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-05-31 02:18:11 (10199) [INFO] * 2025-05-31 02:18:11 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-05-31 02:18:11 (10169) [INFO] * 2025-05-31 02:18:12 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-05-31 02:18:12 (10182) [INFO] Determining fastest mirrors * 2025-05-31 02:18:45 (10182) [INFO] * EA4: 63.247.64.58 * 2025-05-31 02:18:45 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-05-31 02:18:45 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-05-31 02:18:45 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-05-31 02:22:12 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-05-31 02:22:12 (10182) [INFO] Trying other mirror. * 2025-05-31 02:22:12 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:22:12 (10182) [INFO] Trying other mirror. * 2025-05-31 02:25:15 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-31 02:25:15 (10182) [INFO] Trying other mirror. * 2025-05-31 02:28:03 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:28:03 (10182) [INFO] Trying other mirror. * 2025-05-31 02:28:04 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:28:04 (10182) [INFO] Trying other mirror. * 2025-05-31 02:28:34 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-31 02:28:34 (10182) [INFO] Trying other mirror. * 2025-05-31 02:29:35 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:29:35 (10182) [INFO] Trying other mirror. * 2025-05-31 02:29:36 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-05-31 02:29:36 (10182) [INFO] Trying other mirror. * 2025-05-31 02:30:06 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-05-31 02:30:06 (10182) [INFO] Trying other mirror. * 2025-05-31 02:30:36 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:30:36 (10182) [INFO] Trying other mirror. * 2025-05-31 02:30:37 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-05-31 02:30:37 (10182) [INFO] Trying other mirror. * 2025-06-01 01:59:23 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-01 02:03:23 (11252) [INFO] Script is up to date. * 2025-06-01 02:07:26 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-01 02:07:26 (10169) [INFO] * 2025-06-01 02:08:36 (10199) [INFO] * 2025-06-01 02:08:36 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-01 02:08:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-01 02:08:36 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-01 02:08:36 (10169) [INFO] * 2025-06-01 02:08:41 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-01 02:08:41 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-01 02:08:41 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-01 02:08:41 (10169) [INFO] * 2025-06-01 02:08:54 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-01 02:08:57 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-01 02:08:57 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-01 02:08:57 (10169) [INFO] * 2025-06-01 02:08:58 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-01 02:08:58 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-01 02:09:28 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-01 02:09:28 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-01 02:09:28 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-01 02:09:28 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-01 02:12:37 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-01 02:12:37 (10182) [INFO] Trying other mirror. * 2025-06-01 02:12:54 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-06-01 02:12:54 (10182) [INFO] Trying other mirror. * 2025-06-01 02:13:23 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:13:23 (10182) [INFO] Trying other mirror. * 2025-06-01 02:13:32 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:13:32 (10182) [INFO] Trying other mirror. * 2025-06-01 02:13:37 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-01 02:13:37 (10182) [INFO] Trying other mirror. * 2025-06-01 02:14:03 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-06-01 02:14:03 (10182) [INFO] Trying other mirror. * 2025-06-01 02:14:07 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:14:07 (10182) [INFO] Trying other mirror. * 2025-06-01 02:14:34 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-01 02:14:34 (10182) [INFO] Trying other mirror. * 2025-06-01 02:15:20 (10182) [INFO] Metadata Cache Created * 2025-06-01 02:15:20 (10199) [INFO] * 2025-06-01 02:15:20 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-06-01 02:15:20 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-01 02:15:20 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-01 02:15:20 (10169) [INFO] * 2025-06-01 02:15:20 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-01 02:15:20 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-01 02:15:20 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-01 02:15:20 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-01 02:15:20 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-01 02:15:20 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-01 02:15:20 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-01 02:15:20 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-01 02:15:20 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-01 02:15:20 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-01 02:15:21 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-01 02:15:21 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-01 02:15:21 (10199) [INFO] * 2025-06-01 02:15:21 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-01 02:15:21 (10169) [INFO] * 2025-06-01 02:15:22 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-01 02:15:22 (10182) [INFO] Determining fastest mirrors * 2025-06-01 02:15:53 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-01 02:15:53 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-01 02:15:53 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-01 02:15:53 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-01 02:19:20 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-01 02:19:20 (10182) [INFO] Trying other mirror. * 2025-06-01 02:19:20 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:19:20 (10182) [INFO] Trying other mirror. * 2025-06-01 02:22:22 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-01 02:22:22 (10182) [INFO] Trying other mirror. * 2025-06-01 02:25:11 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-01 02:25:11 (10182) [INFO] Trying other mirror. * 2025-06-01 02:25:11 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-01 02:25:11 (10182) [INFO] Trying other mirror. * 2025-06-01 02:25:41 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:25:41 (10182) [INFO] Trying other mirror. * 2025-06-01 02:26:42 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:26:42 (10182) [INFO] Trying other mirror. * 2025-06-01 02:26:43 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-01 02:26:43 (10182) [INFO] Trying other mirror. * 2025-06-01 02:27:13 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:27:13 (10182) [INFO] Trying other mirror. * 2025-06-01 02:27:44 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-01 02:27:44 (10182) [INFO] Trying other mirror. * 2025-06-01 02:27:44 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-01 02:27:44 (10182) [INFO] Trying other mirror. * 2025-06-01 02:28:46 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-01 02:28:46 (10182) [INFO] Trying other mirror. * 2025-06-02 01:57:06 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-02 02:01:06 (11252) [INFO] Script is up to date. * 2025-06-02 02:05:10 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-02 02:05:10 (10169) [INFO] * 2025-06-02 02:06:50 (10199) [INFO] * 2025-06-02 02:06:50 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-02 02:06:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-02 02:06:50 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-02 02:06:50 (10169) [INFO] * 2025-06-02 02:06:54 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-02 02:06:54 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-02 02:06:54 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-02 02:06:54 (10169) [INFO] * 2025-06-02 02:07:08 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-02 02:07:13 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-02 02:07:13 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-02 02:07:13 (10169) [INFO] * 2025-06-02 02:07:14 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-02 02:07:14 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-02 02:07:44 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-02 02:07:44 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-02 02:07:44 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-02 02:07:44 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-02 02:08:31 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-02 02:08:31 (10182) [INFO] Trying other mirror. * 2025-06-02 02:11:23 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:11:23 (10182) [INFO] Trying other mirror. * 2025-06-02 02:11:40 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:11:40 (10182) [INFO] Trying other mirror. * 2025-06-02 02:12:10 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30832 milliseconds') * 2025-06-02 02:12:10 (10182) [INFO] Trying other mirror. * 2025-06-02 02:12:24 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-02 02:12:24 (10182) [INFO] Trying other mirror. * 2025-06-02 02:12:54 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:12:54 (10182) [INFO] Trying other mirror. * 2025-06-02 02:13:41 (10182) [INFO] Metadata Cache Created * 2025-06-02 02:13:41 (10199) [INFO] * 2025-06-02 02:13:41 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30832 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-02 02:13:41 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-02 02:13:41 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-02 02:13:41 (10169) [INFO] * 2025-06-02 02:13:42 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-02 02:13:42 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-02 02:13:42 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-02 02:13:42 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-02 02:13:42 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-02 02:13:42 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-02 02:13:42 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-02 02:13:42 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-02 02:13:42 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-02 02:13:42 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-02 02:13:43 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-02 02:13:43 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-02 02:13:43 (10199) [INFO] * 2025-06-02 02:13:43 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-02 02:13:43 (10169) [INFO] * 2025-06-02 02:13:44 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-02 02:13:44 (10182) [INFO] Determining fastest mirrors * 2025-06-02 02:14:16 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-02 02:14:16 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-02 02:14:16 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-02 02:14:16 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-02 02:15:02 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30046 milliseconds with 0 out of 0 bytes received') * 2025-06-02 02:15:02 (10182) [INFO] Trying other mirror. * 2025-06-02 02:15:33 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30659 milliseconds') * 2025-06-02 02:15:33 (10182) [INFO] Trying other mirror. * 2025-06-02 02:18:43 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-02 02:18:43 (10182) [INFO] Trying other mirror. * 2025-06-02 02:18:43 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-06-02 02:18:43 (10182) [INFO] Trying other mirror. * 2025-06-02 02:19:13 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-06-02 02:19:13 (10182) [INFO] Trying other mirror. * 2025-06-02 02:19:44 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-02 02:19:44 (10182) [INFO] Trying other mirror. * 2025-06-02 02:21:46 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30784 milliseconds') * 2025-06-02 02:21:46 (10182) [INFO] Trying other mirror. * 2025-06-02 02:25:04 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:25:04 (10182) [INFO] Trying other mirror. * 2025-06-02 02:25:04 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:25:04 (10182) [INFO] Trying other mirror. * 2025-06-02 02:26:06 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-02 02:26:06 (10182) [INFO] Trying other mirror. * 2025-06-02 02:26:07 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-02 02:26:07 (10182) [INFO] Trying other mirror. * 2025-06-02 02:26:37 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-02 02:26:37 (10182) [INFO] Trying other mirror. * 2025-06-03 02:11:02 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-03 02:15:03 (11252) [INFO] Script is up to date. * 2025-06-03 02:19:06 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-03 02:19:06 (10169) [INFO] * 2025-06-03 02:20:38 (10199) [INFO] * 2025-06-03 02:20:38 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-03 02:20:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-03 02:20:38 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-03 02:20:38 (10169) [INFO] * 2025-06-03 02:20:43 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-03 02:20:43 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-03 02:20:43 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-03 02:20:43 (10169) [INFO] * 2025-06-03 02:20:54 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-03 02:20:58 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-03 02:20:58 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-03 02:20:58 (10169) [INFO] * 2025-06-03 02:20:58 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-03 02:20:58 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-03 02:21:28 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-03 02:21:28 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-03 02:21:28 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-03 02:21:28 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-03 02:24:37 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-03 02:24:37 (10182) [INFO] Trying other mirror. * 2025-06-03 02:24:54 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:24:54 (10182) [INFO] Trying other mirror. * 2025-06-03 02:25:24 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-03 02:25:24 (10182) [INFO] Trying other mirror. * 2025-06-03 02:25:37 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:25:37 (10182) [INFO] Trying other mirror. * 2025-06-03 02:25:54 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:25:54 (10182) [INFO] Trying other mirror. * 2025-06-03 02:26:41 (10182) [INFO] Metadata Cache Created * 2025-06-03 02:26:42 (10199) [INFO] * 2025-06-03 02:26:42 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-03 02:26:42 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-03 02:26:42 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-03 02:26:42 (10169) [INFO] * 2025-06-03 02:26:42 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-03 02:26:42 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-03 02:26:42 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-03 02:26:42 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-03 02:26:42 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-03 02:26:42 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-03 02:26:42 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-03 02:26:42 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-03 02:26:42 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-03 02:26:42 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-03 02:26:43 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-03 02:26:43 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-03 02:26:43 (10199) [INFO] * 2025-06-03 02:26:43 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-03 02:26:43 (10169) [INFO] * 2025-06-03 02:26:44 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-03 02:26:44 (10182) [INFO] Determining fastest mirrors * 2025-06-03 02:27:16 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-03 02:27:16 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-03 02:27:16 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-03 02:27:16 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-03 02:30:42 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-03 02:30:42 (10182) [INFO] Trying other mirror. * 2025-06-03 02:30:42 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:30:42 (10182) [INFO] Trying other mirror. * 2025-06-03 02:33:45 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:33:45 (10182) [INFO] Trying other mirror. * 2025-06-03 02:36:33 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:36:33 (10182) [INFO] Trying other mirror. * 2025-06-03 02:36:34 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-03 02:36:34 (10182) [INFO] Trying other mirror. * 2025-06-03 02:37:35 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:37:35 (10182) [INFO] Trying other mirror. * 2025-06-03 02:37:35 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-03 02:37:35 (10182) [INFO] Trying other mirror. * 2025-06-03 02:38:06 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-03 02:38:06 (10182) [INFO] Trying other mirror. * 2025-06-03 02:38:06 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-03 02:38:06 (10182) [INFO] Trying other mirror. * 2025-06-03 02:38:36 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:38:36 (10182) [INFO] Trying other mirror. * 2025-06-03 02:38:36 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:38:36 (10182) [INFO] Trying other mirror. * 2025-06-03 02:39:07 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-06-03 02:39:07 (10182) [INFO] Trying other mirror. * 2025-06-03 02:39:38 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-03 02:39:38 (10182) [INFO] Trying other mirror. * 2025-06-03 02:39:38 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-03 02:39:38 (10182) [INFO] Trying other mirror. * 2025-06-03 02:40:39 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-03 02:40:39 (10182) [INFO] Trying other mirror. * 2025-06-04 01:55:29 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-04 01:59:29 (11252) [INFO] Script is up to date. * 2025-06-04 02:03:33 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-04 02:03:33 (10169) [INFO] * 2025-06-04 02:05:02 (10199) [INFO] * 2025-06-04 02:05:02 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-04 02:05:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-04 02:05:03 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-04 02:05:03 (10169) [INFO] * 2025-06-04 02:07:03 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-04 02:07:03 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-04 02:07:03 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-04 02:07:03 (10169) [INFO] * 2025-06-04 02:07:16 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-04 02:07:20 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-04 02:07:20 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-04 02:07:20 (10169) [INFO] * 2025-06-04 02:07:20 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-04 02:07:21 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-04 02:07:51 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-04 02:07:51 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-04 02:07:51 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-04 02:07:51 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-04 02:08:38 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') * 2025-06-04 02:08:38 (10182) [INFO] Trying other mirror. * 2025-06-04 02:09:08 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30065 milliseconds') * 2025-06-04 02:09:08 (10182) [INFO] Trying other mirror. * 2025-06-04 02:09:38 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-04 02:09:38 (10182) [INFO] Trying other mirror. * 2025-06-04 02:12:31 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-06-04 02:12:31 (10182) [INFO] Trying other mirror. * 2025-06-04 02:12:48 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-04 02:12:48 (10182) [INFO] Trying other mirror. * 2025-06-04 02:13:17 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-06-04 02:13:17 (10182) [INFO] Trying other mirror. * 2025-06-04 02:13:27 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-04 02:13:27 (10182) [INFO] Trying other mirror. * 2025-06-04 02:13:32 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-04 02:13:32 (10182) [INFO] Trying other mirror. * 2025-06-04 02:13:47 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-04 02:13:47 (10182) [INFO] Trying other mirror. * 2025-06-04 02:13:57 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-04 02:13:57 (10182) [INFO] Trying other mirror. * 2025-06-04 02:14:02 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-04 02:14:02 (10182) [INFO] Trying other mirror. * 2025-06-04 02:14:28 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-04 02:14:28 (10182) [INFO] Trying other mirror. * 2025-06-04 02:15:16 (10182) [INFO] Metadata Cache Created * 2025-06-04 02:15:16 (10199) [INFO] * 2025-06-04 02:15:16 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30065 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-06-04 02:15:16 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-04 02:15:16 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-04 02:15:16 (10169) [INFO] * 2025-06-04 02:15:16 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-04 02:15:17 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-04 02:15:17 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-04 02:15:17 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-04 02:15:17 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-04 02:15:17 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-04 02:15:17 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-04 02:15:17 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-04 02:15:17 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-04 02:15:17 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-04 02:15:18 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-04 02:15:18 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-04 02:15:18 (10199) [INFO] * 2025-06-04 02:15:18 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-04 02:15:18 (10169) [INFO] * 2025-06-04 02:15:18 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-04 02:15:19 (10182) [INFO] Determining fastest mirrors * 2025-06-04 02:15:50 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-04 02:15:50 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-04 02:15:50 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-04 02:15:50 (10182) [INFO] * epel: dl.fedoraproject.org * 2025-06-04 02:19:16 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-04 02:19:16 (10182) [INFO] Trying other mirror. * 2025-06-04 02:19:16 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-04 02:19:16 (10182) [INFO] Trying other mirror. * 2025-06-04 02:19:46 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-04 02:19:46 (10182) [INFO] Trying other mirror. * 2025-06-04 02:20:16 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-04 02:20:16 (10182) [INFO] Trying other mirror. * 2025-06-04 02:22:18 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-04 02:22:18 (10182) [INFO] Trying other mirror. * 2025-06-04 02:22:19 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-04 02:22:19 (10182) [INFO] Trying other mirror. * 2025-06-05 01:24:43 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-05 01:28:44 (11252) [INFO] Script is up to date. * 2025-06-05 01:32:47 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-05 01:32:47 (10169) [INFO] * 2025-06-05 01:34:24 (10199) [INFO] * 2025-06-05 01:34:24 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-05 01:34:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-05 01:34:24 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-05 01:34:24 (10169) [INFO] * 2025-06-05 01:41:24 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-05 01:41:24 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-05 01:41:24 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-05 01:41:24 (10169) [INFO] * 2025-06-05 01:41:37 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-05 01:41:40 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-05 01:41:40 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-05 01:41:40 (10169) [INFO] * 2025-06-05 01:41:41 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-05 01:41:41 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-05 01:42:11 (10182) [INFO] * EA4: 184.94.196.94 * 2025-06-05 01:42:11 (10182) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 2025-06-05 01:42:11 (10182) [INFO] * cpanel-plugins: 184.94.196.94 * 2025-06-05 01:42:11 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-05 01:42:58 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-05 01:42:58 (10182) [INFO] Trying other mirror. * 2025-06-05 01:43:28 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-05 01:43:28 (10182) [INFO] Trying other mirror. * 2025-06-05 01:46:20 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-05 01:46:20 (10182) [INFO] Trying other mirror. * 2025-06-05 01:46:37 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-05 01:46:37 (10182) [INFO] Trying other mirror. * 2025-06-05 01:47:17 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-05 01:47:17 (10182) [INFO] Trying other mirror. * 2025-06-05 01:47:20 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-05 01:47:20 (10182) [INFO] Trying other mirror. * 2025-06-05 01:48:04 (10182) [INFO] Metadata Cache Created * 2025-06-05 01:48:04 (10199) [INFO] * 2025-06-05 01:48:04 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-05 01:48:04 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-05 01:48:04 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-05 01:48:04 (10169) [INFO] * 2025-06-05 01:48:05 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-05 01:48:05 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-05 01:48:05 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-05 01:48:05 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-05 01:48:05 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-05 01:48:05 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-05 01:48:05 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-05 01:48:05 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-05 01:48:05 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-05 01:48:05 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-05 01:48:06 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-05 01:48:06 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-05 01:48:06 (10199) [INFO] * 2025-06-05 01:48:06 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-05 01:48:06 (10169) [INFO] * 2025-06-05 01:48:07 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-05 01:48:07 (10182) [INFO] Determining fastest mirrors * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] One of the configured repositories failed (Unknown), * 2025-06-05 01:48:37 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-05 01:48:37 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-05 01:48:37 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-05 01:48:37 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-05 01:48:37 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-05 01:48:37 (10182) [INFO] yum --disablerepo= ... * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-05 01:48:37 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-05 01:48:37 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] yum-config-manager --disable * 2025-06-05 01:48:37 (10182) [INFO] or * 2025-06-05 01:48:37 (10182) [INFO] subscription-manager repos --disable= * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-05 01:48:37 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-05 01:48:37 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-05 01:48:37 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-05 01:48:37 (10182) [INFO] compromise: * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-06-05 01:48:37 (10182) [INFO] * 2025-06-05 01:48:37 (10182) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-06-05 01:48:37 (10199) [INFO] * 2025-06-05 01:48:37 (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-05 01:48:37 (6397) [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 * 2025-06-05 01:48:39 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-05 01:48:39 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-05 01:48:39 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-05 01:48:39 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-05 01:48:39 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-06 01:58:54 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-06 02:02:54 (11252) [INFO] Script is up to date. * 2025-06-06 02:06:57 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-06 02:06:57 (10169) [INFO] * 2025-06-06 02:08:29 (10199) [INFO] * 2025-06-06 02:08:29 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-06 02:08:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-06 02:08:29 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-06 02:08:29 (10169) [INFO] * 2025-06-06 02:08:33 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-06 02:08:33 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-06 02:08:33 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-06 02:08:33 (10169) [INFO] * 2025-06-06 02:08:44 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-06 02:08:48 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-06 02:08:48 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-06 02:08:48 (10169) [INFO] * 2025-06-06 02:08:48 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-06 02:08:48 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-06 02:09:18 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-06 02:09:18 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-06 02:09:18 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-06 02:09:18 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-06 02:12:26 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:12:26 (10182) [INFO] Trying other mirror. * 2025-06-06 02:12:44 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:12:44 (10182) [INFO] Trying other mirror. * 2025-06-06 02:13:23 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') * 2025-06-06 02:13:23 (10182) [INFO] Trying other mirror. * 2025-06-06 02:13:27 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:13:27 (10182) [INFO] Trying other mirror. * 2025-06-06 02:13:54 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-06 02:13:54 (10182) [INFO] Trying other mirror. * 2025-06-06 02:13:58 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-06 02:13:58 (10182) [INFO] Trying other mirror. * 2025-06-06 02:14:25 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-06 02:14:25 (10182) [INFO] Trying other mirror. * 2025-06-06 02:14:28 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-06 02:14:28 (10182) [INFO] Trying other mirror. * 2025-06-06 02:14:56 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-06 02:14:56 (10182) [INFO] Trying other mirror. * 2025-06-06 02:15:40 (10182) [INFO] Metadata Cache Created * 2025-06-06 02:15:40 (10199) [INFO] * 2025-06-06 02:15:40 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-06-06 02:15:40 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-06 02:15:40 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-06 02:15:40 (10169) [INFO] * 2025-06-06 02:15:41 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-06 02:15:41 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-06 02:15:41 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-06 02:15:41 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-06 02:15:41 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-06 02:15:41 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-06 02:15:41 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-06 02:15:41 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-06 02:15:41 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-06 02:15:41 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-06 02:15:42 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-06 02:15:42 (10182) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-06 02:15:42 (10199) [INFO] * 2025-06-06 02:15:42 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-06 02:15:42 (10169) [INFO] * 2025-06-06 02:15:42 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-06 02:15:43 (10182) [INFO] Determining fastest mirrors * 2025-06-06 02:16:14 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-06 02:16:14 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-06 02:16:14 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-06 02:16:14 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-06 02:17:01 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-06-06 02:17:01 (10182) [INFO] Trying other mirror. * 2025-06-06 02:20:10 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-06 02:20:10 (10182) [INFO] Trying other mirror. * 2025-06-06 02:20:11 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-06-06 02:20:11 (10182) [INFO] Trying other mirror. * 2025-06-06 02:20:41 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-06 02:20:41 (10182) [INFO] Trying other mirror. * 2025-06-06 02:21:12 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-06-06 02:21:12 (10182) [INFO] Trying other mirror. * 2025-06-06 02:23:14 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-06 02:23:14 (10182) [INFO] Trying other mirror. * 2025-06-06 02:26:32 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:26:32 (10182) [INFO] Trying other mirror. * 2025-06-06 02:26:32 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:26:32 (10182) [INFO] Trying other mirror. * 2025-06-06 02:27:02 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received') * 2025-06-06 02:27:02 (10182) [INFO] Trying other mirror. * 2025-06-06 02:27:34 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30832 milliseconds') * 2025-06-06 02:27:34 (10182) [INFO] Trying other mirror. * 2025-06-06 02:28:35 (10182) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-06 02:28:35 (10182) [INFO] Trying other mirror. * 2025-06-06 02:28:35 (10182) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-06 02:28:35 (10182) [INFO] Trying other mirror. * 2025-06-07 01:48:36 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-07 01:52:36 (11252) [INFO] Script is up to date. * 2025-06-07 01:56:40 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-07 01:56:40 (10169) [INFO] * 2025-06-07 01:57:53 (10199) [INFO] * 2025-06-07 01:57:53 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-07 01:57:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-07 01:57:54 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-07 01:57:54 (10169) [INFO] * 2025-06-07 02:04:55 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-07 02:04:55 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-07 02:04:55 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-07 02:04:55 (10169) [INFO] * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-07 02:05:18 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-07 02:05:18 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-07 02:05:18 (10169) [INFO] * 2025-06-07 02:05:19 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-07 02:05:19 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-07 02:05:51 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-07 02:05:51 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-07 02:05:51 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-07 02:05:51 (10182) [INFO] * epel: mirror.math.princeton.edu * 2025-06-07 02:06:38 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-07 02:06:38 (10182) [INFO] Trying other mirror. * 2025-06-07 02:07:09 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-07 02:07:09 (10182) [INFO] Trying other mirror. * 2025-06-07 02:07:40 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-07 02:07:40 (10182) [INFO] Trying other mirror. * 2025-06-07 02:08:10 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-07 02:08:10 (10182) [INFO] Trying other mirror. * 2025-06-07 02:10:01 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-07 02:10:01 (10182) [INFO] Trying other mirror. * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-07 02:10:01 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-07 02:10:01 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-07 02:10:01 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-07 02:10:01 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-07 02:10:01 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-07 02:10:01 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-07 02:10:01 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-07 02:10:01 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-07 02:10:01 (10182) [INFO] or * 2025-06-07 02:10:01 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-07 02:10:01 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-07 02:10:01 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-07 02:10:01 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-07 02:10:01 (10182) [INFO] compromise: * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-07 02:10:01 (10182) [INFO] * 2025-06-07 02:10:01 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-07 02:10:01 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-07 02:10:01 (10199) [INFO] * 2025-06-07 02:10:01 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-07 02:10:01 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-07 02:10:01 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-07 02:10:01 (10169) [INFO] * 2025-06-07 02:10:02 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-07 02:10:03 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-07 02:10:03 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-07 02:10:03 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-07 02:10:03 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-07 02:10:03 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-07 02:10:03 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-07 02:10:03 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-07 02:10:03 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-07 02:10:03 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-07 02:10:03 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-07 02:10:03 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-07 02:10:03 (10199) [INFO] * 2025-06-07 02:10:03 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-07 02:10:03 (10169) [INFO] * 2025-06-07 02:10:03 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-07 02:10:04 (10182) [INFO] Determining fastest mirrors * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] One of the configured repositories failed (Unknown), * 2025-06-07 02:10:35 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-07 02:10:35 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-07 02:10:35 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-07 02:10:35 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-07 02:10:35 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-07 02:10:35 (10182) [INFO] yum --disablerepo= ... * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-07 02:10:35 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-07 02:10:35 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] yum-config-manager --disable * 2025-06-07 02:10:35 (10182) [INFO] or * 2025-06-07 02:10:35 (10182) [INFO] subscription-manager repos --disable= * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-07 02:10:35 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-07 02:10:35 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-07 02:10:35 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-07 02:10:35 (10182) [INFO] compromise: * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-06-07 02:10:35 (10182) [INFO] * 2025-06-07 02:10:35 (10182) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-06-07 02:10:35 (10199) [INFO] * 2025-06-07 02:10:35 (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-07 02:10:35 (6397) [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 * 2025-06-07 02:10:37 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-07 02:10:37 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-07 02:10:37 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-07 02:10:37 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-07 02:10:37 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-07 02:10:43 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VMygk5HEgh/ea_profile.json * 2025-06-07 02:13:23 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VMygk5HEgh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-07 02:13:23 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-08 01:46:41 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-08 01:50:41 (11252) [INFO] Script is up to date. * 2025-06-08 01:54:43 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-08 01:54:43 (10169) [INFO] * 2025-06-08 01:55:51 (10199) [INFO] * 2025-06-08 01:55:51 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-08 01:55:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-08 01:55:52 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-08 01:55:52 (10169) [INFO] * 2025-06-08 02:02:50 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-08 02:02:50 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-08 02:02:51 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-08 02:02:51 (10169) [INFO] * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-08 02:03:13 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-08 02:03:13 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-08 02:03:13 (10169) [INFO] * 2025-06-08 02:03:13 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-08 02:03:14 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-08 02:03:44 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-08 02:03:44 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-08 02:03:44 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-08 02:03:44 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-08 02:05:51 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:05:51 (10182) [INFO] Trying other mirror. * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-08 02:05:51 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-08 02:05:51 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-08 02:05:51 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-08 02:05:51 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-08 02:05:51 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-08 02:05:51 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-08 02:05:51 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-08 02:05:51 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-08 02:05:51 (10182) [INFO] or * 2025-06-08 02:05:51 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-08 02:05:51 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-08 02:05:51 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-08 02:05:51 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-08 02:05:51 (10182) [INFO] compromise: * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-08 02:05:51 (10182) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-08 02:05:51 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:05:51 (10199) [INFO] * 2025-06-08 02:05:51 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:05:51 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-08 02:05:51 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-08 02:05:51 (10169) [INFO] * 2025-06-08 02:05:51 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-08 02:05:52 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-08 02:05:52 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-08 02:05:52 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-08 02:05:52 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-08 02:05:52 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-08 02:05:52 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-08 02:05:52 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-08 02:05:52 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-08 02:05:52 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-08 02:05:52 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-08 02:05:52 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-08 02:05:52 (10199) [INFO] * 2025-06-08 02:05:52 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-08 02:05:52 (10169) [INFO] * 2025-06-08 02:05:52 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-08 02:05:53 (10182) [INFO] Determining fastest mirrors * 2025-06-08 02:06:24 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-08 02:06:24 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-08 02:06:24 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-08 02:06:24 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-08 02:07:11 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-08 02:07:11 (10182) [INFO] Trying other mirror. * 2025-06-08 02:09:09 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:09:09 (10182) [INFO] Trying other mirror. * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-08 02:09:09 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-08 02:09:09 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-08 02:09:09 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-08 02:09:09 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-08 02:09:09 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-08 02:09:09 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-08 02:09:09 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-08 02:09:09 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-08 02:09:09 (10182) [INFO] or * 2025-06-08 02:09:09 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-08 02:09:09 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-08 02:09:09 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-08 02:09:09 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-08 02:09:09 (10182) [INFO] compromise: * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-08 02:09:09 (10182) [INFO] * 2025-06-08 02:09:09 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-08 02:09:09 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:09:09 (10199) [INFO] * 2025-06-08 02:09:09 (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-08 02:09:09 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-08 02:09:11 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-08 02:09:11 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-08 02:09:11 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-08 02:09:11 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-08 02:09:11 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-09 01:52:31 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-09 01:56:32 (11252) [INFO] Script is up to date. * 2025-06-09 02:00:35 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-09 02:00:35 (10169) [INFO] * 2025-06-09 02:02:11 (10199) [INFO] * 2025-06-09 02:02:11 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-09 02:02:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-09 02:02:12 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-09 02:02:12 (10169) [INFO] * 2025-06-09 02:02:16 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-09 02:02:16 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-09 02:02:16 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-09 02:02:16 (10169) [INFO] * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-09 02:02:40 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-09 02:02:40 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-09 02:02:40 (10169) [INFO] * 2025-06-09 02:02:40 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-09 02:02:40 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-09 02:03:11 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-09 02:03:11 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-09 02:03:11 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-09 02:03:11 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-09 02:03:58 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') * 2025-06-09 02:03:58 (10182) [INFO] Trying other mirror. * 2025-06-09 02:05:48 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:05:48 (10182) [INFO] Trying other mirror. * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-09 02:05:48 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-09 02:05:48 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-09 02:05:48 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-09 02:05:48 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-09 02:05:48 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-09 02:05:48 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-09 02:05:48 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-09 02:05:48 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-09 02:05:48 (10182) [INFO] or * 2025-06-09 02:05:48 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-09 02:05:48 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-09 02:05:48 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-09 02:05:48 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-09 02:05:48 (10182) [INFO] compromise: * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-09 02:05:48 (10182) [INFO] * 2025-06-09 02:05:48 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-09 02:05:48 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:05:48 (10199) [INFO] * 2025-06-09 02:05:48 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:05:48 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-09 02:05:48 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-09 02:05:48 (10169) [INFO] * 2025-06-09 02:05:49 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-09 02:05:49 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-09 02:05:49 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-09 02:05:49 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-09 02:05:49 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-09 02:05:49 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-09 02:05:49 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-09 02:05:49 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-09 02:05:49 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-09 02:05:49 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-09 02:05:49 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-09 02:05:49 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-09 02:05:49 (10199) [INFO] * 2025-06-09 02:05:49 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-09 02:05:49 (10169) [INFO] * 2025-06-09 02:05:50 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-09 02:05:50 (10182) [INFO] Determining fastest mirrors * 2025-06-09 02:06:22 (10182) [INFO] * EA4: 184.94.196.94 * 2025-06-09 02:06:22 (10182) [INFO] * cpanel-addons-production-feed: 184.94.196.94 * 2025-06-09 02:06:22 (10182) [INFO] * cpanel-plugins: 184.94.196.94 * 2025-06-09 02:06:22 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-09 02:08:28 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:08:28 (10182) [INFO] Trying other mirror. * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-09 02:08:28 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-09 02:08:28 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-09 02:08:28 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-09 02:08:28 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-09 02:08:28 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-09 02:08:28 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-09 02:08:28 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-09 02:08:28 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-09 02:08:28 (10182) [INFO] or * 2025-06-09 02:08:28 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-09 02:08:28 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-09 02:08:28 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-09 02:08:28 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-09 02:08:28 (10182) [INFO] compromise: * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-09 02:08:28 (10182) [INFO] * 2025-06-09 02:08:28 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-09 02:08:28 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:08:28 (10199) [INFO] * 2025-06-09 02:08:28 (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-09 02:08:28 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-09 02:08:30 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-09 02:08:30 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-09 02:08:30 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-09 02:08:30 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-09 02:08:30 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-09 02:08:37 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nos2IMzEdF/ea_profile.json * 2025-06-09 02:12:18 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nos2IMzEdF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-09 02:12:18 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-10 01:46:36 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-10 01:50:36 (11252) [INFO] Script is up to date. * 2025-06-10 01:54:39 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-10 01:54:39 (10169) [INFO] * 2025-06-10 01:56:07 (10199) [INFO] * 2025-06-10 01:56:07 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-10 01:56:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-10 01:56:07 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-10 01:56:07 (10169) [INFO] * 2025-06-10 01:56:11 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-10 01:56:11 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-10 01:56:11 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-10 01:56:11 (10169) [INFO] * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-10 01:56:32 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-10 01:56:32 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-10 01:56:32 (10169) [INFO] * 2025-06-10 01:56:33 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-10 01:56:33 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-10 01:57:04 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-10 01:57:04 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-10 01:57:04 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-10 01:57:04 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-10 01:59:10 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 01:59:10 (10182) [INFO] Trying other mirror. * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-10 01:59:10 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-10 01:59:10 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-10 01:59:10 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-10 01:59:10 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-10 01:59:10 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-10 01:59:10 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-10 01:59:10 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-10 01:59:10 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-10 01:59:10 (10182) [INFO] or * 2025-06-10 01:59:10 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-10 01:59:10 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-10 01:59:10 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-10 01:59:10 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-10 01:59:10 (10182) [INFO] compromise: * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-10 01:59:10 (10182) [INFO] * 2025-06-10 01:59:10 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-10 01:59:10 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 01:59:10 (10199) [INFO] * 2025-06-10 01:59:10 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 01:59:10 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-10 01:59:10 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-10 01:59:10 (10169) [INFO] * 2025-06-10 01:59:11 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-10 01:59:11 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-10 01:59:11 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-10 01:59:11 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-10 01:59:11 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-10 01:59:11 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-10 01:59:11 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-10 01:59:11 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-10 01:59:11 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-10 01:59:11 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-10 01:59:11 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-10 01:59:11 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-10 01:59:11 (10199) [INFO] * 2025-06-10 01:59:11 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-10 01:59:11 (10169) [INFO] * 2025-06-10 01:59:12 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-10 01:59:12 (10182) [INFO] Determining fastest mirrors * 2025-06-10 01:59:45 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-10 01:59:45 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-10 01:59:45 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-10 01:59:45 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-10 02:01:51 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 02:01:51 (10182) [INFO] Trying other mirror. * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-10 02:01:51 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-10 02:01:51 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-10 02:01:51 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-10 02:01:51 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-10 02:01:51 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-10 02:01:51 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-10 02:01:51 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-10 02:01:51 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-10 02:01:51 (10182) [INFO] or * 2025-06-10 02:01:51 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-10 02:01:51 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-10 02:01:51 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-10 02:01:51 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-10 02:01:51 (10182) [INFO] compromise: * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-10 02:01:51 (10182) [INFO] * 2025-06-10 02:01:51 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-10 02:01:51 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 02:01:51 (10199) [INFO] * 2025-06-10 02:01: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-10 02:01:51 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-10 02:01:53 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-10 02:01:53 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-10 02:01:53 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-10 02:01:53 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-10 02:01:53 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-10 02:02:01 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8zYNTm1so0/ea_profile.json * 2025-06-10 02:05:14 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8zYNTm1so0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-10 02:05:14 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-11 01:45:21 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-11 01:49:22 (11252) [INFO] Script is up to date. * 2025-06-11 01:53:25 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-11 01:53:25 (10169) [INFO] * 2025-06-11 01:54:51 (10199) [INFO] * 2025-06-11 01:54:51 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-11 01:54:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-11 01:54:51 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.62) does not appear to be up to date. Please upgrade cPanel to 11.110.0.67. * 2025-06-11 01:54:51 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-11 01:54:51 (10169) [INFO] * 2025-06-11 02:01:53 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-11 02:01:53 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-11 02:01:53 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-11 02:01:53 (10169) [INFO] * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-11 02:02:16 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-11 02:02:16 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-11 02:02:16 (10169) [INFO] * 2025-06-11 02:02:16 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 02:02:17 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-11 02:02:47 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-11 02:02:47 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-11 02:02:47 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-11 02:02:47 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-11 02:03:34 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-11 02:03:34 (10182) [INFO] Trying other mirror. * 2025-06-11 02:05:24 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:05:24 (10182) [INFO] Trying other mirror. * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-11 02:05:24 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-11 02:05:24 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-11 02:05:24 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-11 02:05:24 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-11 02:05:24 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-11 02:05:24 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-11 02:05:24 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-11 02:05:24 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-11 02:05:24 (10182) [INFO] or * 2025-06-11 02:05:24 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-11 02:05:24 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-11 02:05:24 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-11 02:05:24 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-11 02:05:24 (10182) [INFO] compromise: * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-11 02:05:24 (10182) [INFO] * 2025-06-11 02:05:24 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-11 02:05:24 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:05:24 (10199) [INFO] * 2025-06-11 02:05:24 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:05:24 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-11 02:05:25 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-11 02:05:25 (10169) [INFO] * 2025-06-11 02:05:25 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 02:05:25 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-11 02:05:25 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-11 02:05:25 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-11 02:05:25 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-11 02:05:25 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-11 02:05:25 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-11 02:05:25 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-11 02:05:25 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-11 02:05:25 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-11 02:05:26 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-11 02:05:26 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-11 02:05:26 (10199) [INFO] * 2025-06-11 02:05:26 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-11 02:05:26 (10169) [INFO] * 2025-06-11 02:05:26 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 02:05:26 (10182) [INFO] Determining fastest mirrors * 2025-06-11 02:05:58 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-11 02:05:58 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-11 02:05:58 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-11 02:05:58 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-11 02:06:45 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') * 2025-06-11 02:06:45 (10182) [INFO] Trying other mirror. * 2025-06-11 02:08:36 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:08:36 (10182) [INFO] Trying other mirror. * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-11 02:08:36 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-11 02:08:36 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-11 02:08:36 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-11 02:08:36 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-11 02:08:36 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-11 02:08:36 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-11 02:08:36 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-11 02:08:36 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-11 02:08:36 (10182) [INFO] or * 2025-06-11 02:08:36 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-11 02:08:36 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-11 02:08:36 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-11 02:08:36 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-11 02:08:36 (10182) [INFO] compromise: * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-11 02:08:36 (10182) [INFO] * 2025-06-11 02:08:36 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-11 02:08:36 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:08:36 (10199) [INFO] * 2025-06-11 02:08:36 (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 02:08:36 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30901 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-11 02:08:37 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-11 02:08:37 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-11 02:08:37 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-11 02:08:37 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-11 02:08:37 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-12 01:45:14 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-12 01:49:14 (11252) [INFO] Script is up to date. * 2025-06-12 01:53:17 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-12 01:53:17 (10169) [INFO] * 2025-06-12 01:54:46 (10199) [INFO] * 2025-06-12 01:54:46 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-12 01:54:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-12 01:54:47 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.62) does not appear to be up to date. Additionally, we were unable to determine the expected version for this build. * 2025-06-12 01:54:47 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-12 01:54:47 (10169) [INFO] * 2025-06-12 02:01:48 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-12 02:01:48 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-12 02:01:48 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-12 02:01:48 (10169) [INFO] * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-12 02:02:09 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-12 02:02:09 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-12 02:02:09 (10169) [INFO] * 2025-06-12 02:02:10 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 02:02:10 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-12 02:02:41 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-12 02:02:41 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-12 02:02:41 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-12 02:02:41 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-12 02:04:47 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:04:47 (10182) [INFO] Trying other mirror. * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-12 02:04:47 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-12 02:04:47 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-12 02:04:47 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-12 02:04:47 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-12 02:04:47 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-12 02:04:47 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-12 02:04:47 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-12 02:04:47 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-12 02:04:47 (10182) [INFO] or * 2025-06-12 02:04:47 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-12 02:04:47 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-12 02:04:47 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-12 02:04:47 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-12 02:04:47 (10182) [INFO] compromise: * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-12 02:04:47 (10182) [INFO] * 2025-06-12 02:04:47 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-12 02:04:47 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:04:47 (10199) [INFO] * 2025-06-12 02:04:47 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:04:47 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-12 02:04:47 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-12 02:04:47 (10169) [INFO] * 2025-06-12 02:04:48 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 02:04:48 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-12 02:04:48 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-12 02:04:48 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-12 02:04:48 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-12 02:04:48 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-12 02:04:48 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-12 02:04:48 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-12 02:04:48 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-12 02:04:48 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-12 02:04:48 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-12 02:04:48 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-12 02:04:48 (10199) [INFO] * 2025-06-12 02:04:48 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-12 02:04:48 (10169) [INFO] * 2025-06-12 02:04:49 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 02:04:49 (10182) [INFO] Determining fastest mirrors * 2025-06-12 02:05:21 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-12 02:05:21 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-12 02:05:21 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-12 02:05:21 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-12 02:06:08 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-12 02:06:08 (10182) [INFO] Trying other mirror. * 2025-06-12 02:07:58 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:07:58 (10182) [INFO] Trying other mirror. * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-12 02:07:58 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-12 02:07:58 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-12 02:07:58 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-12 02:07:58 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-12 02:07:58 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-12 02:07:58 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-12 02:07:58 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-12 02:07:58 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-12 02:07:58 (10182) [INFO] or * 2025-06-12 02:07:58 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-12 02:07:58 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-12 02:07:58 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-12 02:07:58 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-12 02:07:58 (10182) [INFO] compromise: * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-12 02:07:58 (10182) [INFO] * 2025-06-12 02:07:58 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-12 02:07:58 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:07:58 (10199) [INFO] * 2025-06-12 02:07:58 (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 02:07:58 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-12 02:08:00 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-12 02:08:00 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-12 02:08:00 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-12 02:08:00 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-12 02:08:00 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-13 01:51:10 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-13 01:55:11 (11252) [INFO] Script is up to date. * 2025-06-13 01:59:13 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-13 01:59:13 (10169) [INFO] * 2025-06-13 02:00:45 (10199) [INFO] * 2025-06-13 02:00:45 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-13 02:00:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-13 02:00:45 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.62) does not appear to be up to date. Please upgrade cPanel to 11.110.0.68. * 2025-06-13 02:00:45 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-13 02:00:45 (10169) [INFO] * 2025-06-13 02:07:05 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-13 02:07:05 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-13 02:07:05 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-13 02:07:05 (10169) [INFO] * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-13 02:07:28 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-13 02:07:28 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-13 02:07:28 (10169) [INFO] * 2025-06-13 02:07:29 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 02:07:29 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-13 02:08:00 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-13 02:08:00 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-13 02:08:00 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-13 02:08:00 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-13 02:10:06 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:10:06 (10182) [INFO] Trying other mirror. * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-13 02:10:06 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-13 02:10:06 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-13 02:10:06 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-13 02:10:06 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-13 02:10:06 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-13 02:10:06 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-13 02:10:06 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-13 02:10:06 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-13 02:10:06 (10182) [INFO] or * 2025-06-13 02:10:06 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-13 02:10:06 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-13 02:10:06 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-13 02:10:06 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-13 02:10:06 (10182) [INFO] compromise: * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-13 02:10:06 (10182) [INFO] * 2025-06-13 02:10:06 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-13 02:10:06 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:10:06 (10199) [INFO] * 2025-06-13 02:10:06 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:10:06 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-13 02:10:06 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-13 02:10:06 (10169) [INFO] * 2025-06-13 02:10:07 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 02:10:07 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-13 02:10:07 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-13 02:10:07 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-13 02:10:07 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-13 02:10:07 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-13 02:10:07 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-13 02:10:07 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-13 02:10:07 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-13 02:10:07 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-13 02:10:07 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-13 02:10:07 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-13 02:10:07 (10199) [INFO] * 2025-06-13 02:10:07 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-13 02:10:07 (10169) [INFO] * 2025-06-13 02:10:08 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 02:10:08 (10182) [INFO] Determining fastest mirrors * 2025-06-13 02:10:40 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-13 02:10:40 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-13 02:10:40 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-13 02:10:40 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-13 02:12:47 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:12:47 (10182) [INFO] Trying other mirror. * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-13 02:12:47 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-13 02:12:47 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-13 02:12:47 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-13 02:12:47 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-13 02:12:47 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-13 02:12:47 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-13 02:12:47 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-13 02:12:47 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-13 02:12:47 (10182) [INFO] or * 2025-06-13 02:12:47 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-13 02:12:47 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-13 02:12:47 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-13 02:12:47 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-13 02:12:47 (10182) [INFO] compromise: * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-13 02:12:47 (10182) [INFO] * 2025-06-13 02:12:47 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-13 02:12:47 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:12:47 (10199) [INFO] * 2025-06-13 02:12:47 (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 02:12:47 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-13 02:12:49 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-13 02:12:49 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-13 02:12:49 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-13 02:12:49 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-13 02:12:49 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-13 02:12:57 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/990IdiO67J/ea_profile.json * 2025-06-13 02:15:35 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/990IdiO67J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-13 02:15:35 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-14 01:55:45 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-14 01:59:46 (11252) [INFO] Script is up to date. * 2025-06-14 02:03:48 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-14 02:03:48 (10169) [INFO] * 2025-06-14 02:04:54 (10199) [INFO] * 2025-06-14 02:04:54 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-14 02:04:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-14 02:04:55 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-14 02:04:55 (10169) [INFO] * 2025-06-14 02:07:05 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-14 02:07:05 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-14 02:07:05 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-14 02:07:05 (10169) [INFO] * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-14 02:07:27 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-14 02:07:27 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-14 02:07:27 (10169) [INFO] * 2025-06-14 02:07:28 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-14 02:07:28 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-14 02:07:59 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-14 02:07:59 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-14 02:07:59 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-14 02:07:59 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-14 02:08:46 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-14 02:08:46 (10182) [INFO] Trying other mirror. * 2025-06-14 02:10:37 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:10:37 (10182) [INFO] Trying other mirror. * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-14 02:10:37 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-14 02:10:37 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-14 02:10:37 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-14 02:10:37 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-14 02:10:37 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-14 02:10:37 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-14 02:10:37 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-14 02:10:37 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-14 02:10:37 (10182) [INFO] or * 2025-06-14 02:10:37 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-14 02:10:37 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-14 02:10:37 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-14 02:10:37 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-14 02:10:37 (10182) [INFO] compromise: * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-14 02:10:37 (10182) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-14 02:10:37 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:10:37 (10199) [INFO] * 2025-06-14 02:10:37 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:10:37 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-14 02:10:37 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-14 02:10:37 (10169) [INFO] * 2025-06-14 02:10:37 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-14 02:10:38 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-14 02:10:38 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-14 02:10:38 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-14 02:10:38 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-14 02:10:38 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-14 02:10:38 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-14 02:10:38 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-14 02:10:38 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-14 02:10:38 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-14 02:10:38 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-14 02:10:38 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-14 02:10:38 (10199) [INFO] * 2025-06-14 02:10:38 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-14 02:10:38 (10169) [INFO] * 2025-06-14 02:10:38 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-14 02:10:39 (10182) [INFO] Determining fastest mirrors * 2025-06-14 02:11:10 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-14 02:11:10 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-14 02:11:10 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-14 02:11:10 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-14 02:13:17 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:13:17 (10182) [INFO] Trying other mirror. * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-14 02:13:17 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-14 02:13:17 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-14 02:13:17 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-14 02:13:17 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-14 02:13:17 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-14 02:13:17 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-14 02:13:17 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-14 02:13:17 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-14 02:13:17 (10182) [INFO] or * 2025-06-14 02:13:17 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-14 02:13:17 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-14 02:13:17 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-14 02:13:17 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-14 02:13:17 (10182) [INFO] compromise: * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-14 02:13:17 (10182) [INFO] * 2025-06-14 02:13:17 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-14 02:13:17 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:13:17 (10199) [INFO] * 2025-06-14 02:13:17 (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-14 02:13:17 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-14 02:13:19 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-14 02:13:19 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-14 02:13:19 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-14 02:13:19 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-14 02:13:19 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-15 01:46:20 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-15 01:50:21 (11252) [INFO] Script is up to date. * 2025-06-15 01:54:24 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-15 01:54:24 (10169) [INFO] * 2025-06-15 01:55:27 (10199) [INFO] * 2025-06-15 01:55:27 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-15 01:55:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-15 01:55:27 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-15 01:55:27 (10169) [INFO] * 2025-06-15 02:02:27 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-15 02:02:27 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-15 02:02:27 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-15 02:02:27 (10169) [INFO] * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-15 02:02:50 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-15 02:02:50 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-15 02:02:50 (10169) [INFO] * 2025-06-15 02:02:50 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-15 02:02:51 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-15 02:03:21 (10182) [INFO] * EA4: 63.247.64.58 * 2025-06-15 02:03:21 (10182) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-15 02:03:21 (10182) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-15 02:03:21 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-15 02:04:08 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30833 milliseconds') * 2025-06-15 02:04:08 (10182) [INFO] Trying other mirror. * 2025-06-15 02:05:58 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:05:58 (10182) [INFO] Trying other mirror. * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-15 02:05:59 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-15 02:05:59 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-15 02:05:59 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-15 02:05:59 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-15 02:05:59 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-15 02:05:59 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-15 02:05:59 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-15 02:05:59 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-15 02:05:59 (10182) [INFO] or * 2025-06-15 02:05:59 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-15 02:05:59 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-15 02:05:59 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-15 02:05:59 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-15 02:05:59 (10182) [INFO] compromise: * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-15 02:05:59 (10182) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-15 02:05:59 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:05:59 (10199) [INFO] * 2025-06-15 02:05:59 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30833 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:05:59 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-15 02:05:59 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-15 02:05:59 (10169) [INFO] * 2025-06-15 02:05:59 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-15 02:05:59 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-15 02:05:59 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-15 02:05:59 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-15 02:05:59 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-15 02:05:59 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-15 02:05:59 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-15 02:05:59 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-15 02:05:59 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-15 02:05:59 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-15 02:06:00 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-15 02:06:00 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-15 02:06:00 (10199) [INFO] * 2025-06-15 02:06:00 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-15 02:06:00 (10169) [INFO] * 2025-06-15 02:06:00 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-15 02:06:00 (10182) [INFO] Determining fastest mirrors * 2025-06-15 02:06:33 (10182) [INFO] * EA4: 208.74.123.61 * 2025-06-15 02:06:33 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-15 02:06:33 (10182) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-15 02:06:33 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-15 02:07:19 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-15 02:07:19 (10182) [INFO] Trying other mirror. * 2025-06-15 02:09:10 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:09:10 (10182) [INFO] Trying other mirror. * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-15 02:09:10 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-15 02:09:10 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-15 02:09:10 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-15 02:09:10 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-15 02:09:10 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-15 02:09:10 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-15 02:09:10 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-15 02:09:10 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-15 02:09:10 (10182) [INFO] or * 2025-06-15 02:09:10 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-15 02:09:10 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-15 02:09:10 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-15 02:09:10 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-15 02:09:10 (10182) [INFO] compromise: * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-15 02:09:10 (10182) [INFO] * 2025-06-15 02:09:10 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-15 02:09:10 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:09:10 (10199) [INFO] * 2025-06-15 02:09:10 (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-15 02:09:10 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-15 02:09:12 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-15 02:09:12 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-15 02:09:12 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-15 02:09:12 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-15 02:09:12 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-16 01:46:47 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-16 01:50:47 (11252) [INFO] Script is up to date. * 2025-06-16 01:54:51 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-16 01:54:51 (10169) [INFO] * 2025-06-16 01:56:27 (10199) [INFO] * 2025-06-16 01:56:27 (6820) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-16 01:56:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-16 01:56:27 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-16 01:56:27 (10169) [INFO] * 2025-06-16 01:56:32 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-16 01:56:32 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-16 01:56:32 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-16 01:56:32 (10169) [INFO] * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-16 01:56:54 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-16 01:56:54 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-16 01:56:54 (10169) [INFO] * 2025-06-16 01:56:55 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-16 01:56:55 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-16 01:57:25 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-16 01:57:26 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-16 01:57:26 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-16 01:57:26 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-16 01:59:32 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 01:59:32 (10182) [INFO] Trying other mirror. * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-16 01:59:32 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-16 01:59:32 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-16 01:59:32 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-16 01:59:32 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-16 01:59:32 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-16 01:59:32 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-16 01:59:32 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-16 01:59:32 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-16 01:59:32 (10182) [INFO] or * 2025-06-16 01:59:32 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-16 01:59:32 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-16 01:59:32 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-16 01:59:32 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-16 01:59:32 (10182) [INFO] compromise: * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-16 01:59:32 (10182) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-16 01:59:32 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 01:59:32 (10199) [INFO] * 2025-06-16 01:59:32 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 01:59:32 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-16 01:59:32 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-16 01:59:32 (10169) [INFO] * 2025-06-16 01:59:32 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-16 01:59:33 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-16 01:59:33 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-16 01:59:33 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-16 01:59:33 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-16 01:59:33 (10182) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-16 01:59:33 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-16 01:59:33 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-16 01:59:33 (10182) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-16 01:59:33 (10182) [INFO] : wp-toolkit-thirdparties * 2025-06-16 01:59:33 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-16 01:59:33 (10182) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-16 01:59:33 (10199) [INFO] * 2025-06-16 01:59:33 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-16 01:59:33 (10169) [INFO] * 2025-06-16 01:59:33 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-16 01:59:34 (10182) [INFO] Determining fastest mirrors * 2025-06-16 02:00:05 (10182) [INFO] * EA4: 208.74.123.62 * 2025-06-16 02:00:05 (10182) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-16 02:00:05 (10182) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-16 02:00:05 (10182) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-16 02:00:51 (10182) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-16 02:00:51 (10182) [INFO] Trying other mirror. * 2025-06-16 02:02:42 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 02:02:42 (10182) [INFO] Trying other mirror. * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-16 02:02:42 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-16 02:02:42 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-16 02:02:42 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-16 02:02:42 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-16 02:02:42 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-16 02:02:42 (10182) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-16 02:02:42 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-16 02:02:42 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-16 02:02:42 (10182) [INFO] or * 2025-06-16 02:02:42 (10182) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-16 02:02:42 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-16 02:02:42 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-16 02:02:42 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-16 02:02:42 (10182) [INFO] compromise: * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-16 02:02:42 (10182) [INFO] * 2025-06-16 02:02:42 (10182) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-16 02:02:42 (10182) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 02:02:42 (10199) [INFO] * 2025-06-16 02:02:42 (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-16 02:02:42 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-16 02:02:44 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-16 02:02:44 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-16 02:02:44 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-16 02:02:44 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-16 02:02:44 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-16 02:02:52 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VuUfl2qlvF/ea_profile.json * 2025-06-16 02:05:30 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VuUfl2qlvF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-16 02:05:30 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-17 01:45:43 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-17 01:49:43 (11235) [INFO] Newer version of script found. Downloading. * 2025-06-17 01:53:45 (11244) [INFO] Script update to version 67 successful. * 2025-06-17 01:57:48 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-17 01:57:48 (10195) [INFO] * 2025-06-17 01:59:13 (10225) [INFO] * 2025-06-17 01:59:13 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-17 01:59:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-17 01:59:13 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-17 01:59:13 (10195) [INFO] * 2025-06-17 01:59:16 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-17 01:59:16 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-17 01:59:16 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-17 01:59:16 (10195) [INFO] * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-17 01:59:37 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-17 01:59:37 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-17 01:59:37 (10195) [INFO] * 2025-06-17 01:59:38 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-17 01:59:38 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-17 02:00:08 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-17 02:00:08 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-17 02:00:08 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-17 02:00:08 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-17 02:02:14 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:02:14 (10208) [INFO] Trying other mirror. * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-17 02:02:14 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-17 02:02:14 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-17 02:02:14 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-17 02:02:14 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-17 02:02:14 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-17 02:02:14 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-17 02:02:14 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-17 02:02:14 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-17 02:02:14 (10208) [INFO] or * 2025-06-17 02:02:14 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-17 02:02:14 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-17 02:02:14 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-17 02:02:14 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-17 02:02:14 (10208) [INFO] compromise: * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-17 02:02:14 (10208) [INFO] * 2025-06-17 02:02:14 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-17 02:02:14 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:02:14 (10225) [INFO] * 2025-06-17 02:02:14 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:02:14 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-17 02:02:14 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-17 02:02:14 (10195) [INFO] * 2025-06-17 02:02:15 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-17 02:02:15 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-17 02:02:15 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-17 02:02:15 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-17 02:02:15 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-17 02:02:15 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-17 02:02:15 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-17 02:02:15 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-17 02:02:15 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-17 02:02:15 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-17 02:02:15 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-17 02:02:15 (10208) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-17 02:02:15 (10225) [INFO] * 2025-06-17 02:02:15 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-17 02:02:15 (10195) [INFO] * 2025-06-17 02:02:16 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-17 02:02:16 (10208) [INFO] Determining fastest mirrors * 2025-06-17 02:02:48 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-17 02:02:48 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-17 02:02:48 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-17 02:02:48 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-17 02:04:54 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:04:54 (10208) [INFO] Trying other mirror. * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-17 02:04:54 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-17 02:04:54 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-17 02:04:54 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-17 02:04:54 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-17 02:04:54 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-17 02:04:54 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-17 02:04:54 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-17 02:04:54 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-17 02:04:54 (10208) [INFO] or * 2025-06-17 02:04:54 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-17 02:04:54 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-17 02:04:54 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-17 02:04:54 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-17 02:04:54 (10208) [INFO] compromise: * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-17 02:04:54 (10208) [INFO] * 2025-06-17 02:04:54 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-17 02:04:54 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:04:54 (10225) [INFO] * 2025-06-17 02:04:54 (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-17 02:04:54 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzQ4OTY2NjAxOjE3NDkyMjU4MDE6e5r9O9YmjI4gFSf_fF8KDPHZt2FL5nlgbFNW9ybeub9dkvEnVkY6yB0VkVuQV13uT7bBqWt67JaTUhVK65bJ-1lWTjkItYbEUlX_TJLuWwKZ4lSEILBnzIRznputmJT1lkWoCgZ9j5Exq_F_gv-zbQAcc50E6JDQ6azqT__H5BWSmXmet2WiSDnMgDjFZFLe68lathsnNlkJc358qtN4Sv025bi_hdUc_d1nVTe8s3qgeC4f6GpwUOLixkGJOxJDvjAGhOPs_NcFix6LjwEBLglVqjTbcKtsLQpOhRquKkyvD-SdkWiPbZ97hc24FHzK9t59yzGTmUg6_Rw4TK8QBpcBy7tZU8sD7b-ycYoHEOJy5ZOVYkpWaFNjFopZZSwKnUEJxLWO7HXXnlsl2bYnIbp6y7AymuldsdFBFjOjFliKmdYFJikOEV3rxxFlZD-VaH2jaZLXfi6cWMuv58m-7RC6vu_AXuF7dboLrk9vN6Blk_cvwPNMGMfqZMQ5kaDAIUaqQ_31LQHXAGvvi7cyO7ohTXJ01idYIfEzAFN7IV-CD25Xa8E4TWq7mJNUcbYX-bxnnMQLCdj312arroiq1E_4vmwe165IZgqkQEv_05JXkTHsr29mWutxISHac447PXSvVek5WFOUzHWueDz8MbTetGwQJwoYv4d2IOGVKSs=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-17 02:04:56 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-17 02:04:56 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-17 02:04:56 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-17 02:04:56 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-17 02:04:56 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-17 02:05:05 (9314) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DqyokKzgS6/ea_profile.json * 2025-06-17 02:09:30 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DqyokKzgS6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9316. * 2025-06-17 02:09:30 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-18 02:14:35 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-18 02:18:35 (11278) [INFO] Script is up to date. * 2025-06-18 02:22:39 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-18 02:22:39 (10195) [INFO] * 2025-06-18 02:24:07 (10225) [INFO] * 2025-06-18 02:24:07 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-18 02:24:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-18 02:24:08 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-18 02:24:08 (10195) [INFO] * 2025-06-18 02:31:09 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-18 02:31:09 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-18 02:31:09 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-18 02:31:09 (10195) [INFO] * 2025-06-18 02:31:21 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-18 02:31:24 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-18 02:31:24 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-18 02:31:24 (10195) [INFO] * 2025-06-18 02:31:24 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-18 02:31:24 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-18 02:31:54 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-18 02:31:54 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-18 02:31:54 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-18 02:31:54 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-18 02:35:03 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-18 02:35:03 (10208) [INFO] Trying other mirror. * 2025-06-18 02:35:19 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-18 02:35:19 (10208) [INFO] Trying other mirror. * 2025-06-18 02:35:59 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-18 02:35:59 (10208) [INFO] Trying other mirror. * 2025-06-18 02:36:02 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-18 02:36:02 (10208) [INFO] Trying other mirror. * 2025-06-18 02:36:43 (10208) [INFO] Metadata Cache Created * 2025-06-18 02:36:43 (10225) [INFO] * 2025-06-18 02:36:43 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-18 02:36:43 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-18 02:36:43 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-18 02:36:43 (10195) [INFO] * 2025-06-18 02:36:44 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-18 02:36:44 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-18 02:36:44 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-18 02:36:44 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-18 02:36:44 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-18 02:36:44 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-18 02:36:44 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-18 02:36:44 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-18 02:36:44 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-18 02:36:44 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-18 02:36:45 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-18 02:36:45 (10208) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-18 02:36:45 (10225) [INFO] * 2025-06-18 02:36:45 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-18 02:36:45 (10195) [INFO] * 2025-06-18 02:36:46 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-18 02:36:46 (10208) [INFO] Determining fastest mirrors * 2025-06-18 02:37:24 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-18 02:37:24 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-18 02:37:24 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-18 02:37:24 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-18 02:40:50 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-18 02:40:50 (10208) [INFO] Trying other mirror. * 2025-06-18 02:40:50 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-18 02:40:50 (10208) [INFO] Trying other mirror. * 2025-06-18 02:41:21 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-18 02:41:21 (10208) [INFO] Trying other mirror. * 2025-06-18 02:41:44 (10208) [INFO] https://repo.tuxcare.com/centos7-els//updates/x86_64/repodata/166bf4a98933c001c44c5084956ad23443ab433969c7020b36fe7d14aee11909-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:41:44 (10208) [INFO] Trying other mirror. * 2025-06-18 02:42:00 (10208) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:42:00 (10208) [INFO] Trying other mirror. * 2025-06-18 02:42:16 (10208) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:42:16 (10208) [INFO] Trying other mirror. * 2025-06-18 02:42:31 (10208) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:42:31 (10208) [INFO] Trying other mirror. * 2025-06-18 02:42:47 (10208) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:42:47 (10208) [INFO] Trying other mirror. * 2025-06-18 02:43:03 (10208) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:43:03 (10208) [INFO] Trying other mirror. * 2025-06-18 02:43:18 (10208) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:43:18 (10208) [INFO] Trying other mirror. * 2025-06-18 02:43:21 (10208) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:43:21 (10208) [INFO] Trying other mirror. * 2025-06-18 02:43:47 (10208) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/410dd43ac11ac1f987058a82f7ae5fbd906036065cb76888b82c2935f50b1f2f-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:43:47 (10208) [INFO] Trying other mirror. * 2025-06-18 02:43:51 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-18 02:43:51 (10208) [INFO] Trying other mirror. * 2025-06-18 02:44:03 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMTU3ODQyOjE3NTA0MTcwNDI6pZdi7He_LdlMKBN6eWbfqQGcf_BbToaHFjVBAmna-77SUpVZm-yvcQPJCEpEwAMJUWcRlxMenMXfmnWuhNl03szOgP5UjDlNq2IA2gbiLzhn7JYEMtQQWfZsFWSdmwpRCuQBoDi-72abuec9uRDQ0JrPjBO8u-R51XBxZ7L74NbjR9BszsPD6VMH8Orcx9ZOKuWtV9TbAYQHnvziymQWiwqxGVER-384KVTRzTvp5uUaER4XXpvTEvH9qMXfd-n-g5TtbESQ4R-D_xV-yPU5bvhnd32HrxzlMOq_6qCHzed8TqMFNpJg5V2oYjHPp_p-u2BfvBFrvkEJ91Ia2hK4sPHz1S4TJLoxAKZQwv5MVmSlyprKG8JNQVVc3FIYNfHxvrCvoeP8B5WPoivwA2nKg82r8sBQfaIP9w7N4_ki85Nh61TVaYXJnOQ5YaBcicgD1lyP4YjnDxklQBiIju2e2byR36WxXqewEm5smq_-m5n_MMzUkFkwlggenJvmd378aeLo-ao8FT1MzZ_4JiD2wiKPhxAhYjK6uqk7Ad4FmcMuB4__yImR2pZgx_-DcYGr_qrjiBcCB1pRLWTGKsqAcPWExDCqH3hTTxsGnxCefCngyFa_P54uHObZjw1wZBdCN-oaLn5o4dMYiK111klmFv6syBiDfbAy7IBEIwSE0hU%3D/ea-php/7/updates/x86_64/repodata/4ef612dfab94f1172dac445a8cfa2cf20cd714e582589daaee3f74db1487c7a9-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:44:03 (10208) [INFO] Trying other mirror. * 2025-06-18 02:44:18 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMTU3ODQyOjE3NTA0MTcwNDI6pZdi7He_LdlMKBN6eWbfqQGcf_BbToaHFjVBAmna-77SUpVZm-yvcQPJCEpEwAMJUWcRlxMenMXfmnWuhNl03szOgP5UjDlNq2IA2gbiLzhn7JYEMtQQWfZsFWSdmwpRCuQBoDi-72abuec9uRDQ0JrPjBO8u-R51XBxZ7L74NbjR9BszsPD6VMH8Orcx9ZOKuWtV9TbAYQHnvziymQWiwqxGVER-384KVTRzTvp5uUaER4XXpvTEvH9qMXfd-n-g5TtbESQ4R-D_xV-yPU5bvhnd32HrxzlMOq_6qCHzed8TqMFNpJg5V2oYjHPp_p-u2BfvBFrvkEJ91Ia2hK4sPHz1S4TJLoxAKZQwv5MVmSlyprKG8JNQVVc3FIYNfHxvrCvoeP8B5WPoivwA2nKg82r8sBQfaIP9w7N4_ki85Nh61TVaYXJnOQ5YaBcicgD1lyP4YjnDxklQBiIju2e2byR36WxXqewEm5smq_-m5n_MMzUkFkwlggenJvmd378aeLo-ao8FT1MzZ_4JiD2wiKPhxAhYjK6uqk7Ad4FmcMuB4__yImR2pZgx_-DcYGr_qrjiBcCB1pRLWTGKsqAcPWExDCqH3hTTxsGnxCefCngyFa_P54uHObZjw1wZBdCN-oaLn5o4dMYiK111klmFv6syBiDfbAy7IBEIwSE0hU%3D/ea-php/7/updates/x86_64/repodata/10a9211347890ce3c9f800c31bd207948792a08604a0f57e8533c61d8f3ec4c6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-06-18 02:44:18 (10208) [INFO] Trying other mirror. * 2025-06-19 02:06:21 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-19 02:10:21 (11278) [INFO] Script is up to date. * 2025-06-19 02:14:24 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-19 02:14:24 (10195) [INFO] * 2025-06-19 02:15:52 (10225) [INFO] * 2025-06-19 02:15:52 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-19 02:15:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-19 02:15:53 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-19 02:15:53 (10195) [INFO] * 2025-06-19 02:23:38 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-19 02:23:38 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-19 02:23:38 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-19 02:23:38 (10195) [INFO] * 2025-06-19 02:23:47 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-19 02:23:51 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-19 02:23:51 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-19 02:23:51 (10195) [INFO] * 2025-06-19 02:23:52 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-19 02:23:52 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-19 02:24:22 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-19 02:24:22 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-19 02:24:22 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-19 02:24:22 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-19 02:25:08 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2025-06-19 02:25:08 (10208) [INFO] Trying other mirror. * 2025-06-19 02:28:01 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-19 02:28:01 (10208) [INFO] Trying other mirror. * 2025-06-19 02:28:17 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-19 02:28:18 (10208) [INFO] Trying other mirror. * 2025-06-19 02:28:47 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-19 02:28:47 (10208) [INFO] Trying other mirror. * 2025-06-19 02:29:01 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-19 02:29:01 (10208) [INFO] Trying other mirror. * 2025-06-19 02:29:45 (10208) [INFO] Metadata Cache Created * 2025-06-19 02:29:45 (10225) [INFO] * 2025-06-19 02:29:45 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-19 02:29:45 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-19 02:29:45 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-19 02:29:45 (10195) [INFO] * 2025-06-19 02:29:45 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-19 02:29:46 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-19 02:29:46 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-19 02:29:46 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-19 02:29:46 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-19 02:29:46 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-19 02:29:46 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-19 02:29:46 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-19 02:29:46 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-19 02:29:46 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-19 02:29:47 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-19 02:29:47 (10208) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-19 02:29:47 (10225) [INFO] * 2025-06-19 02:29:47 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-19 02:29:47 (10195) [INFO] * 2025-06-19 02:29:47 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-19 02:29:48 (10208) [INFO] Determining fastest mirrors * 2025-06-19 02:30:19 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-19 02:30:19 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-19 02:30:19 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-19 02:30:19 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-19 02:31:06 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') * 2025-06-19 02:31:06 (10208) [INFO] Trying other mirror. * 2025-06-19 02:34:15 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-19 02:34:15 (10208) [INFO] Trying other mirror. * 2025-06-19 02:34:16 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-19 02:34:16 (10208) [INFO] Trying other mirror. * 2025-06-19 02:34:46 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-19 02:34:46 (10208) [INFO] Trying other mirror. * 2025-06-20 01:57:59 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-20 02:01:59 (11278) [INFO] Script is up to date. * 2025-06-20 02:06:03 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-20 02:06:03 (10195) [INFO] * 2025-06-20 02:07:28 (10225) [INFO] * 2025-06-20 02:07:28 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-20 02:07:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-20 02:07:29 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-20 02:07:29 (10195) [INFO] * 2025-06-20 02:07:32 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-20 02:07:32 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-20 02:07:32 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-20 02:07:32 (10195) [INFO] * 2025-06-20 02:07:44 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-20 02:07:47 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-20 02:07:47 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-20 02:07:47 (10195) [INFO] * 2025-06-20 02:07:47 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-20 02:07:47 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-20 02:08:17 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-20 02:08:17 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-20 02:08:17 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-20 02:08:17 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-20 02:11:26 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-06-20 02:11:26 (10208) [INFO] Trying other mirror. * 2025-06-20 02:11:42 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:11:42 (10208) [INFO] Trying other mirror. * 2025-06-20 02:12:12 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:12:12 (10208) [INFO] Trying other mirror. * 2025-06-20 02:12:26 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-20 02:12:26 (10208) [INFO] Trying other mirror. * 2025-06-20 02:12:57 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-20 02:12:57 (10208) [INFO] Trying other mirror. * 2025-06-20 02:13:28 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-20 02:13:28 (10208) [INFO] Trying other mirror. * 2025-06-20 02:13:59 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-20 02:13:59 (10208) [INFO] Trying other mirror. * 2025-06-20 02:14:30 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-06-20 02:14:30 (10208) [INFO] Trying other mirror. * 2025-06-20 02:15:00 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:15:00 (10208) [INFO] Trying other mirror. * 2025-06-20 02:15:42 (10208) [INFO] Metadata Cache Created * 2025-06-20 02:15:42 (10225) [INFO] * 2025-06-20 02:15:42 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-20 02:15:42 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-20 02:15:42 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-20 02:15:42 (10195) [INFO] * 2025-06-20 02:15:43 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-20 02:15:43 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-20 02:15:43 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-20 02:15:43 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-20 02:15:43 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-20 02:15:43 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-20 02:15:43 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-20 02:15:43 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-20 02:15:43 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-20 02:15:43 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-20 02:15:44 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-20 02:15:44 (10208) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-20 02:15:44 (10225) [INFO] * 2025-06-20 02:15:44 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-20 02:15:44 (10195) [INFO] * 2025-06-20 02:15:45 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-20 02:15:45 (10208) [INFO] Determining fastest mirrors * 2025-06-20 02:16:17 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-20 02:16:17 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-20 02:16:17 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-20 02:16:17 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-20 02:17:04 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30599 milliseconds') * 2025-06-20 02:17:04 (10208) [INFO] Trying other mirror. * 2025-06-20 02:17:35 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-20 02:17:35 (10208) [INFO] Trying other mirror. * 2025-06-20 02:20:44 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-20 02:20:44 (10208) [INFO] Trying other mirror. * 2025-06-20 02:20:45 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:20:45 (10208) [INFO] Trying other mirror. * 2025-06-20 02:23:47 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') * 2025-06-20 02:23:47 (10208) [INFO] Trying other mirror. * 2025-06-20 02:26:36 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:26:36 (10208) [INFO] Trying other mirror. * 2025-06-20 02:26:36 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-06-20 02:26:36 (10208) [INFO] Trying other mirror. * 2025-06-20 02:27:37 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:27:37 (10208) [INFO] Trying other mirror. * 2025-06-20 02:27:37 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-20 02:27:37 (10208) [INFO] Trying other mirror. * 2025-06-21 01:58:19 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-21 02:02:19 (11278) [INFO] Script is up to date. * 2025-06-21 02:06:23 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-21 02:06:23 (10195) [INFO] * 2025-06-21 02:07:30 (10225) [INFO] * 2025-06-21 02:07:30 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-21 02:07:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-21 02:07:31 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-21 02:07:31 (10195) [INFO] * 2025-06-21 02:07:34 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-21 02:07:34 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-21 02:07:34 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-21 02:07:34 (10195) [INFO] * 2025-06-21 02:07:48 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-21 02:07:52 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-21 02:07:52 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-21 02:07:52 (10195) [INFO] * 2025-06-21 02:07:53 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-21 02:07:53 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-21 02:08:23 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-21 02:08:23 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-21 02:08:23 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-21 02:08:23 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-21 02:09:10 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-21 02:09:10 (10208) [INFO] Trying other mirror. * 2025-06-21 02:12:03 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-21 02:12:03 (10208) [INFO] Trying other mirror. * 2025-06-21 02:12:19 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:12:19 (10208) [INFO] Trying other mirror. * 2025-06-21 02:12:49 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:12:49 (10208) [INFO] Trying other mirror. * 2025-06-21 02:13:03 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:13:03 (10208) [INFO] Trying other mirror. * 2025-06-21 02:13:48 (10208) [INFO] Metadata Cache Created * 2025-06-21 02:13:48 (10225) [INFO] * 2025-06-21 02:13:48 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-21 02:13:48 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-21 02:13:48 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-21 02:13:48 (10195) [INFO] * 2025-06-21 02:13:49 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-21 02:13:49 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-21 02:13:49 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-21 02:13:49 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-21 02:13:49 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-21 02:13:49 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-21 02:13:49 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-21 02:13:49 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-21 02:13:49 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-21 02:13:49 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-21 02:13:50 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-21 02:13:50 (10208) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-21 02:13:50 (10225) [INFO] * 2025-06-21 02:13:50 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-21 02:13:50 (10195) [INFO] * 2025-06-21 02:13:50 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-21 02:13:51 (10208) [INFO] Determining fastest mirrors * 2025-06-21 02:14:22 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-21 02:14:22 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-21 02:14:22 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-21 02:14:22 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-21 02:15:09 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-21 02:15:09 (10208) [INFO] Trying other mirror. * 2025-06-21 02:15:40 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-21 02:15:40 (10208) [INFO] Trying other mirror. * 2025-06-21 02:18:49 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:18:49 (10208) [INFO] Trying other mirror. * 2025-06-21 02:18:49 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-06-21 02:18:49 (10208) [INFO] Trying other mirror. * 2025-06-21 02:21:52 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-21 02:21:52 (10208) [INFO] Trying other mirror. * 2025-06-21 02:24:39 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:24:39 (10208) [INFO] Trying other mirror. * 2025-06-21 02:24:40 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-21 02:24:40 (10208) [INFO] Trying other mirror. * 2025-06-21 02:25:10 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-21 02:25:10 (10208) [INFO] Trying other mirror. * 2025-06-21 02:25:41 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-21 02:25:41 (10208) [INFO] Trying other mirror. * 2025-06-21 02:26:12 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:26:12 (10208) [INFO] Trying other mirror. * 2025-06-21 02:26:12 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-21 02:26:12 (10208) [INFO] Trying other mirror. * 2025-06-21 02:27:13 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:27:13 (10208) [INFO] Trying other mirror. * 2025-06-21 02:27:13 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-06-21 02:27:13 (10208) [INFO] Trying other mirror. * 2025-06-21 02:27:44 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-21 02:27:44 (10208) [INFO] Trying other mirror. * 2025-06-21 02:27:44 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-21 02:27:44 (10208) [INFO] Trying other mirror. * 2025-06-22 01:57:09 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-22 02:01:10 (11278) [INFO] Script is up to date. * 2025-06-22 02:05:12 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-22 02:05:12 (10195) [INFO] * 2025-06-22 02:06:18 (10225) [INFO] * 2025-06-22 02:06:18 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-22 02:06:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-22 02:06:18 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-22 02:06:18 (10195) [INFO] * 2025-06-22 02:07:03 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-22 02:07:03 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-22 02:07:03 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-22 02:07:03 (10195) [INFO] * 2025-06-22 02:07:16 (259) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-22 02:07:19 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-22 02:07:19 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-22 02:07:19 (10195) [INFO] * 2025-06-22 02:07:20 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-22 02:07:20 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-22 02:07:50 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-22 02:07:50 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-22 02:07:50 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-22 02:07:50 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-22 02:08:38 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') * 2025-06-22 02:08:38 (10208) [INFO] Trying other mirror. * 2025-06-22 02:11:30 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-06-22 02:11:30 (10208) [INFO] Trying other mirror. * 2025-06-22 02:11:47 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:11:47 (10208) [INFO] Trying other mirror. * 2025-06-22 02:12:17 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:12:17 (10208) [INFO] Trying other mirror. * 2025-06-22 02:12:27 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:12:27 (10208) [INFO] Trying other mirror. * 2025-06-22 02:12:31 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') * 2025-06-22 02:12:31 (10208) [INFO] Trying other mirror. * 2025-06-22 02:12:47 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:12:47 (10208) [INFO] Trying other mirror. * 2025-06-22 02:13:02 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:13:02 (10208) [INFO] Trying other mirror. * 2025-06-22 02:13:47 (10208) [INFO] Metadata Cache Created * 2025-06-22 02:13:47 (10225) [INFO] * 2025-06-22 02:13:47 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30598 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-06-22 02:13:47 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-22 02:13:47 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-22 02:13:47 (10195) [INFO] * 2025-06-22 02:13:47 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-22 02:13:48 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-22 02:13:48 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-22 02:13:48 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-22 02:13:48 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-22 02:13:48 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-22 02:13:48 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-22 02:13:48 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-22 02:13:48 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-22 02:13:48 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-22 02:13:49 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-22 02:13:49 (10208) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-22 02:13:49 (10225) [INFO] * 2025-06-22 02:13:49 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-22 02:13:49 (10195) [INFO] * 2025-06-22 02:13:49 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-22 02:13:50 (10208) [INFO] Determining fastest mirrors * 2025-06-22 02:14:21 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-22 02:14:21 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-22 02:14:21 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-22 02:14:21 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-22 02:17:48 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-22 02:17:48 (10208) [INFO] Trying other mirror. * 2025-06-22 02:17:48 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-06-22 02:17:48 (10208) [INFO] Trying other mirror. * 2025-06-22 02:18:19 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:18:19 (10208) [INFO] Trying other mirror. * 2025-06-22 02:18:50 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:18:50 (10208) [INFO] Trying other mirror. * 2025-06-22 02:20:50 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:20:50 (10208) [INFO] Trying other mirror. * 2025-06-22 02:20:51 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-22 02:20:51 (10208) [INFO] Trying other mirror. * 2025-06-22 02:24:10 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-22 02:24:10 (10208) [INFO] Trying other mirror. * 2025-06-22 02:24:41 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:24:41 (10208) [INFO] Trying other mirror. * 2025-06-22 02:25:11 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:25:11 (10208) [INFO] Trying other mirror. * 2025-06-22 02:25:42 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-22 02:25:42 (10208) [INFO] Trying other mirror. * 2025-06-22 02:26:12 (10208) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-22 02:26:12 (10208) [INFO] Trying other mirror. * 2025-06-22 02:26:43 (10208) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-22 02:26:43 (10208) [INFO] Trying other mirror. * 2025-06-23 01:46:06 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-23 01:50:06 (11278) [INFO] Script is up to date. * 2025-06-23 01:54:10 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-23 01:54:10 (10195) [INFO] * 2025-06-23 01:55:39 (10225) [INFO] * 2025-06-23 01:55:39 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-23 01:55:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-23 01:55:40 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-23 01:55:40 (10195) [INFO] * 2025-06-23 01:55:44 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-23 01:55:44 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-23 01:55:44 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-23 01:55:44 (10195) [INFO] * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-23 01:56:08 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-23 01:56:08 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-23 01:56:08 (10195) [INFO] * 2025-06-23 01:56:08 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-23 01:56:08 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-23 01:56:38 (10208) [INFO] * EA4: 184.94.196.97 * 2025-06-23 01:56:38 (10208) [INFO] * cpanel-addons-production-feed: 184.94.196.97 * 2025-06-23 01:56:38 (10208) [INFO] * cpanel-plugins: 184.94.196.97 * 2025-06-23 01:56:38 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-23 01:58:46 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 01:58:46 (10208) [INFO] Trying other mirror. * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-23 01:58:46 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-23 01:58:46 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-23 01:58:46 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-23 01:58:46 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-23 01:58:46 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-23 01:58:46 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-23 01:58:46 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-23 01:58:46 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-23 01:58:46 (10208) [INFO] or * 2025-06-23 01:58:46 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-23 01:58:46 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-23 01:58:46 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-23 01:58:46 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-23 01:58:46 (10208) [INFO] compromise: * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-23 01:58:46 (10208) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-23 01:58:46 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 01:58:46 (10225) [INFO] * 2025-06-23 01:58:46 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 01:58:46 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-23 01:58:46 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-23 01:58:46 (10195) [INFO] * 2025-06-23 01:58:46 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-23 01:58:47 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-23 01:58:47 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-23 01:58:47 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-23 01:58:47 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-23 01:58:47 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-23 01:58:47 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-23 01:58:47 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-23 01:58:47 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-23 01:58:47 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-23 01:58:47 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-23 01:58:47 (10208) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-23 01:58:47 (10225) [INFO] * 2025-06-23 01:58:47 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-23 01:58:47 (10195) [INFO] * 2025-06-23 01:58:47 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-23 01:58:48 (10208) [INFO] Determining fastest mirrors * 2025-06-23 01:59:20 (10208) [INFO] * EA4: 208.74.123.62 * 2025-06-23 01:59:20 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-23 01:59:20 (10208) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-23 01:59:20 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-23 02:00:07 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-23 02:00:07 (10208) [INFO] Trying other mirror. * 2025-06-23 02:00:37 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30315 milliseconds') * 2025-06-23 02:00:37 (10208) [INFO] Trying other mirror. * 2025-06-23 02:02:28 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 02:02:28 (10208) [INFO] Trying other mirror. * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-23 02:02:28 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-23 02:02:28 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-23 02:02:28 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-23 02:02:28 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-23 02:02:28 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-23 02:02:28 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-23 02:02:28 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-23 02:02:28 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-23 02:02:28 (10208) [INFO] or * 2025-06-23 02:02:28 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-23 02:02:28 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-23 02:02:28 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-23 02:02:28 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-23 02:02:28 (10208) [INFO] compromise: * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-23 02:02:28 (10208) [INFO] * 2025-06-23 02:02:28 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-23 02:02:28 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 02:02:28 (10225) [INFO] * 2025-06-23 02:02:28 (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-23 02:02:28 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30315 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-23 02:02:30 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-23 02:02:30 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-23 02:02:30 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-23 02:02:30 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-23 02:02:30 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-23 02:02:37 (9314) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/S20waaPSen/ea_profile.json * 2025-06-23 02:05:16 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/S20waaPSen/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9316. * 2025-06-23 02:05:16 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-24 01:47:16 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-24 01:51:17 (11278) [INFO] Script is up to date. * 2025-06-24 01:55:20 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-24 01:55:20 (10195) [INFO] * 2025-06-24 01:56:46 (10225) [INFO] * 2025-06-24 01:56:46 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-24 01:56:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-24 01:56:46 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-24 01:56:46 (10195) [INFO] * 2025-06-24 02:03:45 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-24 02:03:45 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-24 02:03:45 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-24 02:03:45 (10195) [INFO] * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-24 02:04:08 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-24 02:04:08 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-24 02:04:08 (10195) [INFO] * 2025-06-24 02:04:08 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-24 02:04:09 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-24 02:04:39 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-24 02:04:39 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-24 02:04:39 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-24 02:04:39 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-24 02:06:46 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:06:46 (10208) [INFO] Trying other mirror. * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-24 02:06:46 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-24 02:06:46 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-24 02:06:46 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-24 02:06:46 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-24 02:06:46 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-24 02:06:46 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-24 02:06:46 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-24 02:06:46 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-24 02:06:46 (10208) [INFO] or * 2025-06-24 02:06:46 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-24 02:06:46 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-24 02:06:46 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-24 02:06:46 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-24 02:06:46 (10208) [INFO] compromise: * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-24 02:06:46 (10208) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-24 02:06:46 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:06:46 (10225) [INFO] * 2025-06-24 02:06:46 (6386) [WARN] Initial run of "yum makecache" failed: https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:06:46 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-24 02:06:46 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-24 02:06:46 (10195) [INFO] * 2025-06-24 02:06:46 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-24 02:06:47 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-24 02:06:47 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-24 02:06:47 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-24 02:06:47 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-24 02:06:47 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-24 02:06:47 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-24 02:06:47 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-24 02:06:47 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-24 02:06:47 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-24 02:06:47 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-24 02:06:47 (10208) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-24 02:06:47 (10225) [INFO] * 2025-06-24 02:06:47 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-24 02:06:47 (10195) [INFO] * 2025-06-24 02:06:47 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-24 02:06:48 (10208) [INFO] Determining fastest mirrors * 2025-06-24 02:07:19 (10208) [INFO] * EA4: 208.74.123.61 * 2025-06-24 02:07:19 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-24 02:07:19 (10208) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-24 02:07:19 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-24 02:08:05 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-06-24 02:08:05 (10208) [INFO] Trying other mirror. * 2025-06-24 02:08:36 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-24 02:08:36 (10208) [INFO] Trying other mirror. * 2025-06-24 02:10:27 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:10:27 (10208) [INFO] Trying other mirror. * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-24 02:10:27 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-24 02:10:27 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-24 02:10:27 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-24 02:10:27 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-24 02:10:27 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-24 02:10:27 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-24 02:10:27 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-24 02:10:27 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-24 02:10:27 (10208) [INFO] or * 2025-06-24 02:10:27 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-24 02:10:27 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-24 02:10:27 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-24 02:10:27 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-24 02:10:27 (10208) [INFO] compromise: * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-24 02:10:27 (10208) [INFO] * 2025-06-24 02:10:27 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-24 02:10:27 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:10:27 (10225) [INFO] * 2025-06-24 02:10:27 (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-24 02:10:27 (6397) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-24 02:10:28 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-24 02:10:28 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-24 02:10:28 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-24 02:10:28 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-24 02:10:28 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-25 01:46:47 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-25 01:50:47 (11278) [INFO] Script is up to date. * 2025-06-25 01:54:50 (10194) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-25 01:54:50 (10195) [INFO] * 2025-06-25 01:56:19 (10225) [INFO] * 2025-06-25 01:56:19 (6821) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-25 01:56:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-25 01:56:20 (10194) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-25 01:56:20 (10195) [INFO] * 2025-06-25 02:03:20 (4385) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-25 02:03:20 (4392) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-25 02:03:20 (10194) [INFO] Running: /usr/bin/yum list extras * 2025-06-25 02:03:20 (10195) [INFO] * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-25 02:03:42 (6537) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-25 02:03:42 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-25 02:03:42 (10195) [INFO] * 2025-06-25 02:03:42 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-25 02:03:43 (10208) [INFO] Loading mirror speeds from cached hostfile * 2025-06-25 02:04:13 (10208) [INFO] * EA4: 63.247.64.58 * 2025-06-25 02:04:13 (10208) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-25 02:04:13 (10208) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-25 02:04:13 (10208) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-25 02:05:00 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30604 milliseconds') * 2025-06-25 02:05:00 (10208) [INFO] Trying other mirror. * 2025-06-25 02:05:30 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-25 02:05:31 (10208) [INFO] Trying other mirror. * 2025-06-25 02:06:01 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2025-06-25 02:06:01 (10208) [INFO] Trying other mirror. * 2025-06-25 02:06:32 (10208) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-25 02:06:32 (10208) [INFO] Trying other mirror. * 2025-06-25 02:08:23 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:08:23 (10208) [INFO] Trying other mirror. * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-25 02:08:23 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-25 02:08:23 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-25 02:08:23 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-25 02:08:23 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-25 02:08:23 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-25 02:08:23 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-25 02:08:23 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-25 02:08:23 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-25 02:08:23 (10208) [INFO] or * 2025-06-25 02:08:23 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-25 02:08:23 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-25 02:08:23 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-25 02:08:23 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-25 02:08:23 (10208) [INFO] compromise: * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-25 02:08:23 (10208) [INFO] * 2025-06-25 02:08:23 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-25 02:08:23 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:08:24 (10225) [INFO] * 2025-06-25 02:08:24 (6386) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30604 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:08:24 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-25 02:08:24 (10194) [INFO] Running: /usr/bin/yum clean all * 2025-06-25 02:08:24 (10195) [INFO] * 2025-06-25 02:08:24 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-25 02:08:24 (10208) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-25 02:08:24 (10208) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-25 02:08:24 (10208) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-25 02:08:24 (10208) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-25 02:08:24 (10208) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-25 02:08:24 (10208) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-25 02:08:24 (10208) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-25 02:08:24 (10208) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-25 02:08:24 (10208) [INFO] : wp-toolkit-thirdparties * 2025-06-25 02:08:24 (10208) [INFO] Cleaning up list of fastest mirrors * 2025-06-25 02:08:24 (10208) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-25 02:08:25 (10225) [INFO] * 2025-06-25 02:08:25 (10194) [INFO] Running: /usr/bin/yum makecache * 2025-06-25 02:08:25 (10195) [INFO] * 2025-06-25 02:08:25 (10208) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-25 02:08:25 (10208) [INFO] Determining fastest mirrors * 2025-06-25 02:08:58 (10208) [INFO] * EA4: 208.74.123.62 * 2025-06-25 02:08:58 (10208) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-25 02:08:58 (10208) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-25 02:08:58 (10208) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-25 02:11:04 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:11:04 (10208) [INFO] Trying other mirror. * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-25 02:11:04 (10208) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-25 02:11:04 (10208) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-25 02:11:04 (10208) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-25 02:11:04 (10208) [INFO] distribution release than is supported by the repository (and the * 2025-06-25 02:11:04 (10208) [INFO] packages for the previous distribution release still work). * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-25 02:11:04 (10208) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-25 02:11:04 (10208) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-25 02:11:04 (10208) [INFO] again or use --enablerepo for temporary usage: * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-25 02:11:04 (10208) [INFO] or * 2025-06-25 02:11:04 (10208) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-25 02:11:04 (10208) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-25 02:11:04 (10208) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-25 02:11:04 (10208) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-25 02:11:04 (10208) [INFO] compromise: * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-25 02:11:04 (10208) [INFO] * 2025-06-25 02:11:04 (10208) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-25 02:11:04 (10208) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:11:04 (10225) [INFO] * 2025-06-25 02:11:04 (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-25 02:11:04 (6397) [ERROR] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-25 02:11:06 (3564) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-25 02:11:06 (259) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-25 02:11:06 (4679) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-25 02:11:06 (4685) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-25 02:11:06 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-26 01:50:52 (11256) [INFO] Self-update of script version 67 requested. * 2025-06-26 01:54:52 (11261) [INFO] Newer version of script found. Downloading. * 2025-06-26 01:58:54 (11270) [INFO] Script update to version 68 successful. * 2025-06-26 02:02:57 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-26 02:02:57 (10280) [INFO] * 2025-06-26 02:04:23 (10310) [INFO] * 2025-06-26 02:04:23 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-26 02:04:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-26 02:04:24 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-26 02:04:24 (10280) [INFO] * 2025-06-26 02:07:03 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-26 02:07:03 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-26 02:07:03 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-06-26 02:07:03 (10280) [INFO] * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-26 02:07:27 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-26 02:07:27 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-26 02:07:27 (10280) [INFO] * 2025-06-26 02:07:28 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-26 02:07:28 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-06-26 02:07:59 (10293) [INFO] * EA4: 208.74.123.61 * 2025-06-26 02:07:59 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-26 02:07:59 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-26 02:07:59 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-26 02:08:45 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-26 02:08:45 (10293) [INFO] Trying other mirror. * 2025-06-26 02:09:16 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-26 02:09:16 (10293) [INFO] Trying other mirror. * 2025-06-26 02:11:06 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:11:06 (10293) [INFO] Trying other mirror. * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-26 02:11:06 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-26 02:11:06 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-26 02:11:06 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-26 02:11:06 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-06-26 02:11:06 (10293) [INFO] packages for the previous distribution release still work). * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-26 02:11:06 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-26 02:11:06 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-26 02:11:06 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-26 02:11:06 (10293) [INFO] or * 2025-06-26 02:11:06 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-26 02:11:06 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-26 02:11:06 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-26 02:11:06 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-26 02:11:06 (10293) [INFO] compromise: * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-26 02:11:06 (10293) [INFO] * 2025-06-26 02:11:06 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-26 02:11:06 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:11:06 (10310) [INFO] * 2025-06-26 02:11:06 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:11:06 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-26 02:11:06 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-06-26 02:11:06 (10280) [INFO] * 2025-06-26 02:11:07 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-26 02:11:07 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-26 02:11:07 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-26 02:11:07 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-26 02:11:07 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-26 02:11:07 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-26 02:11:07 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-26 02:11:07 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-26 02:11:07 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-26 02:11:07 (10293) [INFO] : wp-toolkit-thirdparties * 2025-06-26 02:11:07 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-06-26 02:11:07 (10293) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-26 02:11:07 (10310) [INFO] * 2025-06-26 02:11:07 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-26 02:11:07 (10280) [INFO] * 2025-06-26 02:11:08 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-26 02:11:08 (10293) [INFO] Determining fastest mirrors * 2025-06-26 02:11:39 (10293) [INFO] * EA4: 208.74.123.61 * 2025-06-26 02:11:39 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-26 02:11:39 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-26 02:11:39 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-26 02:12:26 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-26 02:12:26 (10293) [INFO] Trying other mirror. * 2025-06-26 02:12:57 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-26 02:12:57 (10293) [INFO] Trying other mirror. * 2025-06-26 02:14:48 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:14:48 (10293) [INFO] Trying other mirror. * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-26 02:14:48 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-26 02:14:48 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-26 02:14:48 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-26 02:14:48 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-06-26 02:14:48 (10293) [INFO] packages for the previous distribution release still work). * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-26 02:14:48 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-26 02:14:48 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-26 02:14:48 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-26 02:14:48 (10293) [INFO] or * 2025-06-26 02:14:48 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-26 02:14:48 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-26 02:14:48 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-26 02:14:48 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-26 02:14:48 (10293) [INFO] compromise: * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-26 02:14:48 (10293) [INFO] * 2025-06-26 02:14:48 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-26 02:14:48 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:14:48 (10310) [INFO] * 2025-06-26 02:14:48 (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-06-26 02:14:48 (6399) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-26 02:14:50 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-26 02:14:50 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-26 02:14:50 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-26 02:14:50 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-26 02:14:50 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-27 01:50:57 (11343) [INFO] Self-update of script version 68 requested. * 2025-06-27 01:54:57 (11365) [INFO] Script is up to date. * 2025-06-27 01:59:01 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-27 01:59:01 (10280) [INFO] * 2025-06-27 02:00:30 (10310) [INFO] * 2025-06-27 02:00:30 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-27 02:00:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-27 02:00:31 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-27 02:00:31 (10280) [INFO] * 2025-06-27 02:07:02 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-27 02:07:02 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-27 02:07:02 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-06-27 02:07:02 (10280) [INFO] * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-27 02:07:26 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-27 02:07:26 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-27 02:07:26 (10280) [INFO] * 2025-06-27 02:07:26 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-27 02:07:26 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-06-27 02:07:57 (10293) [INFO] * EA4: 208.74.123.62 * 2025-06-27 02:07:57 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-27 02:07:57 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-27 02:07:57 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-27 02:08:44 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30831 milliseconds') * 2025-06-27 02:08:44 (10293) [INFO] Trying other mirror. * 2025-06-27 02:09:15 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-06-27 02:09:15 (10293) [INFO] Trying other mirror. * 2025-06-27 02:11:06 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:11:06 (10293) [INFO] Trying other mirror. * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-27 02:11:06 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-27 02:11:06 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-27 02:11:06 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-27 02:11:06 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-06-27 02:11:06 (10293) [INFO] packages for the previous distribution release still work). * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-27 02:11:06 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-27 02:11:06 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-27 02:11:06 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-27 02:11:06 (10293) [INFO] or * 2025-06-27 02:11:06 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-27 02:11:06 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-27 02:11:06 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-27 02:11:06 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-27 02:11:06 (10293) [INFO] compromise: * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-27 02:11:06 (10293) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-27 02:11:06 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:11:06 (10310) [INFO] * 2025-06-27 02:11:06 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:11:06 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-27 02:11:06 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-06-27 02:11:06 (10280) [INFO] * 2025-06-27 02:11:06 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-27 02:11:06 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-27 02:11:06 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-27 02:11:06 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-27 02:11:06 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-27 02:11:06 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-27 02:11:06 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-27 02:11:06 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-27 02:11:06 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-27 02:11:06 (10293) [INFO] : wp-toolkit-thirdparties * 2025-06-27 02:11:06 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-06-27 02:11:06 (10293) [INFO] Other repos take up 992 k of disk space (use --verbose for details) * 2025-06-27 02:11:07 (10310) [INFO] * 2025-06-27 02:11:07 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-27 02:11:07 (10280) [INFO] * 2025-06-27 02:11:07 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-27 02:11:07 (10293) [INFO] Determining fastest mirrors * 2025-06-27 02:11:40 (10293) [INFO] * EA4: 63.247.64.58 * 2025-06-27 02:11:40 (10293) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-06-27 02:11:40 (10293) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-06-27 02:11:40 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-27 02:12:27 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-27 02:12:27 (10293) [INFO] Trying other mirror. * 2025-06-27 02:14:17 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:14:17 (10293) [INFO] Trying other mirror. * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-06-27 02:14:17 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-27 02:14:17 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-27 02:14:17 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-27 02:14:17 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-06-27 02:14:17 (10293) [INFO] packages for the previous distribution release still work). * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-27 02:14:17 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-27 02:14:17 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-27 02:14:17 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-06-27 02:14:17 (10293) [INFO] or * 2025-06-27 02:14:17 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-27 02:14:17 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-27 02:14:17 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-27 02:14:17 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-27 02:14:17 (10293) [INFO] compromise: * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-06-27 02:14:17 (10293) [INFO] * 2025-06-27 02:14:17 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-06-27 02:14:17 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:14:17 (10310) [INFO] * 2025-06-27 02:14:17 (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-06-27 02:14:17 (6399) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUwMzMyNTI2OjE3NTA1OTE3MjY6bCN6cInF889F_BgtTpYnMWJm6HT5bcshV4pHcTreDg8h3c7Jy4749dO_sykGoie0YuVd6BcEzj30jtnzJ6HDmwPxZLH6E1unYHcR_qNO9TjeMzDLP3l8pGp47Fs-z_8WuzOM-lwT0OuXwJ5ZvlS2XGHJfGUPbRegxy_RwSyj7-9dzzdcv3QXOi_JUa1H_L8AhbD6Y5fEdise73p-wa9DubzazDXL1pxChwz4V14iqVpr472bRbC2ZyZn_2jRfQRspPNwQrJVzph2UMcwla-dLu6Su7LQsE1dkYaKnX7S0QNMzhq9v821jYihCnqjRH1Pq2xZzFSOyMRcoOZcwqr0g0TWEKPgg_25KdnNle_n41wNH7TcYgZwoaVbvYXs19NBh_23aV6U9E7tHRIzwybzuIcsVFfQO77fNKvhHsJMQ2ZzFuWSj6d9dGYC4-Io0f87Ys6c_1H8zydcBA8Kd7QQZFTGqPwTuuKSszwaSK_sgBpuIWIGdSIoAZG_XU2JrhMkj58gLrG3uzAYHtL2oq9JjMFBrwiRpH2OmGk_JPp4Qydh9Og_ehaoGkHpQ0lkaArQyDFiIHODPFdWwEMRzJvUjUhjfbH-jGg10yZWNHGD6ZyaAvEFgxrIMxu2Uf_Ay0yr-0NtdGYCc_NSO2f_QsoTHDR9_9dm-IAGq6gbRzjj_ro=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-06-27 02:14:19 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-06-27 02:14:19 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-06-27 02:14:19 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-06-27 02:14:19 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-06-27 02:14:19 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-28 01:47:13 (11343) [INFO] Self-update of script version 68 requested. * 2025-06-28 01:51:13 (11365) [INFO] Script is up to date. * 2025-06-28 01:55:17 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-28 01:55:17 (10280) [INFO] * 2025-06-28 01:56:23 (10310) [INFO] * 2025-06-28 01:56:23 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-28 01:56:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-28 01:56:24 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-28 01:56:24 (10280) [INFO] * 2025-06-28 02:17:00 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-28 02:17:00 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-28 02:17:00 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-06-28 02:17:00 (10280) [INFO] * 2025-06-29 01:57:03 (11343) [INFO] Self-update of script version 68 requested. * 2025-06-29 02:01:04 (11365) [INFO] Script is up to date. * 2025-06-29 02:05:07 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-29 02:05:07 (10280) [INFO] * 2025-06-29 02:06:17 (10310) [INFO] * 2025-06-29 02:06:17 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-29 02:06:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-29 02:06:18 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-29 02:06:18 (10280) [INFO] * 2025-06-29 02:07:03 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-29 02:07:03 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-29 02:07:03 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-06-29 02:07:03 (10280) [INFO] * 2025-06-29 02:07:17 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-29 02:07:20 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-29 02:07:20 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-29 02:07:20 (10280) [INFO] * 2025-06-29 02:07:21 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-29 02:07:21 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-06-29 02:07:51 (10293) [INFO] * EA4: 208.74.123.61 * 2025-06-29 02:07:51 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-29 02:07:51 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-29 02:07:51 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-29 02:11:01 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-29 02:11:01 (10293) [INFO] Trying other mirror. * 2025-06-29 02:11:18 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-06-29 02:11:18 (10293) [INFO] Trying other mirror. * 2025-06-29 02:11:47 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-29 02:11:47 (10293) [INFO] Trying other mirror. * 2025-06-29 02:11:57 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-29 02:11:57 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-29 02:12:02 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:18 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-29 02:12:18 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:28 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') * 2025-06-29 02:12:28 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:32 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-29 02:12:32 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:49 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-29 02:12:49 (10293) [INFO] Trying other mirror. * 2025-06-29 02:12:58 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-29 02:12:58 (10293) [INFO] Trying other mirror. * 2025-06-29 02:13:03 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') * 2025-06-29 02:13:03 (10293) [INFO] Trying other mirror. * 2025-06-29 02:13:20 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-29 02:13:20 (10293) [INFO] Trying other mirror. * 2025-06-29 02:13:29 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-06-29 02:13:29 (10293) [INFO] Trying other mirror. * 2025-06-29 02:13:34 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-29 02:13:34 (10293) [INFO] Trying other mirror. * 2025-06-29 02:13:50 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-06-29 02:13:50 (10293) [INFO] Trying other mirror. * 2025-06-29 02:14:00 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-06-29 02:14:00 (10293) [INFO] Trying other mirror. * 2025-06-29 02:14:43 (10293) [INFO] Metadata Cache Created * 2025-06-29 02:14:43 (10310) [INFO] * 2025-06-29 02:14:43 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30659 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. * 2025-06-29 02:14:43 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-29 02:14:43 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-06-29 02:14:43 (10280) [INFO] * 2025-06-29 02:14:43 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-29 02:14:43 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-29 02:14:43 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-29 02:14:43 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-29 02:14:43 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-29 02:14:43 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-29 02:14:43 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-29 02:14:43 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-29 02:14:43 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-29 02:14:43 (10293) [INFO] : wp-toolkit-thirdparties * 2025-06-29 02:14:44 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-29 02:14:44 (10310) [INFO] * 2025-06-29 02:14:44 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-29 02:14:44 (10280) [INFO] * 2025-06-29 02:14:44 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-29 02:14:45 (10293) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 17690. * 2025-06-29 02:14:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:45 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:02 ago * 2025-06-29 02:14:45 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:47 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:04 ago * 2025-06-29 02:14:47 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:49 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:49 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:49 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:06 ago * 2025-06-29 02:14:49 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:51 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:51 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:51 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:51 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:08 ago * 2025-06-29 02:14:51 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:53 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:53 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:53 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:53 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:10 ago * 2025-06-29 02:14:53 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:55 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:55 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:55 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:55 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:12 ago * 2025-06-29 02:14:55 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:57 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:57 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:57 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:57 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:14 ago * 2025-06-29 02:14:57 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:14:59 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:14:59 (10293) [INFO] The other application is: yum * 2025-06-29 02:14:59 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:14:59 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:16 ago * 2025-06-29 02:14:59 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:01 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:01 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:01 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:01 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:18 ago * 2025-06-29 02:15:01 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:03 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:03 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:03 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:03 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:20 ago * 2025-06-29 02:15:03 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:05 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:05 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:05 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:05 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:22 ago * 2025-06-29 02:15:05 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:07 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:07 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:07 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:07 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:24 ago * 2025-06-29 02:15:07 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:09 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:09 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:26 ago * 2025-06-29 02:15:09 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:11 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:28 ago * 2025-06-29 02:15:11 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:13 (10293) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-06-29 02:15:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:30 ago * 2025-06-29 02:15:13 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:15 (10293) [INFO] Memory : 33 M RSS (3.4 GB VSZ) * 2025-06-29 02:15:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:32 ago * 2025-06-29 02:15:15 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:17 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:34 ago * 2025-06-29 02:15:17 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:19 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:36 ago * 2025-06-29 02:15:19 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:21 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:38 ago * 2025-06-29 02:15:21 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:23 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:40 ago * 2025-06-29 02:15:23 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:25 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:42 ago * 2025-06-29 02:15:25 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:27 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:44 ago * 2025-06-29 02:15:27 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:29 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:46 ago * 2025-06-29 02:15:29 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:31 (10293) [INFO] Memory : 33 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:48 ago * 2025-06-29 02:15:31 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:33 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:50 ago * 2025-06-29 02:15:33 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:35 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:52 ago * 2025-06-29 02:15:35 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:37 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:54 ago * 2025-06-29 02:15:37 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:39 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:56 ago * 2025-06-29 02:15:39 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:41 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 00:58 ago * 2025-06-29 02:15:41 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:43 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:00 ago * 2025-06-29 02:15:43 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:45 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:02 ago * 2025-06-29 02:15:45 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:47 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:04 ago * 2025-06-29 02:15:47 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:49 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:49 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:49 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:06 ago * 2025-06-29 02:15:49 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:51 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:51 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:51 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:51 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:08 ago * 2025-06-29 02:15:51 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:53 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:53 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:53 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:53 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:10 ago * 2025-06-29 02:15:53 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:55 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:55 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:55 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:55 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:12 ago * 2025-06-29 02:15:55 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:57 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:57 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:57 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:57 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:14 ago * 2025-06-29 02:15:57 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:15:59 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:15:59 (10293) [INFO] The other application is: yum * 2025-06-29 02:15:59 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:15:59 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:16 ago * 2025-06-29 02:15:59 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:01 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:01 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:01 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:01 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:18 ago * 2025-06-29 02:16:01 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:03 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:03 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:03 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:03 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:20 ago * 2025-06-29 02:16:03 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:05 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:05 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:05 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:05 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:22 ago * 2025-06-29 02:16:05 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:07 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:07 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:07 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:07 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:24 ago * 2025-06-29 02:16:07 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:09 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:09 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:26 ago * 2025-06-29 02:16:09 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:11 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:28 ago * 2025-06-29 02:16:11 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:13 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:30 ago * 2025-06-29 02:16:13 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:15 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:32 ago * 2025-06-29 02:16:15 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:17 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:34 ago * 2025-06-29 02:16:17 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:19 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:36 ago * 2025-06-29 02:16:19 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:21 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:38 ago * 2025-06-29 02:16:21 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:23 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:40 ago * 2025-06-29 02:16:23 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:25 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:42 ago * 2025-06-29 02:16:25 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:27 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:44 ago * 2025-06-29 02:16:27 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:29 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:46 ago * 2025-06-29 02:16:29 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:31 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:48 ago * 2025-06-29 02:16:31 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:33 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:50 ago * 2025-06-29 02:16:33 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:35 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:52 ago * 2025-06-29 02:16:35 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:37 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:54 ago * 2025-06-29 02:16:37 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:39 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:56 ago * 2025-06-29 02:16:39 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:41 (10293) [INFO] Memory : 34 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 01:58 ago * 2025-06-29 02:16:41 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:43 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:00 ago * 2025-06-29 02:16:43 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:45 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:02 ago * 2025-06-29 02:16:45 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:47 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:04 ago * 2025-06-29 02:16:47 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:49 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:49 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:49 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:06 ago * 2025-06-29 02:16:49 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:51 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:51 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:51 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:51 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:08 ago * 2025-06-29 02:16:51 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:53 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:53 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:53 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:53 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:10 ago * 2025-06-29 02:16:53 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:55 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:55 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:55 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:55 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:12 ago * 2025-06-29 02:16:55 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:57 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:57 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:57 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:57 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:14 ago * 2025-06-29 02:16:57 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:16:59 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:16:59 (10293) [INFO] The other application is: yum * 2025-06-29 02:16:59 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:16:59 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:16 ago * 2025-06-29 02:16:59 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:01 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:01 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:01 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:01 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:18 ago * 2025-06-29 02:17:01 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:03 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:03 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:03 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:03 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:20 ago * 2025-06-29 02:17:03 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:05 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:05 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:05 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:05 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:22 ago * 2025-06-29 02:17:05 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:07 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:07 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:07 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:07 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:24 ago * 2025-06-29 02:17:07 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:09 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:09 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:26 ago * 2025-06-29 02:17:09 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:17:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:11 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:28 ago * 2025-06-29 02:17:11 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:13 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:30 ago * 2025-06-29 02:17:13 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:15 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:32 ago * 2025-06-29 02:17:15 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:17 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:34 ago * 2025-06-29 02:17:17 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:19 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:36 ago * 2025-06-29 02:17:19 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:21 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:38 ago * 2025-06-29 02:17:21 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:23 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:40 ago * 2025-06-29 02:17:23 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:25 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:42 ago * 2025-06-29 02:17:25 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:27 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:44 ago * 2025-06-29 02:17:27 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:29 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:46 ago * 2025-06-29 02:17:29 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:31 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:48 ago * 2025-06-29 02:17:31 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:33 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:50 ago * 2025-06-29 02:17:33 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:35 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:52 ago * 2025-06-29 02:17:35 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:37 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:54 ago * 2025-06-29 02:17:37 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:39 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:56 ago * 2025-06-29 02:17:39 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:41 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 02:58 ago * 2025-06-29 02:17:41 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:43 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:00 ago * 2025-06-29 02:17:43 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:45 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:02 ago * 2025-06-29 02:17:45 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:47 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:04 ago * 2025-06-29 02:17:47 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:50 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:50 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:50 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:07 ago * 2025-06-29 02:17:50 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:52 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:52 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:52 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:52 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:09 ago * 2025-06-29 02:17:52 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:54 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:54 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:54 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:54 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:11 ago * 2025-06-29 02:17:54 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:56 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:56 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:56 (10293) [INFO] Memory : 35 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:56 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:13 ago * 2025-06-29 02:17:56 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:17:58 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:17:58 (10293) [INFO] The other application is: yum * 2025-06-29 02:17:58 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:17:58 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:15 ago * 2025-06-29 02:17:58 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:00 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:00 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:00 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:00 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:17 ago * 2025-06-29 02:18:00 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:02 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:02 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:02 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:02 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:19 ago * 2025-06-29 02:18:02 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:04 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:04 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:04 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:04 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:21 ago * 2025-06-29 02:18:04 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:06 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:06 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:06 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:06 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:23 ago * 2025-06-29 02:18:06 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:08 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:08 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:08 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:08 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:25 ago * 2025-06-29 02:18:08 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:10 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:10 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:10 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:10 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:27 ago * 2025-06-29 02:18:10 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:12 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:12 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:12 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:12 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:29 ago * 2025-06-29 02:18:12 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:14 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:14 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:14 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:14 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:31 ago * 2025-06-29 02:18:14 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:16 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:16 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:16 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:16 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:33 ago * 2025-06-29 02:18:16 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:18 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:18 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:18 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:18 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:35 ago * 2025-06-29 02:18:18 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:20 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:20 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:20 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:20 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:37 ago * 2025-06-29 02:18:20 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:22 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:22 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:22 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:22 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:39 ago * 2025-06-29 02:18:22 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:24 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:24 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:24 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:24 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:41 ago * 2025-06-29 02:18:24 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:26 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:26 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:26 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:26 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:43 ago * 2025-06-29 02:18:26 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:28 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:28 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:28 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:28 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:45 ago * 2025-06-29 02:18:28 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:30 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:30 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:30 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:30 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:47 ago * 2025-06-29 02:18:30 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:32 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:32 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:32 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:32 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:49 ago * 2025-06-29 02:18:32 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:34 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:34 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:34 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:34 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:51 ago * 2025-06-29 02:18:34 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:36 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:36 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:36 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:36 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:53 ago * 2025-06-29 02:18:36 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:38 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:38 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:38 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:38 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:55 ago * 2025-06-29 02:18:38 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:40 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:40 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:40 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:40 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:57 ago * 2025-06-29 02:18:40 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:42 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:42 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:42 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:42 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 03:59 ago * 2025-06-29 02:18:42 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:44 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:44 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:44 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:44 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:01 ago * 2025-06-29 02:18:44 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:46 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:46 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:46 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:46 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:03 ago * 2025-06-29 02:18:46 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:48 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:48 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:48 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:48 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:05 ago * 2025-06-29 02:18:48 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:50 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:50 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:50 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:50 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:07 ago * 2025-06-29 02:18:50 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:52 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:52 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:52 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:52 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:09 ago * 2025-06-29 02:18:52 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:54 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:54 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:54 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:54 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:11 ago * 2025-06-29 02:18:54 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:56 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:56 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:56 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:56 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:13 ago * 2025-06-29 02:18:56 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:18:58 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:18:58 (10293) [INFO] The other application is: yum * 2025-06-29 02:18:58 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:18:58 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:15 ago * 2025-06-29 02:18:58 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:00 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:00 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:00 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:00 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:17 ago * 2025-06-29 02:19:00 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:02 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:02 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:02 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:02 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:19 ago * 2025-06-29 02:19:02 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:04 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:04 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:04 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:04 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:21 ago * 2025-06-29 02:19:04 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:06 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:06 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:06 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:06 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:23 ago * 2025-06-29 02:19:06 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:08 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:08 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:08 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:08 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:25 ago * 2025-06-29 02:19:08 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:10 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:10 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:10 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:10 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:27 ago * 2025-06-29 02:19:10 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:12 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:12 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:12 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:12 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:29 ago * 2025-06-29 02:19:12 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:14 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:14 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:14 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:14 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:31 ago * 2025-06-29 02:19:14 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:16 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:16 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:16 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:16 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:33 ago * 2025-06-29 02:19:16 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:18 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:18 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:18 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:18 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:35 ago * 2025-06-29 02:19:18 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:20 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:20 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:20 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:20 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:37 ago * 2025-06-29 02:19:20 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:22 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:22 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:22 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:22 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:39 ago * 2025-06-29 02:19:22 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:24 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:24 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:24 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:24 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:41 ago * 2025-06-29 02:19:24 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:26 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:26 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:26 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:26 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:43 ago * 2025-06-29 02:19:26 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:28 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:28 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:28 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:28 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:45 ago * 2025-06-29 02:19:28 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:30 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:30 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:30 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:30 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:47 ago * 2025-06-29 02:19:30 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:32 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:32 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:32 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:32 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:49 ago * 2025-06-29 02:19:32 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:34 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:34 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:34 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:34 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:51 ago * 2025-06-29 02:19:34 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:36 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:36 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:36 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:36 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:53 ago * 2025-06-29 02:19:36 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:38 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:38 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:38 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:38 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:55 ago * 2025-06-29 02:19:38 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:40 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:40 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:40 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:40 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:57 ago * 2025-06-29 02:19:40 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:42 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:42 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:42 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:42 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 04:59 ago * 2025-06-29 02:19:42 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:44 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:44 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:44 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:44 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:01 ago * 2025-06-29 02:19:44 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:46 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:46 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:46 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:46 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:03 ago * 2025-06-29 02:19:46 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:48 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:48 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:48 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:48 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:05 ago * 2025-06-29 02:19:48 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:50 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:50 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:50 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:50 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:07 ago * 2025-06-29 02:19:50 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:52 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:52 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:52 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:52 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:09 ago * 2025-06-29 02:19:52 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:54 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:54 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:54 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:54 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:11 ago * 2025-06-29 02:19:54 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:56 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:56 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:56 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:56 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:13 ago * 2025-06-29 02:19:56 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:19:58 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:19:58 (10293) [INFO] The other application is: yum * 2025-06-29 02:19:58 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:19:58 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:15 ago * 2025-06-29 02:19:58 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:00 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:00 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:00 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:00 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:17 ago * 2025-06-29 02:20:00 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:02 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:02 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:02 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:02 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:19 ago * 2025-06-29 02:20:02 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:04 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:04 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:04 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:04 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:21 ago * 2025-06-29 02:20:04 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:06 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:06 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:06 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:06 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:23 ago * 2025-06-29 02:20:06 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:08 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:08 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:08 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:08 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:25 ago * 2025-06-29 02:20:08 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:10 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:10 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:10 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:10 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:27 ago * 2025-06-29 02:20:10 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:12 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:12 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:12 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:12 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:29 ago * 2025-06-29 02:20:12 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:14 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:14 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:14 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:14 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:31 ago * 2025-06-29 02:20:14 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:16 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:16 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:16 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:16 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:33 ago * 2025-06-29 02:20:16 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:18 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:18 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:18 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:18 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:35 ago * 2025-06-29 02:20:18 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:20 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:20 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:20 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:20 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:37 ago * 2025-06-29 02:20:20 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:22 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:22 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:22 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:22 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:39 ago * 2025-06-29 02:20:22 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:24 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:24 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:24 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:24 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:41 ago * 2025-06-29 02:20:24 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:26 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:26 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:26 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:26 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:43 ago * 2025-06-29 02:20:26 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:28 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:28 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:28 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:28 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:45 ago * 2025-06-29 02:20:28 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:30 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:30 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:30 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:30 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:47 ago * 2025-06-29 02:20:30 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:32 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:32 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:32 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:32 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:49 ago * 2025-06-29 02:20:32 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:34 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:34 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:34 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:34 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:51 ago * 2025-06-29 02:20:34 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:36 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:36 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:36 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:36 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:53 ago * 2025-06-29 02:20:36 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:38 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:38 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:38 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:38 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:55 ago * 2025-06-29 02:20:38 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:40 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:40 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:40 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:40 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:57 ago * 2025-06-29 02:20:40 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:42 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:42 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:42 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:42 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 05:59 ago * 2025-06-29 02:20:42 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:44 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:44 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:44 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:44 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:01 ago * 2025-06-29 02:20:44 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:46 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:46 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:46 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:46 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:03 ago * 2025-06-29 02:20:46 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:48 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:48 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:48 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:48 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:05 ago * 2025-06-29 02:20:48 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:50 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:50 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:50 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:50 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:07 ago * 2025-06-29 02:20:50 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:52 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:52 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:52 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:52 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:09 ago * 2025-06-29 02:20:52 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:54 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:54 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:54 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:54 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:11 ago * 2025-06-29 02:20:54 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:56 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:56 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:56 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:56 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:13 ago * 2025-06-29 02:20:56 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:20:58 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:20:58 (10293) [INFO] The other application is: yum * 2025-06-29 02:20:58 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:20:58 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:15 ago * 2025-06-29 02:20:58 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:00 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:00 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:00 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:00 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:17 ago * 2025-06-29 02:21:00 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:02 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:02 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:02 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:02 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:19 ago * 2025-06-29 02:21:02 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:04 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:04 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:04 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:04 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:21 ago * 2025-06-29 02:21:04 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:06 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:06 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:06 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:06 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:23 ago * 2025-06-29 02:21:06 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:08 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:08 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:08 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:08 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:25 ago * 2025-06-29 02:21:08 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:10 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:10 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:10 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:10 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:27 ago * 2025-06-29 02:21:10 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:12 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:12 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:12 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:12 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:29 ago * 2025-06-29 02:21:12 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:14 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:14 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:14 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:14 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:31 ago * 2025-06-29 02:21:14 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:16 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:16 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:16 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:16 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:33 ago * 2025-06-29 02:21:16 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:18 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:18 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:18 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:18 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:35 ago * 2025-06-29 02:21:18 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:20 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:20 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:20 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:20 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:37 ago * 2025-06-29 02:21:20 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:22 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:22 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:22 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:22 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:39 ago * 2025-06-29 02:21:22 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:24 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:24 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:24 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:24 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:41 ago * 2025-06-29 02:21:24 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:26 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:26 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:26 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:26 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:43 ago * 2025-06-29 02:21:26 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:28 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:28 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:28 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:28 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:45 ago * 2025-06-29 02:21:28 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:30 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:30 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:30 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:30 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:47 ago * 2025-06-29 02:21:30 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:32 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:32 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:32 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:32 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:49 ago * 2025-06-29 02:21:32 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:34 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:34 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:34 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:34 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:51 ago * 2025-06-29 02:21:34 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:36 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:36 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:36 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:36 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:53 ago * 2025-06-29 02:21:36 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:38 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:38 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:38 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:38 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:55 ago * 2025-06-29 02:21:38 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:40 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:40 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:40 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:40 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:57 ago * 2025-06-29 02:21:40 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:42 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:42 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:42 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:42 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 06:59 ago * 2025-06-29 02:21:42 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:44 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:44 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:44 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:44 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:01 ago * 2025-06-29 02:21:44 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:46 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:46 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:46 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:46 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:03 ago * 2025-06-29 02:21:46 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:48 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:48 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:48 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:48 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:05 ago * 2025-06-29 02:21:48 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:50 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:50 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:50 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:50 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:07 ago * 2025-06-29 02:21:50 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:52 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:52 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:52 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:52 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:09 ago * 2025-06-29 02:21:52 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:54 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:54 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:54 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:54 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:11 ago * 2025-06-29 02:21:54 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:56 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:56 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:56 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:56 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:13 ago * 2025-06-29 02:21:56 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:21:58 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:21:58 (10293) [INFO] The other application is: yum * 2025-06-29 02:21:58 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:21:58 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:15 ago * 2025-06-29 02:21:58 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:00 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:00 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:00 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:00 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:17 ago * 2025-06-29 02:22:00 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:02 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:02 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:02 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:02 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:19 ago * 2025-06-29 02:22:02 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:04 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:04 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:04 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:04 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:21 ago * 2025-06-29 02:22:04 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:06 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:06 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:06 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:06 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:23 ago * 2025-06-29 02:22:06 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:08 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:09 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:26 ago * 2025-06-29 02:22:09 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:11 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:28 ago * 2025-06-29 02:22:11 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:13 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:30 ago * 2025-06-29 02:22:13 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:15 (10293) [INFO] Memory : 37 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:32 ago * 2025-06-29 02:22:15 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:17 (10293) [INFO] Memory : 39 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:34 ago * 2025-06-29 02:22:17 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:19 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:36 ago * 2025-06-29 02:22:19 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:21 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:38 ago * 2025-06-29 02:22:21 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:23 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:40 ago * 2025-06-29 02:22:23 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:25 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:42 ago * 2025-06-29 02:22:25 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:27 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:44 ago * 2025-06-29 02:22:27 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:29 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:46 ago * 2025-06-29 02:22:29 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:31 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:48 ago * 2025-06-29 02:22:31 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:33 (10293) [INFO] Memory : 42 M RSS (3.3 GB VSZ) * 2025-06-29 02:22:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:50 ago * 2025-06-29 02:22:33 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:35 (10293) [INFO] Memory : 70 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:52 ago * 2025-06-29 02:22:35 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:37 (10293) [INFO] Memory : 85 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:54 ago * 2025-06-29 02:22:37 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:39 (10293) [INFO] Memory : 90 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:56 ago * 2025-06-29 02:22:39 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:41 (10293) [INFO] Memory : 95 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 07:58 ago * 2025-06-29 02:22:41 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:43 (10293) [INFO] Memory : 102 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:00 ago * 2025-06-29 02:22:43 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:45 (10293) [INFO] Memory : 134 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:02 ago * 2025-06-29 02:22:45 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:47 (10293) [INFO] Memory : 172 M RSS (3.5 GB VSZ) * 2025-06-29 02:22:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:04 ago * 2025-06-29 02:22:47 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:22:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:49 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:49 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:49 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:06 ago * 2025-06-29 02:22:49 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:51 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:51 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:51 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:51 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:08 ago * 2025-06-29 02:22:51 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:53 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:53 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:53 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:53 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:10 ago * 2025-06-29 02:22:53 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:55 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:55 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:55 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:55 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:12 ago * 2025-06-29 02:22:55 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:57 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:57 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:57 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:57 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:14 ago * 2025-06-29 02:22:57 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:22:59 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:22:59 (10293) [INFO] The other application is: yum * 2025-06-29 02:22:59 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:22:59 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:16 ago * 2025-06-29 02:22:59 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:01 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:01 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:01 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:23:01 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:18 ago * 2025-06-29 02:23:01 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:03 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:03 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:03 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:23:03 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:20 ago * 2025-06-29 02:23:03 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:05 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:05 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:05 (10293) [INFO] Memory : 140 M RSS (3.4 GB VSZ) * 2025-06-29 02:23:05 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:22 ago * 2025-06-29 02:23:05 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:07 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:07 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:07 (10293) [INFO] Memory : 168 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:07 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:24 ago * 2025-06-29 02:23:07 (10293) [INFO] State : Uninterruptible, pid: 17690 * 2025-06-29 02:23:09 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:09 (10293) [INFO] Memory : 168 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:26 ago * 2025-06-29 02:23:09 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:11 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:28 ago * 2025-06-29 02:23:11 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:13 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:30 ago * 2025-06-29 02:23:13 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:15 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:32 ago * 2025-06-29 02:23:15 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:17 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:34 ago * 2025-06-29 02:23:17 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:19 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:36 ago * 2025-06-29 02:23:19 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:21 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:38 ago * 2025-06-29 02:23:21 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:23 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:40 ago * 2025-06-29 02:23:23 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:25 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:42 ago * 2025-06-29 02:23:25 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:27 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:44 ago * 2025-06-29 02:23:27 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:29 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:46 ago * 2025-06-29 02:23:29 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:31 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:48 ago * 2025-06-29 02:23:31 (10293) [INFO] State : Uninterruptible, pid: 17690 * 2025-06-29 02:23:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:33 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:50 ago * 2025-06-29 02:23:33 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:35 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:52 ago * 2025-06-29 02:23:35 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:37 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:54 ago * 2025-06-29 02:23:37 (10293) [INFO] State : Uninterruptible, pid: 17690 * 2025-06-29 02:23:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:39 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:56 ago * 2025-06-29 02:23:39 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:41 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 08:58 ago * 2025-06-29 02:23:41 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:43 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:00 ago * 2025-06-29 02:23:43 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:23:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:45 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:02 ago * 2025-06-29 02:23:45 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:47 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:47 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:47 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:47 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:04 ago * 2025-06-29 02:23:47 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:49 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:49 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:49 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:49 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:06 ago * 2025-06-29 02:23:49 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:51 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:51 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:51 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:51 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:08 ago * 2025-06-29 02:23:51 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:53 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:53 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:53 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:53 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:10 ago * 2025-06-29 02:23:53 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:55 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:55 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:55 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:55 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:12 ago * 2025-06-29 02:23:55 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:57 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:57 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:57 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:57 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:14 ago * 2025-06-29 02:23:57 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:23:59 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:23:59 (10293) [INFO] The other application is: yum * 2025-06-29 02:23:59 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:23:59 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:16 ago * 2025-06-29 02:23:59 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:01 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:01 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:01 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:01 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:18 ago * 2025-06-29 02:24:01 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:03 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:03 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:03 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:03 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:20 ago * 2025-06-29 02:24:03 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:05 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:05 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:05 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:05 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:22 ago * 2025-06-29 02:24:05 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:07 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:07 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:07 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:07 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:24 ago * 2025-06-29 02:24:07 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:09 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:09 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:09 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:09 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:26 ago * 2025-06-29 02:24:09 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:11 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:11 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:11 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:11 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:28 ago * 2025-06-29 02:24:11 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:13 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:13 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:13 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:13 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:30 ago * 2025-06-29 02:24:13 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:15 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:15 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:15 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:15 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:32 ago * 2025-06-29 02:24:15 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:17 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:17 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:17 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:17 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:34 ago * 2025-06-29 02:24:17 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:19 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:19 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:19 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:19 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:36 ago * 2025-06-29 02:24:19 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:21 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:21 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:21 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:21 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:38 ago * 2025-06-29 02:24:21 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:23 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:23 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:23 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:23 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:40 ago * 2025-06-29 02:24:23 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:25 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:25 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:25 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:25 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:42 ago * 2025-06-29 02:24:25 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:27 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:27 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:27 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:27 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:44 ago * 2025-06-29 02:24:27 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:29 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:29 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:29 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:29 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:46 ago * 2025-06-29 02:24:29 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:31 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:31 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:31 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:31 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:48 ago * 2025-06-29 02:24:31 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:33 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:33 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:33 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:33 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:50 ago * 2025-06-29 02:24:33 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:35 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:35 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:35 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:35 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:52 ago * 2025-06-29 02:24:35 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:37 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:37 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:37 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:37 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:54 ago * 2025-06-29 02:24:37 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:39 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:39 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:39 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:39 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:56 ago * 2025-06-29 02:24:39 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:41 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:41 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:41 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:41 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 09:58 ago * 2025-06-29 02:24:41 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:43 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:43 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:43 (10293) [INFO] Memory : 170 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:43 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 10:00 ago * 2025-06-29 02:24:43 (10293) [INFO] State : Sleeping, pid: 17690 * 2025-06-29 02:24:45 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-06-29 02:24:45 (10293) [INFO] The other application is: yum * 2025-06-29 02:24:45 (10293) [INFO] Memory : 178 M RSS (3.5 GB VSZ) * 2025-06-29 02:24:45 (10293) [INFO] Started: Sun Jun 29 02:14:43 2025 - 10:02 ago * 2025-06-29 02:24:45 (10293) [INFO] State : Running, pid: 17690 * 2025-06-29 02:24:47 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-06-29 02:25:17 (10293) [INFO] * EA4: 208.74.123.62 * 2025-06-29 02:25:17 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-29 02:25:17 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-29 02:25:17 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-30 01:57:51 (11343) [INFO] Self-update of script version 68 requested. * 2025-06-30 02:01:51 (11365) [INFO] Script is up to date. * 2025-06-30 02:05:54 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-30 02:05:54 (10280) [INFO] * 2025-06-30 02:07:25 (10310) [INFO] * 2025-06-30 02:07:25 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-06-30 02:07:26 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-06-30 02:07:26 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-30 02:07:26 (10280) [INFO] * 2025-06-30 02:07:29 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-06-30 02:07:29 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-30 02:07:29 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-06-30 02:07:29 (10280) [INFO] * 2025-06-30 02:07:41 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-06-30 02:07:45 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-06-30 02:07:45 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-30 02:07:45 (10280) [INFO] * 2025-06-30 02:07:45 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-30 02:07:45 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-06-30 02:08:15 (10293) [INFO] * EA4: 208.74.123.62 * 2025-06-30 02:08:15 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-06-30 02:08:15 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-06-30 02:08:15 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-30 02:09:03 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30539 milliseconds') * 2025-06-30 02:09:03 (10293) [INFO] Trying other mirror. * 2025-06-30 02:11:55 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:11:55 (10293) [INFO] Trying other mirror. * 2025-06-30 02:12:13 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:12:13 (10293) [INFO] Trying other mirror. * 2025-06-30 02:12:57 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-30 02:12:57 (10293) [INFO] Trying other mirror. * 2025-06-30 02:13:28 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-30 02:13:28 (10293) [INFO] Trying other mirror. * 2025-06-30 02:13:58 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:13:58 (10293) [INFO] Trying other mirror. * 2025-06-30 02:14:29 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-30 02:14:29 (10293) [INFO] Trying other mirror. * 2025-06-30 02:15:11 (10293) [INFO] Metadata Cache Created * 2025-06-30 02:15:11 (10310) [INFO] * 2025-06-30 02:15:11 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30539 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-06-30 02:15:11 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-30 02:15:11 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-06-30 02:15:11 (10280) [INFO] * 2025-06-30 02:15:12 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-30 02:15:12 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-06-30 02:15:12 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-30 02:15:12 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-30 02:15:12 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-06-30 02:15:12 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-06-30 02:15:12 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-30 02:15:12 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-30 02:15:12 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-06-30 02:15:12 (10293) [INFO] : wp-toolkit-thirdparties * 2025-06-30 02:15:13 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-06-30 02:15:13 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-06-30 02:15:13 (10310) [INFO] * 2025-06-30 02:15:13 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-06-30 02:15:13 (10280) [INFO] * 2025-06-30 02:15:14 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-30 02:15:14 (10293) [INFO] Determining fastest mirrors * 2025-06-30 02:15:45 (10293) [INFO] * EA4: 208.74.123.61 * 2025-06-30 02:15:45 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-06-30 02:15:45 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-06-30 02:15:45 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-06-30 02:16:36 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-30 02:16:36 (10293) [INFO] Trying other mirror. * 2025-06-30 02:19:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-06-30 02:19:53 (10293) [INFO] Trying other mirror. * 2025-06-30 02:19:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-30 02:19:53 (10293) [INFO] Trying other mirror. * 2025-06-30 02:20:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:20:23 (10293) [INFO] Trying other mirror. * 2025-06-30 02:22:55 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-06-30 02:22:55 (10293) [INFO] Trying other mirror. * 2025-06-30 02:25:43 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:25:43 (10293) [INFO] Trying other mirror. * 2025-06-30 02:25:43 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:25:43 (10293) [INFO] Trying other mirror. * 2025-06-30 02:26:44 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:26:44 (10293) [INFO] Trying other mirror. * 2025-06-30 02:26:45 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:26:45 (10293) [INFO] Trying other mirror. * 2025-06-30 02:27:15 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-06-30 02:27:15 (10293) [INFO] Trying other mirror. * 2025-06-30 02:27:15 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-06-30 02:27:15 (10293) [INFO] Trying other mirror. * 2025-07-01 02:21:39 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-01 02:25:40 (11365) [INFO] Script is up to date. * 2025-07-01 02:29:43 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-01 02:29:43 (10280) [INFO] * 2025-07-01 02:31:15 (10310) [INFO] * 2025-07-01 02:31:15 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-01 02:31:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-01 02:31:15 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-01 02:31:15 (10280) [INFO] * 2025-07-01 02:38:13 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-01 02:38:13 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-01 02:38:13 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-01 02:38:13 (10280) [INFO] * 2025-07-01 02:38:25 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-01 02:38:29 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-01 02:38:29 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-01 02:38:29 (10280) [INFO] * 2025-07-01 02:38:29 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-01 02:38:30 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-01 02:38:59 (10293) [INFO] * EA4: 208.74.123.61 * 2025-07-01 02:38:59 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-07-01 02:38:59 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-07-01 02:38:59 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-01 02:39:46 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2025-07-01 02:39:46 (10293) [INFO] Trying other mirror. * 2025-07-01 02:40:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-01 02:40:17 (10293) [INFO] Trying other mirror. * 2025-07-01 02:40:48 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-01 02:40:48 (10293) [INFO] Trying other mirror. * 2025-07-01 02:41:19 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-01 02:41:19 (10293) [INFO] Trying other mirror. * 2025-07-01 02:41:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') * 2025-07-01 02:41:50 (10293) [INFO] Trying other mirror. * 2025-07-01 02:42:20 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-01 02:42:20 (10293) [INFO] Trying other mirror. * 2025-07-01 02:42:51 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-01 02:42:51 (10293) [INFO] Trying other mirror. * 2025-07-01 02:46:08 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-01 02:46:08 (10293) [INFO] Trying other mirror. * 2025-07-01 02:46:33 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-01 02:46:33 (10293) [INFO] Trying other mirror. * 2025-07-01 02:47:12 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-07-01 02:47:12 (10293) [INFO] Trying other mirror. * 2025-07-01 02:47:27 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-01 02:47:27 (10293) [INFO] Trying other mirror. * 2025-07-01 02:47:29 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-01 02:47:29 (10293) [INFO] Trying other mirror. * 2025-07-01 02:48:00 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-01 02:48:00 (10293) [INFO] Trying other mirror. * 2025-07-01 02:48:43 (10293) [INFO] Metadata Cache Created * 2025-07-01 02:48:43 (10310) [INFO] * 2025-07-01 02:48:43 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. * 2025-07-01 02:48:43 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-01 02:48:43 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-01 02:48:43 (10280) [INFO] * 2025-07-01 02:48:44 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-01 02:48:44 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 base * 2025-07-01 02:48:44 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-07-01 02:48:44 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-07-01 02:48:44 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 * 2025-07-01 02:48:44 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-01 02:48:44 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-01 02:48:44 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-01 02:48:44 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-01 02:48:44 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-01 02:48:45 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-01 02:48:45 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-01 02:48:45 (10310) [INFO] * 2025-07-01 02:48:45 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-01 02:48:45 (10280) [INFO] * 2025-07-01 02:48:45 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-01 02:48:46 (10293) [INFO] Determining fastest mirrors * 2025-07-01 02:49:17 (10293) [INFO] * EA4: 208.74.123.61 * 2025-07-01 02:49:17 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-07-01 02:49:17 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-07-01 02:49:17 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-02 01:56:16 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-02 02:00:16 (11365) [INFO] Script is up to date. * 2025-07-02 02:04:20 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-02 02:04:20 (10280) [INFO] * 2025-07-02 02:05:44 (10310) [INFO] * 2025-07-02 02:05:44 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-02 02:05:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-02 02:05:45 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-02 02:05:45 (10280) [INFO] * 2025-07-02 02:05:48 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-02 02:05:48 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-02 02:05:49 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-02 02:05:49 (10280) [INFO] * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-02 02:06:18 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-02 02:06:18 (6530) [INFO] Unsupported YUM repo enabled 'alt-common' without packages installed from /etc/yum.repos.d/alt-common-els.repo, these will be disabled before ELevation * 2025-07-02 02:06:18 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-02 02:06:18 (10280) [INFO] * 2025-07-02 02:06:19 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-02 02:06:19 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-02 02:06:50 (10293) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-07-02 02:06:50 (10293) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') * 2025-07-02 02:06:50 (10293) [INFO] * EA4: 208.74.123.61 * 2025-07-02 02:06:50 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-07-02 02:06:50 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-07-02 02:06:50 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-02 02:09:35 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:09:35 (10293) [INFO] Trying other mirror. * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-07-02 02:09:35 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-02 02:09:35 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-02 02:09:35 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-02 02:09:35 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-02 02:09:35 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-02 02:09:35 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-02 02:09:35 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-02 02:09:35 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-07-02 02:09:35 (10293) [INFO] or * 2025-07-02 02:09:35 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-02 02:09:35 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-02 02:09:35 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-02 02:09:35 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-02 02:09:35 (10293) [INFO] compromise: * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-07-02 02:09:35 (10293) [INFO] * 2025-07-02 02:09:35 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-07-02 02:09:35 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:09:35 (10310) [INFO] * 2025-07-02 02:09:35 (6388) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:09:35 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-02 02:09:35 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-02 02:09:35 (10280) [INFO] * 2025-07-02 02:09:36 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-02 02:09:36 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-02 02:09:36 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-02 02:09:36 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-02 02:09:36 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-02 02:09:36 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-02 02:09:36 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-02 02:09:36 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-02 02:09:36 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-02 02:09:36 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-02 02:09:36 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-02 02:09:36 (10293) [INFO] Other repos take up 996 k of disk space (use --verbose for details) * 2025-07-02 02:09:37 (10310) [INFO] * 2025-07-02 02:09:37 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-02 02:09:37 (10280) [INFO] * 2025-07-02 02:09:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-02 02:09:37 (10293) [INFO] Determining fastest mirrors * 2025-07-02 02:10:09 (10293) [INFO] * EA4: 208.74.123.62 * 2025-07-02 02:10:09 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-07-02 02:10:09 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-07-02 02:10:09 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-02 02:11:20 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-02 02:11:20 (10293) [INFO] Trying other mirror. * 2025-07-02 02:11:51 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-02 02:11:51 (10293) [INFO] Trying other mirror. * 2025-07-02 02:13:59 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:13:59 (10293) [INFO] Trying other mirror. * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-07-02 02:13:59 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-02 02:13:59 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-02 02:13:59 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-02 02:13:59 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-02 02:13:59 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-02 02:13:59 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-02 02:13:59 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-02 02:13:59 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-07-02 02:13:59 (10293) [INFO] or * 2025-07-02 02:13:59 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-02 02:13:59 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-02 02:13:59 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-02 02:13:59 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-02 02:13:59 (10293) [INFO] compromise: * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-07-02 02:13:59 (10293) [INFO] * 2025-07-02 02:13:59 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-07-02 02:13:59 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:13:59 (10310) [INFO] * 2025-07-02 02:13:59 (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-02 02:13:59 (6399) [ERROR] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-02 02:14:01 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-02 02:14:01 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-02 02:14:01 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-02 02:14:01 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-02 02:14:01 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-02 02:14:09 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tcXYFuC_jU/ea_profile.json * 2025-07-02 02:17:28 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tcXYFuC_jU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-02 02:17:28 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-03 01:47:27 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-03 01:51:27 (11365) [INFO] Script is up to date. * 2025-07-03 01:55:31 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-03 01:55:31 (10280) [INFO] * 2025-07-03 01:57:02 (10310) [INFO] * 2025-07-03 01:57:02 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-03 01:57:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-03 01:57:02 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-03 01:57:02 (10280) [INFO] * 2025-07-03 01:57:06 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-03 01:57:06 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-03 01:57:06 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-03 01:57:06 (10280) [INFO] * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-03 01:57:28 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-03 01:57:28 (6530) [INFO] Unsupported YUM repo enabled 'alt-common' without packages installed from /etc/yum.repos.d/alt-common-els.repo, these will be disabled before ELevation * 2025-07-03 01:57:28 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-03 01:57:28 (10280) [INFO] * 2025-07-03 01:57:28 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-03 01:57:29 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-03 01:57:59 (10293) [INFO] * EA4: 184.94.196.93 * 2025-07-03 01:57:59 (10293) [INFO] * cpanel-addons-production-feed: 184.94.196.93 * 2025-07-03 01:57:59 (10293) [INFO] * cpanel-plugins: 184.94.196.93 * 2025-07-03 01:57:59 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-03 01:59:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30900 milliseconds') * 2025-07-03 01:59:10 (10293) [INFO] Trying other mirror. * 2025-07-03 01:59:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-03 01:59:41 (10293) [INFO] Trying other mirror. * 2025-07-03 02:01:31 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-03 02:01:31 (10293) [INFO] Trying other mirror. * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-07-03 02:01:31 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-03 02:01:31 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-03 02:01:31 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-03 02:01:31 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-03 02:01:31 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-03 02:01:31 (10293) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-03 02:01:31 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-03 02:01:31 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-07-03 02:01:31 (10293) [INFO] or * 2025-07-03 02:01:31 (10293) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-03 02:01:31 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-03 02:01:31 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-03 02:01:31 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-03 02:01:31 (10293) [INFO] compromise: * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-07-03 02:01:31 (10293) [INFO] * 2025-07-03 02:01:31 (10293) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-07-03 02:01:31 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-03 02:01:31 (10310) [INFO] * 2025-07-03 02:01:31 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30900 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxMTA4MDU2OjE3NTEzNjcyNTY6ErpipRhhMKDwkNJJQdYpG-TZgWT7pvYPt80tnkjIGqCsKYCnuBEKTXL8pfJgYFbA1n1OZpzj4yYTyhwuAvkKvOiPmeEmwj6RKXMHoUoUWcVVXQCaOUGSZCNNXVW30XIlBU01PQWr7_Uu7SHUudfh2RnCmLrLKREpNB4zpHOGLiFhzfRw_RzpWObkA_vx1A4xQcjUi4fuu9YWVYKmJy2PxkV0pcpb6dCwLq1jsV3rJhn1CDhc7_2TlvP2xH88FFMFrgA3E15Yaz6H2PFUgoWvpBlsPVjT8BoWyokEopwUQe3OtL6h3SA5-u1WwGZu-IuAtq6M5Pd7XnMP2osqmu9lmIeSJPRdy2_Vaks4_SlGEeNvF3--fMt158tuGVUPqmxmJnj2e37ulLOieqUY5zLT3eN0QZAgvfkUjVr-bcudW4JPkE3h3-aBFLuEvas61PuPoukgXuMJXBRa9M9--R8RvXmjlLYgVItw8QYDaDZT_Wra34W6XlaTH1COJkOaUK30oXFXNj76yAoqnfZLW1X1JhJ5PfZDxwwOTsDXCIdRLmEjs8rnGXnZw2kNn9hvtmESDINC7j8AIX4YNjhn4fC20lt1o33PSFsxr28OHzP6qXmoKO6AJSCJQwDeJ-mHtY6N7etrKMjG113QeyCAGCKMyC6wInm3s-1t52lsUDyd2mM=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-07-03 02:01:31 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-03 02:01:31 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-03 02:01:31 (10280) [INFO] * 2025-07-03 02:01:32 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-03 02:01:32 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-03 02:01:32 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-03 02:01:32 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-03 02:01:32 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-03 02:01:32 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-03 02:01:32 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-03 02:01:32 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-03 02:01:32 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-03 02:01:32 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-03 02:01:32 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-03 02:01:32 (10293) [INFO] Other repos take up 996 k of disk space (use --verbose for details) * 2025-07-03 02:01:32 (10310) [INFO] * 2025-07-03 02:01:32 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-03 02:01:32 (10280) [INFO] * 2025-07-03 02:01:33 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-03 02:01:33 (10293) [INFO] Determining fastest mirrors * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-03 02:02:04 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-03 02:02:04 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-03 02:02:04 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-03 02:02:04 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-03 02:02:04 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-03 02:02:04 (10293) [INFO] yum --disablerepo= ... * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-03 02:02:04 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-03 02:02:04 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] yum-config-manager --disable * 2025-07-03 02:02:04 (10293) [INFO] or * 2025-07-03 02:02:04 (10293) [INFO] subscription-manager repos --disable= * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-03 02:02:04 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-03 02:02:04 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-03 02:02:04 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-03 02:02:04 (10293) [INFO] compromise: * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-03 02:02:04 (10293) [INFO] * 2025-07-03 02:02:04 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-03 02:02:04 (10310) [INFO] * 2025-07-03 02:02:04 (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-03 02:02:04 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-03 02:02:06 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-03 02:02:06 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-03 02:02:06 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-03 02:02:06 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-03 02:02:06 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-03 02:02:13 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zo2V4ZNY8l/ea_profile.json * 2025-07-03 02:06:05 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zo2V4ZNY8l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-03 02:06:05 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-04 02:05:45 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-04 02:09:46 (11365) [INFO] Script is up to date. * 2025-07-04 02:13:49 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-04 02:13:49 (10280) [INFO] * 2025-07-04 02:15:16 (10310) [INFO] * 2025-07-04 02:15:16 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-04 02:15:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-04 02:15:16 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-04 02:15:16 (10280) [INFO] * 2025-07-04 02:22:19 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-04 02:22:19 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-04 02:22:19 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-04 02:22:19 (10280) [INFO] * 2025-07-04 02:22:31 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-04 02:22:34 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-04 02:22:34 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-04 02:22:34 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-04 02:22:34 (10280) [INFO] * 2025-07-04 02:22:35 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-04 02:22:35 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-04 02:23:05 (10293) [INFO] * EA4: 63.247.64.58 * 2025-07-04 02:23:05 (10293) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-07-04 02:23:05 (10293) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-07-04 02:23:05 (10293) [INFO] * epel: mirror.math.princeton.edu * 2025-07-04 02:26:37 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-04 02:26:37 (10293) [INFO] Trying other mirror. * 2025-07-04 02:26:56 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-04 02:26:56 (10293) [INFO] Trying other mirror. * 2025-07-04 02:27:26 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-04 02:27:26 (10293) [INFO] Trying other mirror. * 2025-07-04 02:27:35 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-04 02:27:35 (10293) [INFO] Trying other mirror. * 2025-07-04 02:27:57 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-04 02:27:57 (10293) [INFO] Trying other mirror. * 2025-07-04 02:28:05 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-04 02:28:05 (10293) [INFO] Trying other mirror. * 2025-07-04 02:28:49 (10293) [INFO] Metadata Cache Created * 2025-07-04 02:28:50 (10310) [INFO] * 2025-07-04 02:28:50 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-04 02:28:50 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-04 02:28:50 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-04 02:28:50 (10280) [INFO] * 2025-07-04 02:28:50 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-04 02:28:50 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-04 02:28:50 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-04 02:28:50 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-04 02:28:50 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-04 02:28:50 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-04 02:28:50 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-04 02:28:50 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-04 02:28:50 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-04 02:28:50 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-04 02:28:51 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-04 02:28:51 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-04 02:28:51 (10310) [INFO] * 2025-07-04 02:28:51 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-04 02:28:51 (10280) [INFO] * 2025-07-04 02:28:52 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-04 02:28:52 (10293) [INFO] Determining fastest mirrors * 2025-07-04 02:29:24 (10293) [INFO] * EA4: 208.74.123.62 * 2025-07-04 02:29:24 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-07-04 02:29:24 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-07-04 02:29:24 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-04 02:33:35 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-04 02:33:35 (10293) [INFO] Trying other mirror. * 2025-07-04 02:33:35 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-04 02:33:35 (10293) [INFO] Trying other mirror. * 2025-07-04 02:34:06 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-07-04 02:34:06 (10293) [INFO] Trying other mirror. * 2025-07-05 01:57:11 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-05 02:01:11 (11365) [INFO] Script is up to date. * 2025-07-05 02:05:15 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-05 02:05:15 (10280) [INFO] * 2025-07-05 02:06:13 (10310) [INFO] * 2025-07-05 02:06:13 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-05 02:06:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-05 02:06:14 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-05 02:06:14 (10280) [INFO] * 2025-07-05 02:07:05 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-05 02:07:05 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-05 02:07:05 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-05 02:07:05 (10280) [INFO] * 2025-07-05 02:07:19 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-05 02:07:23 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-05 02:07:23 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-05 02:07:23 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-05 02:07:23 (10280) [INFO] * 2025-07-05 02:07:24 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-05 02:07:24 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-05 02:07:54 (10293) [INFO] * EA4: 63.247.64.58 * 2025-07-05 02:07:54 (10293) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-07-05 02:07:54 (10293) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-07-05 02:07:54 (10293) [INFO] * epel: mirror.math.princeton.edu * 2025-07-05 02:09:04 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') * 2025-07-05 02:09:04 (10293) [INFO] Trying other mirror. * 2025-07-05 02:09:34 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-05 02:09:34 (10293) [INFO] Trying other mirror. * 2025-07-05 02:12:27 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-05 02:12:27 (10293) [INFO] Trying other mirror. * 2025-07-05 02:12:45 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-05 02:12:45 (10293) [INFO] Trying other mirror. * 2025-07-05 02:13:13 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-05 02:13:13 (10293) [INFO] Trying other mirror. * 2025-07-05 02:13:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-05 02:13:17 (10293) [INFO] Trying other mirror. * 2025-07-05 02:13:23 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-05 02:13:23 (10293) [INFO] Trying other mirror. * 2025-07-05 02:13:44 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-05 02:13:44 (10293) [INFO] Trying other mirror. * 2025-07-05 02:13:47 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-05 02:13:47 (10293) [INFO] Trying other mirror. * 2025-07-05 02:14:15 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-05 02:14:15 (10293) [INFO] Trying other mirror. * 2025-07-05 02:14:57 (10293) [INFO] Metadata Cache Created * 2025-07-05 02:14:57 (10310) [INFO] * 2025-07-05 02:14:57 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30772 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. * 2025-07-05 02:14:57 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-05 02:14:57 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-05 02:14:57 (10280) [INFO] * 2025-07-05 02:14:58 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-05 02:14:58 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-05 02:14:58 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-05 02:14:58 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-05 02:14:58 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-05 02:14:58 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-05 02:14:58 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-05 02:14:58 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-05 02:14:58 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-05 02:14:58 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-05 02:14:59 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-05 02:14:59 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-05 02:14:59 (10310) [INFO] * 2025-07-05 02:14:59 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-05 02:14:59 (10280) [INFO] * 2025-07-05 02:15:00 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-05 02:15:00 (10293) [INFO] Determining fastest mirrors * 2025-07-05 02:15:34 (10293) [INFO] * EA4: 63.247.64.58 * 2025-07-05 02:15:34 (10293) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-07-05 02:15:34 (10293) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-07-05 02:15:34 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-05 02:19:45 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-05 02:19:45 (10293) [INFO] Trying other mirror. * 2025-07-05 02:19:46 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-05 02:19:46 (10293) [INFO] Trying other mirror. * 2025-07-05 02:20:16 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-07-05 02:20:16 (10293) [INFO] Trying other mirror. * 2025-07-05 02:22:50 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-05 02:22:50 (10293) [INFO] Trying other mirror. * 2025-07-05 02:25:37 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-05 02:25:37 (10293) [INFO] Trying other mirror. * 2025-07-05 02:25:38 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-05 02:25:38 (10293) [INFO] Trying other mirror. * 2025-07-05 02:26:08 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-05 02:26:08 (10293) [INFO] Trying other mirror. * 2025-07-05 02:26:39 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-05 02:26:39 (10293) [INFO] Trying other mirror. * 2025-07-06 01:48:28 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-06 01:52:28 (11365) [INFO] Script is up to date. * 2025-07-06 01:56:31 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-06 01:56:31 (10280) [INFO] * 2025-07-06 01:57:39 (10310) [INFO] * 2025-07-06 01:57:39 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-06 01:57:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-06 01:57:39 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-06 01:57:39 (10280) [INFO] * 2025-07-06 02:04:39 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-06 02:04:39 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-06 02:04:39 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-06 02:04:39 (10280) [INFO] * 2025-07-06 02:12:19 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-06 02:12:23 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-06 02:12:23 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-06 02:12:23 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-06 02:12:23 (10280) [INFO] * 2025-07-06 02:12:23 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-06 02:12:24 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-06 02:12:54 (10293) [INFO] * EA4: 63.247.64.58 * 2025-07-06 02:12:54 (10293) [INFO] * cpanel-addons-production-feed: 63.247.64.58 * 2025-07-06 02:12:54 (10293) [INFO] * cpanel-plugins: 63.247.64.58 * 2025-07-06 02:12:54 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-06 02:14:03 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-06 02:14:03 (10293) [INFO] Trying other mirror. * 2025-07-06 02:17:05 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-06 02:17:05 (10293) [INFO] Trying other mirror. * 2025-07-06 02:17:13 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-06 02:17:13 (10293) [INFO] Trying other mirror. * 2025-07-06 02:18:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-06 02:18:17 (10293) [INFO] Trying other mirror. * 2025-07-07 01:56:16 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-07 02:00:16 (11365) [INFO] Script is up to date. * 2025-07-07 02:04:19 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-07 02:04:19 (10280) [INFO] * 2025-07-07 02:05:50 (10310) [INFO] * 2025-07-07 02:05:50 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-07 02:05:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-07 02:05:50 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-07 02:05:50 (10280) [INFO] * 2025-07-07 02:07:03 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-07 02:07:03 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-07 02:07:03 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-07 02:07:03 (10280) [INFO] * 2025-07-07 02:07:17 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-07 02:07:22 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-07 02:07:22 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-07 02:07:22 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-07 02:07:22 (10280) [INFO] * 2025-07-07 02:07:23 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-07 02:07:23 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-07 02:07:53 (10293) [INFO] * EA4: 208.74.123.62 * 2025-07-07 02:07:53 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-07-07 02:07:53 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-07-07 02:07:53 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-07 02:11:25 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-07 02:11:25 (10293) [INFO] Trying other mirror. * 2025-07-07 02:11:42 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-07 02:11:42 (10293) [INFO] Trying other mirror. * 2025-07-07 02:12:11 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') * 2025-07-07 02:12:11 (10293) [INFO] Trying other mirror. * 2025-07-07 02:12:15 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:12:15 (10293) [INFO] Trying other mirror. * 2025-07-07 02:12:20 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:12:20 (10293) [INFO] Trying other mirror. * 2025-07-07 02:12:42 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:12:42 (10293) [INFO] Trying other mirror. * 2025-07-07 02:13:25 (10293) [INFO] Metadata Cache Created * 2025-07-07 02:13:25 (10310) [INFO] * 2025-07-07 02:13:25 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30800 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-07 02:13:25 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-07 02:13:25 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-07 02:13:25 (10280) [INFO] * 2025-07-07 02:13:25 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-07 02:13:26 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-07 02:13:26 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-07 02:13:26 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-07 02:13:26 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-07 02:13:26 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-07 02:13:26 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-07 02:13:26 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-07 02:13:26 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-07 02:13:26 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-07 02:13:27 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-07 02:13:27 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-07 02:13:27 (10310) [INFO] * 2025-07-07 02:13:27 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-07 02:13:27 (10280) [INFO] * 2025-07-07 02:13:27 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-07 02:13:27 (10293) [INFO] Determining fastest mirrors * 2025-07-07 02:13:59 (10293) [INFO] * EA4: 208.74.123.62 * 2025-07-07 02:13:59 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-07-07 02:13:59 (10293) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-07-07 02:13:59 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-07 02:18:11 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-07 02:18:11 (10293) [INFO] Trying other mirror. * 2025-07-07 02:18:12 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:18:12 (10293) [INFO] Trying other mirror. * 2025-07-07 02:21:14 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:21:14 (10293) [INFO] Trying other mirror. * 2025-07-07 02:24:03 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:24:03 (10293) [INFO] Trying other mirror. * 2025-07-07 02:25:04 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:25:04 (10293) [INFO] Trying other mirror. * 2025-07-07 02:25:04 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-07 02:25:04 (10293) [INFO] Trying other mirror. * 2025-07-07 02:25:35 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-07 02:25:35 (10293) [INFO] Trying other mirror. * 2025-07-07 02:26:05 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30066 milliseconds') * 2025-07-07 02:26:05 (10293) [INFO] Trying other mirror. * 2025-07-08 01:46:32 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-08 01:50:32 (11365) [INFO] Script is up to date. * 2025-07-08 01:54:35 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-08 01:54:35 (10280) [INFO] * 2025-07-08 01:56:00 (10310) [INFO] * 2025-07-08 01:56:00 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-08 01:56:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-08 01:56:01 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-08 01:56:01 (10280) [INFO] * 2025-07-08 02:02:59 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-08 02:02:59 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-08 02:02:59 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-08 02:02:59 (10280) [INFO] * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-08 02:03:35 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-08 02:03:35 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-08 02:03:35 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-08 02:03:35 (10280) [INFO] * 2025-07-08 02:03:36 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-08 02:03:36 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-08 02:04:07 (10293) [INFO] * EA4: 208.74.123.61 * 2025-07-08 02:04:07 (10293) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-07-08 02:04:07 (10293) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-07-08 02:04:07 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-08 02:05:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-08 02:05:17 (10293) [INFO] Trying other mirror. * 2025-07-08 02:08:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-08 02:08:50 (10293) [INFO] Trying other mirror. * 2025-07-08 02:08:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-08 02:08:50 (10293) [INFO] Trying other mirror. * 2025-07-08 02:09:44 (10293) [INFO] https://repo.tuxcare.com/centos7-els//updates/x86_64/repodata/a980f68dd0271ab076dc7a38ef26b2420c41ef065792187e68adbba19eb96cab-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:09:44 (10293) [INFO] Trying other mirror. * 2025-07-08 02:09:59 (10293) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:09:59 (10293) [INFO] Trying other mirror. * 2025-07-08 02:10:15 (10293) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:10:15 (10293) [INFO] Trying other mirror. * 2025-07-08 02:10:31 (10293) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:10:31 (10293) [INFO] Trying other mirror. * 2025-07-08 02:10:46 (10293) [INFO] https://els-rollout.tuxcare.com/slot-4/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:10:46 (10293) [INFO] Trying other mirror. * 2025-07-08 02:11:02 (10293) [INFO] https://els-rollout.tuxcare.com/slot-5/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:11:02 (10293) [INFO] Trying other mirror. * 2025-07-08 02:11:18 (10293) [INFO] https://els-rollout.tuxcare.com/slot-6/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:11:18 (10293) [INFO] Trying other mirror. * 2025-07-08 02:11:20 (10293) [INFO] https://dl.fedoraproject.org/pub/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:11:20 (10293) [INFO] Trying other mirror. * 2025-07-08 02:11:47 (10293) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/a66ae36aa65c5d0887ab52225c46b6b9b212b6865c3272aab3455012005b77f8-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:11:47 (10293) [INFO] Trying other mirror. * 2025-07-08 02:11:51 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-08 02:11:51 (10293) [INFO] Trying other mirror. * 2025-07-08 02:12:03 (10293) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzUxNzA2ODA0OjE3NTE5NjYwMDQ6MVIsrKjYA4293zMIGhvlUbuD95EAyMhMMgtGaMBraomd5MZVxuVNZJ4PQlOdyf9D7x4IYc84TnaZuYv06y4BJkXmMJqpvO4SUNw6sXfP_EL44zzduohGIkKdR8f3gj_rV2_MNQkejNhNJdB6VdFM1ew_90Z86uJZe04Dd281uFPMjugi__rsNE4FpyGxdWT-Orh6XOZ3R6xOywjGqHCUJE0j3ZvJf5TWVnMRpXxs0C0r3QwTVtAz654N1940ZQ0jFrueBmJlA-UJhyH2OUmxAflDBOZAV6qXHVyV7lLyG5ZfDwcUu0jhN3HuVoraFKjanSgZA4CIqwCKOmbvLyGUgXeqMG_D8X4EAt1Fa2nTRTmuDLlgEsDNadJPNld40jwR72jK8XnkjHt5TSvBscH1XpBV6aRl6OguH0SLvl8CsFhw_5LliUXqyRiujKDaqcUr3SJgWVj1tmlVf-Ri0p2UzwOHqNEEAGMHDGyy35IkUz3l_fomXODCQI43bNJXIr8E4UluQG6oLzTY9iG7STwjtENbNe6G871rQWzxfaNVl3Th5S3nKdbb8io7XivkWlkGcUCv1_sYcR6KAbI_PPauOOBQIyqtqHZUOeQ0Cp7Ay-Nl--s7QngEJ1flshlOKAUB-RteZvnkMKUbYrdk5sxTAblVsVMXuxwN-3mPUqWaBo0%3D/ea-php/7/updates/x86_64/repodata/10a9211347890ce3c9f800c31bd207948792a08604a0f57e8533c61d8f3ec4c6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:12:03 (10293) [INFO] Trying other mirror. * 2025-07-08 02:12:19 (10293) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:12:19 (10293) [INFO] Trying other mirror. * 2025-07-08 02:12:34 (10293) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:12:34 (10293) [INFO] Trying other mirror. * 2025-07-08 02:12:50 (10293) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:12:50 (10293) [INFO] Trying other mirror. * 2025-07-08 02:13:06 (10293) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:13:06 (10293) [INFO] Trying other mirror. * 2025-07-08 02:13:21 (10293) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:13:21 (10293) [INFO] Trying other mirror. * 2025-07-08 02:13:37 (10293) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:13:37 (10293) [INFO] Trying other mirror. * 2025-07-08 02:13:53 (10293) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:13:53 (10293) [INFO] Trying other mirror. * 2025-07-08 02:14:08 (10293) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:14:08 (10293) [INFO] Trying other mirror. * 2025-07-08 02:14:38 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-08 02:14:38 (10293) [INFO] Trying other mirror. * 2025-07-08 02:14:39 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-08 02:14:39 (10293) [INFO] Trying other mirror. * 2025-07-08 02:14:54 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.2/wp-toolkit/repodata/6d48ef74306a25fa28ea3e64182f7bf018fff4713faadfb5e665ba693881f9a6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:14:54 (10293) [INFO] Trying other mirror. * 2025-07-08 02:15:09 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:15:09 (10293) [INFO] Trying other mirror. * 2025-07-08 02:15:11 (10293) [INFO] https://pubmirror1.math.uh.edu/fedora-buffet/archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:15:11 (10293) [INFO] Trying other mirror. * 2025-07-08 02:15:40 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-08 02:15:40 (10293) [INFO] Trying other mirror. * 2025-07-08 02:15:41 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-08 02:15:41 (10293) [INFO] Trying other mirror. * 2025-07-08 02:15:41 (10293) [INFO] http://mirror.math.princeton.edu/pub/fedora-archive/epel/7/x86_64/repodata/8b9b4a93a490a3787b09f182250cbaba737fc9c51bc560beecf33988d1abce01-primary.sqlite.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable * 2025-07-08 02:15:41 (10293) [INFO] Trying other mirror. * 2025-07-08 02:16:12 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-08 02:16:12 (10293) [INFO] Trying other mirror. * 2025-07-08 02:16:12 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-08 02:16:12 (10293) [INFO] Trying other mirror. * 2025-07-09 02:00:07 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-09 02:04:07 (11365) [INFO] Script is up to date. * 2025-07-09 02:08:11 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-09 02:08:11 (10280) [INFO] * 2025-07-09 02:09:39 (10310) [INFO] * 2025-07-09 02:09:39 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-09 02:09:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-09 02:09:39 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-09 02:09:39 (10280) [INFO] * 2025-07-09 02:09:43 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-09 02:09:43 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-09 02:09:43 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-09 02:09:43 (10280) [INFO] * 2025-07-09 02:09:55 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-09 02:09:59 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-09 02:09:59 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-09 02:09:59 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-09 02:09:59 (10280) [INFO] * 2025-07-09 02:09:59 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-09 02:10:00 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-09 02:10:29 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-09 02:10:29 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-09 02:10:29 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-09 02:10:29 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-09 02:11:39 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-09 02:11:39 (10293) [INFO] Trying other mirror. * 2025-07-09 02:12:09 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-09 02:12:09 (10293) [INFO] Trying other mirror. * 2025-07-09 02:12:40 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-09 02:12:40 (10293) [INFO] Trying other mirror. * 2025-07-09 02:13:11 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-09 02:13:11 (10293) [INFO] Trying other mirror. * 2025-07-09 02:16:05 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-09 02:16:05 (10293) [INFO] Trying other mirror. * 2025-07-09 02:16:23 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-09 02:16:23 (10293) [INFO] Trying other mirror. * 2025-07-09 02:16:52 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-09 02:16:52 (10293) [INFO] Trying other mirror. * 2025-07-09 02:16:54 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-09 02:16:54 (10293) [INFO] Trying other mirror. * 2025-07-09 02:17:01 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-09 02:17:01 (10293) [INFO] Trying other mirror. * 2025-07-09 02:17:23 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30888 milliseconds') * 2025-07-09 02:17:23 (10293) [INFO] Trying other mirror. * 2025-07-09 02:17:53 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-09 02:17:53 (10293) [INFO] Trying other mirror. * 2025-07-09 02:18:24 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-09 02:18:24 (10293) [INFO] Trying other mirror. * 2025-07-09 02:19:10 (10293) [INFO] Metadata Cache Created * 2025-07-09 02:19:10 (10310) [INFO] * 2025-07-09 02:19:10 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30888 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-07-09 02:19:10 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-09 02:19:10 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-09 02:19:10 (10280) [INFO] * 2025-07-09 02:19:10 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-09 02:19:10 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-09 02:19:10 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-09 02:19:10 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-09 02:19:10 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-09 02:19:10 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-09 02:19:10 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-09 02:19:10 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-09 02:19:10 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-09 02:19:10 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-09 02:19:11 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-09 02:19:11 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-09 02:19:11 (10310) [INFO] * 2025-07-09 02:19:11 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-09 02:19:11 (10280) [INFO] * 2025-07-09 02:19:12 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-09 02:19:12 (10293) [INFO] Determining fastest mirrors * 2025-07-09 02:19:45 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-09 02:19:45 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-09 02:19:45 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-09 02:19:45 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-09 02:23:58 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30783 milliseconds') * 2025-07-09 02:23:58 (10293) [INFO] Trying other mirror. * 2025-07-09 02:23:58 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-09 02:23:58 (10293) [INFO] Trying other mirror. * 2025-07-09 02:24:29 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-09 02:24:29 (10293) [INFO] Trying other mirror. * 2025-07-09 02:24:30 (10293) [INFO] http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/24958397deebd008ab96453190a38fffbf5a1985b3a662a2edf1c8b6c4e53ba4-filelists.sqlite.bz2: [Errno 12] Timeout on http://208.74.123.62/cpanelsync/repos/CentOS/7/EA4/repodata/24958397deebd008ab96453190a38fffbf5a1985b3a662a2edf1c8b6c4e53ba4-filelists.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2025-07-09 02:24:30 (10293) [INFO] Trying other mirror. * 2025-07-09 02:24:59 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-09 02:24:59 (10293) [INFO] Trying other mirror. * 2025-07-09 02:27:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Operation timed out after 30008 milliseconds with 0 out of 0 bytes received') * 2025-07-09 02:27:02 (10293) [INFO] Trying other mirror. * 2025-07-09 02:27:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-09 02:27:02 (10293) [INFO] Trying other mirror. * 2025-07-10 02:18:58 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-10 02:22:59 (11365) [INFO] Script is up to date. * 2025-07-10 02:27:02 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-10 02:27:02 (10280) [INFO] * 2025-07-10 02:28:29 (10310) [INFO] * 2025-07-10 02:28:29 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-10 02:28:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-10 02:28:29 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-10 02:28:29 (10280) [INFO] * 2025-07-10 02:35:27 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-10 02:35:27 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-10 02:35:27 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-10 02:35:27 (10280) [INFO] * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-10 02:36:28 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-10 02:36:28 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-10 02:36:29 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-10 02:36:29 (10280) [INFO] * 2025-07-10 02:36:29 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-10 02:36:29 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-10 02:37:00 (10293) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-07-10 02:37:00 (10293) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-07-10 02:37:00 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-10 02:37:00 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-10 02:37:00 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-10 02:37:00 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-10 02:40:37 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:40:37 (10293) [INFO] Trying other mirror. * 2025-07-10 02:40:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:40:50 (10293) [INFO] Trying other mirror. * 2025-07-10 02:41:14 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:41:14 (10293) [INFO] Trying other mirror. * 2025-07-10 02:41:15 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:41:15 (10293) [INFO] Trying other mirror. * 2025-07-10 02:41:17 (10293) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/89f7ffca74ab20f983dd9a8deb1e336d5717c52d194e71971e652fd5af611de2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-10 02:41:17 (10293) [INFO] Trying other mirror. * 2025-07-10 02:42:03 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:42:03 (10293) [INFO] Trying other mirror. * 2025-07-10 02:42:04 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:42:04 (10293) [INFO] Trying other mirror. * 2025-07-10 02:42:19 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:42:19 (10293) [INFO] Trying other mirror. * 2025-07-10 02:42:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:42:50 (10293) [INFO] Trying other mirror. * 2025-07-10 02:42:50 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:42:50 (10293) [INFO] Trying other mirror. * 2025-07-10 02:43:20 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:43:20 (10293) [INFO] Trying other mirror. * 2025-07-10 02:43:21 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-10 02:43:21 (10293) [INFO] Trying other mirror. * 2025-07-10 02:43:51 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:43:51 (10293) [INFO] Trying other mirror. * 2025-07-10 02:44:21 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:44:21 (10293) [INFO] Trying other mirror. * 2025-07-10 02:44:22 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-10 02:44:22 (10293) [INFO] Trying other mirror. * 2025-07-10 02:44:52 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-10 02:44:52 (10293) [INFO] Trying other mirror. * 2025-07-10 02:44:52 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-10 02:44:52 (10293) [INFO] Trying other mirror. * 2025-07-10 02:45:22 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:45:22 (10293) [INFO] Trying other mirror. * 2025-07-10 02:45:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-10 02:45:53 (10293) [INFO] Trying other mirror. * 2025-07-10 02:46:24 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-10 02:46:24 (10293) [INFO] Trying other mirror. * 2025-07-10 02:46:54 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-10 02:46:54 (10293) [INFO] Trying other mirror. * 2025-07-10 02:48:23 (10293) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/aa7a6fb52e8eeff4fc03048cdc8fac680e99ff306be12c6bc9416c7f3d506f01-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2025-07-10 02:48:23 (10293) [INFO] Trying other mirror. * 2025-07-10 02:48:23 (10293) [INFO] To address this issue please refer to the below wiki article * 2025-07-10 02:48:23 (10293) [INFO] * 2025-07-10 02:48:23 (10293) [INFO] https://wiki.centos.org/yum-errors * 2025-07-10 02:48:23 (10293) [INFO] * 2025-07-10 02:48:23 (10293) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-07-10 02:48:23 (10293) [INFO] * 2025-07-11 01:58:23 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-11 02:02:23 (11365) [INFO] Script is up to date. * 2025-07-11 02:06:27 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-11 02:06:27 (10280) [INFO] * 2025-07-11 02:08:00 (10310) [INFO] * 2025-07-11 02:08:00 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-11 02:08:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-11 02:08:01 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-11 02:08:01 (10280) [INFO] * 2025-07-11 02:08:06 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-11 02:08:06 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-11 02:08:06 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-11 02:08:06 (10280) [INFO] * 2025-07-11 02:08:18 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-11 02:08:22 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-11 02:08:22 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-11 02:08:22 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-11 02:08:22 (10280) [INFO] * 2025-07-11 02:08:22 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-11 02:08:23 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-11 02:08:53 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-11 02:08:53 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-11 02:08:53 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-11 02:08:53 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-11 02:12:24 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-11 02:12:24 (10293) [INFO] Trying other mirror. * 2025-07-11 02:12:45 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-07-11 02:12:45 (10293) [INFO] Trying other mirror. * 2025-07-11 02:13:11 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-11 02:13:11 (10293) [INFO] Trying other mirror. * 2025-07-11 02:13:16 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-11 02:13:16 (10293) [INFO] Trying other mirror. * 2025-07-11 02:13:20 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-11 02:13:20 (10293) [INFO] Trying other mirror. * 2025-07-11 02:13:46 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-11 02:13:46 (10293) [INFO] Trying other mirror. * 2025-07-11 02:14:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-11 02:14:17 (10293) [INFO] Trying other mirror. * 2025-07-11 02:14:47 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-11 02:14:47 (10293) [INFO] Trying other mirror. * 2025-07-11 02:15:33 (10293) [INFO] Metadata Cache Created * 2025-07-11 02:15:33 (10310) [INFO] * 2025-07-11 02:15:33 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-07-11 02:15:33 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-11 02:15:33 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-11 02:15:33 (10280) [INFO] * 2025-07-11 02:15:33 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-11 02:15:34 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-11 02:15:34 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-11 02:15:34 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-11 02:15:34 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-11 02:15:34 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-11 02:15:34 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-11 02:15:34 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-11 02:15:34 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-11 02:15:34 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-11 02:15:35 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-11 02:15:35 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-11 02:15:35 (10310) [INFO] * 2025-07-11 02:15:35 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-11 02:15:35 (10280) [INFO] * 2025-07-11 02:15:35 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-11 02:15:36 (10293) [INFO] Determining fastest mirrors * 2025-07-11 02:16:07 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-11 02:16:07 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-11 02:16:07 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-11 02:16:07 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-11 02:17:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-11 02:17:17 (10293) [INFO] Trying other mirror. * 2025-07-11 02:20:49 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-11 02:20:49 (10293) [INFO] Trying other mirror. * 2025-07-11 02:20:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-11 02:20:50 (10293) [INFO] Trying other mirror. * 2025-07-11 02:21:20 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-11 02:21:20 (10293) [INFO] Trying other mirror. * 2025-07-11 02:23:53 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-11 02:23:53 (10293) [INFO] Trying other mirror. * 2025-07-11 02:26:42 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-11 02:26:42 (10293) [INFO] Trying other mirror. * 2025-07-11 02:27:13 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-11 02:27:13 (10293) [INFO] Trying other mirror. * 2025-07-12 02:13:56 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-12 02:17:57 (11365) [INFO] Script is up to date. * 2025-07-12 02:22:00 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-12 02:22:00 (10280) [INFO] * 2025-07-12 02:23:01 (10310) [INFO] * 2025-07-12 02:23:01 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-12 02:23:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-12 02:23:01 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-12 02:23:01 (10280) [INFO] * 2025-07-12 02:23:05 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-12 02:23:05 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-12 02:23:05 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-12 02:23:05 (10280) [INFO] * 2025-07-12 02:23:17 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-12 02:23:21 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-12 02:23:21 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-12 02:23:21 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-12 02:23:21 (10280) [INFO] * 2025-07-12 02:23:22 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-12 02:23:22 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-12 02:23:52 (10293) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-07-12 02:23:52 (10293) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-07-12 02:23:52 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-12 02:23:52 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-12 02:23:52 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-12 02:23:52 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-12 02:27:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:27:23 (10293) [INFO] Trying other mirror. * 2025-07-12 02:27:40 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-12 02:27:40 (10293) [INFO] Trying other mirror. * 2025-07-12 02:28:10 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30901 milliseconds') * 2025-07-12 02:28:10 (10293) [INFO] Trying other mirror. * 2025-07-12 02:28:13 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:28:13 (10293) [INFO] Trying other mirror. * 2025-07-12 02:28:20 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:28:20 (10293) [INFO] Trying other mirror. * 2025-07-12 02:28:44 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-12 02:28:44 (10293) [INFO] Trying other mirror. * 2025-07-12 02:29:14 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-12 02:29:14 (10293) [INFO] Trying other mirror. * 2025-07-12 02:30:00 (10293) [INFO] Metadata Cache Created * 2025-07-12 02:30:00 (10310) [INFO] * 2025-07-12 02:30:00 (6388) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30901 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-07-12 02:30:00 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-12 02:30:00 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-12 02:30:00 (10280) [INFO] * 2025-07-12 02:30:00 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-12 02:30:01 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-12 02:30:01 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-12 02:30:01 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-12 02:30:01 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-12 02:30:01 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-12 02:30:01 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-12 02:30:01 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-12 02:30:01 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-12 02:30:01 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-12 02:30:02 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-12 02:30:02 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-12 02:30:02 (10310) [INFO] * 2025-07-12 02:30:02 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-12 02:30:02 (10280) [INFO] * 2025-07-12 02:30:02 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-12 02:30:04 (10293) [INFO] Determining fastest mirrors * 2025-07-12 02:30:36 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-12 02:30:36 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-12 02:30:36 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-12 02:30:36 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-12 02:34:47 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-12 02:34:47 (10293) [INFO] Trying other mirror. * 2025-07-12 02:34:48 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-12 02:34:48 (10293) [INFO] Trying other mirror. * 2025-07-12 02:37:51 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-07-12 02:37:51 (10293) [INFO] Trying other mirror. * 2025-07-12 02:39:38 (10293) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-07-12 02:39:38 (10293) [INFO] Trying other mirror. * 2025-07-12 02:39:53 (10293) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-12 02:39:53 (10293) [INFO] Trying other mirror. * 2025-07-12 02:40:09 (10293) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-12 02:40:09 (10293) [INFO] Trying other mirror. * 2025-07-12 02:40:39 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:40:39 (10293) [INFO] Trying other mirror. * 2025-07-12 02:40:39 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:40:39 (10293) [INFO] Trying other mirror. * 2025-07-12 02:40:55 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.2/wp-toolkit/repodata/6d48ef74306a25fa28ea3e64182f7bf018fff4713faadfb5e665ba693881f9a6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-12 02:40:55 (10293) [INFO] Trying other mirror. * 2025-07-12 02:41:10 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.2/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-12 02:41:10 (10293) [INFO] Trying other mirror. * 2025-07-12 02:41:40 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:41:40 (10293) [INFO] Trying other mirror. * 2025-07-12 02:41:40 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:41:40 (10293) [INFO] Trying other mirror. * 2025-07-12 02:42:10 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-12 02:42:10 (10293) [INFO] Trying other mirror. * 2025-07-12 02:42:11 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-12 02:42:11 (10293) [INFO] Trying other mirror. * 2025-07-12 02:42:41 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-12 02:42:41 (10293) [INFO] Trying other mirror. * 2025-07-12 02:42:42 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-12 02:42:42 (10293) [INFO] Trying other mirror. * 2025-07-12 02:43:12 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-12 02:43:12 (10293) [INFO] Trying other mirror. * 2025-07-12 02:43:43 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-07-12 02:43:43 (10293) [INFO] Trying other mirror. * 2025-07-13 01:58:11 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-13 02:02:12 (11365) [INFO] Script is up to date. * 2025-07-13 02:06:15 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-13 02:06:15 (10280) [INFO] * 2025-07-13 02:07:23 (10310) [INFO] * 2025-07-13 02:07:23 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-13 02:07:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-13 02:07:23 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-13 02:07:23 (10280) [INFO] * 2025-07-13 02:07:27 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-13 02:07:27 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-13 02:07:27 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-13 02:07:27 (10280) [INFO] * 2025-07-13 02:07:41 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-13 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:45 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-13 02:07:46 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-13 02:07:46 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-13 02:07:46 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-13 02:07:46 (10280) [INFO] * 2025-07-13 02:07:46 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-13 02:07:46 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-13 02:08:16 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-13 02:08:16 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-13 02:08:16 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-13 02:08:16 (10293) [INFO] * epel: mirror.math.princeton.edu * 2025-07-13 02:09:26 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-13 02:09:26 (10293) [INFO] Trying other mirror. * 2025-07-13 02:09:57 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-13 02:09:57 (10293) [INFO] Trying other mirror. * 2025-07-13 02:12:49 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-13 02:12:49 (10293) [INFO] Trying other mirror. * 2025-07-13 02:13:08 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-13 02:13:08 (10293) [INFO] Trying other mirror. * 2025-07-13 02:13:36 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-13 02:13:36 (10293) [INFO] Trying other mirror. * 2025-07-13 02:13:39 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-13 02:13:39 (10293) [INFO] Trying other mirror. * 2025-07-13 02:13:46 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-13 02:13:46 (10293) [INFO] Trying other mirror. * 2025-07-13 02:14:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-13 02:14:10 (10293) [INFO] Trying other mirror. * 2025-07-13 02:14:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-13 02:14:17 (10293) [INFO] Trying other mirror. * 2025-07-13 02:14:47 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-07-13 02:14:47 (10293) [INFO] Trying other mirror. * 2025-07-13 02:15:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-13 02:15:17 (10293) [INFO] Trying other mirror. * 2025-07-13 02:16:01 (10293) [INFO] Metadata Cache Created * 2025-07-13 02:16:01 (10310) [INFO] * 2025-07-13 02:16:01 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-13 02:16:01 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-13 02:16:01 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-13 02:16:01 (10280) [INFO] * 2025-07-13 02:16:02 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-13 02:16:02 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-13 02:16:02 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-13 02:16:02 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-13 02:16:02 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-13 02:16:02 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-13 02:16:02 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-13 02:16:02 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-13 02:16:02 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-13 02:16:02 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-13 02:16:03 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-13 02:16:03 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-13 02:16:04 (10310) [INFO] * 2025-07-13 02:16:04 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-13 02:16:04 (10280) [INFO] * 2025-07-13 02:16:04 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-13 02:16:04 (10293) [INFO] Determining fastest mirrors * 2025-07-13 02:16:36 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-13 02:16:36 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-13 02:16:36 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-13 02:16:36 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-13 02:17:46 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-13 02:17:46 (10293) [INFO] Trying other mirror. * 2025-07-13 02:18:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-13 02:18:17 (10293) [INFO] Trying other mirror. * 2025-07-13 02:21:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-13 02:21:50 (10293) [INFO] Trying other mirror. * 2025-07-13 02:21:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-13 02:21:50 (10293) [INFO] Trying other mirror. * 2025-07-13 02:24:52 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-13 02:24:52 (10293) [INFO] Trying other mirror. * 2025-07-13 02:27:42 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-13 02:27:42 (10293) [INFO] Trying other mirror. * 2025-07-14 01:57:54 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-14 02:01:54 (11365) [INFO] Script is up to date. * 2025-07-14 02:05:57 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-14 02:05:57 (10280) [INFO] * 2025-07-14 02:07:24 (10310) [INFO] * 2025-07-14 02:07:24 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-14 02:07:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-14 02:07:25 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-14 02:07:25 (10280) [INFO] * 2025-07-14 02:07:29 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-14 02:07:29 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-14 02:07:29 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-14 02:07:29 (10280) [INFO] * 2025-07-14 02:07:42 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-14 02:07:46 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-14 02:07:46 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-14 02:07:46 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-14 02:07:46 (10280) [INFO] * 2025-07-14 02:07:46 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-14 02:07:46 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-14 02:08:16 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-14 02:08:16 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-14 02:08:16 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-14 02:08:16 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-14 02:09:26 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-14 02:09:26 (10293) [INFO] Trying other mirror. * 2025-07-14 02:12:18 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-14 02:12:18 (10293) [INFO] Trying other mirror. * 2025-07-14 02:12:37 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-07-14 02:12:37 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:05 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:13:05 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:07 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:13:07 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:14 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:13:14 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:35 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-14 02:13:35 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:38 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-14 02:13:38 (10293) [INFO] Trying other mirror. * 2025-07-14 02:13:45 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-14 02:13:45 (10293) [INFO] Trying other mirror. * 2025-07-14 02:14:09 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-07-14 02:14:09 (10293) [INFO] Trying other mirror. * 2025-07-14 02:14:16 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') * 2025-07-14 02:14:16 (10293) [INFO] Trying other mirror. * 2025-07-14 02:15:01 (10293) [INFO] Metadata Cache Created * 2025-07-14 02:15:01 (10310) [INFO] * 2025-07-14 02:15:01 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30799 milliseconds') Trying other mirror. * 2025-07-14 02:15:01 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-14 02:15:01 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-14 02:15:01 (10280) [INFO] * 2025-07-14 02:15:01 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-14 02:15:01 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-14 02:15:01 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-14 02:15:01 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-14 02:15:01 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-14 02:15:01 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-14 02:15:01 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-14 02:15:01 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-14 02:15:01 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-14 02:15:01 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-14 02:15:03 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-14 02:15:03 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-14 02:15:03 (10310) [INFO] * 2025-07-14 02:15:03 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-14 02:15:03 (10280) [INFO] * 2025-07-14 02:15:04 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-14 02:15:04 (10293) [INFO] Determining fastest mirrors * 2025-07-14 02:15:37 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-14 02:15:37 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-14 02:15:37 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-14 02:15:37 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-14 02:16:46 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30771 milliseconds') * 2025-07-14 02:16:46 (10293) [INFO] Trying other mirror. * 2025-07-14 02:20:19 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:20:19 (10293) [INFO] Trying other mirror. * 2025-07-14 02:20:20 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30884 milliseconds') * 2025-07-14 02:20:20 (10293) [INFO] Trying other mirror. * 2025-07-14 02:23:22 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-14 02:23:22 (10293) [INFO] Trying other mirror. * 2025-07-14 02:26:10 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:26:10 (10293) [INFO] Trying other mirror. * 2025-07-14 02:26:10 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-14 02:26:10 (10293) [INFO] Trying other mirror. * 2025-07-14 02:26:41 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-14 02:26:41 (10293) [INFO] Trying other mirror. * 2025-07-14 02:27:12 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-14 02:27:12 (10293) [INFO] Trying other mirror. * 2025-07-14 02:27:43 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-14 02:27:43 (10293) [INFO] Trying other mirror. * 2025-07-14 02:27:43 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-14 02:27:43 (10293) [INFO] Trying other mirror. * 2025-07-15 02:00:10 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-15 02:04:10 (11365) [INFO] Script is up to date. * 2025-07-15 02:08:13 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-15 02:08:13 (10280) [INFO] * 2025-07-15 02:09:39 (10310) [INFO] * 2025-07-15 02:09:40 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-15 02:09:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-15 02:09:40 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-15 02:09:40 (10280) [INFO] * 2025-07-15 02:09:44 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-15 02:09:44 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-15 02:09:44 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-15 02:09:44 (10280) [INFO] * 2025-07-15 02:09:55 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-15 02:09:58 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-15 02:09:58 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-15 02:09:58 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-15 02:09:58 (10280) [INFO] * 2025-07-15 02:09:58 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-15 02:09:58 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-15 02:10:28 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-15 02:10:28 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-15 02:10:28 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-15 02:10:28 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-15 02:11:38 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-15 02:11:38 (10293) [INFO] Trying other mirror. * 2025-07-15 02:12:09 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30830 milliseconds') * 2025-07-15 02:12:09 (10293) [INFO] Trying other mirror. * 2025-07-15 02:12:40 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-15 02:12:40 (10293) [INFO] Trying other mirror. * 2025-07-15 02:13:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30596 milliseconds') * 2025-07-15 02:13:10 (10293) [INFO] Trying other mirror. * 2025-07-15 02:13:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-15 02:13:41 (10293) [INFO] Trying other mirror. * 2025-07-15 02:16:52 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-15 02:16:52 (10293) [INFO] Trying other mirror. * 2025-07-15 02:17:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-15 02:17:17 (10293) [INFO] Trying other mirror. * 2025-07-15 02:18:13 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-15 02:18:13 (10293) [INFO] Trying other mirror. * 2025-07-15 02:18:18 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-15 02:18:18 (10293) [INFO] Trying other mirror. * 2025-07-15 02:18:49 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-15 02:18:49 (10293) [INFO] Trying other mirror. * 2025-07-15 02:19:20 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-07-15 02:19:20 (10293) [INFO] Trying other mirror. * 2025-07-15 02:19:50 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-15 02:19:50 (10293) [INFO] Trying other mirror. * 2025-07-15 02:20:33 (10293) [INFO] Metadata Cache Created * 2025-07-15 02:20:33 (10310) [INFO] * 2025-07-15 02:20:33 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30830 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-15 02:20:33 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-15 02:20:33 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-15 02:20:33 (10280) [INFO] * 2025-07-15 02:20:33 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-15 02:20:33 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-15 02:20:33 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-15 02:20:33 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-15 02:20:33 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-15 02:20:33 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-15 02:20:33 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-15 02:20:33 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-15 02:20:33 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-15 02:20:33 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-15 02:20:34 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-15 02:20:34 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-15 02:20:34 (10310) [INFO] * 2025-07-15 02:20:34 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-15 02:20:34 (10280) [INFO] * 2025-07-15 02:20:35 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-15 02:20:35 (10293) [INFO] Determining fastest mirrors * 2025-07-15 02:21:06 (10293) [INFO] * 2025-07-15 02:21:06 (10293) [INFO] * 2025-07-15 02:21:06 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-15 02:21:06 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-15 02:21:06 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-15 02:21:06 (10293) [INFO] * 2025-07-15 02:21:06 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-15 02:21:06 (10293) [INFO] * 2025-07-15 02:21:06 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-15 02:21:06 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-15 02:21:06 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-15 02:21:07 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-15 02:21:07 (10293) [INFO] yum --disablerepo= ... * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-15 02:21:07 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-15 02:21:07 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] yum-config-manager --disable * 2025-07-15 02:21:07 (10293) [INFO] or * 2025-07-15 02:21:07 (10293) [INFO] subscription-manager repos --disable= * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-15 02:21:07 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-15 02:21:07 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-15 02:21:07 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-15 02:21:07 (10293) [INFO] compromise: * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-15 02:21:07 (10293) [INFO] * 2025-07-15 02:21:07 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-15 02:21:07 (10310) [INFO] * 2025-07-15 02:21: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-15 02:21: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-15 02:21:08 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-15 02:21:08 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-15 02:21:08 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-15 02:21:08 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-15 02:21:08 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-15 02:21:15 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VUZhKTS7wy/ea_profile.json * 2025-07-15 02:24:36 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VUZhKTS7wy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-15 02:24:36 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-16 01:00:32 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-16 01:04:32 (11365) [INFO] Script is up to date. * 2025-07-16 01:08:35 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-16 01:08:35 (10280) [INFO] * 2025-07-16 01:09:52 (10310) [INFO] * 2025-07-16 01:09:52 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-16 01:09:52 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-16 01:09:52 (10280) [INFO] * 2025-07-16 01:09:56 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-16 01:09:56 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-16 01:09:56 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-16 01:09:56 (10280) [INFO] * 2025-07-16 01:10:06 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-16 01:10:11 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-16 01:10:11 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-16 01:10:11 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-16 01:10:11 (10280) [INFO] * 2025-07-16 01:10:11 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-16 01:10:12 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-16 01:10:42 (10293) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-07-16 01:10:42 (10293) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-07-16 01:10:42 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-16 01:10:42 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-16 01:10:42 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-16 01:10:42 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-16 01:14:12 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:14:12 (10293) [INFO] Trying other mirror. * 2025-07-16 01:14:28 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:14:28 (10293) [INFO] Trying other mirror. * 2025-07-16 01:14:59 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-16 01:14:59 (10293) [INFO] Trying other mirror. * 2025-07-16 01:15:02 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30032 milliseconds with 0 out of 0 bytes received') * 2025-07-16 01:15:02 (10293) [INFO] Trying other mirror. * 2025-07-16 01:15:09 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:15:09 (10293) [INFO] Trying other mirror. * 2025-07-16 01:15:30 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-16 01:15:30 (10293) [INFO] Trying other mirror. * 2025-07-16 01:15:33 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') * 2025-07-16 01:15:33 (10293) [INFO] Trying other mirror. * 2025-07-16 01:16:18 (10293) [INFO] Metadata Cache Created * 2025-07-16 01:16:18 (10310) [INFO] * 2025-07-16 01:16:18 (6388) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Operation timed out after 30032 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30597 milliseconds') Trying other mirror. * 2025-07-16 01:16:18 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-16 01:16:18 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-16 01:16:18 (10280) [INFO] * 2025-07-16 01:16:18 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-16 01:16:18 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-16 01:16:18 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-16 01:16:18 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-16 01:16:18 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-16 01:16:18 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-16 01:16:18 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-16 01:16:18 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-16 01:16:18 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-16 01:16:18 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-16 01:16:19 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-16 01:16:19 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-16 01:16:19 (10310) [INFO] * 2025-07-16 01:16:19 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-16 01:16:19 (10280) [INFO] * 2025-07-16 01:16:20 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-16 01:16:20 (10293) [INFO] Determining fastest mirrors * 2025-07-16 01:16:53 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-16 01:16:53 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-16 01:16:53 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-16 01:16:53 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-16 01:21:05 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-16 01:21:05 (10293) [INFO] Trying other mirror. * 2025-07-16 01:21:05 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-16 01:21:05 (10293) [INFO] Trying other mirror. * 2025-07-16 01:21:35 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:21:35 (10293) [INFO] Trying other mirror. * 2025-07-16 01:22:06 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-16 01:22:06 (10293) [INFO] Trying other mirror. * 2025-07-16 01:24:08 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:24:08 (10293) [INFO] Trying other mirror. * 2025-07-16 01:27:26 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-16 01:27:26 (10293) [INFO] Trying other mirror. * 2025-07-16 01:27:26 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-16 01:27:26 (10293) [INFO] Trying other mirror. * 2025-07-16 01:27:56 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:27:56 (10293) [INFO] Trying other mirror. * 2025-07-16 01:28:59 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-16 01:28:59 (10293) [INFO] Trying other mirror. * 2025-07-16 01:28:59 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-16 01:28:59 (10293) [INFO] Trying other mirror. * 2025-07-16 01:29:29 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:29:29 (10293) [INFO] Trying other mirror. * 2025-07-16 01:29:59 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-16 01:29:59 (10293) [INFO] Trying other mirror. * 2025-07-17 02:07:40 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-17 02:11:41 (11365) [INFO] Script is up to date. * 2025-07-17 02:15:44 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-17 02:15:44 (10280) [INFO] * 2025-07-17 02:17:04 (10310) [INFO] * 2025-07-17 02:17:04 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-17 02:17:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-17 02:17:04 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-17 02:17:04 (10280) [INFO] * 2025-07-17 02:17:09 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-17 02:17:09 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-17 02:17:09 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-17 02:17:09 (10280) [INFO] * 2025-07-17 02:17:20 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-17 02:17:23 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-17 02:17:23 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-17 02:17:23 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-17 02:17:23 (10280) [INFO] * 2025-07-17 02:17:23 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-17 02:17:23 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-17 02:17:53 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-17 02:17:53 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-17 02:17:53 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-17 02:17:53 (10293) [INFO] * epel: mirror.math.princeton.edu * 2025-07-17 02:21:24 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:21:24 (10293) [INFO] Trying other mirror. * 2025-07-17 02:21:42 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-17 02:21:42 (10293) [INFO] Trying other mirror. * 2025-07-17 02:22:10 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') * 2025-07-17 02:22:10 (10293) [INFO] Trying other mirror. * 2025-07-17 02:22:16 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:22:16 (10293) [INFO] Trying other mirror. * 2025-07-17 02:22:22 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-17 02:22:22 (10293) [INFO] Trying other mirror. * 2025-07-17 02:22:52 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:22:52 (10293) [INFO] Trying other mirror. * 2025-07-17 02:23:23 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-17 02:23:23 (10293) [INFO] Trying other mirror. * 2025-07-17 02:23:53 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30005 milliseconds') * 2025-07-17 02:23:53 (10293) [INFO] Trying other mirror. * 2025-07-17 02:24:23 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-17 02:24:23 (10293) [INFO] Trying other mirror. * 2025-07-17 02:25:07 (10293) [INFO] Metadata Cache Created * 2025-07-17 02:25:08 (10310) [INFO] * 2025-07-17 02:25:08 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30005 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. * 2025-07-17 02:25:08 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-17 02:25:08 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-17 02:25:08 (10280) [INFO] * 2025-07-17 02:25:08 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-17 02:25:08 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-17 02:25:08 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-17 02:25:08 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-17 02:25:08 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-17 02:25:08 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-17 02:25:08 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-17 02:25:08 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-17 02:25:08 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-17 02:25:08 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-17 02:25:09 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-17 02:25:09 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-17 02:25:09 (10310) [INFO] * 2025-07-17 02:25:09 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-17 02:25:09 (10280) [INFO] * 2025-07-17 02:25:09 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-17 02:25:09 (10293) [INFO] Determining fastest mirrors * 2025-07-17 02:25:41 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-17 02:25:41 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-17 02:25:41 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-17 02:25:41 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-17 02:29:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-17 02:29:53 (10293) [INFO] Trying other mirror. * 2025-07-17 02:29:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-07-17 02:29:53 (10293) [INFO] Trying other mirror. * 2025-07-17 02:30:24 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30886 milliseconds') * 2025-07-17 02:30:24 (10293) [INFO] Trying other mirror. * 2025-07-17 02:30:54 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:30:54 (10293) [INFO] Trying other mirror. * 2025-07-17 02:32:56 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:32:56 (10293) [INFO] Trying other mirror. * 2025-07-17 02:36:15 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-17 02:36:15 (10293) [INFO] Trying other mirror. * 2025-07-17 02:36:15 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-17 02:36:15 (10293) [INFO] Trying other mirror. * 2025-07-17 02:36:45 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-17 02:36:45 (10293) [INFO] Trying other mirror. * 2025-07-18 02:02:29 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-18 02:06:29 (11365) [INFO] Script is up to date. * 2025-07-18 02:10:33 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-18 02:10:33 (10280) [INFO] * 2025-07-18 02:11:58 (10310) [INFO] * 2025-07-18 02:11:58 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-18 02:11:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-18 02:11:58 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-18 02:11:58 (10280) [INFO] * 2025-07-18 02:12:01 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-18 02:12:01 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-18 02:12:01 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-18 02:12:01 (10280) [INFO] * 2025-07-18 02:12:12 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-18 02:12:15 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-18 02:12:15 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-18 02:12:15 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-18 02:12:15 (10280) [INFO] * 2025-07-18 02:12:15 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-18 02:12:15 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-18 02:12:45 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-18 02:12:45 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-18 02:12:45 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-18 02:12:45 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-18 02:16:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-18 02:16:17 (10293) [INFO] Trying other mirror. * 2025-07-18 02:16:34 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:16:34 (10293) [INFO] Trying other mirror. * 2025-07-18 02:17:03 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:17:03 (10293) [INFO] Trying other mirror. * 2025-07-18 02:17:13 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:17:13 (10293) [INFO] Trying other mirror. * 2025-07-18 02:17:55 (10293) [INFO] Metadata Cache Created * 2025-07-18 02:17:55 (10310) [INFO] * 2025-07-18 02:17:55 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-18 02:17:55 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-18 02:17:55 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-18 02:17:55 (10280) [INFO] * 2025-07-18 02:17:55 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-18 02:17:56 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-18 02:17:56 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-18 02:17:56 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-18 02:17:56 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-18 02:17:56 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-18 02:17:56 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-18 02:17:56 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-18 02:17:56 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-18 02:17:56 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-18 02:17:57 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-18 02:17:57 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-18 02:17:57 (10310) [INFO] * 2025-07-18 02:17:57 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-18 02:17:57 (10280) [INFO] * 2025-07-18 02:17:57 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-18 02:17:58 (10293) [INFO] Determining fastest mirrors * 2025-07-18 02:18:30 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-18 02:18:30 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-18 02:18:30 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-18 02:18:30 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-18 02:19:39 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30597 milliseconds') * 2025-07-18 02:19:39 (10293) [INFO] Trying other mirror. * 2025-07-18 02:20:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-18 02:20:10 (10293) [INFO] Trying other mirror. * 2025-07-18 02:20:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-18 02:20:41 (10293) [INFO] Trying other mirror. * 2025-07-18 02:24:14 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-18 02:24:14 (10293) [INFO] Trying other mirror. * 2025-07-18 02:24:14 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-18 02:24:14 (10293) [INFO] Trying other mirror. * 2025-07-18 02:24:44 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:24:44 (10293) [INFO] Trying other mirror. * 2025-07-18 02:27:16 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:27:16 (10293) [INFO] Trying other mirror. * 2025-07-18 02:30:05 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-18 02:30:05 (10293) [INFO] Trying other mirror. * 2025-07-18 02:31:07 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:31:07 (10293) [INFO] Trying other mirror. * 2025-07-18 02:31:07 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-18 02:31:07 (10293) [INFO] Trying other mirror. * 2025-07-18 02:31:37 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-18 02:31:37 (10293) [INFO] Trying other mirror. * 2025-07-19 02:04:16 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-19 02:08:17 (11365) [INFO] Script is up to date. * 2025-07-19 02:12:20 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-19 02:12:20 (10280) [INFO] * 2025-07-19 02:13:18 (10310) [INFO] * 2025-07-19 02:13:18 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-19 02:13:18 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-19 02:13:18 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-19 02:13:18 (10280) [INFO] * 2025-07-19 02:13:22 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-19 02:13:22 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-19 02:13:23 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-19 02:13:23 (10280) [INFO] * 2025-07-19 02:13:33 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-19 02:13:36 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-19 02:13:36 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-19 02:13:36 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-19 02:13:36 (10280) [INFO] * 2025-07-19 02:13:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-19 02:13:37 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-19 02:14:07 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-19 02:14:07 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-19 02:14:07 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-19 02:14:07 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-19 02:17:39 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:17:39 (10293) [INFO] Trying other mirror. * 2025-07-19 02:17:57 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:17:57 (10293) [INFO] Trying other mirror. * 2025-07-19 02:18:36 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-19 02:18:36 (10293) [INFO] Trying other mirror. * 2025-07-19 02:19:06 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:19:06 (10293) [INFO] Trying other mirror. * 2025-07-19 02:19:37 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-19 02:19:37 (10293) [INFO] Trying other mirror. * 2025-07-19 02:20:19 (10293) [INFO] Metadata Cache Created * 2025-07-19 02:20:19 (10310) [INFO] * 2025-07-19 02:20:19 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. * 2025-07-19 02:20:19 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-19 02:20:19 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-19 02:20:19 (10280) [INFO] * 2025-07-19 02:20:20 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-19 02:20:20 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-19 02:20:20 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-19 02:20:20 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-19 02:20:20 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-19 02:20:20 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-19 02:20:20 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-19 02:20:20 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-19 02:20:20 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-19 02:20:20 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-19 02:20:21 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-19 02:20:21 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-19 02:20:21 (10310) [INFO] * 2025-07-19 02:20:21 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-19 02:20:21 (10280) [INFO] * 2025-07-19 02:20:21 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-19 02:20:22 (10293) [INFO] Determining fastest mirrors * 2025-07-19 02:20:53 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-19 02:20:53 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-19 02:20:53 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-19 02:20:53 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-19 02:25:06 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30771 milliseconds') * 2025-07-19 02:25:06 (10293) [INFO] Trying other mirror. * 2025-07-19 02:25:06 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30771 milliseconds') * 2025-07-19 02:25:06 (10293) [INFO] Trying other mirror. * 2025-07-19 02:25:36 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:25:36 (10293) [INFO] Trying other mirror. * 2025-07-19 02:26:07 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-19 02:26:07 (10293) [INFO] Trying other mirror. * 2025-07-19 02:28:09 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-19 02:28:09 (10293) [INFO] Trying other mirror. * 2025-07-19 02:31:27 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:31:27 (10293) [INFO] Trying other mirror. * 2025-07-19 02:31:27 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30595 milliseconds') * 2025-07-19 02:31:27 (10293) [INFO] Trying other mirror. * 2025-07-19 02:32:29 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:32:29 (10293) [INFO] Trying other mirror. * 2025-07-19 02:32:30 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-19 02:32:30 (10293) [INFO] Trying other mirror. * 2025-07-19 02:33:00 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-19 02:33:00 (10293) [INFO] Trying other mirror. * 2025-07-19 02:33:30 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:33:30 (10293) [INFO] Trying other mirror. * 2025-07-19 02:34:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-19 02:34:02 (10293) [INFO] Trying other mirror. * 2025-07-20 01:47:56 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-20 01:51:56 (11365) [INFO] Script is up to date. * 2025-07-20 01:55:59 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-20 01:55:59 (10280) [INFO] * 2025-07-20 01:56:55 (10310) [INFO] * 2025-07-20 01:56:55 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-20 01:56:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-20 01:56:55 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-20 01:56:55 (10280) [INFO] * 2025-07-20 01:56:59 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-20 01:56:59 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-20 01:56:59 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-20 01:56:59 (10280) [INFO] * 2025-07-20 01:57:12 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-20 01:57:16 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-20 01:57:16 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-20 01:57:16 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-20 01:57:16 (10280) [INFO] * 2025-07-20 01:57:16 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-20 01:57:16 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-20 01:57:46 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-20 01:57:46 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-20 01:57:46 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-20 01:57:46 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-20 02:01:17 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:01:17 (10293) [INFO] Trying other mirror. * 2025-07-20 02:01:33 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:01:33 (10293) [INFO] Trying other mirror. * 2025-07-20 02:02:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-20 02:02:17 (10293) [INFO] Trying other mirror. * 2025-07-20 02:02:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-20 02:02:17 (10293) [INFO] Trying other mirror. * 2025-07-20 02:02:53 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:02:53 (10293) [INFO] Trying other mirror. * 2025-07-20 02:03:00 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:03:00 (10293) [INFO] Trying other mirror. * 2025-07-20 02:03:18 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-20 02:03:18 (10293) [INFO] Trying other mirror. * 2025-07-20 02:03:48 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:03:48 (10293) [INFO] Trying other mirror. * 2025-07-20 02:03:49 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') * 2025-07-20 02:03:49 (10293) [INFO] Trying other mirror. * 2025-07-20 02:04:19 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-20 02:04:19 (10293) [INFO] Trying other mirror. * 2025-07-20 02:04:19 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:04:19 (10293) [INFO] Trying other mirror. * 2025-07-20 02:04:50 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:04:50 (10293) [INFO] Trying other mirror. * 2025-07-20 02:04:50 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:04:50 (10293) [INFO] Trying other mirror. * 2025-07-20 02:04:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-20 02:04:50 (10293) [INFO] Trying other mirror. * 2025-07-20 02:05:20 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:05:20 (10293) [INFO] Trying other mirror. * 2025-07-20 02:05:20 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:05:20 (10293) [INFO] Trying other mirror. * 2025-07-20 02:05:20 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:05:20 (10293) [INFO] Trying other mirror. * 2025-07-20 02:05:51 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:05:51 (10293) [INFO] Trying other mirror. * 2025-07-20 02:05:51 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-20 02:05:51 (10293) [INFO] Trying other mirror. * 2025-07-20 02:06:21 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:06:21 (10293) [INFO] Trying other mirror. * 2025-07-20 02:06:51 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:06:51 (10293) [INFO] Trying other mirror. * 2025-07-20 02:07:57 (10293) [INFO] Metadata Cache Created * 2025-07-20 02:07:57 (10310) [INFO] * 2025-07-20 02:07:57 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30831 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-20 02:07:57 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-20 02:07:57 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-20 02:07:57 (10280) [INFO] * 2025-07-20 02:07:57 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-20 02:07:58 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-20 02:07:58 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-20 02:07:58 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-20 02:07:58 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-20 02:07:58 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-20 02:07:58 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-20 02:07:58 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-20 02:07:58 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-20 02:07:58 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-20 02:07:58 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-20 02:07:58 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-20 02:07:58 (10310) [INFO] * 2025-07-20 02:07:58 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-20 02:07:58 (10280) [INFO] * 2025-07-20 02:07:58 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-20 02:07:59 (10293) [INFO] Determining fastest mirrors * 2025-07-20 02:08:32 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-20 02:08:32 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-20 02:08:32 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-20 02:08:32 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-20 02:09:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:09:41 (10293) [INFO] Trying other mirror. * 2025-07-20 02:10:12 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-20 02:10:12 (10293) [INFO] Trying other mirror. * 2025-07-20 02:10:43 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:10:43 (10293) [INFO] Trying other mirror. * 2025-07-20 02:11:13 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30689 milliseconds') * 2025-07-20 02:11:13 (10293) [INFO] Trying other mirror. * 2025-07-20 02:14:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-20 02:14:23 (10293) [INFO] Trying other mirror. * 2025-07-20 02:14:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-20 02:14:23 (10293) [INFO] Trying other mirror. * 2025-07-20 02:14:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-20 02:14:53 (10293) [INFO] Trying other mirror. * 2025-07-20 02:15:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-20 02:15:23 (10293) [INFO] Trying other mirror. * 2025-07-20 02:15:41 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:15:41 (10293) [INFO] Trying other mirror. * 2025-07-20 02:15:41 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/4714f6e99a17fd299715585b9b8ab7cbb77f9ec78dab4f2767db658af02993b0-filelists.sqlite.bz2: (28, 'Connection timed out after 30690 milliseconds') * 2025-07-20 02:15:41 (10293) [INFO] Trying other mirror. * 2025-07-20 02:16:39 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.3/wp-toolkit/repodata/5a661c238d64e820d7068bde4d9328acf3e977bb772db3aff64a70219c328718-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-20 02:16:39 (10293) [INFO] Trying other mirror. * 2025-07-20 02:16:44 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-20 02:16:44 (10293) [INFO] Trying other mirror. * 2025-07-20 02:16:45 (10293) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.7.3/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-20 02:16:45 (10293) [INFO] Trying other mirror. * 2025-07-20 02:17:15 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-07-20 02:17:15 (10293) [INFO] Trying other mirror. * 2025-07-21 01:56:38 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-21 02:00:39 (11365) [INFO] Script is up to date. * 2025-07-21 02:04:42 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-21 02:04:42 (10280) [INFO] * 2025-07-21 02:06:03 (10310) [INFO] * 2025-07-21 02:06:03 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-21 02:06:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-21 02:06:03 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-21 02:06:03 (10280) [INFO] * 2025-07-21 02:06:07 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-21 02:06:07 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-21 02:06:07 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-21 02:06:07 (10280) [INFO] * 2025-07-21 02:06:19 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-21 02:06:21 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-21 02:06:21 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-21 02:06:21 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-21 02:06:21 (10280) [INFO] * 2025-07-21 02:06:22 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-21 02:06:22 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-21 02:06:52 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-21 02:06:52 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-21 02:06:52 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-21 02:06:52 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-21 02:10:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-21 02:10:23 (10293) [INFO] Trying other mirror. * 2025-07-21 02:10:42 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:10:42 (10293) [INFO] Trying other mirror. * 2025-07-21 02:11:13 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:11:13 (10293) [INFO] Trying other mirror. * 2025-07-21 02:11:19 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:11:19 (10293) [INFO] Trying other mirror. * 2025-07-21 02:11:44 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:11:44 (10293) [INFO] Trying other mirror. * 2025-07-21 02:11:50 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:11:50 (10293) [INFO] Trying other mirror. * 2025-07-21 02:12:14 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-21 02:12:14 (10293) [INFO] Trying other mirror. * 2025-07-21 02:12:21 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-21 02:12:21 (10293) [INFO] Trying other mirror. * 2025-07-21 02:12:52 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') * 2025-07-21 02:12:52 (10293) [INFO] Trying other mirror. * 2025-07-21 02:13:22 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-21 02:13:22 (10293) [INFO] Trying other mirror. * 2025-07-21 02:13:52 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-07-21 02:13:52 (10293) [INFO] Trying other mirror. * 2025-07-21 02:14:35 (10293) [INFO] Metadata Cache Created * 2025-07-21 02:14:35 (10310) [INFO] * 2025-07-21 02:14:35 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30536 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. * 2025-07-21 02:14:35 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-21 02:14:35 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-21 02:14:35 (10280) [INFO] * 2025-07-21 02:14:36 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-21 02:14:36 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-21 02:14:36 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-21 02:14:36 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-21 02:14:36 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-21 02:14:36 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-21 02:14:36 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-21 02:14:36 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-21 02:14:36 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-21 02:14:36 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-21 02:14:37 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-21 02:14:37 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-21 02:14:37 (10310) [INFO] * 2025-07-21 02:14:37 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-21 02:14:37 (10280) [INFO] * 2025-07-21 02:14:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-21 02:14:38 (10293) [INFO] Determining fastest mirrors * 2025-07-21 02:15:09 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-21 02:15:09 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-21 02:15:09 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-21 02:15:09 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-21 02:16:19 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-21 02:16:19 (10293) [INFO] Trying other mirror. * 2025-07-21 02:19:52 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-21 02:19:52 (10293) [INFO] Trying other mirror. * 2025-07-21 02:19:53 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-21 02:19:53 (10293) [INFO] Trying other mirror. * 2025-07-21 02:20:23 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30721 milliseconds') * 2025-07-21 02:20:23 (10293) [INFO] Trying other mirror. * 2025-07-21 02:22:55 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30532 milliseconds') * 2025-07-21 02:22:55 (10293) [INFO] Trying other mirror. * 2025-07-21 02:25:43 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-21 02:25:43 (10293) [INFO] Trying other mirror. * 2025-07-21 02:25:43 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-21 02:25:43 (10293) [INFO] Trying other mirror. * 2025-07-22 01:57:03 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-22 02:01:04 (11365) [INFO] Script is up to date. * 2025-07-22 02:05:07 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-22 02:05:07 (10280) [INFO] * 2025-07-22 02:06:28 (10310) [INFO] * 2025-07-22 02:06:28 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-22 02:06:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-22 02:06:28 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-22 02:06:28 (10280) [INFO] * 2025-07-22 02:06:32 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-22 02:06:32 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-22 02:06:32 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-22 02:06:32 (10280) [INFO] * 2025-07-22 02:06:44 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-22 02:06:47 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-22 02:06:47 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-22 02:06:47 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-22 02:06:47 (10280) [INFO] * 2025-07-22 02:06:48 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-22 02:06:48 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-22 02:07:18 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-22 02:07:18 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-22 02:07:18 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-22 02:07:18 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-22 02:08:28 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30661 milliseconds') * 2025-07-22 02:08:28 (10293) [INFO] Trying other mirror. * 2025-07-22 02:08:59 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-22 02:08:59 (10293) [INFO] Trying other mirror. * 2025-07-22 02:11:50 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:11:50 (10293) [INFO] Trying other mirror. * 2025-07-22 02:12:08 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:12:08 (10293) [INFO] Trying other mirror. * 2025-07-22 02:12:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') * 2025-07-22 02:12:41 (10293) [INFO] Trying other mirror. * 2025-07-22 02:12:46 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-22 02:12:46 (10293) [INFO] Trying other mirror. * 2025-07-22 02:13:12 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-22 02:13:12 (10293) [INFO] Trying other mirror. * 2025-07-22 02:13:17 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:13:17 (10293) [INFO] Trying other mirror. * 2025-07-22 02:13:42 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-22 02:13:42 (10293) [INFO] Trying other mirror. * 2025-07-22 02:14:26 (10293) [INFO] Metadata Cache Created * 2025-07-22 02:14:26 (10310) [INFO] * 2025-07-22 02:14:26 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30661 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30596 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') Trying other mirror. * 2025-07-22 02:14:26 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-22 02:14:26 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-22 02:14:26 (10280) [INFO] * 2025-07-22 02:14:26 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-22 02:14:27 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-22 02:14:27 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-22 02:14:27 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-22 02:14:27 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-22 02:14:27 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-22 02:14:27 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-22 02:14:27 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-22 02:14:27 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-22 02:14:27 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-22 02:14:27 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-22 02:14:27 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-22 02:14:28 (10310) [INFO] * 2025-07-22 02:14:28 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-22 02:14:28 (10280) [INFO] * 2025-07-22 02:14:28 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-22 02:14:28 (10293) [INFO] Determining fastest mirrors * 2025-07-22 02:15:00 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-22 02:15:00 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-22 02:15:00 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-22 02:15:00 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-22 02:19:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:19:10 (10293) [INFO] Trying other mirror. * 2025-07-22 02:19:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'timed out before SSL handshake') * 2025-07-22 02:19:10 (10293) [INFO] Trying other mirror. * 2025-07-22 02:22:13 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30770 milliseconds') * 2025-07-22 02:22:13 (10293) [INFO] Trying other mirror. * 2025-07-22 02:25:00 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:25:00 (10293) [INFO] Trying other mirror. * 2025-07-22 02:25:00 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'Connection timed out after 30885 milliseconds') * 2025-07-22 02:25:00 (10293) [INFO] Trying other mirror. * 2025-07-22 02:26:01 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-22 02:26:01 (10293) [INFO] Trying other mirror. * 2025-07-22 02:26:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30767 milliseconds') * 2025-07-22 02:26:02 (10293) [INFO] Trying other mirror. * 2025-07-23 02:08:16 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-23 02:12:17 (11365) [INFO] Script is up to date. * 2025-07-23 02:16:20 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-23 02:16:20 (10280) [INFO] * 2025-07-23 02:17:42 (10310) [INFO] * 2025-07-23 02:17:42 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-23 02:17:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-23 02:17:42 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-23 02:17:42 (10280) [INFO] * 2025-07-23 02:17:46 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-23 02:17:46 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-23 02:17:46 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-23 02:17:46 (10280) [INFO] * 2025-07-23 02:17:55 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-23 02:17:58 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-23 02:17:58 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-23 02:17:58 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-23 02:17:58 (10280) [INFO] * 2025-07-23 02:17:59 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-23 02:17:59 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-23 02:18:30 (10293) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-07-23 02:18:30 (10293) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') * 2025-07-23 02:18:30 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-23 02:18:30 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-23 02:18:30 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-23 02:18:30 (10293) [INFO] * epel: mirror.math.princeton.edu * 2025-07-23 02:22:00 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-23 02:22:00 (10293) [INFO] Trying other mirror. * 2025-07-23 02:22:16 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:22:16 (10293) [INFO] Trying other mirror. * 2025-07-23 02:22:47 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-23 02:22:47 (10293) [INFO] Trying other mirror. * 2025-07-23 02:22:55 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:22:55 (10293) [INFO] Trying other mirror. * 2025-07-23 02:23:02 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-23 02:23:02 (10293) [INFO] Trying other mirror. * 2025-07-23 02:23:32 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:23:32 (10293) [INFO] Trying other mirror. * 2025-07-23 02:24:15 (10293) [INFO] Metadata Cache Created * 2025-07-23 02:24:15 (10310) [INFO] * 2025-07-23 02:24:15 (6388) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30537 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-23 02:24:15 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-23 02:24:15 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-23 02:24:15 (10280) [INFO] * 2025-07-23 02:24:16 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-23 02:24:16 (10293) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 30453. * 2025-07-23 02:24:16 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-07-23 02:24:16 (10293) [INFO] The other application is: yum * 2025-07-23 02:24:16 (10293) [INFO] Memory : 36 M RSS (363 MB VSZ) * 2025-07-23 02:24:16 (10293) [INFO] Started: Wed Jul 23 02:24:05 2025 - 00:11 ago * 2025-07-23 02:24:16 (10293) [INFO] State : Running, pid: 30453 * 2025-07-23 02:24:18 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-07-23 02:24:18 (10293) [INFO] The other application is: yum * 2025-07-23 02:24:18 (10293) [INFO] Memory : 85 M RSS (413 MB VSZ) * 2025-07-23 02:24:18 (10293) [INFO] Started: Wed Jul 23 02:24:05 2025 - 00:13 ago * 2025-07-23 02:24:18 (10293) [INFO] State : Running, pid: 30453 * 2025-07-23 02:24:20 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-07-23 02:24:20 (10293) [INFO] The other application is: yum * 2025-07-23 02:24:20 (10293) [INFO] Memory : 90 M RSS (417 MB VSZ) * 2025-07-23 02:24:20 (10293) [INFO] Started: Wed Jul 23 02:24:05 2025 - 00:15 ago * 2025-07-23 02:24:20 (10293) [INFO] State : Running, pid: 30453 * 2025-07-23 02:24:22 (10293) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-07-23 02:24:22 (10293) [INFO] The other application is: yum * 2025-07-23 02:24:22 (10293) [INFO] Memory : 97 M RSS (424 MB VSZ) * 2025-07-23 02:24:22 (10293) [INFO] Started: Wed Jul 23 02:24:05 2025 - 00:17 ago * 2025-07-23 02:24:22 (10293) [INFO] State : Running, pid: 30453 * 2025-07-23 02:24:24 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-23 02:24:24 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-23 02:24:24 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-23 02:24:24 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-23 02:24:24 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-23 02:24:24 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-23 02:24:24 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-23 02:24:24 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-23 02:24:24 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-23 02:24:25 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-23 02:24:25 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-23 02:24:25 (10310) [INFO] * 2025-07-23 02:24:25 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-23 02:24:25 (10280) [INFO] * 2025-07-23 02:24:25 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-23 02:24:26 (10293) [INFO] Determining fastest mirrors * 2025-07-23 02:24:59 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-23 02:24:59 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-23 02:24:59 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-23 02:24:59 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-23 02:29:10 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30601 milliseconds') * 2025-07-23 02:29:10 (10293) [INFO] Trying other mirror. * 2025-07-23 02:29:11 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-23 02:29:11 (10293) [INFO] Trying other mirror. * 2025-07-23 02:29:41 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:29:41 (10293) [INFO] Trying other mirror. * 2025-07-23 02:30:11 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-23 02:30:11 (10293) [INFO] Trying other mirror. * 2025-07-23 02:32:14 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30769 milliseconds') * 2025-07-23 02:32:14 (10293) [INFO] Trying other mirror. * 2025-07-23 02:35:31 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:35:31 (10293) [INFO] Trying other mirror. * 2025-07-23 02:35:32 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-23 02:35:32 (10293) [INFO] Trying other mirror. * 2025-07-23 02:36:33 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:36:33 (10293) [INFO] Trying other mirror. * 2025-07-23 02:36:34 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-23 02:36:34 (10293) [INFO] Trying other mirror. * 2025-07-23 02:37:34 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-23 02:37:34 (10293) [INFO] Trying other mirror. * 2025-07-24 01:56:31 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-24 02:00:32 (11365) [INFO] Script is up to date. * 2025-07-24 02:04:35 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-24 02:04:35 (10280) [INFO] * 2025-07-24 02:05:50 (10310) [INFO] * 2025-07-24 02:05:50 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-24 02:05:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-24 02:05:50 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-24 02:05:50 (10280) [INFO] * 2025-07-24 02:05:53 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-24 02:05:53 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-24 02:05:53 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-24 02:05:53 (10280) [INFO] * 2025-07-24 02:06:04 (261) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-24 02:06:07 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-24 02:06:07 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-24 02:06:07 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-24 02:06:07 (10280) [INFO] * 2025-07-24 02:06:08 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-24 02:06:08 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-24 02:06:38 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-24 02:06:38 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-24 02:06:38 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-24 02:06:38 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-07-24 02:10:08 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:10:08 (10293) [INFO] Trying other mirror. * 2025-07-24 02:10:25 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:10:25 (10293) [INFO] Trying other mirror. * 2025-07-24 02:11:03 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:11:03 (10293) [INFO] Trying other mirror. * 2025-07-24 02:11:44 (10293) [INFO] Metadata Cache Created * 2025-07-24 02:11:44 (10310) [INFO] * 2025-07-24 02:11:44 (6388) [WARN] Initial run of "yum makecache" failed: https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-07-24 02:11:44 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-24 02:11:44 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-24 02:11:44 (10280) [INFO] * 2025-07-24 02:11:44 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-24 02:11:45 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-24 02:11:45 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-24 02:11:45 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-24 02:11:45 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-24 02:11:45 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-24 02:11:45 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-24 02:11:45 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-24 02:11:45 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-24 02:11:45 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-24 02:11:45 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-24 02:11:45 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-24 02:11:45 (10310) [INFO] * 2025-07-24 02:11:45 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-24 02:11:45 (10280) [INFO] * 2025-07-24 02:11:46 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-24 02:11:46 (10293) [INFO] Determining fastest mirrors * 2025-07-24 02:12:18 (10293) [INFO] * EA4: 5.78.136.185 * 2025-07-24 02:12:18 (10293) [INFO] * cpanel-addons-production-feed: 5.78.136.185 * 2025-07-24 02:12:18 (10293) [INFO] * cpanel-plugins: 5.78.136.185 * 2025-07-24 02:12:18 (10293) [INFO] * epel: pubmirror1.math.uh.edu * 2025-07-24 02:16:28 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:16:28 (10293) [INFO] Trying other mirror. * 2025-07-24 02:16:28 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-24 02:16:28 (10293) [INFO] Trying other mirror. * 2025-07-24 02:16:58 (10293) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'Connection timed out after 30535 milliseconds') * 2025-07-24 02:16:58 (10293) [INFO] Trying other mirror. * 2025-07-24 02:19:30 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30539 milliseconds') * 2025-07-24 02:19:30 (10293) [INFO] Trying other mirror. * 2025-07-24 02:22:17 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:22:17 (10293) [INFO] Trying other mirror. * 2025-07-24 02:22:18 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/f19044932626155f0cd849e88972b84875fc85e3308b4d622844a911c4ef54d0-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:22:18 (10293) [INFO] Trying other mirror. * 2025-07-24 02:22:48 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'Connection timed out after 30534 milliseconds') * 2025-07-24 02:22:48 (10293) [INFO] Trying other mirror. * 2025-07-24 02:23:49 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:23:49 (10293) [INFO] Trying other mirror. * 2025-07-24 02:23:49 (10293) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/5369f2a80023772257211f0a8bafad10a8939d12c2997809d5bce0f65d7a0f91-filelists.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:23:49 (10293) [INFO] Trying other mirror. * 2025-07-24 02:24:51 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'Connection timed out after 30768 milliseconds') * 2025-07-24 02:24:51 (10293) [INFO] Trying other mirror. * 2025-07-24 02:25:21 (10293) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-07-24 02:25:21 (10293) [INFO] Trying other mirror. * 2025-07-25 01:46:19 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-25 01:50:19 (11365) [INFO] Script is up to date. * 2025-07-25 01:54:21 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-25 01:54:21 (10280) [INFO] * 2025-07-25 01:55:38 (10310) [INFO] * 2025-07-25 01:55:38 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-25 01:55:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-25 01:55:38 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-25 01:55:38 (10280) [INFO] * 2025-07-25 01:55:41 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-25 01:55:41 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-25 01:55:41 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-25 01:55:41 (10280) [INFO] * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-25 01:56:16 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-25 01:56:16 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-25 01:56:16 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-25 01:56:16 (10280) [INFO] * 2025-07-25 01:56:16 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-25 01:56:16 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-25 01:56:47 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-25 01:56:47 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-25 01:56:47 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-25 01:56:47 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-25 01:56:47 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-25 01:56:47 (10293) [INFO] yum --disablerepo= ... * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-25 01:56:47 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-25 01:56:47 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] yum-config-manager --disable * 2025-07-25 01:56:47 (10293) [INFO] or * 2025-07-25 01:56:47 (10293) [INFO] subscription-manager repos --disable= * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-25 01:56:47 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-25 01:56:47 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-25 01:56:47 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-25 01:56:47 (10293) [INFO] compromise: * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-25 01:56:47 (10293) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-25 01:56:47 (10310) [INFO] * 2025-07-25 01:56:47 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-25 01:56:47 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-25 01:56:47 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-25 01:56:47 (10280) [INFO] * 2025-07-25 01:56:47 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-25 01:56:48 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-25 01:56:48 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-25 01:56:48 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-25 01:56:48 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-25 01:56:48 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-25 01:56:48 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-25 01:56:48 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-25 01:56:48 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-25 01:56:48 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-25 01:56:48 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-25 01:56:48 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-25 01:56:48 (10310) [INFO] * 2025-07-25 01:56:48 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-25 01:56:48 (10280) [INFO] * 2025-07-25 01:56:48 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-25 01:56:48 (10293) [INFO] Determining fastest mirrors * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-25 01:57:19 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-25 01:57:19 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-25 01:57:19 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-25 01:57:19 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-25 01:57:19 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-25 01:57:19 (10293) [INFO] yum --disablerepo= ... * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-25 01:57:19 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-25 01:57:19 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] yum-config-manager --disable * 2025-07-25 01:57:19 (10293) [INFO] or * 2025-07-25 01:57:19 (10293) [INFO] subscription-manager repos --disable= * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-25 01:57:19 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-25 01:57:19 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-25 01:57:19 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-25 01:57:19 (10293) [INFO] compromise: * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-25 01:57:19 (10293) [INFO] * 2025-07-25 01:57:19 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-25 01:57:19 (10310) [INFO] * 2025-07-25 01:57:19 (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-25 01:57:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-25 01:57:20 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-25 01:57:20 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-25 01:57:20 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-25 01:57:20 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-25 01:57:20 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-25 01:57:26 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rbyNh41dfq/ea_profile.json * 2025-07-25 02:01:48 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rbyNh41dfq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-25 02:01:48 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-26 01:45:30 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-26 01:49:31 (11365) [INFO] Script is up to date. * 2025-07-26 01:53:33 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-26 01:53:33 (10280) [INFO] * 2025-07-26 01:54:27 (10310) [INFO] * 2025-07-26 01:54:27 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-26 01:54:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-26 01:54:28 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-26 01:54:28 (10280) [INFO] * 2025-07-26 01:54:31 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-26 01:54:31 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-26 01:54:31 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-26 01:54:31 (10280) [INFO] * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-26 01:55:05 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-26 01:55:05 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-26 01:55:05 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-26 01:55:05 (10280) [INFO] * 2025-07-26 01:55:05 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-26 01:55:05 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-26 01:55:36 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-26 01:55:36 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-26 01:55:36 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-26 01:55:36 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-26 01:55:36 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-26 01:55:36 (10293) [INFO] yum --disablerepo= ... * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-26 01:55:36 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-26 01:55:36 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] yum-config-manager --disable * 2025-07-26 01:55:36 (10293) [INFO] or * 2025-07-26 01:55:36 (10293) [INFO] subscription-manager repos --disable= * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-26 01:55:36 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-26 01:55:36 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-26 01:55:36 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-26 01:55:36 (10293) [INFO] compromise: * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-26 01:55:36 (10293) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-26 01:55:36 (10310) [INFO] * 2025-07-26 01:55:36 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-26 01:55:36 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-26 01:55:36 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-26 01:55:36 (10280) [INFO] * 2025-07-26 01:55:36 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-26 01:55:37 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-26 01:55:37 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-26 01:55:37 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-26 01:55:37 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-26 01:55:37 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-26 01:55:37 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-26 01:55:37 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-26 01:55:37 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-26 01:55:37 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-26 01:55:37 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-26 01:55:37 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-26 01:55:37 (10310) [INFO] * 2025-07-26 01:55:37 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-26 01:55:37 (10280) [INFO] * 2025-07-26 01:55:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-26 01:55:38 (10293) [INFO] Determining fastest mirrors * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-26 01:56:09 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-26 01:56:09 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-26 01:56:09 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-26 01:56:09 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-26 01:56:09 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-26 01:56:09 (10293) [INFO] yum --disablerepo= ... * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-26 01:56:09 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-26 01:56:09 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] yum-config-manager --disable * 2025-07-26 01:56:09 (10293) [INFO] or * 2025-07-26 01:56:09 (10293) [INFO] subscription-manager repos --disable= * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-26 01:56:09 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-26 01:56:09 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-26 01:56:09 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-26 01:56:09 (10293) [INFO] compromise: * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-26 01:56:09 (10293) [INFO] * 2025-07-26 01:56:09 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-26 01:56:09 (10310) [INFO] * 2025-07-26 01:56:09 (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-26 01:56:09 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-26 01:56:10 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-26 01:56:10 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-26 01:56:10 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-26 01:56:10 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-26 01:56:10 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-26 01:56:16 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sKe0RrQn1H/ea_profile.json * 2025-07-26 01:58:38 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sKe0RrQn1H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-26 01:58:38 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-27 01:43:48 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-27 01:47:49 (11365) [INFO] Script is up to date. * 2025-07-27 01:51:51 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-27 01:51:51 (10280) [INFO] * 2025-07-27 01:52:43 (10310) [INFO] * 2025-07-27 01:52:43 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-27 01:52:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-27 01:52:44 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-27 01:52:44 (10280) [INFO] * 2025-07-27 01:52:46 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-27 01:52:46 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-27 01:52:46 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-27 01:52:46 (10280) [INFO] * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-27 01:53:21 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-27 01:53:21 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-27 01:53:21 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-27 01:53:21 (10280) [INFO] * 2025-07-27 01:53:21 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-27 01:53:21 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-27 01:53:53 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-27 01:53:53 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-27 01:53:53 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-27 01:53:53 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-27 01:53:53 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-27 01:53:53 (10293) [INFO] yum --disablerepo= ... * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-27 01:53:53 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-27 01:53:53 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] yum-config-manager --disable * 2025-07-27 01:53:53 (10293) [INFO] or * 2025-07-27 01:53:53 (10293) [INFO] subscription-manager repos --disable= * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-27 01:53:53 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-27 01:53:53 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-27 01:53:53 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-27 01:53:53 (10293) [INFO] compromise: * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-27 01:53:53 (10293) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-27 01:53:53 (10310) [INFO] * 2025-07-27 01:53:53 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-27 01:53:53 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-27 01:53:53 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-27 01:53:53 (10280) [INFO] * 2025-07-27 01:53:53 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-27 01:53:54 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-27 01:53:54 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-27 01:53:54 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-27 01:53:54 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-27 01:53:54 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-27 01:53:54 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-27 01:53:54 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-27 01:53:54 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-27 01:53:54 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-27 01:53:54 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-27 01:53:54 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-27 01:53:54 (10310) [INFO] * 2025-07-27 01:53:54 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-27 01:53:54 (10280) [INFO] * 2025-07-27 01:53:54 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-27 01:53:54 (10293) [INFO] Determining fastest mirrors * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-27 01:54:26 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-27 01:54:26 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-27 01:54:26 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-27 01:54:26 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-27 01:54:26 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-27 01:54:26 (10293) [INFO] yum --disablerepo= ... * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-27 01:54:26 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-27 01:54:26 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] yum-config-manager --disable * 2025-07-27 01:54:26 (10293) [INFO] or * 2025-07-27 01:54:26 (10293) [INFO] subscription-manager repos --disable= * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-27 01:54:26 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-27 01:54:26 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-27 01:54:26 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-27 01:54:26 (10293) [INFO] compromise: * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-27 01:54:26 (10293) [INFO] * 2025-07-27 01:54:26 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-27 01:54:26 (10310) [INFO] * 2025-07-27 01:54:26 (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-27 01:54:26 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-27 01:54:27 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-27 01:54:27 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-27 01:54:27 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-27 01:54:27 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-27 01:54:27 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-27 01:54:34 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ctPJx9jFLi/ea_profile.json * 2025-07-27 01:56:54 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ctPJx9jFLi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-27 01:56:54 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-28 01:48:25 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-28 01:52:26 (11365) [INFO] Script is up to date. * 2025-07-28 01:56:29 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-28 01:56:29 (10280) [INFO] * 2025-07-28 01:57:40 (10310) [INFO] * 2025-07-28 01:57:40 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-28 01:57:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-28 01:57:40 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-28 01:57:40 (10280) [INFO] * 2025-07-28 01:57:43 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-28 01:57:43 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-28 01:57:43 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-28 01:57:43 (10280) [INFO] * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-28 01:58:18 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-28 01:58:18 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-28 01:58:18 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-28 01:58:18 (10280) [INFO] * 2025-07-28 01:58:18 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-28 01:58:19 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-28 01:58:49 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-28 01:58:49 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-28 01:58:49 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-28 01:58:49 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-28 01:58:49 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-28 01:58:49 (10293) [INFO] yum --disablerepo= ... * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-28 01:58:49 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-28 01:58:49 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] yum-config-manager --disable * 2025-07-28 01:58:49 (10293) [INFO] or * 2025-07-28 01:58:49 (10293) [INFO] subscription-manager repos --disable= * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-28 01:58:49 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-28 01:58:49 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-28 01:58:49 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-28 01:58:49 (10293) [INFO] compromise: * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-28 01:58:49 (10293) [INFO] * 2025-07-28 01:58:49 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-28 01:58:49 (10310) [INFO] * 2025-07-28 01:58:49 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-28 01:58:49 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-28 01:58:49 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-28 01:58:49 (10280) [INFO] * 2025-07-28 01:58:50 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-28 01:58:50 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-28 01:58:50 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-28 01:58:50 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-28 01:58:50 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-28 01:58:50 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-28 01:58:50 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-28 01:58:50 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-28 01:58:50 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-28 01:58:50 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-28 01:58:50 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-28 01:58:50 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-28 01:58:50 (10310) [INFO] * 2025-07-28 01:58:50 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-28 01:58:50 (10280) [INFO] * 2025-07-28 01:58:51 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-28 01:58:51 (10293) [INFO] Determining fastest mirrors * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-28 01:59:22 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-28 01:59:22 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-28 01:59:22 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-28 01:59:22 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-28 01:59:22 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-28 01:59:22 (10293) [INFO] yum --disablerepo= ... * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-28 01:59:22 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-28 01:59:22 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] yum-config-manager --disable * 2025-07-28 01:59:22 (10293) [INFO] or * 2025-07-28 01:59:22 (10293) [INFO] subscription-manager repos --disable= * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-28 01:59:22 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-28 01:59:22 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-28 01:59:22 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-28 01:59:22 (10293) [INFO] compromise: * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-28 01:59:22 (10293) [INFO] * 2025-07-28 01:59:22 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-28 01:59:22 (10310) [INFO] * 2025-07-28 01:59: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-07-28 01:59: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-28 01:59:23 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-28 01:59:23 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-28 01:59:23 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-28 01:59:23 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-28 01:59:23 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-28 01:59:28 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/o9RF6rJsTD/ea_profile.json * 2025-07-28 02:01:48 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/o9RF6rJsTD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-28 02:01:48 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-29 01:42:34 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-29 01:46:35 (11365) [INFO] Script is up to date. * 2025-07-29 01:50:37 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-29 01:50:37 (10280) [INFO] * 2025-07-29 01:51:48 (10310) [INFO] * 2025-07-29 01:51:48 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-29 01:51:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-29 01:51:49 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-29 01:51:49 (10280) [INFO] * 2025-07-29 01:51:52 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-29 01:51:52 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-29 01:51:52 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-29 01:51:52 (10280) [INFO] * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-29 01:52:26 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-29 01:52:26 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-29 01:52:26 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-29 01:52:26 (10280) [INFO] * 2025-07-29 01:52:26 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-29 01:52:27 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-29 01:52:58 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-29 01:52:58 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-29 01:52:58 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-29 01:52:58 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-29 01:52:58 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-29 01:52:58 (10293) [INFO] yum --disablerepo= ... * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-29 01:52:58 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-29 01:52:58 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] yum-config-manager --disable * 2025-07-29 01:52:58 (10293) [INFO] or * 2025-07-29 01:52:58 (10293) [INFO] subscription-manager repos --disable= * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-29 01:52:58 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-29 01:52:58 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-29 01:52:58 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-29 01:52:58 (10293) [INFO] compromise: * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-29 01:52:58 (10293) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-29 01:52:58 (10310) [INFO] * 2025-07-29 01:52:58 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-29 01:52:58 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-29 01:52:58 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-29 01:52:58 (10280) [INFO] * 2025-07-29 01:52:58 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-29 01:52:58 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-29 01:52:58 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-29 01:52:58 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-29 01:52:58 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-29 01:52:58 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-29 01:52:58 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-29 01:52:58 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-29 01:52:58 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-29 01:52:58 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-29 01:52:59 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-29 01:52:59 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-29 01:52:59 (10310) [INFO] * 2025-07-29 01:52:59 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-29 01:52:59 (10280) [INFO] * 2025-07-29 01:52:59 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-29 01:52:59 (10293) [INFO] Determining fastest mirrors * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-29 01:53:29 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-29 01:53:29 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-29 01:53:29 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-29 01:53:29 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-29 01:53:29 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-29 01:53:29 (10293) [INFO] yum --disablerepo= ... * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-29 01:53:29 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-29 01:53:29 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] yum-config-manager --disable * 2025-07-29 01:53:29 (10293) [INFO] or * 2025-07-29 01:53:29 (10293) [INFO] subscription-manager repos --disable= * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-29 01:53:29 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-29 01:53:29 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-29 01:53:29 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-29 01:53:29 (10293) [INFO] compromise: * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-29 01:53:29 (10293) [INFO] * 2025-07-29 01:53:29 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-29 01:53:29 (10310) [INFO] * 2025-07-29 01:53:29 (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-29 01:53:29 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-29 01:53:31 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-29 01:53:31 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-29 01:53:31 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-29 01:53:31 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-29 01:53:31 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-29 01:53:36 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qneYvIuQCT/ea_profile.json * 2025-07-29 01:56:27 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qneYvIuQCT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-29 01:56:27 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-30 01:42:40 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-30 01:46:40 (11365) [INFO] Script is up to date. * 2025-07-30 01:50:44 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-30 01:50:44 (10280) [INFO] * 2025-07-30 01:51:58 (10310) [INFO] * 2025-07-30 01:51:59 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-30 01:51:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-30 01:51:59 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-30 01:51:59 (10280) [INFO] * 2025-07-30 01:52:03 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-30 01:52:03 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-30 01:52:03 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-30 01:52:03 (10280) [INFO] * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-30 01:52:36 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-30 01:52:36 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-30 01:52:36 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-30 01:52:36 (10280) [INFO] * 2025-07-30 01:52:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-30 01:52:37 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-30 01:53:07 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-30 01:53:07 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-30 01:53:07 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-30 01:53:07 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-30 01:53:07 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-30 01:53:07 (10293) [INFO] yum --disablerepo= ... * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-30 01:53:07 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-30 01:53:07 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] yum-config-manager --disable * 2025-07-30 01:53:07 (10293) [INFO] or * 2025-07-30 01:53:07 (10293) [INFO] subscription-manager repos --disable= * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-30 01:53:07 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-30 01:53:07 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-30 01:53:07 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-30 01:53:07 (10293) [INFO] compromise: * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-30 01:53:07 (10293) [INFO] * 2025-07-30 01:53:07 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-30 01:53:07 (10310) [INFO] * 2025-07-30 01:53:07 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-30 01:53:07 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-30 01:53:07 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-30 01:53:07 (10280) [INFO] * 2025-07-30 01:53:08 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-30 01:53:08 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-30 01:53:08 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-30 01:53:08 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-30 01:53:08 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-30 01:53:08 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-30 01:53:08 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-30 01:53:08 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-30 01:53:08 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-30 01:53:08 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-30 01:53:08 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-30 01:53:08 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-30 01:53:08 (10310) [INFO] * 2025-07-30 01:53:08 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-30 01:53:08 (10280) [INFO] * 2025-07-30 01:53:08 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-30 01:53:09 (10293) [INFO] Determining fastest mirrors * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-30 01:53:39 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-30 01:53:39 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-30 01:53:39 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-30 01:53:39 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-30 01:53:39 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-30 01:53:39 (10293) [INFO] yum --disablerepo= ... * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-30 01:53:39 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-30 01:53:39 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] yum-config-manager --disable * 2025-07-30 01:53:39 (10293) [INFO] or * 2025-07-30 01:53:39 (10293) [INFO] subscription-manager repos --disable= * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-30 01:53:39 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-30 01:53:39 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-30 01:53:39 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-30 01:53:39 (10293) [INFO] compromise: * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-30 01:53:39 (10293) [INFO] * 2025-07-30 01:53:39 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-30 01:53:39 (10310) [INFO] * 2025-07-30 01:53:39 (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-30 01:53:39 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-30 01:53:41 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-30 01:53:41 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-30 01:53:41 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-30 01:53:41 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-30 01:53:41 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-30 01:53:47 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wKQhQ7s1Sp/ea_profile.json * 2025-07-30 01:56:38 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wKQhQ7s1Sp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-30 01:56:38 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-31 01:42:44 (11343) [INFO] Self-update of script version 68 requested. * 2025-07-31 01:46:45 (11365) [INFO] Script is up to date. * 2025-07-31 01:50:48 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-31 01:50:48 (10280) [INFO] * 2025-07-31 01:52:03 (10310) [INFO] * 2025-07-31 01:52:03 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-07-31 01:52:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-07-31 01:52:03 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-31 01:52:03 (10280) [INFO] * 2025-07-31 01:52:06 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-07-31 01:52:06 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-31 01:52:06 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-31 01:52:06 (10280) [INFO] * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-07-31 01:52:40 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-07-31 01:52:40 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-07-31 01:52:40 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-31 01:52:40 (10280) [INFO] * 2025-07-31 01:52:41 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 01:52:41 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-31 01:53:12 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-31 01:53:12 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-31 01:53:12 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-31 01:53:12 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-31 01:53:12 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-31 01:53:12 (10293) [INFO] yum --disablerepo= ... * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-31 01:53:12 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-31 01:53:12 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] yum-config-manager --disable * 2025-07-31 01:53:12 (10293) [INFO] or * 2025-07-31 01:53:12 (10293) [INFO] subscription-manager repos --disable= * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-31 01:53:12 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-31 01:53:12 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-31 01:53:12 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-31 01:53:12 (10293) [INFO] compromise: * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-31 01:53:12 (10293) [INFO] * 2025-07-31 01:53:12 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-31 01:53:12 (10310) [INFO] * 2025-07-31 01:53:12 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-31 01:53:12 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-31 01:53:12 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-31 01:53:12 (10280) [INFO] * 2025-07-31 01:53:13 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 01:53:13 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-07-31 01:53:13 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-07-31 01:53:13 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-07-31 01:53:13 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-07-31 01:53:13 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-07-31 01:53:13 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-31 01:53:13 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-31 01:53:13 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-07-31 01:53:13 (10293) [INFO] : wp-toolkit-thirdparties * 2025-07-31 01:53:13 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-31 01:53:13 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-07-31 01:53:13 (10310) [INFO] * 2025-07-31 01:53:13 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-31 01:53:13 (10280) [INFO] * 2025-07-31 01:53:14 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 01:53:14 (10293) [INFO] Determining fastest mirrors * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-31 01:53:45 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-31 01:53:45 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-31 01:53:45 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-31 01:53:45 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-31 01:53:45 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-31 01:53:45 (10293) [INFO] yum --disablerepo= ... * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-31 01:53:45 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-31 01:53:45 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] yum-config-manager --disable * 2025-07-31 01:53:45 (10293) [INFO] or * 2025-07-31 01:53:45 (10293) [INFO] subscription-manager repos --disable= * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-31 01:53:45 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-31 01:53:45 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-31 01:53:45 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-31 01:53:45 (10293) [INFO] compromise: * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-31 01:53:45 (10293) [INFO] * 2025-07-31 01:53:45 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-31 01:53:45 (10310) [INFO] * 2025-07-31 01:53:45 (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 01:53:45 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-07-31 01:53:47 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-07-31 01:53:47 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-07-31 01:53:47 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-07-31 01:53:47 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-07-31 01:53:47 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-31 01:53:53 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Dv4P_eemu1/ea_profile.json * 2025-07-31 01:56:13 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Dv4P_eemu1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-31 01:56:13 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-01 01:47:26 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-01 01:51:27 (11365) [INFO] Script is up to date. * 2025-08-01 01:55:29 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-01 01:55:29 (10280) [INFO] * 2025-08-01 01:56:47 (10310) [INFO] * 2025-08-01 01:56:47 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-01 01:56:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-01 01:56:47 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-01 01:56:47 (10280) [INFO] * 2025-08-01 01:56:51 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-01 01:56:51 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-01 01:56:51 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-01 01:56:51 (10280) [INFO] * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-01 01:57:26 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-01 01:57:26 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-01 01:57:26 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-01 01:57:26 (10280) [INFO] * 2025-08-01 01:57:26 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 01:57:26 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-01 01:57:58 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-01 01:57:58 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-01 01:57:58 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-01 01:57:58 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-01 01:57:58 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-01 01:57:58 (10293) [INFO] yum --disablerepo= ... * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-01 01:57:58 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-01 01:57:58 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] yum-config-manager --disable * 2025-08-01 01:57:58 (10293) [INFO] or * 2025-08-01 01:57:58 (10293) [INFO] subscription-manager repos --disable= * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-01 01:57:58 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-01 01:57:58 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-01 01:57:58 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-01 01:57:58 (10293) [INFO] compromise: * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-01 01:57:58 (10293) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-01 01:57:58 (10310) [INFO] * 2025-08-01 01:57:58 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-01 01:57:58 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-01 01:57:58 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-01 01:57:58 (10280) [INFO] * 2025-08-01 01:57:58 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 01:57:59 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-01 01:57:59 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-01 01:57:59 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-01 01:57:59 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-01 01:57:59 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-01 01:57:59 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-01 01:57:59 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-01 01:57:59 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-01 01:57:59 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-01 01:57:59 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-01 01:57:59 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-01 01:57:59 (10310) [INFO] * 2025-08-01 01:57:59 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-01 01:57:59 (10280) [INFO] * 2025-08-01 01:57:59 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 01:58:00 (10293) [INFO] Determining fastest mirrors * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-01 01:58:30 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-01 01:58:30 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-01 01:58:30 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-01 01:58:30 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-01 01:58:30 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-01 01:58:30 (10293) [INFO] yum --disablerepo= ... * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-01 01:58:30 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-01 01:58:30 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] yum-config-manager --disable * 2025-08-01 01:58:30 (10293) [INFO] or * 2025-08-01 01:58:30 (10293) [INFO] subscription-manager repos --disable= * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-01 01:58:30 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-01 01:58:30 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-01 01:58:30 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-01 01:58:30 (10293) [INFO] compromise: * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-01 01:58:30 (10293) [INFO] * 2025-08-01 01:58:30 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-01 01:58:30 (10310) [INFO] * 2025-08-01 01:58:30 (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 01:58:30 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-01 01:58:32 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-01 01:58:32 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-01 01:58:32 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-01 01:58:32 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-01 01:58:32 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-01 01:58:37 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mGJnd_HvYv/ea_profile.json * 2025-08-01 02:00:58 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mGJnd_HvYv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-01 02:00:58 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-02 01:45:57 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-02 01:49:58 (11365) [INFO] Script is up to date. * 2025-08-02 01:54:01 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-02 01:54:01 (10280) [INFO] * 2025-08-02 01:54:53 (10310) [INFO] * 2025-08-02 01:54:53 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-02 01:54:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-02 01:54:53 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-02 01:54:53 (10280) [INFO] * 2025-08-02 01:54:56 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-02 01:54:56 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-02 01:54:56 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-02 01:54:56 (10280) [INFO] * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-02 01:55:31 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-02 01:55:31 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-02 01:55:31 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-02 01:55:31 (10280) [INFO] * 2025-08-02 01:55:31 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 01:55:31 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-02 01:56:03 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-02 01:56:03 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-02 01:56:03 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-02 01:56:03 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-02 01:56:03 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-02 01:56:03 (10293) [INFO] yum --disablerepo= ... * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-02 01:56:03 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-02 01:56:03 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] yum-config-manager --disable * 2025-08-02 01:56:03 (10293) [INFO] or * 2025-08-02 01:56:03 (10293) [INFO] subscription-manager repos --disable= * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-02 01:56:03 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-02 01:56:03 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-02 01:56:03 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-02 01:56:03 (10293) [INFO] compromise: * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-02 01:56:03 (10293) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-02 01:56:03 (10310) [INFO] * 2025-08-02 01:56:03 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-02 01:56:03 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-02 01:56:03 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-02 01:56:03 (10280) [INFO] * 2025-08-02 01:56:03 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 01:56:04 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-02 01:56:04 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-02 01:56:04 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-02 01:56:04 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-02 01:56:04 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-02 01:56:04 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-02 01:56:04 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-02 01:56:04 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-02 01:56:04 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-02 01:56:04 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-02 01:56:04 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-02 01:56:04 (10310) [INFO] * 2025-08-02 01:56:04 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-02 01:56:04 (10280) [INFO] * 2025-08-02 01:56:04 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 01:56:04 (10293) [INFO] Determining fastest mirrors * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-02 01:56:35 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-02 01:56:35 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-02 01:56:35 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-02 01:56:35 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-02 01:56:35 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-02 01:56:35 (10293) [INFO] yum --disablerepo= ... * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-02 01:56:35 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-02 01:56:35 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] yum-config-manager --disable * 2025-08-02 01:56:35 (10293) [INFO] or * 2025-08-02 01:56:35 (10293) [INFO] subscription-manager repos --disable= * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-02 01:56:35 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-02 01:56:35 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-02 01:56:35 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-02 01:56:35 (10293) [INFO] compromise: * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-02 01:56:35 (10293) [INFO] * 2025-08-02 01:56:35 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-02 01:56:35 (10310) [INFO] * 2025-08-02 01:56:35 (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 01:56:35 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-02 01:56:36 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-02 01:56:36 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-02 01:56:36 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-02 01:56:36 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-02 01:56:36 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-02 01:56:43 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kmFUPQygwe/ea_profile.json * 2025-08-02 01:59:34 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kmFUPQygwe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-02 01:59:34 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-03 01:43:47 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-03 01:47:47 (11365) [INFO] Script is up to date. * 2025-08-03 01:51:50 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-03 01:51:50 (10280) [INFO] * 2025-08-03 01:52:43 (10310) [INFO] * 2025-08-03 01:52:43 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-03 01:52:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-03 01:52:43 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-03 01:52:43 (10280) [INFO] * 2025-08-03 01:52:46 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-03 01:52:46 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-03 01:52:46 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-03 01:52:46 (10280) [INFO] * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-03 01:53:21 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-03 01:53:21 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-03 01:53:21 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-03 01:53:21 (10280) [INFO] * 2025-08-03 01:53:22 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 01:53:22 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-03 01:53:54 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-03 01:53:54 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-03 01:53:54 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-03 01:53:54 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-03 01:53:54 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-03 01:53:54 (10293) [INFO] yum --disablerepo= ... * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-03 01:53:54 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-03 01:53:54 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] yum-config-manager --disable * 2025-08-03 01:53:54 (10293) [INFO] or * 2025-08-03 01:53:54 (10293) [INFO] subscription-manager repos --disable= * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-03 01:53:54 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-03 01:53:54 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-03 01:53:54 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-03 01:53:54 (10293) [INFO] compromise: * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-03 01:53:54 (10293) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-03 01:53:54 (10310) [INFO] * 2025-08-03 01:53:54 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-03 01:53:54 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-03 01:53:54 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-03 01:53:54 (10280) [INFO] * 2025-08-03 01:53:54 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 01:53:54 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-03 01:53:54 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-03 01:53:54 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-03 01:53:54 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-03 01:53:54 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-03 01:53:54 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-03 01:53:54 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-03 01:53:54 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-03 01:53:54 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-03 01:53:55 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-03 01:53:55 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-03 01:53:55 (10310) [INFO] * 2025-08-03 01:53:55 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-03 01:53:55 (10280) [INFO] * 2025-08-03 01:53:55 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 01:53:55 (10293) [INFO] Determining fastest mirrors * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-03 01:54:26 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-03 01:54:26 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-03 01:54:26 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-03 01:54:26 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-03 01:54:26 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-03 01:54:26 (10293) [INFO] yum --disablerepo= ... * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-03 01:54:26 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-03 01:54:26 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] yum-config-manager --disable * 2025-08-03 01:54:26 (10293) [INFO] or * 2025-08-03 01:54:26 (10293) [INFO] subscription-manager repos --disable= * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-03 01:54:26 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-03 01:54:26 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-03 01:54:26 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-03 01:54:26 (10293) [INFO] compromise: * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-03 01:54:26 (10293) [INFO] * 2025-08-03 01:54:26 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-03 01:54:26 (10310) [INFO] * 2025-08-03 01:54:26 (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 01:54:26 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-03 01:54:28 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-03 01:54:28 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-03 01:54:28 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-03 01:54:28 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-03 01:54:28 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-03 01:54:34 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gX1B1k93rC/ea_profile.json * 2025-08-03 01:56:53 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gX1B1k93rC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-03 01:56:53 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-04 01:43:42 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-04 01:47:42 (11365) [INFO] Script is up to date. * 2025-08-04 01:51:45 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-04 01:51:45 (10280) [INFO] * 2025-08-04 01:52:56 (10310) [INFO] * 2025-08-04 01:52:56 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-04 01:52:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-04 01:52:56 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-04 01:52:56 (10280) [INFO] * 2025-08-04 01:53:00 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-04 01:53:00 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-04 01:53:00 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-04 01:53:00 (10280) [INFO] * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-04 01:53:34 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-04 01:53:34 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-04 01:53:34 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-04 01:53:34 (10280) [INFO] * 2025-08-04 01:53:35 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 01:53:35 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-04 01:54:06 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-04 01:54:06 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-04 01:54:06 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-04 01:54:06 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-04 01:54:06 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-04 01:54:06 (10293) [INFO] yum --disablerepo= ... * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-04 01:54:06 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-04 01:54:06 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] yum-config-manager --disable * 2025-08-04 01:54:06 (10293) [INFO] or * 2025-08-04 01:54:06 (10293) [INFO] subscription-manager repos --disable= * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-04 01:54:06 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-04 01:54:06 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-04 01:54:06 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-04 01:54:06 (10293) [INFO] compromise: * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-04 01:54:06 (10293) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-04 01:54:06 (10310) [INFO] * 2025-08-04 01:54:06 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-04 01:54:06 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-04 01:54:06 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-04 01:54:06 (10280) [INFO] * 2025-08-04 01:54:06 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 01:54:07 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-04 01:54:07 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-04 01:54:07 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-04 01:54:07 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-04 01:54:07 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-04 01:54:07 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-04 01:54:07 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-04 01:54:07 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-04 01:54:07 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-04 01:54:07 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-04 01:54:07 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-04 01:54:07 (10310) [INFO] * 2025-08-04 01:54:07 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-04 01:54:07 (10280) [INFO] * 2025-08-04 01:54:07 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 01:54:08 (10293) [INFO] Determining fastest mirrors * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-04 01:54:39 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-04 01:54:39 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-04 01:54:39 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-04 01:54:39 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-04 01:54:39 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-04 01:54:39 (10293) [INFO] yum --disablerepo= ... * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-04 01:54:39 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-04 01:54:39 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] yum-config-manager --disable * 2025-08-04 01:54:39 (10293) [INFO] or * 2025-08-04 01:54:39 (10293) [INFO] subscription-manager repos --disable= * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-04 01:54:39 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-04 01:54:39 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-04 01:54:39 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-04 01:54:39 (10293) [INFO] compromise: * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-04 01:54:39 (10293) [INFO] * 2025-08-04 01:54:39 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-04 01:54:39 (10310) [INFO] * 2025-08-04 01:54:39 (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 01:54:39 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-04 01:54:41 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-04 01:54:41 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-04 01:54:41 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-04 01:54:41 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-04 01:54:41 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-04 01:54:47 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LOtV6__vUZ/ea_profile.json * 2025-08-04 01:57:38 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LOtV6__vUZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-04 01:57:38 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-05 01:42:46 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-05 01:46:46 (11365) [INFO] Script is up to date. * 2025-08-05 01:50:49 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-05 01:50:49 (10280) [INFO] * 2025-08-05 01:52:04 (10310) [INFO] * 2025-08-05 01:52:04 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-05 01:52:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-05 01:52:04 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-05 01:52:04 (10280) [INFO] * 2025-08-05 01:52:07 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-05 01:52:07 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-05 01:52:07 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-05 01:52:07 (10280) [INFO] * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-05 01:52:42 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-05 01:52:42 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-05 01:52:42 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-05 01:52:42 (10280) [INFO] * 2025-08-05 01:52:43 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-05 01:52:43 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-05 01:53:14 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-05 01:53:14 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-05 01:53:14 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-05 01:53:14 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-05 01:53:14 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-05 01:53:14 (10293) [INFO] yum --disablerepo= ... * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-05 01:53:14 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-05 01:53:14 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] yum-config-manager --disable * 2025-08-05 01:53:14 (10293) [INFO] or * 2025-08-05 01:53:14 (10293) [INFO] subscription-manager repos --disable= * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-05 01:53:14 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-05 01:53:14 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-05 01:53:14 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-05 01:53:14 (10293) [INFO] compromise: * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-05 01:53:14 (10293) [INFO] * 2025-08-05 01:53:14 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-05 01:53:14 (10310) [INFO] * 2025-08-05 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-05 01:53:14 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-05 01:53:14 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-05 01:53:14 (10280) [INFO] * 2025-08-05 01:53:15 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-05 01:53:15 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-05 01:53:15 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-05 01:53:15 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-05 01:53:15 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-05 01:53:15 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-05 01:53:15 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-05 01:53:15 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-05 01:53:15 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-05 01:53:15 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-05 01:53:15 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-05 01:53:15 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-05 01:53:15 (10310) [INFO] * 2025-08-05 01:53:15 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-05 01:53:15 (10280) [INFO] * 2025-08-05 01:53:16 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-05 01:53:16 (10293) [INFO] Determining fastest mirrors * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-05 01:53:47 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-05 01:53:47 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-05 01:53:47 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-05 01:53:47 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-05 01:53:47 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-05 01:53:47 (10293) [INFO] yum --disablerepo= ... * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-05 01:53:47 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-05 01:53:47 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] yum-config-manager --disable * 2025-08-05 01:53:47 (10293) [INFO] or * 2025-08-05 01:53:47 (10293) [INFO] subscription-manager repos --disable= * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-05 01:53:47 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-05 01:53:47 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-05 01:53:47 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-05 01:53:47 (10293) [INFO] compromise: * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-05 01:53:47 (10293) [INFO] * 2025-08-05 01:53:47 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-05 01:53:47 (10310) [INFO] * 2025-08-05 01:53:47 (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-05 01:53:47 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-05 01:53:48 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-05 01:53:48 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-05 01:53:48 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-05 01:53:48 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-05 01:53:48 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-05 01:53:54 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NbwbFzBubj/ea_profile.json * 2025-08-05 01:56:44 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NbwbFzBubj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-05 01:56:44 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-06 01:42:37 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-06 01:46:37 (11365) [INFO] Script is up to date. * 2025-08-06 01:50:40 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-06 01:50:40 (10280) [INFO] * 2025-08-06 01:51:56 (10310) [INFO] * 2025-08-06 01:51:56 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-06 01:51:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-06 01:51:56 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-06 01:51:56 (10280) [INFO] * 2025-08-06 01:51:59 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-06 01:51:59 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-06 01:51:59 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-06 01:51:59 (10280) [INFO] * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-06 01:52:33 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-06 01:52:33 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-06 01:52:33 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-06 01:52:33 (10280) [INFO] * 2025-08-06 01:52:33 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-06 01:52:33 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-06 01:53:05 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-06 01:53:05 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-06 01:53:05 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-06 01:53:05 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-06 01:53:05 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-06 01:53:05 (10293) [INFO] yum --disablerepo= ... * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-06 01:53:05 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-06 01:53:05 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] yum-config-manager --disable * 2025-08-06 01:53:05 (10293) [INFO] or * 2025-08-06 01:53:05 (10293) [INFO] subscription-manager repos --disable= * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-06 01:53:05 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-06 01:53:05 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-06 01:53:05 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-06 01:53:05 (10293) [INFO] compromise: * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-06 01:53:05 (10293) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-06 01:53:05 (10310) [INFO] * 2025-08-06 01:53:05 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-06 01:53:05 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-06 01:53:05 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-06 01:53:05 (10280) [INFO] * 2025-08-06 01:53:05 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-06 01:53:06 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-06 01:53:06 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-06 01:53:06 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-06 01:53:06 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-06 01:53:06 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-06 01:53:06 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-06 01:53:06 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-06 01:53:06 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-06 01:53:06 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-06 01:53:06 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-06 01:53:06 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-06 01:53:06 (10310) [INFO] * 2025-08-06 01:53:06 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-06 01:53:06 (10280) [INFO] * 2025-08-06 01:53:06 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-06 01:53:07 (10293) [INFO] Determining fastest mirrors * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-06 01:53:37 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-06 01:53:37 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-06 01:53:37 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-06 01:53:37 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-06 01:53:37 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-06 01:53:37 (10293) [INFO] yum --disablerepo= ... * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-06 01:53:37 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-06 01:53:37 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] yum-config-manager --disable * 2025-08-06 01:53:37 (10293) [INFO] or * 2025-08-06 01:53:37 (10293) [INFO] subscription-manager repos --disable= * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-06 01:53:37 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-06 01:53:37 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-06 01:53:37 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-06 01:53:37 (10293) [INFO] compromise: * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-06 01:53:37 (10293) [INFO] * 2025-08-06 01:53:37 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-06 01:53:37 (10310) [INFO] * 2025-08-06 01:53:37 (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-06 01:53:37 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-06 01:53:39 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-06 01:53:39 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-06 01:53:39 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-06 01:53:39 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-06 01:53:39 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-06 01:53:45 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cLInj2esuV/ea_profile.json * 2025-08-06 01:56:05 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cLInj2esuV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-06 01:56:05 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-07 01:47:19 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-07 01:51:20 (11365) [INFO] Script is up to date. * 2025-08-07 01:55:22 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-07 01:55:22 (10280) [INFO] * 2025-08-07 01:56:40 (10310) [INFO] * 2025-08-07 01:56:40 (6823) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-07 01:56:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-07 01:56:40 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-07 01:56:40 (10280) [INFO] * 2025-08-07 01:56:43 (4387) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-07 01:56:43 (4394) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-07 01:56:43 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-07 01:56:43 (10280) [INFO] * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-07 01:57:19 (6539) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-07 01:57:19 (6506) [ERROR] 22 package(s) installed from unsupported YUM repo 'alt-common' from /etc/yum.repos.d/alt-common-els.repo * 2025-08-07 01:57:19 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-07 01:57:19 (10280) [INFO] * 2025-08-07 01:57:19 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-07 01:57:19 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-07 01:57:50 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-07 01:57:50 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-07 01:57:50 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-07 01:57:50 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-07 01:57:50 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-07 01:57:50 (10293) [INFO] yum --disablerepo= ... * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-07 01:57:50 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-07 01:57:50 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] yum-config-manager --disable * 2025-08-07 01:57:50 (10293) [INFO] or * 2025-08-07 01:57:50 (10293) [INFO] subscription-manager repos --disable= * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-07 01:57:50 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-07 01:57:50 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-07 01:57:50 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-07 01:57:50 (10293) [INFO] compromise: * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-07 01:57:50 (10293) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-07 01:57:50 (10310) [INFO] * 2025-08-07 01:57:50 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-07 01:57:50 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-07 01:57:50 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-07 01:57:50 (10280) [INFO] * 2025-08-07 01:57:50 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-07 01:57:51 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-07 01:57:51 (10293) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-07 01:57:51 (10293) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-07 01:57:51 (10293) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-07 01:57:51 (10293) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-07 01:57:51 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-07 01:57:51 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-07 01:57:51 (10293) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-07 01:57:51 (10293) [INFO] : wp-toolkit-thirdparties * 2025-08-07 01:57:51 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-07 01:57:51 (10293) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-07 01:57:51 (10310) [INFO] * 2025-08-07 01:57:51 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-07 01:57:51 (10280) [INFO] * 2025-08-07 01:57:51 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-07 01:57:52 (10293) [INFO] Determining fastest mirrors * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-07 01:58:23 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-07 01:58:23 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-07 01:58:23 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-07 01:58:23 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-07 01:58:23 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-07 01:58:23 (10293) [INFO] yum --disablerepo= ... * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-07 01:58:23 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-07 01:58:23 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] yum-config-manager --disable * 2025-08-07 01:58:23 (10293) [INFO] or * 2025-08-07 01:58:23 (10293) [INFO] subscription-manager repos --disable= * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-07 01:58:23 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-07 01:58:23 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-07 01:58:23 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-07 01:58:23 (10293) [INFO] compromise: * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-07 01:58:23 (10293) [INFO] * 2025-08-07 01:58:23 (10293) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-07 01:58:23 (10310) [INFO] * 2025-08-07 01:58:23 (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-07 01:58:23 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-07 01:58:25 (3566) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-07 01:58:25 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-07 01:58:25 (4681) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-07 01:58:25 (4687) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-07 01:58:25 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-07 01:58:31 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jk7q4b0VDW/ea_profile.json * 2025-08-07 02:00:51 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jk7q4b0VDW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-07 02:00:51 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-08 01:47:34 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-08 01:51:34 (11348) [INFO] Newer version of script found. Downloading. * 2025-08-08 01:55:36 (11357) [INFO] Script update to version 69 successful. * 2025-08-08 01:59:38 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-08 01:59:38 (10285) [INFO] * 2025-08-08 02:00:56 (10315) [INFO] * 2025-08-08 02:00:56 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-08 02:00:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-08 02:00:57 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-08 02:00:57 (10285) [INFO] * 2025-08-08 02:01:00 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-08 02:01:00 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-08 02:01:00 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-08 02:01:00 (10285) [INFO] * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-08 02:01:35 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-08 02:01:35 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-08 02:01:35 (10285) [INFO] * 2025-08-08 02:01:35 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 02:01:36 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-08 02:02:07 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-08 02:02:07 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-08 02:02:07 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-08 02:02:07 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-08 02:02:07 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-08 02:02:07 (10298) [INFO] yum --disablerepo= ... * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-08 02:02:07 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-08 02:02:07 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-08 02:02:07 (10298) [INFO] * 2025-08-08 02:02:07 (10298) [INFO] yum-config-manager --disable * 2025-08-08 02:02:07 (10298) [INFO] or * 2025-08-08 02:02:08 (10298) [INFO] subscription-manager repos --disable= * 2025-08-08 02:02:08 (10298) [INFO] * 2025-08-08 02:02:08 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-08 02:02:08 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-08 02:02:08 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-08 02:02:08 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-08 02:02:08 (10298) [INFO] compromise: * 2025-08-08 02:02:08 (10298) [INFO] * 2025-08-08 02:02:08 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-08 02:02:08 (10298) [INFO] * 2025-08-08 02:02:08 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-08 02:02:08 (10315) [INFO] * 2025-08-08 02:02:08 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-08 02:02:08 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-08 02:02:08 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-08 02:02:08 (10285) [INFO] * 2025-08-08 02:02:08 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 02:02:08 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-08 02:02:08 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-08 02:02:08 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-08 02:02:08 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-08 02:02:08 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-08 02:02:08 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-08 02:02:08 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-08 02:02:08 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-08 02:02:08 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-08 02:02:08 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-08 02:02:08 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-08 02:02:08 (10315) [INFO] * 2025-08-08 02:02:08 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-08 02:02:08 (10285) [INFO] * 2025-08-08 02:02:09 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 02:02:09 (10298) [INFO] Determining fastest mirrors * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-08 02:02:41 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-08 02:02:41 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-08 02:02:41 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-08 02:02:41 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-08 02:02:41 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-08 02:02:41 (10298) [INFO] yum --disablerepo= ... * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-08 02:02:41 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-08 02:02:41 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] yum-config-manager --disable * 2025-08-08 02:02:41 (10298) [INFO] or * 2025-08-08 02:02:41 (10298) [INFO] subscription-manager repos --disable= * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-08 02:02:41 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-08 02:02:41 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-08 02:02:41 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-08 02:02:41 (10298) [INFO] compromise: * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-08 02:02:41 (10298) [INFO] * 2025-08-08 02:02:41 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-08 02:02:41 (10315) [INFO] * 2025-08-08 02:02:41 (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 02:02:41 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-08 02:02:42 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-08 02:02:42 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-08 02:02:42 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-08 02:02:42 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-08 02:02:42 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-08 02:02:48 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/d11GXv65az/ea_profile.json * 2025-08-08 02:05:16 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/d11GXv65az/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-08 02:05:16 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-09 01:44:38 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-09 01:48:38 (11370) [INFO] Script is up to date. * 2025-08-09 01:52:41 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-09 01:52:41 (10285) [INFO] * 2025-08-09 01:53:32 (10315) [INFO] * 2025-08-09 01:53:32 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-09 01:53:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-09 01:53:33 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-09 01:53:33 (10285) [INFO] * 2025-08-09 01:53:36 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-09 01:53:36 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-09 01:53:36 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-09 01:53:36 (10285) [INFO] * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-09 01:54:10 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-09 01:54:10 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-09 01:54:10 (10285) [INFO] * 2025-08-09 01:54:11 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 01:54:11 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-09 01:54:42 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-09 01:54:42 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-09 01:54:42 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-09 01:54:42 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-09 01:54:42 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-09 01:54:42 (10298) [INFO] yum --disablerepo= ... * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-09 01:54:42 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-09 01:54:42 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] yum-config-manager --disable * 2025-08-09 01:54:42 (10298) [INFO] or * 2025-08-09 01:54:42 (10298) [INFO] subscription-manager repos --disable= * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-09 01:54:42 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-09 01:54:42 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-09 01:54:42 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-09 01:54:42 (10298) [INFO] compromise: * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-09 01:54:42 (10298) [INFO] * 2025-08-09 01:54:42 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-09 01:54:42 (10315) [INFO] * 2025-08-09 01:54:42 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-09 01:54:42 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-09 01:54:42 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-09 01:54:42 (10285) [INFO] * 2025-08-09 01:54:43 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 01:54:43 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-09 01:54:43 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-09 01:54:43 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-09 01:54:43 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-09 01:54:43 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-09 01:54:43 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-09 01:54:43 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-09 01:54:43 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-09 01:54:43 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-09 01:54:43 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-09 01:54:43 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-09 01:54:43 (10315) [INFO] * 2025-08-09 01:54:43 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-09 01:54:43 (10285) [INFO] * 2025-08-09 01:54:44 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 01:54:44 (10298) [INFO] Determining fastest mirrors * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-09 01:55:15 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-09 01:55:15 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-09 01:55:15 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-09 01:55:15 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-09 01:55:15 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-09 01:55:15 (10298) [INFO] yum --disablerepo= ... * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-09 01:55:15 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-09 01:55:15 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] yum-config-manager --disable * 2025-08-09 01:55:15 (10298) [INFO] or * 2025-08-09 01:55:15 (10298) [INFO] subscription-manager repos --disable= * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-09 01:55:15 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-09 01:55:15 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-09 01:55:15 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-09 01:55:15 (10298) [INFO] compromise: * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-09 01:55:15 (10298) [INFO] * 2025-08-09 01:55:15 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-09 01:55:15 (10315) [INFO] * 2025-08-09 01:55:15 (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 01:55:15 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-09 01:55:17 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-09 01:55:17 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-09 01:55:17 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-09 01:55:17 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-09 01:55:17 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-09 01:55:23 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qarez1mqmD/ea_profile.json * 2025-08-09 01:57:50 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qarez1mqmD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-09 01:57:50 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-10 01:45:11 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-10 01:49:11 (11370) [INFO] Script is up to date. * 2025-08-10 01:53:14 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-10 01:53:14 (10285) [INFO] * 2025-08-10 01:54:04 (10315) [INFO] * 2025-08-10 01:54:04 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-10 01:54:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-10 01:54:04 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-10 01:54:04 (10285) [INFO] * 2025-08-10 01:54:07 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-10 01:54:07 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-10 01:54:07 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-10 01:54:07 (10285) [INFO] * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-10 01:54:44 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-10 01:54:44 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-10 01:54:44 (10285) [INFO] * 2025-08-10 01:54:44 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 01:54:45 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-10 01:55:18 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-10 01:55:18 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-10 01:55:18 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-10 01:55:18 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-10 01:55:18 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-10 01:55:18 (10298) [INFO] yum --disablerepo= ... * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-10 01:55:18 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-10 01:55:18 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] yum-config-manager --disable * 2025-08-10 01:55:18 (10298) [INFO] or * 2025-08-10 01:55:18 (10298) [INFO] subscription-manager repos --disable= * 2025-08-10 01:55:18 (10298) [INFO] * 2025-08-10 01:55:18 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-10 01:55:18 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-10 01:55:18 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-10 01:55:18 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-10 01:55:18 (10298) [INFO] compromise: * 2025-08-10 01:55:19 (10298) [INFO] * 2025-08-10 01:55:19 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-10 01:55:19 (10298) [INFO] * 2025-08-10 01:55:19 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-10 01:55:19 (10315) [INFO] * 2025-08-10 01:55:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-10 01:55:19 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-10 01:55:19 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-10 01:55:19 (10285) [INFO] * 2025-08-10 01:55:19 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 01:55:19 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-10 01:55:19 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-10 01:55:19 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-10 01:55:19 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-10 01:55:19 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-10 01:55:19 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-10 01:55:19 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-10 01:55:19 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-10 01:55:19 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-10 01:55:19 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-10 01:55:19 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-10 01:55:20 (10315) [INFO] * 2025-08-10 01:55:20 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-10 01:55:20 (10285) [INFO] * 2025-08-10 01:55:20 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 01:55:20 (10298) [INFO] Determining fastest mirrors * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-10 01:55:54 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-10 01:55:54 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-10 01:55:54 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-10 01:55:54 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-10 01:55:54 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-10 01:55:54 (10298) [INFO] yum --disablerepo= ... * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-10 01:55:54 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-10 01:55:54 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] yum-config-manager --disable * 2025-08-10 01:55:54 (10298) [INFO] or * 2025-08-10 01:55:54 (10298) [INFO] subscription-manager repos --disable= * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-10 01:55:54 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-10 01:55:54 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-10 01:55:54 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-10 01:55:54 (10298) [INFO] compromise: * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-10 01:55:54 (10298) [INFO] * 2025-08-10 01:55:54 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-10 01:55:54 (10315) [INFO] * 2025-08-10 01:55:54 (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 01:55:54 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-10 01:55:56 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-10 01:55:56 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-10 01:55:56 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-10 01:55:56 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-10 01:55:56 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-10 01:56:02 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QE5MXju7eI/ea_profile.json * 2025-08-10 01:59:00 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QE5MXju7eI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-10 01:59:00 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-11 01:42:48 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-11 01:46:49 (11370) [INFO] Script is up to date. * 2025-08-11 01:50:52 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-11 01:50:52 (10285) [INFO] * 2025-08-11 01:52:03 (10315) [INFO] * 2025-08-11 01:52:03 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-11 01:52:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-11 01:52:03 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-11 01:52:03 (10285) [INFO] * 2025-08-11 01:52:06 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-11 01:52:06 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-11 01:52:06 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-11 01:52:06 (10285) [INFO] * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-11 01:52:41 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-11 01:52:41 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-11 01:52:41 (10285) [INFO] * 2025-08-11 01:52:41 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 01:52:42 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-11 01:53:12 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-11 01:53:12 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-11 01:53:12 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-11 01:53:12 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-11 01:53:12 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-11 01:53:12 (10298) [INFO] yum --disablerepo= ... * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-11 01:53:12 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-11 01:53:12 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] yum-config-manager --disable * 2025-08-11 01:53:12 (10298) [INFO] or * 2025-08-11 01:53:12 (10298) [INFO] subscription-manager repos --disable= * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-11 01:53:12 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-11 01:53:12 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-11 01:53:12 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-11 01:53:12 (10298) [INFO] compromise: * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-11 01:53:12 (10298) [INFO] * 2025-08-11 01:53:12 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-11 01:53:12 (10315) [INFO] * 2025-08-11 01:53:12 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-11 01:53:12 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-11 01:53:12 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-11 01:53:12 (10285) [INFO] * 2025-08-11 01:53:13 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 01:53:13 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-11 01:53:13 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-11 01:53:13 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-11 01:53:13 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-11 01:53:13 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-11 01:53:13 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-11 01:53:13 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-11 01:53:13 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-11 01:53:13 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-11 01:53:13 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-11 01:53:13 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-11 01:53:13 (10315) [INFO] * 2025-08-11 01:53:13 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-11 01:53:13 (10285) [INFO] * 2025-08-11 01:53:13 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 01:53:14 (10298) [INFO] Determining fastest mirrors * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-11 01:53:44 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-11 01:53:44 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-11 01:53:44 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-11 01:53:44 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-11 01:53:44 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-11 01:53:44 (10298) [INFO] yum --disablerepo= ... * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-11 01:53:44 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-11 01:53:44 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] yum-config-manager --disable * 2025-08-11 01:53:44 (10298) [INFO] or * 2025-08-11 01:53:44 (10298) [INFO] subscription-manager repos --disable= * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-11 01:53:44 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-11 01:53:44 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-11 01:53:44 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-11 01:53:44 (10298) [INFO] compromise: * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-11 01:53:44 (10298) [INFO] * 2025-08-11 01:53:44 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-11 01:53:44 (10315) [INFO] * 2025-08-11 01:53:44 (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 01:53:44 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-11 01:53:46 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-11 01:53:46 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-11 01:53:46 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-11 01:53:46 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-11 01:53:46 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-11 01:53:52 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4X3d2hFg50/ea_profile.json * 2025-08-11 01:57:13 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4X3d2hFg50/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-11 01:57:13 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-12 01:47:32 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-12 01:51:33 (11370) [INFO] Script is up to date. * 2025-08-12 01:55:35 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-12 01:55:35 (10285) [INFO] * 2025-08-12 01:56:50 (10315) [INFO] * 2025-08-12 01:56:50 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-12 01:56:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-12 01:56:51 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-12 01:56:51 (10285) [INFO] * 2025-08-12 01:56:54 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-12 01:56:54 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-12 01:56:54 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-12 01:56:54 (10285) [INFO] * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-12 01:57:28 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-12 01:57:28 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-12 01:57:28 (10285) [INFO] * 2025-08-12 01:57:29 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 01:57:29 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-12 01:58:00 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-12 01:58:00 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-12 01:58:00 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-12 01:58:00 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-12 01:58:00 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-12 01:58:00 (10298) [INFO] yum --disablerepo= ... * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-12 01:58:00 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-12 01:58:00 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] yum-config-manager --disable * 2025-08-12 01:58:00 (10298) [INFO] or * 2025-08-12 01:58:00 (10298) [INFO] subscription-manager repos --disable= * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-12 01:58:00 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-12 01:58:00 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-12 01:58:00 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-12 01:58:00 (10298) [INFO] compromise: * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-12 01:58:00 (10298) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-12 01:58:00 (10315) [INFO] * 2025-08-12 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-12 01:58:00 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-12 01:58:00 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-12 01:58:00 (10285) [INFO] * 2025-08-12 01:58:00 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 01:58:00 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-12 01:58:00 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-12 01:58:00 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-12 01:58:00 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-12 01:58:00 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-12 01:58:00 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-12 01:58:00 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-12 01:58:00 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-12 01:58:00 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-12 01:58:00 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-12 01:58:00 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-12 01:58:01 (10315) [INFO] * 2025-08-12 01:58:01 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-12 01:58:01 (10285) [INFO] * 2025-08-12 01:58:01 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 01:58:01 (10298) [INFO] Determining fastest mirrors * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-12 01:58:33 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-12 01:58:33 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-12 01:58:33 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-12 01:58:33 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-12 01:58:33 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-12 01:58:33 (10298) [INFO] yum --disablerepo= ... * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-12 01:58:33 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-12 01:58:33 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] yum-config-manager --disable * 2025-08-12 01:58:33 (10298) [INFO] or * 2025-08-12 01:58:33 (10298) [INFO] subscription-manager repos --disable= * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-12 01:58:33 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-12 01:58:33 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-12 01:58:33 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-12 01:58:33 (10298) [INFO] compromise: * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-12 01:58:33 (10298) [INFO] * 2025-08-12 01:58:33 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-12 01:58:33 (10315) [INFO] * 2025-08-12 01:58:33 (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 01:58:33 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-12 01:58:34 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-12 01:58:34 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-12 01:58:34 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-12 01:58:34 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-12 01:58:34 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-12 01:58:40 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sGWUNBlhP3/ea_profile.json * 2025-08-12 02:01:08 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sGWUNBlhP3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-12 02:01:08 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-13 01:43:03 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-13 01:47:03 (11370) [INFO] Script is up to date. * 2025-08-13 01:51:06 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-13 01:51:06 (10285) [INFO] * 2025-08-13 01:52:23 (10315) [INFO] * 2025-08-13 01:52:23 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-13 01:52:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-13 01:52:24 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-13 01:52:24 (10285) [INFO] * 2025-08-13 01:52:27 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-13 01:52:27 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-13 01:52:27 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-13 01:52:27 (10285) [INFO] * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-13 01:53:03 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-13 01:53:03 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-13 01:53:03 (10285) [INFO] * 2025-08-13 01:53:03 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 01:53:04 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-13 01:53:34 (10298) [INFO] * 2025-08-13 01:53:34 (10298) [INFO] * 2025-08-13 01:53:34 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-13 01:53:34 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-13 01:53:34 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-13 01:53:34 (10298) [INFO] * 2025-08-13 01:53:34 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-13 01:53:35 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-13 01:53:35 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-13 01:53:35 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-13 01:53:35 (10298) [INFO] yum --disablerepo= ... * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-13 01:53:35 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-13 01:53:35 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] yum-config-manager --disable * 2025-08-13 01:53:35 (10298) [INFO] or * 2025-08-13 01:53:35 (10298) [INFO] subscription-manager repos --disable= * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-13 01:53:35 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-13 01:53:35 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-13 01:53:35 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-13 01:53:35 (10298) [INFO] compromise: * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-13 01:53:35 (10298) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-13 01:53:35 (10315) [INFO] * 2025-08-13 01:53:35 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-13 01:53:35 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-13 01:53:35 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-13 01:53:35 (10285) [INFO] * 2025-08-13 01:53:35 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 01:53:35 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-13 01:53:35 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-13 01:53:35 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-13 01:53:35 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-13 01:53:35 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-13 01:53:35 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-13 01:53:35 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-13 01:53:35 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-13 01:53:35 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-13 01:53:35 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-13 01:53:35 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-13 01:53:35 (10315) [INFO] * 2025-08-13 01:53:35 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-13 01:53:35 (10285) [INFO] * 2025-08-13 01:53:36 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 01:53:36 (10298) [INFO] Determining fastest mirrors * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-13 01:54:07 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-13 01:54:07 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-13 01:54:07 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-13 01:54:07 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-13 01:54:07 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-13 01:54:07 (10298) [INFO] yum --disablerepo= ... * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-13 01:54:07 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-13 01:54:07 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] yum-config-manager --disable * 2025-08-13 01:54:07 (10298) [INFO] or * 2025-08-13 01:54:07 (10298) [INFO] subscription-manager repos --disable= * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-13 01:54:07 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-13 01:54:07 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-13 01:54:07 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-13 01:54:07 (10298) [INFO] compromise: * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-13 01:54:07 (10298) [INFO] * 2025-08-13 01:54:07 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-13 01:54:07 (10315) [INFO] * 2025-08-13 01:54:07 (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 01:54:07 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-13 01:54:09 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-13 01:54:09 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-13 01:54:09 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-13 01:54:09 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-13 01:54:09 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-13 01:54:14 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JGH0vFIn1N/ea_profile.json * 2025-08-13 01:57:12 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JGH0vFIn1N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-13 01:57:12 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-14 01:42:50 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-14 01:46:50 (11370) [INFO] Script is up to date. * 2025-08-14 01:50:54 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-14 01:50:54 (10285) [INFO] * 2025-08-14 01:52:11 (10315) [INFO] * 2025-08-14 01:52:11 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-14 01:52:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-14 01:52:11 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-14 01:52:11 (10285) [INFO] * 2025-08-14 01:52:14 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-14 01:52:14 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-14 01:52:14 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-14 01:52:14 (10285) [INFO] * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-14 01:52:49 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-14 01:52:49 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-14 01:52:49 (10285) [INFO] * 2025-08-14 01:52:49 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 01:52:49 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-14 01:53:20 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-14 01:53:20 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-14 01:53:20 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-14 01:53:20 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-14 01:53:20 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-14 01:53:20 (10298) [INFO] yum --disablerepo= ... * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-14 01:53:20 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-14 01:53:20 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] yum-config-manager --disable * 2025-08-14 01:53:20 (10298) [INFO] or * 2025-08-14 01:53:20 (10298) [INFO] subscription-manager repos --disable= * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-14 01:53:20 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-14 01:53:20 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-14 01:53:20 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-14 01:53:20 (10298) [INFO] compromise: * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-14 01:53:20 (10298) [INFO] * 2025-08-14 01:53:20 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-14 01:53:20 (10315) [INFO] * 2025-08-14 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-14 01:53:20 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-14 01:53:20 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-14 01:53:20 (10285) [INFO] * 2025-08-14 01:53:21 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 01:53:21 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-14 01:53:21 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-14 01:53:21 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-14 01:53:21 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-14 01:53:21 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-14 01:53:21 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-14 01:53:21 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-14 01:53:21 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-14 01:53:21 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-14 01:53:21 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-14 01:53:21 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-14 01:53:21 (10315) [INFO] * 2025-08-14 01:53:21 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-14 01:53:21 (10285) [INFO] * 2025-08-14 01:53:22 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 01:53:22 (10298) [INFO] Determining fastest mirrors * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-14 01:53:54 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-14 01:53:54 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-14 01:53:54 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-14 01:53:54 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-14 01:53:54 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-14 01:53:54 (10298) [INFO] yum --disablerepo= ... * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-14 01:53:54 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-14 01:53:54 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] yum-config-manager --disable * 2025-08-14 01:53:54 (10298) [INFO] or * 2025-08-14 01:53:54 (10298) [INFO] subscription-manager repos --disable= * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-14 01:53:54 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-14 01:53:54 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-14 01:53:54 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-14 01:53:54 (10298) [INFO] compromise: * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-14 01:53:54 (10298) [INFO] * 2025-08-14 01:53:54 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-14 01:53:54 (10315) [INFO] * 2025-08-14 01:53:54 (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 01:53:54 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-14 01:53:55 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-14 01:53:55 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-14 01:53:55 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-14 01:53:55 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-14 01:53:55 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-14 01:54:02 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/16JemyRQ2_/ea_profile.json * 2025-08-14 01:57:31 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/16JemyRQ2_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-14 01:57:31 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-15 01:42:50 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-15 01:46:50 (11370) [INFO] Script is up to date. * 2025-08-15 01:50:53 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-15 01:50:53 (10285) [INFO] * 2025-08-15 01:52:12 (10315) [INFO] * 2025-08-15 01:52:12 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-15 01:52:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-15 01:52:12 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-15 01:52:12 (10285) [INFO] * 2025-08-15 01:52:16 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-15 01:52:16 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-15 01:52:16 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-15 01:52:16 (10285) [INFO] * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-15 01:52:51 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-15 01:52:51 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-15 01:52:51 (10285) [INFO] * 2025-08-15 01:52:52 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-15 01:52:52 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-15 01:53:23 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-15 01:53:23 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-15 01:53:23 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-15 01:53:23 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-15 01:53:23 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-15 01:53:23 (10298) [INFO] yum --disablerepo= ... * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-15 01:53:23 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-15 01:53:23 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] yum-config-manager --disable * 2025-08-15 01:53:23 (10298) [INFO] or * 2025-08-15 01:53:23 (10298) [INFO] subscription-manager repos --disable= * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-15 01:53:23 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-15 01:53:23 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-15 01:53:23 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-15 01:53:23 (10298) [INFO] compromise: * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-15 01:53:23 (10298) [INFO] * 2025-08-15 01:53:23 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-15 01:53:23 (10315) [INFO] * 2025-08-15 01:53:23 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-15 01:53:23 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-15 01:53:23 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-15 01:53:23 (10285) [INFO] * 2025-08-15 01:53:24 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-15 01:53:24 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-15 01:53:24 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-15 01:53:24 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-15 01:53:24 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-15 01:53:24 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-15 01:53:24 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-15 01:53:24 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-15 01:53:24 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-15 01:53:24 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-15 01:53:24 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-15 01:53:24 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-15 01:53:24 (10315) [INFO] * 2025-08-15 01:53:24 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-15 01:53:24 (10285) [INFO] * 2025-08-15 01:53:24 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-15 01:53:25 (10298) [INFO] Determining fastest mirrors * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-15 01:53:56 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-15 01:53:56 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-15 01:53:56 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-15 01:53:56 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-15 01:53:56 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-15 01:53:56 (10298) [INFO] yum --disablerepo= ... * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-15 01:53:56 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-15 01:53:56 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] yum-config-manager --disable * 2025-08-15 01:53:56 (10298) [INFO] or * 2025-08-15 01:53:56 (10298) [INFO] subscription-manager repos --disable= * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-15 01:53:56 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-15 01:53:56 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-15 01:53:56 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-15 01:53:56 (10298) [INFO] compromise: * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-15 01:53:56 (10298) [INFO] * 2025-08-15 01:53:56 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-15 01:53:56 (10315) [INFO] * 2025-08-15 01:53:56 (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-15 01:53:56 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-15 01:53:57 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-15 01:53:57 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-15 01:53:57 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-15 01:53:57 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-15 01:53:57 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-15 01:54:04 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IwF7jeBUUA/ea_profile.json * 2025-08-15 01:56:32 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IwF7jeBUUA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-15 01:56:32 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-16 01:44:04 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-16 01:48:04 (11370) [INFO] Script is up to date. * 2025-08-16 01:52:07 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-16 01:52:07 (10285) [INFO] * 2025-08-16 01:53:05 (10315) [INFO] * 2025-08-16 01:53:05 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-16 01:53:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-16 01:53:05 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-16 01:53:05 (10285) [INFO] * 2025-08-16 01:53:09 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-16 01:53:09 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-16 01:53:09 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-16 01:53:09 (10285) [INFO] * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-16 01:53:45 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-16 01:53:45 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-16 01:53:45 (10285) [INFO] * 2025-08-16 01:53:45 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 01:53:46 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-16 01:54:17 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-16 01:54:17 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-16 01:54:17 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-16 01:54:17 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-16 01:54:17 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-16 01:54:17 (10298) [INFO] yum --disablerepo= ... * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-16 01:54:17 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-16 01:54:17 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] yum-config-manager --disable * 2025-08-16 01:54:17 (10298) [INFO] or * 2025-08-16 01:54:17 (10298) [INFO] subscription-manager repos --disable= * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-16 01:54:17 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-16 01:54:17 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-16 01:54:17 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-16 01:54:17 (10298) [INFO] compromise: * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-16 01:54:17 (10298) [INFO] * 2025-08-16 01:54:17 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-16 01:54:17 (10315) [INFO] * 2025-08-16 01:54:17 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-16 01:54:17 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-16 01:54:17 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-16 01:54:17 (10285) [INFO] * 2025-08-16 01:54:18 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 01:54:18 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-16 01:54:18 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-16 01:54:18 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-16 01:54:18 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-16 01:54:18 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-16 01:54:18 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-16 01:54:18 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-16 01:54:18 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-16 01:54:18 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-16 01:54:18 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-16 01:54:18 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-16 01:54:18 (10315) [INFO] * 2025-08-16 01:54:18 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-16 01:54:18 (10285) [INFO] * 2025-08-16 01:54:19 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 01:54:19 (10298) [INFO] Determining fastest mirrors * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-16 01:54:51 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-16 01:54:51 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-16 01:54:51 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-16 01:54:51 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-16 01:54:51 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-16 01:54:51 (10298) [INFO] yum --disablerepo= ... * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-16 01:54:51 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-16 01:54:51 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] yum-config-manager --disable * 2025-08-16 01:54:51 (10298) [INFO] or * 2025-08-16 01:54:51 (10298) [INFO] subscription-manager repos --disable= * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-16 01:54:51 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-16 01:54:51 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-16 01:54:51 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-16 01:54:51 (10298) [INFO] compromise: * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-16 01:54:51 (10298) [INFO] * 2025-08-16 01:54:51 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-16 01:54:51 (10315) [INFO] * 2025-08-16 01:54:51 (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 01:54:51 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-16 01:54:52 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-16 01:54:52 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-16 01:54:52 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-16 01:54:52 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-16 01:54:52 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-16 01:54:58 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/w2_CwGQR0d/ea_profile.json * 2025-08-16 01:57:26 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/w2_CwGQR0d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-16 01:57:26 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-17 01:43:52 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-17 01:47:53 (11370) [INFO] Script is up to date. * 2025-08-17 01:51:55 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-17 01:51:55 (10285) [INFO] * 2025-08-17 01:52:48 (10315) [INFO] * 2025-08-17 01:52:48 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-17 01:52:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-17 01:52:48 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-17 01:52:48 (10285) [INFO] * 2025-08-17 01:52:52 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-17 01:52:52 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-17 01:52:52 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-17 01:52:52 (10285) [INFO] * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-17 01:53:26 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-17 01:53:26 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-17 01:53:26 (10285) [INFO] * 2025-08-17 01:53:26 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 01:53:27 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-17 01:53:57 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-17 01:53:57 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-17 01:53:57 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-17 01:53:57 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-17 01:53:57 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-17 01:53:57 (10298) [INFO] yum --disablerepo= ... * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-17 01:53:57 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-17 01:53:57 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] yum-config-manager --disable * 2025-08-17 01:53:57 (10298) [INFO] or * 2025-08-17 01:53:57 (10298) [INFO] subscription-manager repos --disable= * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-17 01:53:57 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-17 01:53:57 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-17 01:53:57 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-17 01:53:57 (10298) [INFO] compromise: * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-17 01:53:57 (10298) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-17 01:53:57 (10315) [INFO] * 2025-08-17 01:53:57 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-17 01:53:57 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-17 01:53:57 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-17 01:53:57 (10285) [INFO] * 2025-08-17 01:53:57 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 01:53:58 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-17 01:53:58 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-17 01:53:58 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-17 01:53:58 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-17 01:53:58 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-17 01:53:58 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-17 01:53:58 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-17 01:53:58 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-17 01:53:58 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-17 01:53:58 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-17 01:53:58 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-17 01:53:58 (10315) [INFO] * 2025-08-17 01:53:58 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-17 01:53:58 (10285) [INFO] * 2025-08-17 01:53:58 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 01:53:59 (10298) [INFO] Determining fastest mirrors * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-17 01:54:30 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-17 01:54:30 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-17 01:54:30 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-17 01:54:30 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-17 01:54:30 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-17 01:54:30 (10298) [INFO] yum --disablerepo= ... * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-17 01:54:30 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-17 01:54:30 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] yum-config-manager --disable * 2025-08-17 01:54:30 (10298) [INFO] or * 2025-08-17 01:54:30 (10298) [INFO] subscription-manager repos --disable= * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-17 01:54:30 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-17 01:54:30 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-17 01:54:30 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-17 01:54:30 (10298) [INFO] compromise: * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-17 01:54:30 (10298) [INFO] * 2025-08-17 01:54:30 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-17 01:54:30 (10315) [INFO] * 2025-08-17 01:54:30 (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 01:54:30 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-17 01:54:31 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-17 01:54:31 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-17 01:54:31 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-17 01:54:31 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-17 01:54:31 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-17 01:54:37 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AmgpyZqGDA/ea_profile.json * 2025-08-17 01:57:04 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AmgpyZqGDA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-17 01:57:04 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-18 01:44:06 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-18 01:48:06 (11370) [INFO] Script is up to date. * 2025-08-18 01:52:09 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-18 01:52:09 (10285) [INFO] * 2025-08-18 01:53:19 (10315) [INFO] * 2025-08-18 01:53:19 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-18 01:53:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-18 01:53:19 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-18 01:53:19 (10285) [INFO] * 2025-08-18 01:53:22 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-18 01:53:22 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-18 01:53:22 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-18 01:53:22 (10285) [INFO] * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-18 01:53:56 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-18 01:53:56 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-18 01:53:56 (10285) [INFO] * 2025-08-18 01:53:56 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 01:53:56 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-18 01:54:27 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-18 01:54:27 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-18 01:54:27 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-18 01:54:27 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-18 01:54:27 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-18 01:54:27 (10298) [INFO] yum --disablerepo= ... * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-18 01:54:27 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-18 01:54:27 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] yum-config-manager --disable * 2025-08-18 01:54:27 (10298) [INFO] or * 2025-08-18 01:54:27 (10298) [INFO] subscription-manager repos --disable= * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-18 01:54:27 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-18 01:54:27 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-18 01:54:27 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-18 01:54:27 (10298) [INFO] compromise: * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-18 01:54:27 (10298) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-18 01:54:27 (10315) [INFO] * 2025-08-18 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-18 01:54:27 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-18 01:54:27 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-18 01:54:27 (10285) [INFO] * 2025-08-18 01:54:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 01:54:28 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-18 01:54:28 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-18 01:54:28 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-18 01:54:28 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-18 01:54:28 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-18 01:54:28 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-18 01:54:28 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-18 01:54:28 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-18 01:54:28 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-18 01:54:28 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-18 01:54:28 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-18 01:54:28 (10315) [INFO] * 2025-08-18 01:54:28 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-18 01:54:28 (10285) [INFO] * 2025-08-18 01:54:28 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 01:54:29 (10298) [INFO] Determining fastest mirrors * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-18 01:54:59 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-18 01:54:59 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-18 01:54:59 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-18 01:54:59 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-18 01:54:59 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-18 01:54:59 (10298) [INFO] yum --disablerepo= ... * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-18 01:54:59 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-18 01:54:59 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] yum-config-manager --disable * 2025-08-18 01:54:59 (10298) [INFO] or * 2025-08-18 01:54:59 (10298) [INFO] subscription-manager repos --disable= * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-18 01:54:59 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-18 01:54:59 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-18 01:54:59 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-18 01:54:59 (10298) [INFO] compromise: * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-18 01:54:59 (10298) [INFO] * 2025-08-18 01:54:59 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-18 01:54:59 (10315) [INFO] * 2025-08-18 01:54:59 (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 01:54:59 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-18 01:55:01 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-18 01:55:01 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-18 01:55:01 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-18 01:55:01 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-18 01:55:01 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-18 01:55:08 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/H175ZV_uGX/ea_profile.json * 2025-08-18 01:58:06 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/H175ZV_uGX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-18 01:58:06 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-19 01:42:50 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-19 01:46:50 (11370) [INFO] Script is up to date. * 2025-08-19 01:50:53 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-19 01:50:53 (10285) [INFO] * 2025-08-19 01:52:09 (10315) [INFO] * 2025-08-19 01:52:09 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-19 01:52:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-19 01:52:09 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-19 01:52:09 (10285) [INFO] * 2025-08-19 01:52:12 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-19 01:52:12 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-19 01:52:12 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-19 01:52:12 (10285) [INFO] * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-19 01:52:47 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-19 01:52:47 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-19 01:52:47 (10285) [INFO] * 2025-08-19 01:52:47 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 01:52:48 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-19 01:53:19 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-19 01:53:19 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-19 01:53:19 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-19 01:53:19 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-19 01:53:19 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-19 01:53:19 (10298) [INFO] yum --disablerepo= ... * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-19 01:53:19 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-19 01:53:19 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] yum-config-manager --disable * 2025-08-19 01:53:19 (10298) [INFO] or * 2025-08-19 01:53:19 (10298) [INFO] subscription-manager repos --disable= * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-19 01:53:19 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-19 01:53:19 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-19 01:53:19 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-19 01:53:19 (10298) [INFO] compromise: * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-19 01:53:19 (10298) [INFO] * 2025-08-19 01:53:19 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-19 01:53:19 (10315) [INFO] * 2025-08-19 01:53:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-19 01:53:19 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-19 01:53:19 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-19 01:53:19 (10285) [INFO] * 2025-08-19 01:53:20 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 01:53:20 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-19 01:53:20 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-19 01:53:20 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-19 01:53:20 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-19 01:53:20 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-19 01:53:20 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-19 01:53:20 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-19 01:53:20 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-19 01:53:20 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-19 01:53:20 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-19 01:53:20 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-19 01:53:20 (10315) [INFO] * 2025-08-19 01:53:20 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-19 01:53:20 (10285) [INFO] * 2025-08-19 01:53:21 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 01:53:21 (10298) [INFO] Determining fastest mirrors * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-19 01:53:52 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-19 01:53:52 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-19 01:53:52 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-19 01:53:52 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-19 01:53:52 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-19 01:53:52 (10298) [INFO] yum --disablerepo= ... * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-19 01:53:52 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-19 01:53:52 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] yum-config-manager --disable * 2025-08-19 01:53:52 (10298) [INFO] or * 2025-08-19 01:53:52 (10298) [INFO] subscription-manager repos --disable= * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-19 01:53:52 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-19 01:53:52 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-19 01:53:52 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-19 01:53:52 (10298) [INFO] compromise: * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-19 01:53:52 (10298) [INFO] * 2025-08-19 01:53:52 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-19 01:53:52 (10315) [INFO] * 2025-08-19 01:53: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 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-19 01:53:54 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-19 01:53:54 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-19 01:53:54 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-19 01:53:54 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-19 01:53:54 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-19 01:53:59 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qPbiKFjDC9/ea_profile.json * 2025-08-19 01:56:26 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qPbiKFjDC9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-19 01:56:26 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-20 01:47:30 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-20 01:51:30 (11370) [INFO] Script is up to date. * 2025-08-20 01:55:33 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-20 01:55:33 (10285) [INFO] * 2025-08-20 01:56:51 (10315) [INFO] * 2025-08-20 01:56:51 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-20 01:56:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-20 01:56:52 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-20 01:56:52 (10285) [INFO] * 2025-08-20 01:56:56 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-20 01:56:56 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-20 01:56:56 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-20 01:56:56 (10285) [INFO] * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-20 01:57:31 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-20 01:57:31 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-20 01:57:31 (10285) [INFO] * 2025-08-20 01:57:31 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-20 01:57:31 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-20 01:58:02 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-20 01:58:02 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-20 01:58:02 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-20 01:58:02 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-20 01:58:02 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-20 01:58:02 (10298) [INFO] yum --disablerepo= ... * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-20 01:58:02 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-20 01:58:02 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] yum-config-manager --disable * 2025-08-20 01:58:02 (10298) [INFO] or * 2025-08-20 01:58:02 (10298) [INFO] subscription-manager repos --disable= * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-20 01:58:02 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-20 01:58:02 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-20 01:58:02 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-20 01:58:02 (10298) [INFO] compromise: * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-20 01:58:02 (10298) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-20 01:58:02 (10315) [INFO] * 2025-08-20 01:58:02 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-20 01:58:02 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-20 01:58:02 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-20 01:58:02 (10285) [INFO] * 2025-08-20 01:58:02 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-20 01:58:03 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-20 01:58:03 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-20 01:58:03 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-20 01:58:03 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-20 01:58:03 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-20 01:58:03 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-20 01:58:03 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-20 01:58:03 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-20 01:58:03 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-20 01:58:03 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-20 01:58:03 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-20 01:58:03 (10315) [INFO] * 2025-08-20 01:58:03 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-20 01:58:03 (10285) [INFO] * 2025-08-20 01:58:03 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-20 01:58:04 (10298) [INFO] Determining fastest mirrors * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-20 01:58:35 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-20 01:58:35 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-20 01:58:35 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-20 01:58:35 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-20 01:58:35 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-20 01:58:35 (10298) [INFO] yum --disablerepo= ... * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-20 01:58:35 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-20 01:58:35 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] yum-config-manager --disable * 2025-08-20 01:58:35 (10298) [INFO] or * 2025-08-20 01:58:35 (10298) [INFO] subscription-manager repos --disable= * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-20 01:58:35 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-20 01:58:35 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-20 01:58:35 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-20 01:58:35 (10298) [INFO] compromise: * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-20 01:58:35 (10298) [INFO] * 2025-08-20 01:58:35 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-20 01:58:35 (10315) [INFO] * 2025-08-20 01:58:35 (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-20 01:58:35 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-20 01:58:36 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-20 01:58:36 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-20 01:58:36 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-20 01:58:36 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-20 01:58:36 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-20 01:58:42 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YO6GvFw04D/ea_profile.json * 2025-08-20 02:01:09 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YO6GvFw04D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-20 02:01:09 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-21 01:42:46 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-21 01:46:46 (11370) [INFO] Script is up to date. * 2025-08-21 01:50:49 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-21 01:50:49 (10285) [INFO] * 2025-08-21 01:52:09 (10315) [INFO] * 2025-08-21 01:52:09 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-21 01:52:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-21 01:52:09 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-21 01:52:09 (10285) [INFO] * 2025-08-21 01:52:13 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-21 01:52:13 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-21 01:52:13 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-21 01:52:13 (10285) [INFO] * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-21 01:52:47 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-21 01:52:47 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-21 01:52:47 (10285) [INFO] * 2025-08-21 01:52:48 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 01:52:48 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-21 01:53:19 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-21 01:53:19 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-21 01:53:19 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-21 01:53:19 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-21 01:53:19 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-21 01:53:19 (10298) [INFO] yum --disablerepo= ... * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-21 01:53:19 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-21 01:53:19 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] yum-config-manager --disable * 2025-08-21 01:53:19 (10298) [INFO] or * 2025-08-21 01:53:19 (10298) [INFO] subscription-manager repos --disable= * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-21 01:53:19 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-21 01:53:19 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-21 01:53:19 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-21 01:53:19 (10298) [INFO] compromise: * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-21 01:53:19 (10298) [INFO] * 2025-08-21 01:53:19 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-21 01:53:19 (10315) [INFO] * 2025-08-21 01:53:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-21 01:53:19 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-21 01:53:19 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-21 01:53:19 (10285) [INFO] * 2025-08-21 01:53:20 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 01:53:20 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-21 01:53:20 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-21 01:53:20 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-21 01:53:20 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-21 01:53:20 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-21 01:53:20 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-21 01:53:20 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-21 01:53:20 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-21 01:53:20 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-21 01:53:20 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-21 01:53:20 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-21 01:53:20 (10315) [INFO] * 2025-08-21 01:53:20 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-21 01:53:20 (10285) [INFO] * 2025-08-21 01:53:21 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 01:53:21 (10298) [INFO] Determining fastest mirrors * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-21 01:53:52 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-21 01:53:52 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-21 01:53:52 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-21 01:53:52 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-21 01:53:52 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-21 01:53:52 (10298) [INFO] yum --disablerepo= ... * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-21 01:53:52 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-21 01:53:52 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] yum-config-manager --disable * 2025-08-21 01:53:52 (10298) [INFO] or * 2025-08-21 01:53:52 (10298) [INFO] subscription-manager repos --disable= * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-21 01:53:52 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-21 01:53:52 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-21 01:53:52 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-21 01:53:52 (10298) [INFO] compromise: * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-21 01:53:52 (10298) [INFO] * 2025-08-21 01:53:52 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-21 01:53:52 (10315) [INFO] * 2025-08-21 01:53: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-21 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-21 01:53:54 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-21 01:53:54 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-21 01:53:54 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-21 01:53:54 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-21 01:53:54 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-21 01:54:00 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ur48kE1rif/ea_profile.json * 2025-08-21 01:56:26 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ur48kE1rif/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-21 01:56:26 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-22 01:53:18 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-22 01:57:18 (11370) [INFO] Script is up to date. * 2025-08-22 02:01:22 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-22 02:01:22 (10285) [INFO] * 2025-08-22 02:02:35 (10315) [INFO] * 2025-08-22 02:02:35 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-22 02:02:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-22 02:02:35 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-22 02:02:35 (10285) [INFO] * 2025-08-22 02:02:39 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-22 02:02:39 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-22 02:02:39 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-22 02:02:39 (10285) [INFO] * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-22 02:03:14 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-22 02:03:14 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-22 02:03:14 (10285) [INFO] * 2025-08-22 02:03:15 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-22 02:03:15 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-22 02:03:46 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-22 02:03:46 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-22 02:03:46 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-22 02:03:46 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-22 02:03:46 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-22 02:03:46 (10298) [INFO] yum --disablerepo= ... * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-22 02:03:46 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-22 02:03:46 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] yum-config-manager --disable * 2025-08-22 02:03:46 (10298) [INFO] or * 2025-08-22 02:03:46 (10298) [INFO] subscription-manager repos --disable= * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-22 02:03:46 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-22 02:03:46 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-22 02:03:46 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-22 02:03:46 (10298) [INFO] compromise: * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-22 02:03:46 (10298) [INFO] * 2025-08-22 02:03:46 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-22 02:03:46 (10315) [INFO] * 2025-08-22 02:03:46 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-22 02:03:46 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-22 02:03:46 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-22 02:03:46 (10285) [INFO] * 2025-08-22 02:03:47 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-22 02:03:47 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-22 02:03:47 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-22 02:03:47 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-22 02:03:47 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-22 02:03:47 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-22 02:03:47 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-22 02:03:47 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-22 02:03:47 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-22 02:03:47 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-22 02:03:47 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-22 02:03:47 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-22 02:03:47 (10315) [INFO] * 2025-08-22 02:03:47 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-22 02:03:47 (10285) [INFO] * 2025-08-22 02:03:48 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-22 02:03:48 (10298) [INFO] Determining fastest mirrors * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-22 02:04:20 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-22 02:04:20 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-22 02:04:20 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-22 02:04:20 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-22 02:04:20 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-22 02:04:20 (10298) [INFO] yum --disablerepo= ... * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-22 02:04:20 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-22 02:04:20 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] yum-config-manager --disable * 2025-08-22 02:04:20 (10298) [INFO] or * 2025-08-22 02:04:20 (10298) [INFO] subscription-manager repos --disable= * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-22 02:04:20 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-22 02:04:20 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-22 02:04:20 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-22 02:04:20 (10298) [INFO] compromise: * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-22 02:04:20 (10298) [INFO] * 2025-08-22 02:04:20 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-22 02:04:20 (10315) [INFO] * 2025-08-22 02:04:20 (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-22 02:04:20 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-22 02:04:21 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-22 02:04:21 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-22 02:04:21 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-22 02:04:21 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-22 02:04:21 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-22 02:04:28 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pbIzbqa3Xy/ea_profile.json * 2025-08-22 02:06:54 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pbIzbqa3Xy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-22 02:06:54 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-23 01:44:30 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-23 01:48:30 (11370) [INFO] Script is up to date. * 2025-08-23 01:52:33 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-23 01:52:33 (10285) [INFO] * 2025-08-23 01:53:29 (10315) [INFO] * 2025-08-23 01:53:29 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-23 01:53:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-23 01:53:30 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-23 01:53:30 (10285) [INFO] * 2025-08-23 01:53:33 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-23 01:53:33 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-23 01:53:33 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-23 01:53:33 (10285) [INFO] * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-23 01:54:08 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-23 01:54:08 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-23 01:54:08 (10285) [INFO] * 2025-08-23 01:54:08 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 01:54:09 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-23 01:54:40 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-23 01:54:40 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-23 01:54:40 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-23 01:54:40 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-23 01:54:40 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-23 01:54:40 (10298) [INFO] yum --disablerepo= ... * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-23 01:54:40 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-23 01:54:40 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] yum-config-manager --disable * 2025-08-23 01:54:40 (10298) [INFO] or * 2025-08-23 01:54:40 (10298) [INFO] subscription-manager repos --disable= * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-23 01:54:40 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-23 01:54:40 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-23 01:54:40 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-23 01:54:40 (10298) [INFO] compromise: * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-23 01:54:40 (10298) [INFO] * 2025-08-23 01:54:40 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-23 01:54:40 (10315) [INFO] * 2025-08-23 01:54:40 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-23 01:54:40 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-23 01:54:40 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-23 01:54:40 (10285) [INFO] * 2025-08-23 01:54:41 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 01:54:41 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-23 01:54:41 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-23 01:54:41 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-23 01:54:41 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-23 01:54:41 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-23 01:54:41 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-23 01:54:41 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-23 01:54:41 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-23 01:54:41 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-23 01:54:41 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-23 01:54:41 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-23 01:54:41 (10315) [INFO] * 2025-08-23 01:54:41 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-23 01:54:41 (10285) [INFO] * 2025-08-23 01:54:42 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 01:54:42 (10298) [INFO] Determining fastest mirrors * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-23 01:55:14 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-23 01:55:14 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-23 01:55:14 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-23 01:55:14 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-23 01:55:14 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-23 01:55:14 (10298) [INFO] yum --disablerepo= ... * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-23 01:55:14 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-23 01:55:14 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] yum-config-manager --disable * 2025-08-23 01:55:14 (10298) [INFO] or * 2025-08-23 01:55:14 (10298) [INFO] subscription-manager repos --disable= * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-23 01:55:14 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-23 01:55:14 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-23 01:55:14 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-23 01:55:14 (10298) [INFO] compromise: * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-23 01:55:14 (10298) [INFO] * 2025-08-23 01:55:14 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-23 01:55:14 (10315) [INFO] * 2025-08-23 01:55:14 (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 01:55:14 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-23 01:55:15 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-23 01:55:15 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-23 01:55:15 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-23 01:55:15 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-23 01:55:15 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-23 01:55:22 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hOWwFOTz3R/ea_profile.json * 2025-08-23 01:59:21 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hOWwFOTz3R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-23 01:59:21 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-24 01:44:33 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-24 01:48:33 (11370) [INFO] Script is up to date. * 2025-08-24 01:52:36 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-24 01:52:36 (10285) [INFO] * 2025-08-24 01:53:28 (10315) [INFO] * 2025-08-24 01:53:28 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-24 01:53:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-24 01:53:28 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-24 01:53:28 (10285) [INFO] * 2025-08-24 01:53:33 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-24 01:53:33 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-24 01:53:33 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-24 01:53:33 (10285) [INFO] * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-24 01:54:08 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-24 01:54:08 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-24 01:54:08 (10285) [INFO] * 2025-08-24 01:54:08 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 01:54:08 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-24 01:54:40 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-24 01:54:40 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-24 01:54:40 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-24 01:54:40 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-24 01:54:40 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-24 01:54:40 (10298) [INFO] yum --disablerepo= ... * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-24 01:54:40 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-24 01:54:40 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] yum-config-manager --disable * 2025-08-24 01:54:40 (10298) [INFO] or * 2025-08-24 01:54:40 (10298) [INFO] subscription-manager repos --disable= * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-24 01:54:40 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-24 01:54:40 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-24 01:54:40 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-24 01:54:40 (10298) [INFO] compromise: * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-24 01:54:40 (10298) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-24 01:54:40 (10315) [INFO] * 2025-08-24 01:54:40 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-24 01:54:40 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-24 01:54:40 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-24 01:54:40 (10285) [INFO] * 2025-08-24 01:54:40 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 01:54:41 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-24 01:54:41 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-24 01:54:41 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-24 01:54:41 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-24 01:54:41 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-24 01:54:41 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-24 01:54:41 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-24 01:54:41 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-24 01:54:41 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-24 01:54:41 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-24 01:54:41 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-24 01:54:41 (10315) [INFO] * 2025-08-24 01:54:41 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-24 01:54:41 (10285) [INFO] * 2025-08-24 01:54:41 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 01:54:41 (10298) [INFO] Determining fastest mirrors * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-24 01:55:13 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-24 01:55:13 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-24 01:55:13 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-24 01:55:13 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-24 01:55:13 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-24 01:55:13 (10298) [INFO] yum --disablerepo= ... * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-24 01:55:13 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-24 01:55:13 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] yum-config-manager --disable * 2025-08-24 01:55:13 (10298) [INFO] or * 2025-08-24 01:55:13 (10298) [INFO] subscription-manager repos --disable= * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-24 01:55:13 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-24 01:55:13 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-24 01:55:13 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-24 01:55:13 (10298) [INFO] compromise: * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-24 01:55:13 (10298) [INFO] * 2025-08-24 01:55:13 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-24 01:55:13 (10315) [INFO] * 2025-08-24 01:55: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-24 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-24 01:55:14 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-24 01:55:14 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-24 01:55:14 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-24 01:55:14 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-24 01:55:14 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-24 01:55:21 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NKvMmXIUpb/ea_profile.json * 2025-08-24 01:58:19 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NKvMmXIUpb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-24 01:58:19 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-25 01:43:22 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-25 01:47:23 (11370) [INFO] Script is up to date. * 2025-08-25 01:51:25 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-25 01:51:25 (10285) [INFO] * 2025-08-25 01:52:34 (10315) [INFO] * 2025-08-25 01:52:34 (6818) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-25 01:52:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-25 01:52:34 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-25 01:52:34 (10285) [INFO] * 2025-08-25 01:52:37 (4382) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-25 01:52:37 (4389) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-25 01:52:37 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-25 01:52:37 (10285) [INFO] * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-25 01:53:11 (6534) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-25 01:53:11 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-25 01:53:11 (10285) [INFO] * 2025-08-25 01:53:11 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 01:53:12 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-25 01:53:43 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-25 01:53:43 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-25 01:53:43 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-25 01:53:43 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-25 01:53:43 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-25 01:53:43 (10298) [INFO] yum --disablerepo= ... * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-25 01:53:43 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-25 01:53:43 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] yum-config-manager --disable * 2025-08-25 01:53:43 (10298) [INFO] or * 2025-08-25 01:53:43 (10298) [INFO] subscription-manager repos --disable= * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-25 01:53:43 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-25 01:53:43 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-25 01:53:43 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-25 01:53:43 (10298) [INFO] compromise: * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-25 01:53:43 (10298) [INFO] * 2025-08-25 01:53:43 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-25 01:53:43 (10315) [INFO] * 2025-08-25 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-25 01:53:43 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-25 01:53:43 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-25 01:53:43 (10285) [INFO] * 2025-08-25 01:53:44 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 01:53:44 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-25 01:53:44 (10298) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-25 01:53:44 (10298) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-25 01:53:44 (10298) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-25 01:53:44 (10298) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-25 01:53:44 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-25 01:53:44 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-25 01:53:44 (10298) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-25 01:53:44 (10298) [INFO] : wp-toolkit-thirdparties * 2025-08-25 01:53:44 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-25 01:53:44 (10298) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-25 01:53:44 (10315) [INFO] * 2025-08-25 01:53:44 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-25 01:53:44 (10285) [INFO] * 2025-08-25 01:53:44 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 01:53:44 (10298) [INFO] Determining fastest mirrors * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-25 01:54:15 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-25 01:54:15 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-25 01:54:15 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-25 01:54:15 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-25 01:54:15 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-25 01:54:15 (10298) [INFO] yum --disablerepo= ... * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-25 01:54:15 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-25 01:54:15 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] yum-config-manager --disable * 2025-08-25 01:54:15 (10298) [INFO] or * 2025-08-25 01:54:15 (10298) [INFO] subscription-manager repos --disable= * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-25 01:54:15 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-25 01:54:15 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-25 01:54:15 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-25 01:54:15 (10298) [INFO] compromise: * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-25 01:54:15 (10298) [INFO] * 2025-08-25 01:54:15 (10298) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-25 01:54:15 (10315) [INFO] * 2025-08-25 01:54:15 (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-25 01:54:15 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-25 01:54:17 (3561) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-25 01:54:17 (261) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-25 01:54:17 (4676) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-25 01:54:17 (4682) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-25 01:54:17 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-25 01:54:23 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/slIs6O3OHz/ea_profile.json * 2025-08-25 01:56:50 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/slIs6O3OHz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-25 01:56:50 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-26 01:43:46 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-26 01:47:46 (11353) [INFO] Newer version of script found. Downloading. * 2025-08-26 01:51:48 (11362) [INFO] Script update to version 70 successful. * 2025-08-26 01:55:50 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-26 01:55:50 (10381) [INFO] * 2025-08-26 01:57:09 (10411) [INFO] * 2025-08-26 01:57:09 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-26 01:57:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-26 01:57:09 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-26 01:57:09 (10381) [INFO] * 2025-08-26 01:57:12 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-26 01:57:12 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-26 01:57:12 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-26 01:57:12 (10381) [INFO] * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-26 01:57:48 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-26 01:57:48 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-26 01:57:48 (10381) [INFO] * 2025-08-26 01:57:48 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-26 01:57:48 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-26 01:58:19 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-26 01:58:19 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-26 01:58:19 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-26 01:58:19 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-26 01:58:19 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-26 01:58:19 (10394) [INFO] yum --disablerepo= ... * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-26 01:58:19 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-26 01:58:19 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] yum-config-manager --disable * 2025-08-26 01:58:19 (10394) [INFO] or * 2025-08-26 01:58:19 (10394) [INFO] subscription-manager repos --disable= * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-26 01:58:19 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-26 01:58:19 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-26 01:58:19 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-26 01:58:19 (10394) [INFO] compromise: * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-26 01:58:19 (10394) [INFO] * 2025-08-26 01:58:19 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-26 01:58:19 (10411) [INFO] * 2025-08-26 01:58:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-26 01:58:19 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-26 01:58:19 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-26 01:58:19 (10381) [INFO] * 2025-08-26 01:58:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-26 01:58:20 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-26 01:58:20 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-26 01:58:20 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-26 01:58:20 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-26 01:58:20 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-26 01:58:20 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-26 01:58:20 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-26 01:58:20 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-26 01:58:20 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-26 01:58:20 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-26 01:58:20 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-26 01:58:20 (10411) [INFO] * 2025-08-26 01:58:20 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-26 01:58:20 (10381) [INFO] * 2025-08-26 01:58:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-26 01:58:21 (10394) [INFO] Determining fastest mirrors * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-26 01:58:52 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-26 01:58:52 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-26 01:58:52 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-26 01:58:52 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-26 01:58:52 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-26 01:58:52 (10394) [INFO] yum --disablerepo= ... * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-26 01:58:52 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-26 01:58:52 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] yum-config-manager --disable * 2025-08-26 01:58:52 (10394) [INFO] or * 2025-08-26 01:58:52 (10394) [INFO] subscription-manager repos --disable= * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-26 01:58:52 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-26 01:58:52 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-26 01:58:52 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-26 01:58:52 (10394) [INFO] compromise: * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-26 01:58:52 (10394) [INFO] * 2025-08-26 01:58:52 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-26 01:58:52 (10411) [INFO] * 2025-08-26 01:58:52 (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-26 01:58:52 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-26 01:58:54 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-26 01:58:54 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-26 01:58:54 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-26 01:58:54 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-26 01:58:54 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-26 01:59:00 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OaQDYvSPwk/ea_profile.json * 2025-08-26 02:01:27 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OaQDYvSPwk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-26 02:01:27 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-27 01:42:48 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-27 01:46:48 (11467) [INFO] Script is up to date. * 2025-08-27 01:50:51 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-27 01:50:51 (10381) [INFO] * 2025-08-27 01:52:08 (10411) [INFO] * 2025-08-27 01:52:08 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-27 01:52:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-27 01:52:08 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-27 01:52:08 (10381) [INFO] * 2025-08-27 01:52:11 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-27 01:52:11 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-27 01:52:11 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-27 01:52:11 (10381) [INFO] * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-27 01:52:46 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-27 01:52:46 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-27 01:52:46 (10381) [INFO] * 2025-08-27 01:52:46 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-27 01:52:47 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-27 01:53:19 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-27 01:53:19 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-27 01:53:19 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-27 01:53:19 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-27 01:53:19 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-27 01:53:19 (10394) [INFO] yum --disablerepo= ... * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-27 01:53:19 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-27 01:53:19 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] yum-config-manager --disable * 2025-08-27 01:53:19 (10394) [INFO] or * 2025-08-27 01:53:19 (10394) [INFO] subscription-manager repos --disable= * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-27 01:53:19 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-27 01:53:19 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-27 01:53:19 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-27 01:53:19 (10394) [INFO] compromise: * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-27 01:53:19 (10394) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-27 01:53:19 (10411) [INFO] * 2025-08-27 01:53:19 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-27 01:53:19 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-27 01:53:19 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-27 01:53:19 (10381) [INFO] * 2025-08-27 01:53:19 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-27 01:53:20 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-27 01:53:20 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-27 01:53:20 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-27 01:53:20 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-27 01:53:20 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-27 01:53:20 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-27 01:53:20 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-27 01:53:20 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-27 01:53:20 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-27 01:53:20 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-27 01:53:20 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-27 01:53:20 (10411) [INFO] * 2025-08-27 01:53:20 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-27 01:53:20 (10381) [INFO] * 2025-08-27 01:53:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-27 01:53:21 (10394) [INFO] Determining fastest mirrors * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-27 01:53:53 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-27 01:53:53 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-27 01:53:53 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-27 01:53:53 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-27 01:53:53 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-27 01:53:53 (10394) [INFO] yum --disablerepo= ... * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-27 01:53:53 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-27 01:53:53 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] yum-config-manager --disable * 2025-08-27 01:53:53 (10394) [INFO] or * 2025-08-27 01:53:53 (10394) [INFO] subscription-manager repos --disable= * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-27 01:53:53 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-27 01:53:53 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-27 01:53:53 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-27 01:53:53 (10394) [INFO] compromise: * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-27 01:53:53 (10394) [INFO] * 2025-08-27 01:53:53 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-27 01:53:53 (10411) [INFO] * 2025-08-27 01:53: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-08-27 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-27 01:53:54 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-27 01:53:54 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-27 01:53:54 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-27 01:53:54 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-27 01:53:54 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-27 01:54:01 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YmV7ma76x8/ea_profile.json * 2025-08-27 01:56:30 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YmV7ma76x8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-27 01:56:30 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-28 01:43:19 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-28 01:47:20 (11467) [INFO] Script is up to date. * 2025-08-28 01:51:23 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-28 01:51:23 (10381) [INFO] * 2025-08-28 01:52:38 (10411) [INFO] * 2025-08-28 01:52:38 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-28 01:52:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-28 01:52:38 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-28 01:52:38 (10381) [INFO] * 2025-08-28 01:52:42 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-28 01:52:42 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-28 01:52:42 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-28 01:52:42 (10381) [INFO] * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-28 01:53:16 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-28 01:53:16 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-28 01:53:16 (10381) [INFO] * 2025-08-28 01:53:16 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 01:53:17 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-28 01:53:48 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-28 01:53:48 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-28 01:53:48 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-28 01:53:48 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-28 01:53:48 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-28 01:53:48 (10394) [INFO] yum --disablerepo= ... * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-28 01:53:48 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-28 01:53:48 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] yum-config-manager --disable * 2025-08-28 01:53:48 (10394) [INFO] or * 2025-08-28 01:53:48 (10394) [INFO] subscription-manager repos --disable= * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-28 01:53:48 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-28 01:53:48 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-28 01:53:48 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-28 01:53:48 (10394) [INFO] compromise: * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-28 01:53:48 (10394) [INFO] * 2025-08-28 01:53:48 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-28 01:53:48 (10411) [INFO] * 2025-08-28 01:53:48 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-28 01:53:48 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-28 01:53:48 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-28 01:53:48 (10381) [INFO] * 2025-08-28 01:53:49 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 01:53:49 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-28 01:53:49 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-28 01:53:49 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-28 01:53:49 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-28 01:53:49 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-28 01:53:49 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-28 01:53:49 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-28 01:53:49 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-28 01:53:49 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-28 01:53:49 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-28 01:53:49 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-28 01:53:49 (10411) [INFO] * 2025-08-28 01:53:49 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-28 01:53:49 (10381) [INFO] * 2025-08-28 01:53:50 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 01:53:50 (10394) [INFO] Determining fastest mirrors * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-28 01:54:21 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-28 01:54:21 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-28 01:54:21 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-28 01:54:21 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-28 01:54:21 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-28 01:54:21 (10394) [INFO] yum --disablerepo= ... * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-28 01:54:21 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-28 01:54:21 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] yum-config-manager --disable * 2025-08-28 01:54:21 (10394) [INFO] or * 2025-08-28 01:54:21 (10394) [INFO] subscription-manager repos --disable= * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-28 01:54:21 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-28 01:54:21 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-28 01:54:21 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-28 01:54:21 (10394) [INFO] compromise: * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-28 01:54:21 (10394) [INFO] * 2025-08-28 01:54:21 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-28 01:54:21 (10411) [INFO] * 2025-08-28 01:54:21 (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 01:54:21 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-28 01:54:22 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-28 01:54:22 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-28 01:54:22 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-28 01:54:22 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-28 01:54:22 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-28 01:54:28 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/247Q8O_7Ix/ea_profile.json * 2025-08-28 01:56:55 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/247Q8O_7Ix/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-28 01:56:55 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-29 01:42:55 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-29 01:46:56 (11467) [INFO] Script is up to date. * 2025-08-29 01:50:59 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-29 01:50:59 (10381) [INFO] * 2025-08-29 01:52:18 (10411) [INFO] * 2025-08-29 01:52:18 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-29 01:52:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-29 01:52:19 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-29 01:52:19 (10381) [INFO] * 2025-08-29 01:52:22 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-29 01:52:22 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-29 01:52:22 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-29 01:52:22 (10381) [INFO] * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-29 01:53:03 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-29 01:53:03 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-29 01:53:03 (10381) [INFO] * 2025-08-29 01:53:04 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 01:53:04 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-29 01:53:35 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-29 01:53:35 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-29 01:53:35 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-29 01:53:35 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-29 01:53:35 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-29 01:53:35 (10394) [INFO] yum --disablerepo= ... * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-29 01:53:35 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-29 01:53:35 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] yum-config-manager --disable * 2025-08-29 01:53:35 (10394) [INFO] or * 2025-08-29 01:53:35 (10394) [INFO] subscription-manager repos --disable= * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-29 01:53:35 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-29 01:53:35 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-29 01:53:35 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-29 01:53:35 (10394) [INFO] compromise: * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-29 01:53:35 (10394) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-29 01:53:35 (10411) [INFO] * 2025-08-29 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-29 01:53:35 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-29 01:53:35 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-29 01:53:35 (10381) [INFO] * 2025-08-29 01:53:35 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 01:53:35 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-29 01:53:35 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-29 01:53:35 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-29 01:53:35 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-29 01:53:35 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-29 01:53:35 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-29 01:53:35 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-29 01:53:35 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-29 01:53:35 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-29 01:53:35 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-29 01:53:35 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-29 01:53:35 (10411) [INFO] * 2025-08-29 01:53:35 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-29 01:53:35 (10381) [INFO] * 2025-08-29 01:53:36 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 01:53:36 (10394) [INFO] Determining fastest mirrors * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-29 01:54:08 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-29 01:54:08 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-29 01:54:08 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-29 01:54:08 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-29 01:54:08 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-29 01:54:08 (10394) [INFO] yum --disablerepo= ... * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-29 01:54:08 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-29 01:54:08 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] yum-config-manager --disable * 2025-08-29 01:54:08 (10394) [INFO] or * 2025-08-29 01:54:08 (10394) [INFO] subscription-manager repos --disable= * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-29 01:54:08 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-29 01:54:08 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-29 01:54:08 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-29 01:54:08 (10394) [INFO] compromise: * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-29 01:54:08 (10394) [INFO] * 2025-08-29 01:54:08 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-29 01:54:08 (10411) [INFO] * 2025-08-29 01:54:08 (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 01:54:08 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-29 01:54:09 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-29 01:54:09 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-29 01:54:09 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-29 01:54:09 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-29 01:54:09 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-29 01:54:15 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g0bf4IhfMJ/ea_profile.json * 2025-08-29 01:56:43 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g0bf4IhfMJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-29 01:56:43 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-30 01:44:36 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-30 01:48:37 (11467) [INFO] Script is up to date. * 2025-08-30 01:52:39 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-30 01:52:39 (10381) [INFO] * 2025-08-30 01:53:32 (10411) [INFO] * 2025-08-30 01:53:32 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-30 01:53:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-30 01:53:32 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-30 01:53:32 (10381) [INFO] * 2025-08-30 01:53:36 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-30 01:53:36 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-30 01:53:36 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-30 01:53:36 (10381) [INFO] * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-30 01:54:11 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-30 01:54:11 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-30 01:54:11 (10381) [INFO] * 2025-08-30 01:54:11 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 01:54:12 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-30 01:54:43 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-30 01:54:43 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-30 01:54:43 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-30 01:54:43 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-30 01:54:43 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-30 01:54:43 (10394) [INFO] yum --disablerepo= ... * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-30 01:54:43 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-30 01:54:43 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] yum-config-manager --disable * 2025-08-30 01:54:43 (10394) [INFO] or * 2025-08-30 01:54:43 (10394) [INFO] subscription-manager repos --disable= * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-30 01:54:43 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-30 01:54:43 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-30 01:54:43 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-30 01:54:43 (10394) [INFO] compromise: * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-30 01:54:43 (10394) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-30 01:54:43 (10411) [INFO] * 2025-08-30 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-30 01:54:43 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-30 01:54:43 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-30 01:54:43 (10381) [INFO] * 2025-08-30 01:54:43 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 01:54:44 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-30 01:54:44 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-30 01:54:44 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-30 01:54:44 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-30 01:54:44 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-30 01:54:44 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-30 01:54:44 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-30 01:54:44 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-30 01:54:44 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-30 01:54:44 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-30 01:54:44 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-30 01:54:44 (10411) [INFO] * 2025-08-30 01:54:44 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-30 01:54:44 (10381) [INFO] * 2025-08-30 01:54:44 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 01:54:45 (10394) [INFO] Determining fastest mirrors * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-30 01:55:16 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-30 01:55:16 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-30 01:55:16 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-30 01:55:16 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-30 01:55:16 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-30 01:55:16 (10394) [INFO] yum --disablerepo= ... * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-30 01:55:16 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-30 01:55:16 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] yum-config-manager --disable * 2025-08-30 01:55:16 (10394) [INFO] or * 2025-08-30 01:55:16 (10394) [INFO] subscription-manager repos --disable= * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-30 01:55:16 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-30 01:55:16 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-30 01:55:16 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-30 01:55:16 (10394) [INFO] compromise: * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-30 01:55:16 (10394) [INFO] * 2025-08-30 01:55:16 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-30 01:55:16 (10411) [INFO] * 2025-08-30 01:55: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-08-30 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-30 01:55:17 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-30 01:55:17 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-30 01:55:17 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-30 01:55:17 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-30 01:55:17 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-30 01:55:24 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XEIgyINIyr/ea_profile.json * 2025-08-30 01:57:52 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XEIgyINIyr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-30 01:57:52 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-31 01:44:01 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-31 01:48:01 (11467) [INFO] Script is up to date. * 2025-08-31 01:52:05 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-31 01:52:05 (10381) [INFO] * 2025-08-31 01:52:56 (10411) [INFO] * 2025-08-31 01:52:56 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-08-31 01:52:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-08-31 01:52:57 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-31 01:52:57 (10381) [INFO] * 2025-08-31 01:53:01 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-08-31 01:53:01 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-31 01:53:01 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-31 01:53:01 (10381) [INFO] * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-08-31 01:53:36 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-08-31 01:53:36 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-31 01:53:36 (10381) [INFO] * 2025-08-31 01:53:37 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 01:53:37 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-31 01:54:09 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-31 01:54:09 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-31 01:54:09 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-31 01:54:09 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-31 01:54:09 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-31 01:54:09 (10394) [INFO] yum --disablerepo= ... * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-31 01:54:09 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-31 01:54:09 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] yum-config-manager --disable * 2025-08-31 01:54:09 (10394) [INFO] or * 2025-08-31 01:54:09 (10394) [INFO] subscription-manager repos --disable= * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-31 01:54:09 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-31 01:54:09 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-31 01:54:09 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-31 01:54:09 (10394) [INFO] compromise: * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-31 01:54:09 (10394) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-31 01:54:09 (10411) [INFO] * 2025-08-31 01:54:09 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-31 01:54:09 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-31 01:54:09 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-31 01:54:09 (10381) [INFO] * 2025-08-31 01:54:09 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 01:54:10 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-08-31 01:54:10 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-08-31 01:54:10 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-08-31 01:54:10 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-08-31 01:54:10 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-08-31 01:54:10 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-31 01:54:10 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-31 01:54:10 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-08-31 01:54:10 (10394) [INFO] : wp-toolkit-thirdparties * 2025-08-31 01:54:10 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-31 01:54:10 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-08-31 01:54:10 (10411) [INFO] * 2025-08-31 01:54:10 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-31 01:54:10 (10381) [INFO] * 2025-08-31 01:54:10 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 01:54:11 (10394) [INFO] Determining fastest mirrors * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-31 01:54:42 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-31 01:54:42 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-31 01:54:42 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-31 01:54:42 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-31 01:54:42 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-31 01:54:42 (10394) [INFO] yum --disablerepo= ... * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-31 01:54:42 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-31 01:54:42 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] yum-config-manager --disable * 2025-08-31 01:54:42 (10394) [INFO] or * 2025-08-31 01:54:42 (10394) [INFO] subscription-manager repos --disable= * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-31 01:54:42 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-31 01:54:42 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-31 01:54:42 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-31 01:54:42 (10394) [INFO] compromise: * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-31 01:54:42 (10394) [INFO] * 2025-08-31 01:54:42 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-31 01:54:42 (10411) [INFO] * 2025-08-31 01:54:42 (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 01:54:42 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-08-31 01:54:44 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-08-31 01:54:44 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-08-31 01:54:44 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-08-31 01:54:44 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-08-31 01:54:44 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-31 01:54:51 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OFIhRXFVwG/ea_profile.json * 2025-08-31 01:57:18 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OFIhRXFVwG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-31 01:57:18 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-01 01:42:52 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-01 01:46:53 (11467) [INFO] Script is up to date. * 2025-09-01 01:50:56 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-01 01:50:56 (10381) [INFO] * 2025-09-01 01:52:17 (10411) [INFO] * 2025-09-01 01:52:17 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-01 01:52:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-01 01:52:17 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-01 01:52:17 (10381) [INFO] * 2025-09-01 01:52:21 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-01 01:52:21 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-01 01:52:21 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-01 01:52:21 (10381) [INFO] * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-01 01:52:57 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-01 01:52:57 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-01 01:52:57 (10381) [INFO] * 2025-09-01 01:52:58 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 01:52:58 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-01 01:53:29 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-01 01:53:29 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-01 01:53:29 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-01 01:53:29 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-01 01:53:29 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-01 01:53:29 (10394) [INFO] yum --disablerepo= ... * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-01 01:53:29 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-01 01:53:29 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] yum-config-manager --disable * 2025-09-01 01:53:29 (10394) [INFO] or * 2025-09-01 01:53:29 (10394) [INFO] subscription-manager repos --disable= * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-01 01:53:29 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-01 01:53:29 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-01 01:53:29 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-01 01:53:29 (10394) [INFO] compromise: * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-01 01:53:29 (10394) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-01 01:53:29 (10411) [INFO] * 2025-09-01 01:53:29 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-01 01:53:29 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-01 01:53:29 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-01 01:53:29 (10381) [INFO] * 2025-09-01 01:53:29 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 01:53:30 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-01 01:53:30 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-01 01:53:30 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-01 01:53:30 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-01 01:53:30 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-01 01:53:30 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-01 01:53:30 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-01 01:53:30 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-01 01:53:30 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-01 01:53:30 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-01 01:53:30 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-01 01:53:30 (10411) [INFO] * 2025-09-01 01:53:30 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-01 01:53:30 (10381) [INFO] * 2025-09-01 01:53:30 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 01:53:31 (10394) [INFO] Determining fastest mirrors * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-01 01:54:01 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-01 01:54:01 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-01 01:54:01 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-01 01:54:01 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-01 01:54:01 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-01 01:54:01 (10394) [INFO] yum --disablerepo= ... * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-01 01:54:01 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-01 01:54:01 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] yum-config-manager --disable * 2025-09-01 01:54:01 (10394) [INFO] or * 2025-09-01 01:54:01 (10394) [INFO] subscription-manager repos --disable= * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-01 01:54:01 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-01 01:54:01 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-01 01:54:01 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-01 01:54:01 (10394) [INFO] compromise: * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-01 01:54:01 (10394) [INFO] * 2025-09-01 01:54:01 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-01 01:54:01 (10411) [INFO] * 2025-09-01 01:54:01 (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 01:54:01 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-01 01:54:03 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-01 01:54:03 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-01 01:54:03 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-01 01:54:03 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-01 01:54:03 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-01 01:54:09 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bnnxdULoKZ/ea_profile.json * 2025-09-01 01:56:35 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bnnxdULoKZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-01 01:56:35 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-02 01:43:27 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-02 01:47:28 (11467) [INFO] Script is up to date. * 2025-09-02 01:51:31 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-02 01:51:31 (10381) [INFO] * 2025-09-02 01:52:53 (10411) [INFO] * 2025-09-02 01:52:53 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-02 01:52:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-02 01:52:53 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-02 01:52:53 (10381) [INFO] * 2025-09-02 01:52:57 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-02 01:52:57 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-02 01:52:57 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-02 01:52:57 (10381) [INFO] * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-02 01:53:32 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-02 01:53:32 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-02 01:53:32 (10381) [INFO] * 2025-09-02 01:53:32 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 01:53:33 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-02 01:54:04 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-02 01:54:04 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-02 01:54:04 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-02 01:54:04 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-02 01:54:04 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-02 01:54:04 (10394) [INFO] yum --disablerepo= ... * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-02 01:54:04 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-02 01:54:04 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] yum-config-manager --disable * 2025-09-02 01:54:04 (10394) [INFO] or * 2025-09-02 01:54:04 (10394) [INFO] subscription-manager repos --disable= * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-02 01:54:04 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-02 01:54:04 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-02 01:54:04 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-02 01:54:04 (10394) [INFO] compromise: * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-02 01:54:04 (10394) [INFO] * 2025-09-02 01:54:04 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-02 01:54:04 (10411) [INFO] * 2025-09-02 01:54:04 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-02 01:54:04 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-02 01:54:04 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-02 01:54:04 (10381) [INFO] * 2025-09-02 01:54:05 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 01:54:05 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-02 01:54:05 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-02 01:54:05 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-02 01:54:05 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-02 01:54:05 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-02 01:54:05 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-02 01:54:05 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-02 01:54:05 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-02 01:54:05 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-02 01:54:05 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-02 01:54:05 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-02 01:54:05 (10411) [INFO] * 2025-09-02 01:54:05 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-02 01:54:05 (10381) [INFO] * 2025-09-02 01:54:05 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 01:54:06 (10394) [INFO] Determining fastest mirrors * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-02 01:54:37 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-02 01:54:37 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-02 01:54:37 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-02 01:54:37 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-02 01:54:37 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-02 01:54:37 (10394) [INFO] yum --disablerepo= ... * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-02 01:54:37 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-02 01:54:37 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] yum-config-manager --disable * 2025-09-02 01:54:37 (10394) [INFO] or * 2025-09-02 01:54:37 (10394) [INFO] subscription-manager repos --disable= * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-02 01:54:37 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-02 01:54:37 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-02 01:54:37 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-02 01:54:37 (10394) [INFO] compromise: * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-02 01:54:37 (10394) [INFO] * 2025-09-02 01:54:37 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-02 01:54:37 (10411) [INFO] * 2025-09-02 01:54: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 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-02 01:54:39 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-02 01:54:39 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-02 01:54:39 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-02 01:54:39 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-02 01:54:39 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-02 01:54:45 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_XzO0zOwLb/ea_profile.json * 2025-09-02 01:57:43 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_XzO0zOwLb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-02 01:57:43 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-03 01:49:24 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-03 01:53:24 (11467) [INFO] Script is up to date. * 2025-09-03 01:57:28 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-03 01:57:28 (10381) [INFO] * 2025-09-03 01:58:43 (10411) [INFO] * 2025-09-03 01:58:43 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-03 01:58:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-03 01:58:44 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-03 01:58:44 (10381) [INFO] * 2025-09-03 01:58:47 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-03 01:58:47 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-03 01:58:47 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-03 01:58:47 (10381) [INFO] * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-03 01:59:22 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-03 01:59:22 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-03 01:59:22 (10381) [INFO] * 2025-09-03 01:59:23 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 01:59:23 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-03 01:59:54 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-03 01:59:54 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-03 01:59:54 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-03 01:59:54 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-03 01:59:54 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-03 01:59:54 (10394) [INFO] yum --disablerepo= ... * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-03 01:59:54 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-03 01:59:54 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] yum-config-manager --disable * 2025-09-03 01:59:54 (10394) [INFO] or * 2025-09-03 01:59:54 (10394) [INFO] subscription-manager repos --disable= * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-03 01:59:54 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-03 01:59:54 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-03 01:59:54 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-03 01:59:54 (10394) [INFO] compromise: * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-03 01:59:54 (10394) [INFO] * 2025-09-03 01:59:54 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-03 01:59:54 (10411) [INFO] * 2025-09-03 01:59: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-03 01:59:54 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-03 01:59:54 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-03 01:59:54 (10381) [INFO] * 2025-09-03 01:59:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 01:59:55 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-03 01:59:55 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-03 01:59:55 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-03 01:59:55 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-03 01:59:55 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-03 01:59:55 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-03 01:59:55 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-03 01:59:55 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-03 01:59:55 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-03 01:59:55 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-03 01:59:55 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-03 01:59:55 (10411) [INFO] * 2025-09-03 01:59:55 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-03 01:59:55 (10381) [INFO] * 2025-09-03 01:59:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 01:59:56 (10394) [INFO] Determining fastest mirrors * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-03 02:00:27 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-03 02:00:27 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-03 02:00:27 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-03 02:00:27 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-03 02:00:27 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-03 02:00:27 (10394) [INFO] yum --disablerepo= ... * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-03 02:00:27 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-03 02:00:27 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] yum-config-manager --disable * 2025-09-03 02:00:27 (10394) [INFO] or * 2025-09-03 02:00:27 (10394) [INFO] subscription-manager repos --disable= * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-03 02:00:27 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-03 02:00:27 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-03 02:00:27 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-03 02:00:27 (10394) [INFO] compromise: * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-03 02:00:27 (10394) [INFO] * 2025-09-03 02:00:27 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-03 02:00:27 (10411) [INFO] * 2025-09-03 02:00:27 (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 02:00:27 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-03 02:00:28 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-03 02:00:28 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-03 02:00:28 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-03 02:00:28 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-03 02:00:28 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-03 02:00:35 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QDeKXdBXJn/ea_profile.json * 2025-09-03 02:03:03 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QDeKXdBXJn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-03 02:03:03 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-04 01:42:49 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-04 01:46:50 (11467) [INFO] Script is up to date. * 2025-09-04 01:50:53 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-04 01:50:53 (10381) [INFO] * 2025-09-04 01:52:10 (10411) [INFO] * 2025-09-04 01:52:10 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-04 01:52:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-04 01:52:10 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-04 01:52:10 (10381) [INFO] * 2025-09-04 01:52:13 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-04 01:52:13 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-04 01:52:13 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-04 01:52:13 (10381) [INFO] * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-04 01:52:50 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-04 01:52:50 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-04 01:52:50 (10381) [INFO] * 2025-09-04 01:52:51 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 01:52:51 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-04 01:53:22 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-04 01:53:22 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-04 01:53:22 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-04 01:53:22 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-04 01:53:22 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-04 01:53:22 (10394) [INFO] yum --disablerepo= ... * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-04 01:53:22 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-04 01:53:22 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] yum-config-manager --disable * 2025-09-04 01:53:22 (10394) [INFO] or * 2025-09-04 01:53:22 (10394) [INFO] subscription-manager repos --disable= * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-04 01:53:22 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-04 01:53:22 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-04 01:53:22 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-04 01:53:22 (10394) [INFO] compromise: * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-04 01:53:22 (10394) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-04 01:53:22 (10411) [INFO] * 2025-09-04 01:53:22 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-04 01:53:22 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-04 01:53:22 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-04 01:53:22 (10381) [INFO] * 2025-09-04 01:53:22 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 01:53:23 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-04 01:53:23 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-04 01:53:23 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-04 01:53:23 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-04 01:53:23 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-04 01:53:23 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-04 01:53:23 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-04 01:53:23 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-04 01:53:23 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-04 01:53:23 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-04 01:53:23 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-04 01:53:23 (10411) [INFO] * 2025-09-04 01:53:23 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-04 01:53:23 (10381) [INFO] * 2025-09-04 01:53:23 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 01:53:23 (10394) [INFO] Determining fastest mirrors * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-04 01:53:54 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-04 01:53:54 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-04 01:53:54 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-04 01:53:54 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-04 01:53:54 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-04 01:53:54 (10394) [INFO] yum --disablerepo= ... * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-04 01:53:54 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-04 01:53:54 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] yum-config-manager --disable * 2025-09-04 01:53:54 (10394) [INFO] or * 2025-09-04 01:53:54 (10394) [INFO] subscription-manager repos --disable= * 2025-09-04 01:53:54 (10394) [INFO] * 2025-09-04 01:53:54 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-04 01:53:54 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-04 01:53:54 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-04 01:53:55 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-04 01:53:55 (10394) [INFO] compromise: * 2025-09-04 01:53:55 (10394) [INFO] * 2025-09-04 01:53:55 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-04 01:53:55 (10394) [INFO] * 2025-09-04 01:53:55 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-04 01:53:55 (10411) [INFO] * 2025-09-04 01:53:55 (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 01:53:55 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-04 01:53:56 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-04 01:53:56 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-04 01:53:56 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-04 01:53:56 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-04 01:53:56 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-04 01:54:02 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XwxM6w2MaA/ea_profile.json * 2025-09-04 01:56:28 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XwxM6w2MaA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-04 01:56:28 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-05 01:42:58 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-05 01:46:59 (11467) [INFO] Script is up to date. * 2025-09-05 01:51:01 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-05 01:51:01 (10381) [INFO] * 2025-09-05 01:52:20 (10411) [INFO] * 2025-09-05 01:52:20 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-05 01:52:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-05 01:52:20 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-05 01:52:20 (10381) [INFO] * 2025-09-05 01:52:23 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-05 01:52:23 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-05 01:52:23 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-05 01:52:23 (10381) [INFO] * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-05 01:53:05 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-05 01:53:05 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-05 01:53:05 (10381) [INFO] * 2025-09-05 01:53:05 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 01:53:06 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-05 01:53:37 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-05 01:53:37 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-05 01:53:37 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-05 01:53:37 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-05 01:53:37 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-05 01:53:37 (10394) [INFO] yum --disablerepo= ... * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-05 01:53:37 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-05 01:53:37 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] yum-config-manager --disable * 2025-09-05 01:53:37 (10394) [INFO] or * 2025-09-05 01:53:37 (10394) [INFO] subscription-manager repos --disable= * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-05 01:53:37 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-05 01:53:37 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-05 01:53:37 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-05 01:53:37 (10394) [INFO] compromise: * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-05 01:53:37 (10394) [INFO] * 2025-09-05 01:53:37 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-05 01:53:37 (10411) [INFO] * 2025-09-05 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-05 01:53:37 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-05 01:53:37 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-05 01:53:37 (10381) [INFO] * 2025-09-05 01:53:38 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 01:53:38 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-05 01:53:38 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-05 01:53:38 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-05 01:53:38 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-05 01:53:38 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-05 01:53:38 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-05 01:53:38 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-05 01:53:38 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-05 01:53:38 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-05 01:53:38 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-05 01:53:38 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-05 01:53:38 (10411) [INFO] * 2025-09-05 01:53:38 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-05 01:53:38 (10381) [INFO] * 2025-09-05 01:53:39 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 01:53:39 (10394) [INFO] Determining fastest mirrors * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-05 01:54:10 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-05 01:54:10 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-05 01:54:10 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-05 01:54:10 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-05 01:54:10 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-05 01:54:10 (10394) [INFO] yum --disablerepo= ... * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-05 01:54:10 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-05 01:54:10 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] yum-config-manager --disable * 2025-09-05 01:54:10 (10394) [INFO] or * 2025-09-05 01:54:10 (10394) [INFO] subscription-manager repos --disable= * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-05 01:54:10 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-05 01:54:10 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-05 01:54:10 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-05 01:54:10 (10394) [INFO] compromise: * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-05 01:54:10 (10394) [INFO] * 2025-09-05 01:54:10 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-05 01:54:10 (10411) [INFO] * 2025-09-05 01:54:10 (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 01:54:10 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-05 01:54:11 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-05 01:54:11 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-05 01:54:11 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-05 01:54:11 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-05 01:54:11 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-05 01:54:18 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VEcuESE1Vw/ea_profile.json * 2025-09-05 01:56:46 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VEcuESE1Vw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-05 01:56:46 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-06 01:44:40 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-06 01:48:41 (11467) [INFO] Script is up to date. * 2025-09-06 01:52:43 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-06 01:52:43 (10381) [INFO] * 2025-09-06 01:53:45 (10411) [INFO] * 2025-09-06 01:53:45 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-06 01:53:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-06 01:53:45 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-06 01:53:45 (10381) [INFO] * 2025-09-06 01:53:48 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-06 01:53:48 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-06 01:53:48 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-06 01:53:48 (10381) [INFO] * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-06 01:54:23 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-06 01:54:23 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-06 01:54:23 (10381) [INFO] * 2025-09-06 01:54:24 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 01:54:24 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-06 01:54:55 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-06 01:54:55 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-06 01:54:55 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-06 01:54:55 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-06 01:54:55 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-06 01:54:55 (10394) [INFO] yum --disablerepo= ... * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-06 01:54:55 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-06 01:54:55 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] yum-config-manager --disable * 2025-09-06 01:54:55 (10394) [INFO] or * 2025-09-06 01:54:55 (10394) [INFO] subscription-manager repos --disable= * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-06 01:54:55 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-06 01:54:55 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-06 01:54:55 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-06 01:54:55 (10394) [INFO] compromise: * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-06 01:54:55 (10394) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-06 01:54:55 (10411) [INFO] * 2025-09-06 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-06 01:54:55 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-06 01:54:55 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-06 01:54:55 (10381) [INFO] * 2025-09-06 01:54:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 01:54:56 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-06 01:54:56 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-06 01:54:56 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-06 01:54:56 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-06 01:54:56 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-06 01:54:56 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-06 01:54:56 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-06 01:54:56 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-06 01:54:56 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-06 01:54:56 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-06 01:54:56 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-06 01:54:56 (10411) [INFO] * 2025-09-06 01:54:56 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-06 01:54:56 (10381) [INFO] * 2025-09-06 01:54:56 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 01:54:56 (10394) [INFO] Determining fastest mirrors * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-06 01:55:28 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-06 01:55:28 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-06 01:55:28 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-06 01:55:28 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-06 01:55:28 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-06 01:55:28 (10394) [INFO] yum --disablerepo= ... * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-06 01:55:28 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-06 01:55:28 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] yum-config-manager --disable * 2025-09-06 01:55:28 (10394) [INFO] or * 2025-09-06 01:55:28 (10394) [INFO] subscription-manager repos --disable= * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-06 01:55:28 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-06 01:55:28 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-06 01:55:28 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-06 01:55:28 (10394) [INFO] compromise: * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-06 01:55:28 (10394) [INFO] * 2025-09-06 01:55:28 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-06 01:55:28 (10411) [INFO] * 2025-09-06 01:55:28 (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 01:55:28 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-06 01:55:29 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-06 01:55:29 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-06 01:55:29 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-06 01:55:29 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-06 01:55:29 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-06 01:55:34 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5JpZ93Sz9j/ea_profile.json * 2025-09-06 01:58:09 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5JpZ93Sz9j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-06 01:58:09 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-07 01:44:35 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-07 01:48:36 (11467) [INFO] Script is up to date. * 2025-09-07 01:52:38 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-07 01:52:38 (10381) [INFO] * 2025-09-07 01:53:35 (10411) [INFO] * 2025-09-07 01:53:35 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-07 01:53:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-07 01:53:36 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-07 01:53:36 (10381) [INFO] * 2025-09-07 01:53:38 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-07 01:53:38 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-07 01:53:38 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-07 01:53:38 (10381) [INFO] * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-07 01:54:13 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-07 01:54:13 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-07 01:54:13 (10381) [INFO] * 2025-09-07 01:54:13 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 01:54:13 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-07 01:54:45 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-07 01:54:45 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-07 01:54:45 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-07 01:54:45 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-07 01:54:45 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-07 01:54:45 (10394) [INFO] yum --disablerepo= ... * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-07 01:54:45 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-07 01:54:45 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] yum-config-manager --disable * 2025-09-07 01:54:45 (10394) [INFO] or * 2025-09-07 01:54:45 (10394) [INFO] subscription-manager repos --disable= * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-07 01:54:45 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-07 01:54:45 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-07 01:54:45 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-07 01:54:45 (10394) [INFO] compromise: * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-07 01:54:45 (10394) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-07 01:54:45 (10411) [INFO] * 2025-09-07 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-07 01:54:45 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-07 01:54:45 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-07 01:54:45 (10381) [INFO] * 2025-09-07 01:54:45 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 01:54:46 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-07 01:54:46 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-07 01:54:46 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-07 01:54:46 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-07 01:54:46 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-07 01:54:46 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-07 01:54:46 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-07 01:54:46 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-07 01:54:46 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-07 01:54:46 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-07 01:54:46 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-07 01:54:46 (10411) [INFO] * 2025-09-07 01:54:46 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-07 01:54:46 (10381) [INFO] * 2025-09-07 01:54:46 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 01:54:47 (10394) [INFO] Determining fastest mirrors * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-07 01:55:18 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-07 01:55:18 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-07 01:55:18 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-07 01:55:18 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-07 01:55:18 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-07 01:55:18 (10394) [INFO] yum --disablerepo= ... * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-07 01:55:18 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-07 01:55:18 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] yum-config-manager --disable * 2025-09-07 01:55:18 (10394) [INFO] or * 2025-09-07 01:55:18 (10394) [INFO] subscription-manager repos --disable= * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-07 01:55:18 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-07 01:55:18 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-07 01:55:18 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-07 01:55:18 (10394) [INFO] compromise: * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-07 01:55:18 (10394) [INFO] * 2025-09-07 01:55:18 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-07 01:55:18 (10411) [INFO] * 2025-09-07 01:55:18 (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 01:55:18 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-07 01:55:19 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-07 01:55:19 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-07 01:55:19 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-07 01:55:19 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-07 01:55:19 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-07 01:55:26 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kIGpRoBigF/ea_profile.json * 2025-09-07 01:58:56 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kIGpRoBigF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-07 01:58:56 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-08 01:43:55 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-08 01:47:55 (11467) [INFO] Script is up to date. * 2025-09-08 01:51:58 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-08 01:51:58 (10381) [INFO] * 2025-09-08 01:53:08 (10411) [INFO] * 2025-09-08 01:53:08 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-08 01:53:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-08 01:53:08 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-08 01:53:08 (10381) [INFO] * 2025-09-08 01:53:13 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-08 01:53:13 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-08 01:53:13 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-08 01:53:13 (10381) [INFO] * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-08 01:53:47 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-08 01:53:47 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-08 01:53:47 (10381) [INFO] * 2025-09-08 01:53:48 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 01:53:48 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-08 01:54:18 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-08 01:54:18 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-08 01:54:18 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-08 01:54:18 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-08 01:54:18 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-08 01:54:18 (10394) [INFO] yum --disablerepo= ... * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-08 01:54:18 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-08 01:54:18 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] yum-config-manager --disable * 2025-09-08 01:54:18 (10394) [INFO] or * 2025-09-08 01:54:18 (10394) [INFO] subscription-manager repos --disable= * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-08 01:54:18 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-08 01:54:18 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-08 01:54:18 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-08 01:54:18 (10394) [INFO] compromise: * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-08 01:54:18 (10394) [INFO] * 2025-09-08 01:54:18 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-08 01:54:18 (10411) [INFO] * 2025-09-08 01:54:18 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-08 01:54:18 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-08 01:54:18 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-08 01:54:18 (10381) [INFO] * 2025-09-08 01:54:19 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 01:54:19 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-08 01:54:19 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-08 01:54:19 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-08 01:54:19 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-08 01:54:19 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-08 01:54:19 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-08 01:54:19 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-08 01:54:19 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-08 01:54:19 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-08 01:54:19 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-08 01:54:19 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-08 01:54:19 (10411) [INFO] * 2025-09-08 01:54:19 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-08 01:54:19 (10381) [INFO] * 2025-09-08 01:54:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 01:54:20 (10394) [INFO] Determining fastest mirrors * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-08 01:54:50 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-08 01:54:50 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-08 01:54:50 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-08 01:54:50 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-08 01:54:50 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-08 01:54:50 (10394) [INFO] yum --disablerepo= ... * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-08 01:54:50 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-08 01:54:50 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] yum-config-manager --disable * 2025-09-08 01:54:50 (10394) [INFO] or * 2025-09-08 01:54:50 (10394) [INFO] subscription-manager repos --disable= * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-08 01:54:50 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-08 01:54:50 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-08 01:54:50 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-08 01:54:50 (10394) [INFO] compromise: * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-08 01:54:50 (10394) [INFO] * 2025-09-08 01:54:50 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-08 01:54:50 (10411) [INFO] * 2025-09-08 01:54: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-08 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-08 01:54:52 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-08 01:54:52 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-08 01:54:52 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-08 01:54:52 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-08 01:54:52 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-08 01:54:59 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jEkI9JX62A/ea_profile.json * 2025-09-08 01:57:27 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jEkI9JX62A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-08 01:57:27 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-09 01:44:00 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-09 01:48:01 (11467) [INFO] Script is up to date. * 2025-09-09 01:52:04 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-09 01:52:04 (10381) [INFO] * 2025-09-09 01:53:27 (10411) [INFO] * 2025-09-09 01:53:27 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-09 01:53:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-09 01:53:28 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-09 01:53:28 (10381) [INFO] * 2025-09-09 01:53:31 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-09 01:53:31 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-09 01:53:31 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-09 01:53:31 (10381) [INFO] * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-09 01:54:05 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-09 01:54:05 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-09 01:54:05 (10381) [INFO] * 2025-09-09 01:54:06 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 01:54:06 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-09 01:54:37 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-09 01:54:37 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-09 01:54:37 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-09 01:54:37 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-09 01:54:37 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-09 01:54:37 (10394) [INFO] yum --disablerepo= ... * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-09 01:54:37 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-09 01:54:37 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] yum-config-manager --disable * 2025-09-09 01:54:37 (10394) [INFO] or * 2025-09-09 01:54:37 (10394) [INFO] subscription-manager repos --disable= * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-09 01:54:37 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-09 01:54:37 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-09 01:54:37 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-09 01:54:37 (10394) [INFO] compromise: * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-09 01:54:37 (10394) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-09 01:54:37 (10411) [INFO] * 2025-09-09 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-09 01:54:37 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-09 01:54:37 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-09 01:54:37 (10381) [INFO] * 2025-09-09 01:54:37 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 01:54:38 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-09 01:54:38 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-09 01:54:38 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-09 01:54:38 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-09 01:54:38 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-09 01:54:38 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-09 01:54:38 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-09 01:54:38 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-09 01:54:38 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-09 01:54:38 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-09 01:54:38 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-09 01:54:38 (10411) [INFO] * 2025-09-09 01:54:38 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-09 01:54:38 (10381) [INFO] * 2025-09-09 01:54:38 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 01:54:39 (10394) [INFO] Determining fastest mirrors * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-09 01:55:10 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-09 01:55:10 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-09 01:55:10 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-09 01:55:10 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-09 01:55:10 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-09 01:55:10 (10394) [INFO] yum --disablerepo= ... * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-09 01:55:10 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-09 01:55:10 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] yum-config-manager --disable * 2025-09-09 01:55:10 (10394) [INFO] or * 2025-09-09 01:55:10 (10394) [INFO] subscription-manager repos --disable= * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-09 01:55:10 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-09 01:55:10 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-09 01:55:10 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-09 01:55:10 (10394) [INFO] compromise: * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-09 01:55:10 (10394) [INFO] * 2025-09-09 01:55:10 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-09 01:55:10 (10411) [INFO] * 2025-09-09 01:55:10 (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 01:55:10 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-09 01:55:12 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-09 01:55:12 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-09 01:55:12 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-09 01:55:12 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-09 01:55:12 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-09 01:55:17 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/FZ01WpFdC8/ea_profile.json * 2025-09-09 01:58:46 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/FZ01WpFdC8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-09 01:58:46 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-10 01:51:14 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-10 01:55:14 (11467) [INFO] Script is up to date. * 2025-09-10 01:59:17 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-10 01:59:17 (10381) [INFO] * 2025-09-10 02:00:38 (10411) [INFO] * 2025-09-10 02:00:38 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-10 02:00:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-10 02:00:39 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-10 02:00:39 (10381) [INFO] * 2025-09-10 02:00:43 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-10 02:00:43 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-10 02:00:43 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-10 02:00:43 (10381) [INFO] * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-10 02:01:20 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-10 02:01:20 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-10 02:01:20 (10381) [INFO] * 2025-09-10 02:01:21 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 02:01:21 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-10 02:01:52 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-10 02:01:52 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-10 02:01:52 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-10 02:01:52 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-10 02:01:52 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-10 02:01:52 (10394) [INFO] yum --disablerepo= ... * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-10 02:01:52 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-10 02:01:52 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] yum-config-manager --disable * 2025-09-10 02:01:52 (10394) [INFO] or * 2025-09-10 02:01:52 (10394) [INFO] subscription-manager repos --disable= * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-10 02:01:52 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-10 02:01:52 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-10 02:01:52 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-10 02:01:52 (10394) [INFO] compromise: * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-10 02:01:52 (10394) [INFO] * 2025-09-10 02:01:52 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-10 02:01:52 (10411) [INFO] * 2025-09-10 02:01:52 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-10 02:01:52 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-10 02:01:52 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-10 02:01:52 (10381) [INFO] * 2025-09-10 02:01:53 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 02:01:53 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-10 02:01:53 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-10 02:01:53 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-10 02:01:53 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-10 02:01:53 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-10 02:01:53 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-10 02:01:53 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-10 02:01:53 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-10 02:01:53 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-10 02:01:53 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-10 02:01:53 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-10 02:01:53 (10411) [INFO] * 2025-09-10 02:01:53 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-10 02:01:53 (10381) [INFO] * 2025-09-10 02:01:53 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 02:01:54 (10394) [INFO] Determining fastest mirrors * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-10 02:02:25 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-10 02:02:25 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-10 02:02:25 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-10 02:02:25 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-10 02:02:25 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-10 02:02:25 (10394) [INFO] yum --disablerepo= ... * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-10 02:02:25 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-10 02:02:25 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] yum-config-manager --disable * 2025-09-10 02:02:25 (10394) [INFO] or * 2025-09-10 02:02:25 (10394) [INFO] subscription-manager repos --disable= * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-10 02:02:25 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-10 02:02:25 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-10 02:02:25 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-10 02:02:25 (10394) [INFO] compromise: * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-10 02:02:25 (10394) [INFO] * 2025-09-10 02:02:25 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-10 02:02:25 (10411) [INFO] * 2025-09-10 02:02: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-10 02:02: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-10 02:02:26 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-10 02:02:26 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-10 02:02:26 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-10 02:02:26 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-10 02:02:26 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-10 02:02:33 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iZ2eW6cqZq/ea_profile.json * 2025-09-10 02:05:02 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iZ2eW6cqZq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-10 02:05:02 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-11 01:54:51 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-11 01:58:52 (11467) [INFO] Script is up to date. * 2025-09-11 02:02:55 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-11 02:02:55 (10381) [INFO] * 2025-09-11 02:04:12 (10411) [INFO] * 2025-09-11 02:04:12 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-11 02:04:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-11 02:04:14 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-11 02:04:14 (10381) [INFO] * 2025-09-11 02:04:17 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-11 02:04:17 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-11 02:04:17 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-11 02:04:17 (10381) [INFO] * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-11 02:04:54 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-11 02:04:54 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-11 02:04:54 (10381) [INFO] * 2025-09-11 02:04:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 02:04:55 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-11 02:05:27 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-11 02:05:27 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-11 02:05:27 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-11 02:05:27 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-11 02:05:27 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-11 02:05:27 (10394) [INFO] yum --disablerepo= ... * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-11 02:05:27 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-11 02:05:27 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] yum-config-manager --disable * 2025-09-11 02:05:27 (10394) [INFO] or * 2025-09-11 02:05:27 (10394) [INFO] subscription-manager repos --disable= * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-11 02:05:27 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-11 02:05:27 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-11 02:05:27 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-11 02:05:27 (10394) [INFO] compromise: * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-11 02:05:27 (10394) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-11 02:05:27 (10411) [INFO] * 2025-09-11 02:05:27 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-11 02:05:27 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-11 02:05:27 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-11 02:05:27 (10381) [INFO] * 2025-09-11 02:05:27 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 02:05:28 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-11 02:05:28 (10394) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-11 02:05:28 (10394) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-11 02:05:28 (10394) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-11 02:05:28 (10394) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-11 02:05:28 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-11 02:05:28 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-11 02:05:28 (10394) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-11 02:05:28 (10394) [INFO] : wp-toolkit-thirdparties * 2025-09-11 02:05:28 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-11 02:05:28 (10394) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-11 02:05:28 (10411) [INFO] * 2025-09-11 02:05:28 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-11 02:05:28 (10381) [INFO] * 2025-09-11 02:05:28 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 02:05:29 (10394) [INFO] Determining fastest mirrors * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-11 02:06:00 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-11 02:06:00 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-11 02:06:00 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-11 02:06:00 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-11 02:06:00 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-11 02:06:00 (10394) [INFO] yum --disablerepo= ... * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-11 02:06:00 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-11 02:06:00 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] yum-config-manager --disable * 2025-09-11 02:06:00 (10394) [INFO] or * 2025-09-11 02:06:00 (10394) [INFO] subscription-manager repos --disable= * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-11 02:06:00 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-11 02:06:00 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-11 02:06:00 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-11 02:06:00 (10394) [INFO] compromise: * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-11 02:06:00 (10394) [INFO] * 2025-09-11 02:06:00 (10394) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-11 02:06:00 (10411) [INFO] * 2025-09-11 02:06:00 (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 02:06:00 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-11 02:06:02 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-11 02:06:02 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-11 02:06:02 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-11 02:06:02 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-11 02:06:02 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-11 02:06:09 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ozU0ufLjmq/ea_profile.json * 2025-09-11 02:08:39 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ozU0ufLjmq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-11 02:08:39 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-12 01:42:50 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-12 01:46:51 (11450) [INFO] Newer version of script found. Downloading. * 2025-09-12 01:50:52 (11459) [INFO] Script update to version 71 successful. * 2025-09-12 01:54:55 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-12 01:54:55 (10379) [INFO] * 2025-09-12 01:56:13 (10409) [INFO] * 2025-09-12 01:56:13 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-12 01:56:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-12 01:56:13 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-12 01:56:13 (10379) [INFO] * 2025-09-12 01:56:16 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-12 01:56:16 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-12 01:56:16 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-12 01:56:16 (10379) [INFO] * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-12 01:56:51 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-12 01:56:51 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-12 01:56:51 (10379) [INFO] * 2025-09-12 01:56:51 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 01:56:51 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-12 01:57:22 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-12 01:57:22 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-12 01:57:22 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-12 01:57:22 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-12 01:57:22 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-12 01:57:22 (10392) [INFO] yum --disablerepo= ... * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-12 01:57:22 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-12 01:57:22 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] yum-config-manager --disable * 2025-09-12 01:57:22 (10392) [INFO] or * 2025-09-12 01:57:22 (10392) [INFO] subscription-manager repos --disable= * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-12 01:57:22 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-12 01:57:22 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-12 01:57:22 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-12 01:57:22 (10392) [INFO] compromise: * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-12 01:57:22 (10392) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-12 01:57:22 (10409) [INFO] * 2025-09-12 01:57:22 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-12 01:57:22 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-12 01:57:22 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-12 01:57:22 (10379) [INFO] * 2025-09-12 01:57:22 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 01:57:23 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-12 01:57:23 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-12 01:57:23 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-12 01:57:23 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-12 01:57:23 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-12 01:57:23 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-12 01:57:23 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-12 01:57:23 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-12 01:57:23 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-12 01:57:23 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-12 01:57:23 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-12 01:57:23 (10409) [INFO] * 2025-09-12 01:57:23 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-12 01:57:23 (10379) [INFO] * 2025-09-12 01:57:23 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 01:57:23 (10392) [INFO] Determining fastest mirrors * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-12 01:57:54 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-12 01:57:54 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-12 01:57:54 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-12 01:57:54 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-12 01:57:54 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-12 01:57:54 (10392) [INFO] yum --disablerepo= ... * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-12 01:57:54 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-12 01:57:54 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] yum-config-manager --disable * 2025-09-12 01:57:54 (10392) [INFO] or * 2025-09-12 01:57:54 (10392) [INFO] subscription-manager repos --disable= * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-12 01:57:54 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-12 01:57:54 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-12 01:57:54 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-12 01:57:54 (10392) [INFO] compromise: * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-12 01:57:54 (10392) [INFO] * 2025-09-12 01:57:54 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-12 01:57:54 (10409) [INFO] * 2025-09-12 01:57:54 (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 01:57:54 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-12 01:57:56 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-12 01:57:56 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-12 01:57:56 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-12 01:57:56 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-12 01:57:56 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-12 01:58:02 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ClkHlOEN9t/ea_profile.json * 2025-09-12 02:00:59 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ClkHlOEN9t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-12 02:00:59 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-13 01:48:49 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-13 01:52:49 (11465) [INFO] Script is up to date. * 2025-09-13 01:56:52 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-13 01:56:52 (10379) [INFO] * 2025-09-13 01:57:50 (10409) [INFO] * 2025-09-13 01:57:50 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-13 01:57:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-13 01:57:51 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-13 01:57:51 (10379) [INFO] * 2025-09-13 01:57:55 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-13 01:57:55 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-13 01:57:55 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-13 01:57:55 (10379) [INFO] * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-13 01:58:30 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-13 01:58:30 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-13 01:58:30 (10379) [INFO] * 2025-09-13 01:58:30 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 01:58:31 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-13 01:59:02 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-13 01:59:02 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-13 01:59:02 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-13 01:59:02 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-13 01:59:02 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-13 01:59:02 (10392) [INFO] yum --disablerepo= ... * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-13 01:59:02 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-13 01:59:02 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] yum-config-manager --disable * 2025-09-13 01:59:02 (10392) [INFO] or * 2025-09-13 01:59:02 (10392) [INFO] subscription-manager repos --disable= * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-13 01:59:02 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-13 01:59:02 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-13 01:59:02 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-13 01:59:02 (10392) [INFO] compromise: * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-13 01:59:02 (10392) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-13 01:59:02 (10409) [INFO] * 2025-09-13 01:59:02 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-13 01:59:02 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-13 01:59:02 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-13 01:59:02 (10379) [INFO] * 2025-09-13 01:59:02 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 01:59:03 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-13 01:59:03 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-13 01:59:03 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-13 01:59:03 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-13 01:59:03 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-13 01:59:03 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-13 01:59:03 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-13 01:59:03 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-13 01:59:03 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-13 01:59:03 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-13 01:59:03 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-13 01:59:03 (10409) [INFO] * 2025-09-13 01:59:03 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-13 01:59:03 (10379) [INFO] * 2025-09-13 01:59:03 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 01:59:03 (10392) [INFO] Determining fastest mirrors * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-13 01:59:34 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-13 01:59:34 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-13 01:59:34 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-13 01:59:34 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-13 01:59:34 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-13 01:59:34 (10392) [INFO] yum --disablerepo= ... * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-13 01:59:34 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-13 01:59:34 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] yum-config-manager --disable * 2025-09-13 01:59:34 (10392) [INFO] or * 2025-09-13 01:59:34 (10392) [INFO] subscription-manager repos --disable= * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-13 01:59:34 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-13 01:59:34 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-13 01:59:34 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-13 01:59:34 (10392) [INFO] compromise: * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-13 01:59:34 (10392) [INFO] * 2025-09-13 01:59:34 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-13 01:59:35 (10409) [INFO] * 2025-09-13 01:59: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-13 01:59: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-13 01:59:36 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-13 01:59:36 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-13 01:59:36 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-13 01:59:36 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-13 01:59:36 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-13 01:59:42 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IFH5prgC9R/ea_profile.json * 2025-09-13 02:02:42 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/IFH5prgC9R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-13 02:02:42 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-14 01:44:10 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-14 01:48:10 (11465) [INFO] Script is up to date. * 2025-09-14 01:52:13 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-14 01:52:13 (10379) [INFO] * 2025-09-14 01:53:08 (10409) [INFO] * 2025-09-14 01:53:08 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-14 01:53:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-14 01:53:08 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-14 01:53:08 (10379) [INFO] * 2025-09-14 01:53:11 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-14 01:53:11 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-14 01:53:11 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-14 01:53:11 (10379) [INFO] * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-14 01:53:46 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-14 01:53:46 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-14 01:53:46 (10379) [INFO] * 2025-09-14 01:53:46 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 01:53:47 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-14 01:54:18 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-14 01:54:18 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-14 01:54:18 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-14 01:54:18 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-14 01:54:18 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-14 01:54:18 (10392) [INFO] yum --disablerepo= ... * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-14 01:54:18 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-14 01:54:18 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] yum-config-manager --disable * 2025-09-14 01:54:18 (10392) [INFO] or * 2025-09-14 01:54:18 (10392) [INFO] subscription-manager repos --disable= * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-14 01:54:18 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-14 01:54:18 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-14 01:54:18 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-14 01:54:18 (10392) [INFO] compromise: * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-14 01:54:18 (10392) [INFO] * 2025-09-14 01:54:18 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-14 01:54:18 (10409) [INFO] * 2025-09-14 01:54:18 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-14 01:54:18 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-14 01:54:18 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-14 01:54:18 (10379) [INFO] * 2025-09-14 01:54:19 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 01:54:19 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-14 01:54:19 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-14 01:54:19 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-14 01:54:19 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-14 01:54:19 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-14 01:54:19 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-14 01:54:19 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-14 01:54:19 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-14 01:54:19 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-14 01:54:19 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-14 01:54:19 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-14 01:54:19 (10409) [INFO] * 2025-09-14 01:54:19 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-14 01:54:19 (10379) [INFO] * 2025-09-14 01:54:20 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 01:54:20 (10392) [INFO] Determining fastest mirrors * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-14 01:54:51 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-14 01:54:51 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-14 01:54:51 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-14 01:54:51 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-14 01:54:51 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-14 01:54:51 (10392) [INFO] yum --disablerepo= ... * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-14 01:54:51 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-14 01:54:51 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] yum-config-manager --disable * 2025-09-14 01:54:51 (10392) [INFO] or * 2025-09-14 01:54:51 (10392) [INFO] subscription-manager repos --disable= * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-14 01:54:51 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-14 01:54:51 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-14 01:54:51 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-14 01:54:51 (10392) [INFO] compromise: * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-14 01:54:51 (10392) [INFO] * 2025-09-14 01:54:51 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-14 01:54:51 (10409) [INFO] * 2025-09-14 01:54:51 (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 01:54:51 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-14 01:54:52 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-14 01:54:52 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-14 01:54:52 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-14 01:54:52 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-14 01:54:52 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-14 01:54:59 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oC76sSnyAY/ea_profile.json * 2025-09-14 01:57:57 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oC76sSnyAY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-14 01:57:57 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-15 01:43:25 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-15 01:47:25 (11465) [INFO] Script is up to date. * 2025-09-15 01:51:28 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-15 01:51:28 (10379) [INFO] * 2025-09-15 01:52:43 (10409) [INFO] * 2025-09-15 01:52:43 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-15 01:52:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-15 01:52:43 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-15 01:52:43 (10379) [INFO] * 2025-09-15 01:52:47 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-15 01:52:47 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-15 01:52:47 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-15 01:52:47 (10379) [INFO] * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-15 01:53:22 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-15 01:53:22 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-15 01:53:22 (10379) [INFO] * 2025-09-15 01:53:23 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 01:53:23 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-15 01:53:55 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-15 01:53:55 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-15 01:53:55 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-15 01:53:55 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-15 01:53:55 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-15 01:53:55 (10392) [INFO] yum --disablerepo= ... * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-15 01:53:55 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-15 01:53:55 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] yum-config-manager --disable * 2025-09-15 01:53:55 (10392) [INFO] or * 2025-09-15 01:53:55 (10392) [INFO] subscription-manager repos --disable= * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-15 01:53:55 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-15 01:53:55 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-15 01:53:55 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-15 01:53:55 (10392) [INFO] compromise: * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-15 01:53:55 (10392) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-15 01:53:55 (10409) [INFO] * 2025-09-15 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-15 01:53:55 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-15 01:53:55 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-15 01:53:55 (10379) [INFO] * 2025-09-15 01:53:55 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 01:53:55 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-15 01:53:55 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-15 01:53:55 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-15 01:53:55 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-15 01:53:55 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-15 01:53:55 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-15 01:53:55 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-15 01:53:55 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-15 01:53:55 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-15 01:53:55 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-15 01:53:55 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-15 01:53:55 (10409) [INFO] * 2025-09-15 01:53:55 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-15 01:53:55 (10379) [INFO] * 2025-09-15 01:53:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 01:53:56 (10392) [INFO] Determining fastest mirrors * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-15 01:54:27 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-15 01:54:27 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-15 01:54:27 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-15 01:54:27 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-15 01:54:27 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-15 01:54:27 (10392) [INFO] yum --disablerepo= ... * 2025-09-15 01:54:27 (10392) [INFO] * 2025-09-15 01:54:27 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-15 01:54:28 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-15 01:54:28 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-15 01:54:28 (10392) [INFO] * 2025-09-15 01:54:28 (10392) [INFO] yum-config-manager --disable * 2025-09-15 01:54:28 (10392) [INFO] or * 2025-09-15 01:54:28 (10392) [INFO] subscription-manager repos --disable= * 2025-09-15 01:54:28 (10392) [INFO] * 2025-09-15 01:54:28 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-15 01:54:28 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-15 01:54:28 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-15 01:54:28 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-15 01:54:28 (10392) [INFO] compromise: * 2025-09-15 01:54:28 (10392) [INFO] * 2025-09-15 01:54:28 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-15 01:54:28 (10392) [INFO] * 2025-09-15 01:54:28 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-15 01:54:28 (10409) [INFO] * 2025-09-15 01:54:28 (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 01:54:28 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-15 01:54:29 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-15 01:54:29 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-15 01:54:29 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-15 01:54:29 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-15 01:54:29 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-15 01:54:35 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_ke5DJQdcJ/ea_profile.json * 2025-09-15 01:57:33 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_ke5DJQdcJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-15 01:57:33 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-16 01:42:58 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-16 01:46:58 (11465) [INFO] Script is up to date. * 2025-09-16 01:51:01 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-16 01:51:01 (10379) [INFO] * 2025-09-16 01:52:19 (10409) [INFO] * 2025-09-16 01:52:19 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-16 01:52:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-16 01:52:19 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-16 01:52:19 (10379) [INFO] * 2025-09-16 01:52:22 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-16 01:52:22 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-16 01:52:22 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-16 01:52:22 (10379) [INFO] * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-16 01:52:59 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-16 01:52:59 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-16 01:52:59 (10379) [INFO] * 2025-09-16 01:52:59 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 01:53:00 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-16 01:53:30 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-16 01:53:30 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-16 01:53:30 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-16 01:53:30 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-16 01:53:30 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-16 01:53:30 (10392) [INFO] yum --disablerepo= ... * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-16 01:53:30 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-16 01:53:30 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] yum-config-manager --disable * 2025-09-16 01:53:30 (10392) [INFO] or * 2025-09-16 01:53:30 (10392) [INFO] subscription-manager repos --disable= * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-16 01:53:30 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-16 01:53:30 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-16 01:53:30 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-16 01:53:30 (10392) [INFO] compromise: * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-16 01:53:30 (10392) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-16 01:53:30 (10409) [INFO] * 2025-09-16 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-16 01:53:30 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-16 01:53:30 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-16 01:53:30 (10379) [INFO] * 2025-09-16 01:53:30 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 01:53:31 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-16 01:53:31 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-16 01:53:31 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-16 01:53:31 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-16 01:53:31 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-16 01:53:31 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-16 01:53:31 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-16 01:53:31 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-16 01:53:31 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-16 01:53:31 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-16 01:53:31 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-16 01:53:31 (10409) [INFO] * 2025-09-16 01:53:31 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-16 01:53:31 (10379) [INFO] * 2025-09-16 01:53:31 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 01:53:31 (10392) [INFO] Determining fastest mirrors * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-16 01:54:02 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-16 01:54:02 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-16 01:54:02 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-16 01:54:02 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-16 01:54:02 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-16 01:54:02 (10392) [INFO] yum --disablerepo= ... * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-16 01:54:02 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-16 01:54:02 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] yum-config-manager --disable * 2025-09-16 01:54:02 (10392) [INFO] or * 2025-09-16 01:54:02 (10392) [INFO] subscription-manager repos --disable= * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-16 01:54:02 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-16 01:54:02 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-16 01:54:02 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-16 01:54:02 (10392) [INFO] compromise: * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-16 01:54:02 (10392) [INFO] * 2025-09-16 01:54:02 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-16 01:54:02 (10409) [INFO] * 2025-09-16 01:54:02 (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 01:54:02 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-16 01:54:03 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-16 01:54:03 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-16 01:54:03 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-16 01:54:03 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-16 01:54:03 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-16 01:54:10 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9bK8vifzJI/ea_profile.json * 2025-09-16 01:56:15 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9bK8vifzJI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-16 01:56:15 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-17 01:47:30 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-17 01:51:30 (11465) [INFO] Script is up to date. * 2025-09-17 01:55:33 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-17 01:55:33 (10379) [INFO] * 2025-09-17 01:56:50 (10409) [INFO] * 2025-09-17 01:56:50 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-17 01:56:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-17 01:56:50 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-17 01:56:50 (10379) [INFO] * 2025-09-17 01:56:54 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-17 01:56:54 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-17 01:56:54 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-17 01:56:54 (10379) [INFO] * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-17 01:57:28 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-17 01:57:28 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-17 01:57:28 (10379) [INFO] * 2025-09-17 01:57:28 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 01:57:28 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-17 01:58:00 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-17 01:58:00 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-17 01:58:00 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-17 01:58:00 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-17 01:58:00 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-17 01:58:00 (10392) [INFO] yum --disablerepo= ... * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-17 01:58:00 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-17 01:58:00 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] yum-config-manager --disable * 2025-09-17 01:58:00 (10392) [INFO] or * 2025-09-17 01:58:00 (10392) [INFO] subscription-manager repos --disable= * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-17 01:58:00 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-17 01:58:00 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-17 01:58:00 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-17 01:58:00 (10392) [INFO] compromise: * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-17 01:58:00 (10392) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-17 01:58:00 (10409) [INFO] * 2025-09-17 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-17 01:58:00 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-17 01:58:00 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-17 01:58:00 (10379) [INFO] * 2025-09-17 01:58:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 01:58:01 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-17 01:58:01 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-17 01:58:01 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-17 01:58:01 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-17 01:58:01 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-17 01:58:01 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-17 01:58:01 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-17 01:58:01 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-17 01:58:01 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-17 01:58:01 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-17 01:58:01 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-17 01:58:01 (10409) [INFO] * 2025-09-17 01:58:01 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-17 01:58:01 (10379) [INFO] * 2025-09-17 01:58:02 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 01:58:02 (10392) [INFO] Determining fastest mirrors * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-17 01:58:33 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-17 01:58:33 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-17 01:58:33 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-17 01:58:33 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-17 01:58:33 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-17 01:58:33 (10392) [INFO] yum --disablerepo= ... * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-17 01:58:33 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-17 01:58:33 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] yum-config-manager --disable * 2025-09-17 01:58:33 (10392) [INFO] or * 2025-09-17 01:58:33 (10392) [INFO] subscription-manager repos --disable= * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-17 01:58:33 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-17 01:58:33 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-17 01:58:33 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-17 01:58:33 (10392) [INFO] compromise: * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-17 01:58:33 (10392) [INFO] * 2025-09-17 01:58:33 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-17 01:58:33 (10409) [INFO] * 2025-09-17 01:58:33 (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 01:58:33 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-17 01:58:35 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-17 01:58:35 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-17 01:58:35 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-17 01:58:35 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-17 01:58:35 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-17 01:58:41 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gXCSQ8a2oJ/ea_profile.json * 2025-09-17 02:01:09 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gXCSQ8a2oJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-17 02:01:09 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-18 01:49:55 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-18 01:53:55 (11465) [INFO] Script is up to date. * 2025-09-18 01:57:59 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-18 01:57:59 (10379) [INFO] * 2025-09-18 01:59:21 (10409) [INFO] * 2025-09-18 01:59:21 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-18 01:59:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-18 01:59:21 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-18 01:59:21 (10379) [INFO] * 2025-09-18 01:59:24 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-18 01:59:24 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-18 01:59:24 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-18 01:59:24 (10379) [INFO] * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-18 01:59:59 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-18 01:59:59 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-18 01:59:59 (10379) [INFO] * 2025-09-18 01:59:59 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 01:59:59 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-18 02:00:31 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-18 02:00:31 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-18 02:00:31 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-18 02:00:31 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-18 02:00:31 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-18 02:00:31 (10392) [INFO] yum --disablerepo= ... * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-18 02:00:31 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-18 02:00:31 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] yum-config-manager --disable * 2025-09-18 02:00:31 (10392) [INFO] or * 2025-09-18 02:00:31 (10392) [INFO] subscription-manager repos --disable= * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-18 02:00:31 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-18 02:00:31 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-18 02:00:31 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-18 02:00:31 (10392) [INFO] compromise: * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-18 02:00:31 (10392) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-18 02:00:31 (10409) [INFO] * 2025-09-18 02:00:31 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-18 02:00:31 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-18 02:00:31 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-18 02:00:31 (10379) [INFO] * 2025-09-18 02:00:31 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 02:00:32 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-18 02:00:32 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-18 02:00:32 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-18 02:00:32 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-18 02:00:32 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-18 02:00:32 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-18 02:00:32 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-18 02:00:32 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-18 02:00:32 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-18 02:00:32 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-18 02:00:32 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-18 02:00:32 (10409) [INFO] * 2025-09-18 02:00:32 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-18 02:00:32 (10379) [INFO] * 2025-09-18 02:00:32 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 02:00:32 (10392) [INFO] Determining fastest mirrors * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-18 02:01:04 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-18 02:01:04 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-18 02:01:04 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-18 02:01:04 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-18 02:01:04 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-18 02:01:04 (10392) [INFO] yum --disablerepo= ... * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-18 02:01:04 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-18 02:01:04 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] yum-config-manager --disable * 2025-09-18 02:01:04 (10392) [INFO] or * 2025-09-18 02:01:04 (10392) [INFO] subscription-manager repos --disable= * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-18 02:01:04 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-18 02:01:04 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-18 02:01:04 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-18 02:01:04 (10392) [INFO] compromise: * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-18 02:01:04 (10392) [INFO] * 2025-09-18 02:01:04 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-18 02:01:04 (10409) [INFO] * 2025-09-18 02:01:04 (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 02:01:04 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-18 02:01:05 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-18 02:01:05 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-18 02:01:05 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-18 02:01:05 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-18 02:01:05 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-18 02:01:12 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rO4A6LHGy8/ea_profile.json * 2025-09-18 02:04:09 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rO4A6LHGy8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-18 02:04:09 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-19 01:48:11 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-19 01:52:11 (11465) [INFO] Script is up to date. * 2025-09-19 01:56:14 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-19 01:56:14 (10379) [INFO] * 2025-09-19 01:57:28 (10409) [INFO] * 2025-09-19 01:57:28 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-19 01:57:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-19 01:57:29 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-19 01:57:29 (10379) [INFO] * 2025-09-19 01:57:32 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-19 01:57:32 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-19 01:57:32 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-19 01:57:32 (10379) [INFO] * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-19 01:58:07 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-19 01:58:07 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-19 01:58:07 (10379) [INFO] * 2025-09-19 01:58:07 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 01:58:07 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-19 01:58:38 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-19 01:58:38 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-19 01:58:38 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-19 01:58:38 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-19 01:58:38 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-19 01:58:38 (10392) [INFO] yum --disablerepo= ... * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-19 01:58:38 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-19 01:58:38 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] yum-config-manager --disable * 2025-09-19 01:58:38 (10392) [INFO] or * 2025-09-19 01:58:38 (10392) [INFO] subscription-manager repos --disable= * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-19 01:58:38 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-19 01:58:38 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-19 01:58:38 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-19 01:58:38 (10392) [INFO] compromise: * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-19 01:58:38 (10392) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-19 01:58:38 (10409) [INFO] * 2025-09-19 01:58:38 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-19 01:58:38 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-19 01:58:38 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-19 01:58:38 (10379) [INFO] * 2025-09-19 01:58:38 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 01:58:38 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-19 01:58:38 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-19 01:58:38 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-19 01:58:38 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-19 01:58:38 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-19 01:58:38 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-19 01:58:38 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-19 01:58:38 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-19 01:58:38 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-19 01:58:38 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-19 01:58:38 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-19 01:58:39 (10409) [INFO] * 2025-09-19 01:58:39 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-19 01:58:39 (10379) [INFO] * 2025-09-19 01:58:39 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 01:58:39 (10392) [INFO] Determining fastest mirrors * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-19 01:59:11 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-19 01:59:11 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-19 01:59:11 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-19 01:59:11 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-19 01:59:11 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-19 01:59:11 (10392) [INFO] yum --disablerepo= ... * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-19 01:59:11 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-19 01:59:11 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] yum-config-manager --disable * 2025-09-19 01:59:11 (10392) [INFO] or * 2025-09-19 01:59:11 (10392) [INFO] subscription-manager repos --disable= * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-19 01:59:11 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-19 01:59:11 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-19 01:59:11 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-19 01:59:11 (10392) [INFO] compromise: * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-19 01:59:11 (10392) [INFO] * 2025-09-19 01:59:11 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-19 01:59:11 (10409) [INFO] * 2025-09-19 01:59:11 (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 01:59:11 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-19 01:59:12 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-19 01:59:12 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-19 01:59:12 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-19 01:59:12 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-19 01:59:12 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-19 01:59:17 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0ctbNPeim5/ea_profile.json * 2025-09-19 02:01:45 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0ctbNPeim5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-19 02:01:45 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-20 01:44:07 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-20 01:48:08 (11465) [INFO] Script is up to date. * 2025-09-20 01:52:11 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-20 01:52:11 (10379) [INFO] * 2025-09-20 01:53:05 (10409) [INFO] * 2025-09-20 01:53:05 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-20 01:53:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-20 01:53:06 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-20 01:53:06 (10379) [INFO] * 2025-09-20 01:53:09 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-20 01:53:09 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-20 01:53:09 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-20 01:53:09 (10379) [INFO] * 2025-09-20 01:53:44 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:44 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-20 01:53:45 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-20 01:53:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-20 01:53:45 (10379) [INFO] * 2025-09-20 01:53:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 01:53:45 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-20 01:54:16 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-20 01:54:16 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-20 01:54:16 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-20 01:54:16 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-20 01:54:16 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-20 01:54:16 (10392) [INFO] yum --disablerepo= ... * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-20 01:54:16 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-20 01:54:16 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] yum-config-manager --disable * 2025-09-20 01:54:16 (10392) [INFO] or * 2025-09-20 01:54:16 (10392) [INFO] subscription-manager repos --disable= * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-20 01:54:16 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-20 01:54:16 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-20 01:54:16 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-20 01:54:16 (10392) [INFO] compromise: * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-20 01:54:16 (10392) [INFO] * 2025-09-20 01:54:16 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-20 01:54:16 (10409) [INFO] * 2025-09-20 01:54:16 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-20 01:54:16 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-20 01:54:16 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-20 01:54:16 (10379) [INFO] * 2025-09-20 01:54:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 01:54:17 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-20 01:54:17 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-20 01:54:17 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-20 01:54:17 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-20 01:54:17 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-20 01:54:17 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-20 01:54:17 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-20 01:54:17 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-20 01:54:17 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-20 01:54:17 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-20 01:54:17 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-20 01:54:17 (10409) [INFO] * 2025-09-20 01:54:17 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-20 01:54:17 (10379) [INFO] * 2025-09-20 01:54:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 01:54:18 (10392) [INFO] Determining fastest mirrors * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-20 01:54:50 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-20 01:54:50 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-20 01:54:50 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-20 01:54:50 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-20 01:54:50 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-20 01:54:50 (10392) [INFO] yum --disablerepo= ... * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-20 01:54:50 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-20 01:54:50 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] yum-config-manager --disable * 2025-09-20 01:54:50 (10392) [INFO] or * 2025-09-20 01:54:50 (10392) [INFO] subscription-manager repos --disable= * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-20 01:54:50 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-20 01:54:50 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-20 01:54:50 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-20 01:54:50 (10392) [INFO] compromise: * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-20 01:54:50 (10392) [INFO] * 2025-09-20 01:54:50 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-20 01:54:50 (10409) [INFO] * 2025-09-20 01:54: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-20 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-20 01:54:51 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-20 01:54:51 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-20 01:54:51 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-20 01:54:51 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-20 01:54:51 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-20 01:54:58 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lEMnkJZiQ1/ea_profile.json * 2025-09-20 01:57:25 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lEMnkJZiQ1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-20 01:57:25 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-21 01:44:28 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-21 01:48:28 (11465) [INFO] Script is up to date. * 2025-09-21 01:52:31 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-21 01:52:31 (10379) [INFO] * 2025-09-21 01:53:26 (10409) [INFO] * 2025-09-21 01:53:26 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-21 01:53:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-21 01:53:29 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-21 01:53:29 (10379) [INFO] * 2025-09-21 01:53:32 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-21 01:53:32 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-21 01:53:32 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-21 01:53:32 (10379) [INFO] * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-21 01:54:08 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-21 01:54:08 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-21 01:54:08 (10379) [INFO] * 2025-09-21 01:54:08 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 01:54:09 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-21 01:54:39 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-21 01:54:39 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-21 01:54:39 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-21 01:54:39 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-21 01:54:39 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-21 01:54:39 (10392) [INFO] yum --disablerepo= ... * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-21 01:54:39 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-21 01:54:39 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] yum-config-manager --disable * 2025-09-21 01:54:39 (10392) [INFO] or * 2025-09-21 01:54:39 (10392) [INFO] subscription-manager repos --disable= * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-21 01:54:39 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-21 01:54:39 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-21 01:54:39 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-21 01:54:39 (10392) [INFO] compromise: * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-21 01:54:39 (10392) [INFO] * 2025-09-21 01:54:39 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-21 01:54:39 (10409) [INFO] * 2025-09-21 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-21 01:54:39 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-21 01:54:39 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-21 01:54:39 (10379) [INFO] * 2025-09-21 01:54:40 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 01:54:40 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-21 01:54:40 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-21 01:54:40 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-21 01:54:40 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-21 01:54:40 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-21 01:54:40 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-21 01:54:40 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-21 01:54:40 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-21 01:54:40 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-21 01:54:40 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-21 01:54:40 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-21 01:54:40 (10409) [INFO] * 2025-09-21 01:54:40 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-21 01:54:40 (10379) [INFO] * 2025-09-21 01:54:41 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 01:54:41 (10392) [INFO] Determining fastest mirrors * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-21 01:55:12 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-21 01:55:12 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-21 01:55:12 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-21 01:55:12 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-21 01:55:12 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-21 01:55:12 (10392) [INFO] yum --disablerepo= ... * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-21 01:55:12 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-21 01:55:12 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] yum-config-manager --disable * 2025-09-21 01:55:12 (10392) [INFO] or * 2025-09-21 01:55:12 (10392) [INFO] subscription-manager repos --disable= * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-21 01:55:12 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-21 01:55:12 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-21 01:55:12 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-21 01:55:12 (10392) [INFO] compromise: * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-21 01:55:12 (10392) [INFO] * 2025-09-21 01:55:12 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-21 01:55:12 (10409) [INFO] * 2025-09-21 01:55:12 (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 01:55:12 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-21 01:55:14 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-21 01:55:14 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-21 01:55:14 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-21 01:55:14 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-21 01:55:14 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-21 01:55:20 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Fs8DzuzLrR/ea_profile.json * 2025-09-21 01:57:48 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Fs8DzuzLrR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-21 01:57:48 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-22 01:43:19 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-22 01:47:19 (11465) [INFO] Script is up to date. * 2025-09-22 01:51:22 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-22 01:51:22 (10379) [INFO] * 2025-09-22 01:52:38 (10409) [INFO] * 2025-09-22 01:52:38 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-22 01:52:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-22 01:52:39 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-22 01:52:39 (10379) [INFO] * 2025-09-22 01:52:42 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-22 01:52:42 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-22 01:52:42 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-22 01:52:42 (10379) [INFO] * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-22 01:53:17 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-22 01:53:17 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-22 01:53:17 (10379) [INFO] * 2025-09-22 01:53:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 01:53:18 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-22 01:53:48 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-22 01:53:48 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-22 01:53:48 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-22 01:53:48 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-22 01:53:48 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-22 01:53:48 (10392) [INFO] yum --disablerepo= ... * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-22 01:53:48 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-22 01:53:48 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] yum-config-manager --disable * 2025-09-22 01:53:48 (10392) [INFO] or * 2025-09-22 01:53:48 (10392) [INFO] subscription-manager repos --disable= * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-22 01:53:48 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-22 01:53:48 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-22 01:53:48 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-22 01:53:48 (10392) [INFO] compromise: * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-22 01:53:48 (10392) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-22 01:53:48 (10409) [INFO] * 2025-09-22 01:53:48 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-22 01:53:48 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-22 01:53:48 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-22 01:53:48 (10379) [INFO] * 2025-09-22 01:53:48 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 01:53:49 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-22 01:53:49 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-22 01:53:49 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-22 01:53:49 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-22 01:53:49 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-22 01:53:49 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-22 01:53:49 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-22 01:53:49 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-22 01:53:49 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-22 01:53:49 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-22 01:53:49 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-22 01:53:49 (10409) [INFO] * 2025-09-22 01:53:49 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-22 01:53:49 (10379) [INFO] * 2025-09-22 01:53:49 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 01:53:50 (10392) [INFO] Determining fastest mirrors * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-22 01:54:21 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-22 01:54:21 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-22 01:54:21 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-22 01:54:21 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-22 01:54:21 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-22 01:54:21 (10392) [INFO] yum --disablerepo= ... * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-22 01:54:21 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-22 01:54:21 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] yum-config-manager --disable * 2025-09-22 01:54:21 (10392) [INFO] or * 2025-09-22 01:54:21 (10392) [INFO] subscription-manager repos --disable= * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-22 01:54:21 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-22 01:54:21 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-22 01:54:21 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-22 01:54:21 (10392) [INFO] compromise: * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-22 01:54:21 (10392) [INFO] * 2025-09-22 01:54:21 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-22 01:54:21 (10409) [INFO] * 2025-09-22 01:54:21 (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 01:54:21 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-22 01:54:23 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-22 01:54:23 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-22 01:54:23 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-22 01:54:23 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-22 01:54:23 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-22 01:54:29 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hgRIeivv0H/ea_profile.json * 2025-09-22 01:57:26 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/hgRIeivv0H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-22 01:57:26 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-23 01:44:53 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-23 01:48:54 (11465) [INFO] Script is up to date. * 2025-09-23 01:52:57 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-23 01:52:57 (10379) [INFO] * 2025-09-23 01:54:13 (10409) [INFO] * 2025-09-23 01:54:13 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-23 01:54:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-23 01:54:14 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-23 01:54:14 (10379) [INFO] * 2025-09-23 01:54:18 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-23 01:54:18 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-23 01:54:18 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-23 01:54:18 (10379) [INFO] * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-23 01:54:54 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-23 01:54:54 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-23 01:54:54 (10379) [INFO] * 2025-09-23 01:54:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 01:54:55 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-23 01:55:25 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-23 01:55:25 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-23 01:55:25 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-23 01:55:25 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-23 01:55:25 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-23 01:55:25 (10392) [INFO] yum --disablerepo= ... * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-23 01:55:25 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-23 01:55:25 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] yum-config-manager --disable * 2025-09-23 01:55:25 (10392) [INFO] or * 2025-09-23 01:55:25 (10392) [INFO] subscription-manager repos --disable= * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-23 01:55:25 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-23 01:55:25 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-23 01:55:25 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-23 01:55:25 (10392) [INFO] compromise: * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-23 01:55:25 (10392) [INFO] * 2025-09-23 01:55:25 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-23 01:55:25 (10409) [INFO] * 2025-09-23 01:55:25 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-23 01:55:25 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-23 01:55:25 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-23 01:55:25 (10379) [INFO] * 2025-09-23 01:55:26 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 01:55:26 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-23 01:55:26 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-23 01:55:26 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-23 01:55:26 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-23 01:55:26 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-23 01:55:26 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-23 01:55:26 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-23 01:55:26 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-23 01:55:26 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-23 01:55:26 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-23 01:55:27 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-23 01:55:27 (10409) [INFO] * 2025-09-23 01:55:27 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-23 01:55:27 (10379) [INFO] * 2025-09-23 01:55:27 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 01:55:27 (10392) [INFO] Determining fastest mirrors * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-23 01:55:58 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-23 01:55:58 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-23 01:55:58 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-23 01:55:58 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-23 01:55:58 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-23 01:55:58 (10392) [INFO] yum --disablerepo= ... * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-23 01:55:58 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-23 01:55:58 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] yum-config-manager --disable * 2025-09-23 01:55:58 (10392) [INFO] or * 2025-09-23 01:55:58 (10392) [INFO] subscription-manager repos --disable= * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-23 01:55:58 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-23 01:55:58 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-23 01:55:58 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-23 01:55:58 (10392) [INFO] compromise: * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-23 01:55:58 (10392) [INFO] * 2025-09-23 01:55:58 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-23 01:55:58 (10409) [INFO] * 2025-09-23 01:55: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-23 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-23 01:55:59 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-23 01:55:59 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-23 01:55:59 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-23 01:55:59 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-23 01:55:59 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-23 01:56:06 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c3seNlB234/ea_profile.json * 2025-09-23 01:58:33 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c3seNlB234/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-23 01:58:33 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-24 01:48:53 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-24 01:52:54 (11465) [INFO] Script is up to date. * 2025-09-24 01:56:56 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-24 01:56:56 (10379) [INFO] * 2025-09-24 01:58:15 (10409) [INFO] * 2025-09-24 01:58:15 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-24 01:58:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-24 01:58:16 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-24 01:58:16 (10379) [INFO] * 2025-09-24 01:58:19 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-24 01:58:19 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-24 01:58:19 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-24 01:58:19 (10379) [INFO] * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-24 01:58:55 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-24 01:58:55 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-24 01:58:55 (10379) [INFO] * 2025-09-24 01:58:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 01:58:56 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-24 01:59:27 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-24 01:59:27 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-24 01:59:27 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-24 01:59:27 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-24 01:59:27 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-24 01:59:27 (10392) [INFO] yum --disablerepo= ... * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-24 01:59:27 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-24 01:59:27 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] yum-config-manager --disable * 2025-09-24 01:59:27 (10392) [INFO] or * 2025-09-24 01:59:27 (10392) [INFO] subscription-manager repos --disable= * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-24 01:59:27 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-24 01:59:27 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-24 01:59:27 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-24 01:59:27 (10392) [INFO] compromise: * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-24 01:59:27 (10392) [INFO] * 2025-09-24 01:59:27 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-24 01:59:27 (10409) [INFO] * 2025-09-24 01:59:27 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-24 01:59:27 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-24 01:59:27 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-24 01:59:27 (10379) [INFO] * 2025-09-24 01:59:28 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 01:59:28 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-24 01:59:28 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-24 01:59:28 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-24 01:59:28 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-24 01:59:28 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-24 01:59:28 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-24 01:59:28 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-24 01:59:28 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-24 01:59:28 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-24 01:59:28 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-24 01:59:28 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-24 01:59:28 (10409) [INFO] * 2025-09-24 01:59:28 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-24 01:59:28 (10379) [INFO] * 2025-09-24 01:59:28 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 01:59:28 (10392) [INFO] Determining fastest mirrors * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-24 01:59:59 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-24 01:59:59 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-24 01:59:59 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-24 01:59:59 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-24 01:59:59 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-24 01:59:59 (10392) [INFO] yum --disablerepo= ... * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-24 01:59:59 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-24 01:59:59 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] yum-config-manager --disable * 2025-09-24 01:59:59 (10392) [INFO] or * 2025-09-24 01:59:59 (10392) [INFO] subscription-manager repos --disable= * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-24 01:59:59 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-24 01:59:59 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-24 01:59:59 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-24 01:59:59 (10392) [INFO] compromise: * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-24 01:59:59 (10392) [INFO] * 2025-09-24 01:59:59 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-24 01:59:59 (10409) [INFO] * 2025-09-24 01:59:59 (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 01:59:59 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-24 02:00:01 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-24 02:00:01 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-24 02:00:01 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-24 02:00:01 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-24 02:00:01 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-24 02:00:09 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JOFrMIsadA/ea_profile.json * 2025-09-24 02:03:07 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JOFrMIsadA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-24 02:03:07 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-25 01:43:23 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-25 01:47:23 (11465) [INFO] Script is up to date. * 2025-09-25 01:51:26 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-25 01:51:26 (10379) [INFO] * 2025-09-25 01:52:43 (10409) [INFO] * 2025-09-25 01:52:43 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-25 01:52:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-25 01:52:44 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-25 01:52:44 (10379) [INFO] * 2025-09-25 01:52:47 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-25 01:52:47 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-25 01:52:48 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-25 01:52:48 (10379) [INFO] * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-25 01:53:23 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-25 01:53:23 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-25 01:53:23 (10379) [INFO] * 2025-09-25 01:53:24 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 01:53:24 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-25 01:53:54 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-25 01:53:54 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-25 01:53:54 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-25 01:53:54 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-25 01:53:54 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-25 01:53:54 (10392) [INFO] yum --disablerepo= ... * 2025-09-25 01:53:54 (10392) [INFO] * 2025-09-25 01:53:54 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-25 01:53:54 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-25 01:53:55 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-25 01:53:55 (10392) [INFO] * 2025-09-25 01:53:55 (10392) [INFO] yum-config-manager --disable * 2025-09-25 01:53:55 (10392) [INFO] or * 2025-09-25 01:53:55 (10392) [INFO] subscription-manager repos --disable= * 2025-09-25 01:53:55 (10392) [INFO] * 2025-09-25 01:53:55 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-25 01:53:55 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-25 01:53:55 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-25 01:53:55 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-25 01:53:55 (10392) [INFO] compromise: * 2025-09-25 01:53:55 (10392) [INFO] * 2025-09-25 01:53:55 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-25 01:53:55 (10392) [INFO] * 2025-09-25 01:53:55 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-25 01:53:55 (10409) [INFO] * 2025-09-25 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-25 01:53:55 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-25 01:53:55 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-25 01:53:55 (10379) [INFO] * 2025-09-25 01:53:55 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 01:53:55 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-25 01:53:55 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-25 01:53:55 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-25 01:53:55 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-25 01:53:55 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-25 01:53:55 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-25 01:53:55 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-25 01:53:55 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-25 01:53:55 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-25 01:53:55 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-25 01:53:55 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-25 01:53:55 (10409) [INFO] * 2025-09-25 01:53:55 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-25 01:53:55 (10379) [INFO] * 2025-09-25 01:53:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 01:53:56 (10392) [INFO] Determining fastest mirrors * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-25 01:54:26 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-25 01:54:26 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-25 01:54:26 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-25 01:54:26 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-25 01:54:26 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-25 01:54:26 (10392) [INFO] yum --disablerepo= ... * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-25 01:54:26 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-25 01:54:26 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] yum-config-manager --disable * 2025-09-25 01:54:26 (10392) [INFO] or * 2025-09-25 01:54:26 (10392) [INFO] subscription-manager repos --disable= * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-25 01:54:26 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-25 01:54:26 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-25 01:54:26 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-25 01:54:26 (10392) [INFO] compromise: * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-25 01:54:26 (10392) [INFO] * 2025-09-25 01:54:26 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-25 01:54:26 (10409) [INFO] * 2025-09-25 01:54: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-09-25 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-25 01:54:28 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-25 01:54:28 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-25 01:54:28 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-25 01:54:28 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-25 01:54:28 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-25 01:54:34 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/45hYKSco3z/ea_profile.json * 2025-09-25 01:58:03 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/45hYKSco3z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-25 01:58:03 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-26 01:49:59 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-26 01:53:59 (11465) [INFO] Script is up to date. * 2025-09-26 01:58:03 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-26 01:58:03 (10379) [INFO] * 2025-09-26 01:59:22 (10409) [INFO] * 2025-09-26 01:59:22 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-26 01:59:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-26 01:59:23 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-26 01:59:23 (10379) [INFO] * 2025-09-26 01:59:26 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-26 01:59:26 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-26 01:59:26 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-26 01:59:26 (10379) [INFO] * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-26 02:00:06 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-26 02:00:06 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-26 02:00:06 (10379) [INFO] * 2025-09-26 02:00:06 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 02:00:07 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-26 02:00:38 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-26 02:00:38 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-26 02:00:38 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-26 02:00:38 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-26 02:00:38 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-26 02:00:38 (10392) [INFO] yum --disablerepo= ... * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-26 02:00:38 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-26 02:00:38 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] yum-config-manager --disable * 2025-09-26 02:00:38 (10392) [INFO] or * 2025-09-26 02:00:38 (10392) [INFO] subscription-manager repos --disable= * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-26 02:00:38 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-26 02:00:38 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-26 02:00:38 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-26 02:00:38 (10392) [INFO] compromise: * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-26 02:00:38 (10392) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-26 02:00:38 (10409) [INFO] * 2025-09-26 02:00:38 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-26 02:00:38 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-26 02:00:38 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-26 02:00:38 (10379) [INFO] * 2025-09-26 02:00:38 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 02:00:39 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-26 02:00:39 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-26 02:00:39 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-26 02:00:39 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-26 02:00:39 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-26 02:00:39 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-26 02:00:39 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-26 02:00:39 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-26 02:00:39 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-26 02:00:39 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-26 02:00:39 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-26 02:00:39 (10409) [INFO] * 2025-09-26 02:00:39 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-26 02:00:39 (10379) [INFO] * 2025-09-26 02:00:39 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 02:00:40 (10392) [INFO] Determining fastest mirrors * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-26 02:01:10 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-26 02:01:10 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-26 02:01:10 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-26 02:01:10 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-26 02:01:10 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-26 02:01:10 (10392) [INFO] yum --disablerepo= ... * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-26 02:01:10 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-26 02:01:10 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] yum-config-manager --disable * 2025-09-26 02:01:10 (10392) [INFO] or * 2025-09-26 02:01:10 (10392) [INFO] subscription-manager repos --disable= * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-26 02:01:10 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-26 02:01:10 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-26 02:01:10 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-26 02:01:10 (10392) [INFO] compromise: * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-26 02:01:10 (10392) [INFO] * 2025-09-26 02:01:10 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-26 02:01:10 (10409) [INFO] * 2025-09-26 02:01:10 (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 02:01:10 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-26 02:01:12 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-26 02:01:12 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-26 02:01:12 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-26 02:01:12 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-26 02:01:12 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-26 02:01:19 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dEAxZtRKK8/ea_profile.json * 2025-09-26 02:03:45 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dEAxZtRKK8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-26 02:03:45 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-27 01:44:02 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-27 01:48:03 (11465) [INFO] Script is up to date. * 2025-09-27 01:52:06 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-27 01:52:06 (10379) [INFO] * 2025-09-27 01:53:03 (10409) [INFO] * 2025-09-27 01:53:03 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-27 01:53:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-27 01:53:03 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-27 01:53:03 (10379) [INFO] * 2025-09-27 01:53:07 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-27 01:53:07 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-27 01:53:07 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-27 01:53:07 (10379) [INFO] * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-27 01:53:43 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-27 01:53:43 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-27 01:53:43 (10379) [INFO] * 2025-09-27 01:53:43 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 01:53:43 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-27 01:54:14 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-27 01:54:14 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-27 01:54:14 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-27 01:54:14 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-27 01:54:14 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-27 01:54:14 (10392) [INFO] yum --disablerepo= ... * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-27 01:54:14 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-27 01:54:14 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] yum-config-manager --disable * 2025-09-27 01:54:14 (10392) [INFO] or * 2025-09-27 01:54:14 (10392) [INFO] subscription-manager repos --disable= * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-27 01:54:14 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-27 01:54:14 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-27 01:54:14 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-27 01:54:14 (10392) [INFO] compromise: * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-27 01:54:14 (10392) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-27 01:54:14 (10409) [INFO] * 2025-09-27 01:54:14 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-27 01:54:14 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-27 01:54:14 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-27 01:54:14 (10379) [INFO] * 2025-09-27 01:54:14 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 01:54:15 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-27 01:54:15 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-27 01:54:15 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-27 01:54:15 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-27 01:54:15 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-27 01:54:15 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-27 01:54:15 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-27 01:54:15 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-27 01:54:15 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-27 01:54:15 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-27 01:54:15 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-27 01:54:15 (10409) [INFO] * 2025-09-27 01:54:15 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-27 01:54:15 (10379) [INFO] * 2025-09-27 01:54:15 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 01:54:16 (10392) [INFO] Determining fastest mirrors * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-27 01:54:47 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-27 01:54:47 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-27 01:54:47 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-27 01:54:47 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-27 01:54:47 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-27 01:54:47 (10392) [INFO] yum --disablerepo= ... * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-27 01:54:47 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-27 01:54:47 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] yum-config-manager --disable * 2025-09-27 01:54:47 (10392) [INFO] or * 2025-09-27 01:54:47 (10392) [INFO] subscription-manager repos --disable= * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-27 01:54:47 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-27 01:54:47 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-27 01:54:47 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-27 01:54:47 (10392) [INFO] compromise: * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-27 01:54:47 (10392) [INFO] * 2025-09-27 01:54:47 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-27 01:54:47 (10409) [INFO] * 2025-09-27 01:54:47 (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 01:54:47 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-27 01:54:48 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-27 01:54:48 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-27 01:54:48 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-27 01:54:48 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-27 01:54:48 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-27 01:54:55 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cCvI8CykNz/ea_profile.json * 2025-09-27 01:57:22 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cCvI8CykNz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-27 01:57:22 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-28 01:44:43 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-28 01:48:43 (11465) [INFO] Script is up to date. * 2025-09-28 01:52:47 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-28 01:52:47 (10379) [INFO] * 2025-09-28 01:53:40 (10409) [INFO] * 2025-09-28 01:53:40 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-28 01:53:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-28 01:53:40 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-28 01:53:40 (10379) [INFO] * 2025-09-28 01:53:43 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-28 01:53:43 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-28 01:53:43 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-28 01:53:43 (10379) [INFO] * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-28 01:54:19 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-28 01:54:19 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-28 01:54:19 (10379) [INFO] * 2025-09-28 01:54:20 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 01:54:20 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-28 01:54:53 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-28 01:54:53 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-28 01:54:53 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-28 01:54:53 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-28 01:54:53 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-28 01:54:53 (10392) [INFO] yum --disablerepo= ... * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-28 01:54:53 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-28 01:54:53 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] yum-config-manager --disable * 2025-09-28 01:54:53 (10392) [INFO] or * 2025-09-28 01:54:53 (10392) [INFO] subscription-manager repos --disable= * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-28 01:54:53 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-28 01:54:53 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-28 01:54:53 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-28 01:54:53 (10392) [INFO] compromise: * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-28 01:54:53 (10392) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-28 01:54:53 (10409) [INFO] * 2025-09-28 01:54:53 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-28 01:54:53 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-28 01:54:53 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-28 01:54:53 (10379) [INFO] * 2025-09-28 01:54:53 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 01:54:54 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-28 01:54:54 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-28 01:54:54 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-28 01:54:54 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-28 01:54:54 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-28 01:54:54 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-28 01:54:54 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-28 01:54:54 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-28 01:54:54 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-28 01:54:54 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-28 01:54:54 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-28 01:54:54 (10409) [INFO] * 2025-09-28 01:54:54 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-28 01:54:54 (10379) [INFO] * 2025-09-28 01:54:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 01:54:55 (10392) [INFO] Determining fastest mirrors * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-28 01:55:26 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-28 01:55:26 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-28 01:55:26 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-28 01:55:26 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-28 01:55:26 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-28 01:55:26 (10392) [INFO] yum --disablerepo= ... * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-28 01:55:26 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-28 01:55:26 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] yum-config-manager --disable * 2025-09-28 01:55:26 (10392) [INFO] or * 2025-09-28 01:55:26 (10392) [INFO] subscription-manager repos --disable= * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-28 01:55:26 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-28 01:55:26 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-28 01:55:26 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-28 01:55:26 (10392) [INFO] compromise: * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-28 01:55:26 (10392) [INFO] * 2025-09-28 01:55:26 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-28 01:55:26 (10409) [INFO] * 2025-09-28 01:55: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-09-28 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-28 01:55:27 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-28 01:55:27 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-28 01:55:27 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-28 01:55:27 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-28 01:55:27 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-28 01:55:34 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UPCKMJqSMz/ea_profile.json * 2025-09-28 01:58:02 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UPCKMJqSMz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-28 01:58:02 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-29 01:43:21 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-29 01:47:21 (11465) [INFO] Script is up to date. * 2025-09-29 01:51:24 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-29 01:51:24 (10379) [INFO] * 2025-09-29 01:52:34 (10409) [INFO] * 2025-09-29 01:52:34 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-29 01:52:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-29 01:52:35 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-29 01:52:35 (10379) [INFO] * 2025-09-29 01:52:38 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-29 01:52:38 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-29 01:52:38 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-29 01:52:38 (10379) [INFO] * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-29 01:53:18 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-29 01:53:18 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-29 01:53:18 (10379) [INFO] * 2025-09-29 01:53:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 01:53:19 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-29 01:53:50 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-29 01:53:50 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-29 01:53:50 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-29 01:53:50 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-29 01:53:50 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-29 01:53:50 (10392) [INFO] yum --disablerepo= ... * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-29 01:53:50 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-29 01:53:50 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] yum-config-manager --disable * 2025-09-29 01:53:50 (10392) [INFO] or * 2025-09-29 01:53:50 (10392) [INFO] subscription-manager repos --disable= * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-29 01:53:50 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-29 01:53:50 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-29 01:53:50 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-29 01:53:50 (10392) [INFO] compromise: * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-29 01:53:50 (10392) [INFO] * 2025-09-29 01:53:50 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-29 01:53:50 (10409) [INFO] * 2025-09-29 01:53:50 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-29 01:53:50 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-29 01:53:50 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-29 01:53:50 (10379) [INFO] * 2025-09-29 01:53:51 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 01:53:51 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-29 01:53:51 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-29 01:53:51 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-29 01:53:51 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-29 01:53:51 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-29 01:53:51 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-29 01:53:51 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-29 01:53:51 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-29 01:53:51 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-29 01:53:51 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-29 01:53:51 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-29 01:53:51 (10409) [INFO] * 2025-09-29 01:53:51 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-29 01:53:51 (10379) [INFO] * 2025-09-29 01:53:52 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 01:53:52 (10392) [INFO] Determining fastest mirrors * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-29 01:54:22 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-29 01:54:22 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-29 01:54:22 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-29 01:54:22 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-29 01:54:22 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-29 01:54:22 (10392) [INFO] yum --disablerepo= ... * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-29 01:54:22 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-29 01:54:22 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] yum-config-manager --disable * 2025-09-29 01:54:22 (10392) [INFO] or * 2025-09-29 01:54:22 (10392) [INFO] subscription-manager repos --disable= * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-29 01:54:22 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-29 01:54:22 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-29 01:54:22 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-29 01:54:22 (10392) [INFO] compromise: * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-29 01:54:22 (10392) [INFO] * 2025-09-29 01:54:22 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-29 01:54:22 (10409) [INFO] * 2025-09-29 01:54:22 (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 01:54:22 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-29 01:54:24 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-29 01:54:24 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-29 01:54:24 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-29 01:54:24 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-29 01:54:24 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-29 01:54:30 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YBl9WLKvb4/ea_profile.json * 2025-09-29 01:56:56 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YBl9WLKvb4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-29 01:56:56 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-30 01:43:40 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-30 01:47:40 (11465) [INFO] Script is up to date. * 2025-09-30 01:51:44 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-30 01:51:44 (10379) [INFO] * 2025-09-30 01:53:00 (10409) [INFO] * 2025-09-30 01:53:00 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-09-30 01:53:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-09-30 01:53:00 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-30 01:53:00 (10379) [INFO] * 2025-09-30 01:53:04 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-09-30 01:53:04 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-30 01:53:04 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-30 01:53:04 (10379) [INFO] * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-09-30 01:53:40 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-09-30 01:53:40 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-30 01:53:40 (10379) [INFO] * 2025-09-30 01:53:40 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 01:53:40 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-30 01:54:11 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-30 01:54:11 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-30 01:54:11 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-30 01:54:11 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-30 01:54:11 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-30 01:54:11 (10392) [INFO] yum --disablerepo= ... * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-30 01:54:11 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-30 01:54:11 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] yum-config-manager --disable * 2025-09-30 01:54:11 (10392) [INFO] or * 2025-09-30 01:54:11 (10392) [INFO] subscription-manager repos --disable= * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-30 01:54:11 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-30 01:54:11 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-30 01:54:11 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-30 01:54:11 (10392) [INFO] compromise: * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-30 01:54:11 (10392) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-30 01:54:11 (10409) [INFO] * 2025-09-30 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-30 01:54:11 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-30 01:54:11 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-30 01:54:11 (10379) [INFO] * 2025-09-30 01:54:11 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 01:54:12 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-09-30 01:54:12 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-09-30 01:54:12 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-09-30 01:54:12 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-09-30 01:54:12 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-09-30 01:54:12 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-30 01:54:12 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-30 01:54:12 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-09-30 01:54:12 (10392) [INFO] : wp-toolkit-thirdparties * 2025-09-30 01:54:12 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-30 01:54:12 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-09-30 01:54:12 (10409) [INFO] * 2025-09-30 01:54:12 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-30 01:54:12 (10379) [INFO] * 2025-09-30 01:54:12 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 01:54:13 (10392) [INFO] Determining fastest mirrors * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-30 01:54:43 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-30 01:54:43 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-30 01:54:43 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-30 01:54:43 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-30 01:54:43 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-30 01:54:43 (10392) [INFO] yum --disablerepo= ... * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-30 01:54:43 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-30 01:54:43 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] yum-config-manager --disable * 2025-09-30 01:54:43 (10392) [INFO] or * 2025-09-30 01:54:43 (10392) [INFO] subscription-manager repos --disable= * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-30 01:54:43 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-30 01:54:43 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-30 01:54:43 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-30 01:54:43 (10392) [INFO] compromise: * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-30 01:54:43 (10392) [INFO] * 2025-09-30 01:54:43 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-30 01:54:43 (10409) [INFO] * 2025-09-30 01:54: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-30 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-09-30 01:54:45 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-09-30 01:54:45 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-09-30 01:54:45 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-09-30 01:54:45 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-09-30 01:54:45 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-30 01:54:51 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9UAkj7Nn6P/ea_profile.json * 2025-09-30 01:57:20 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9UAkj7Nn6P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-30 01:57:20 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-01 01:43:19 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-01 01:47:20 (11465) [INFO] Script is up to date. * 2025-10-01 01:51:23 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-01 01:51:23 (10379) [INFO] * 2025-10-01 01:52:37 (10409) [INFO] * 2025-10-01 01:52:37 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-01 01:52:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-01 01:52:37 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-01 01:52:37 (10379) [INFO] * 2025-10-01 01:52:41 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-01 01:52:41 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-01 01:52:41 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-01 01:52:41 (10379) [INFO] * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-01 01:53:16 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-01 01:53:16 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-01 01:53:16 (10379) [INFO] * 2025-10-01 01:53:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 01:53:17 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-01 01:53:49 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-01 01:53:49 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-01 01:53:49 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-01 01:53:49 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-01 01:53:49 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-01 01:53:49 (10392) [INFO] yum --disablerepo= ... * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-01 01:53:49 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-01 01:53:49 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] yum-config-manager --disable * 2025-10-01 01:53:49 (10392) [INFO] or * 2025-10-01 01:53:49 (10392) [INFO] subscription-manager repos --disable= * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-01 01:53:49 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-01 01:53:49 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-01 01:53:49 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-01 01:53:49 (10392) [INFO] compromise: * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-01 01:53:49 (10392) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-01 01:53:49 (10409) [INFO] * 2025-10-01 01:53:49 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-01 01:53:49 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-01 01:53:49 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-01 01:53:49 (10379) [INFO] * 2025-10-01 01:53:49 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 01:53:50 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-01 01:53:50 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-01 01:53:50 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-01 01:53:50 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-01 01:53:50 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-01 01:53:50 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-01 01:53:50 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-01 01:53:50 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-01 01:53:50 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-01 01:53:50 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-01 01:53:50 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-01 01:53:50 (10409) [INFO] * 2025-10-01 01:53:50 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-01 01:53:50 (10379) [INFO] * 2025-10-01 01:53:50 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 01:53:50 (10392) [INFO] Determining fastest mirrors * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-01 01:54:22 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-01 01:54:22 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-01 01:54:22 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-01 01:54:22 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-01 01:54:22 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-01 01:54:22 (10392) [INFO] yum --disablerepo= ... * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-01 01:54:22 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-01 01:54:22 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] yum-config-manager --disable * 2025-10-01 01:54:22 (10392) [INFO] or * 2025-10-01 01:54:22 (10392) [INFO] subscription-manager repos --disable= * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-01 01:54:22 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-01 01:54:22 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-01 01:54:22 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-01 01:54:22 (10392) [INFO] compromise: * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-01 01:54:22 (10392) [INFO] * 2025-10-01 01:54:22 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-01 01:54:22 (10409) [INFO] * 2025-10-01 01:54:22 (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 01:54:22 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-01 01:54:23 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-01 01:54:23 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-01 01:54:23 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-01 01:54:23 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-01 01:54:23 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-01 01:54:29 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/f3M3oEGQXr/ea_profile.json * 2025-10-01 01:56:57 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/f3M3oEGQXr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-01 01:56:57 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-02 01:48:09 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-02 01:52:09 (11465) [INFO] Script is up to date. * 2025-10-02 01:56:13 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-02 01:56:13 (10379) [INFO] * 2025-10-02 01:57:30 (10409) [INFO] * 2025-10-02 01:57:30 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-02 01:57:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-02 01:57:30 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-02 01:57:30 (10379) [INFO] * 2025-10-02 01:57:34 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-02 01:57:34 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-02 01:57:34 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-02 01:57:34 (10379) [INFO] * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-02 01:58:09 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-02 01:58:09 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-02 01:58:09 (10379) [INFO] * 2025-10-02 01:58:09 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 01:58:09 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-02 01:58:40 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-02 01:58:40 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-02 01:58:40 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-02 01:58:40 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-02 01:58:40 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-02 01:58:40 (10392) [INFO] yum --disablerepo= ... * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-02 01:58:40 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-02 01:58:40 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] yum-config-manager --disable * 2025-10-02 01:58:40 (10392) [INFO] or * 2025-10-02 01:58:40 (10392) [INFO] subscription-manager repos --disable= * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-02 01:58:40 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-02 01:58:40 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-02 01:58:40 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-02 01:58:40 (10392) [INFO] compromise: * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-02 01:58:40 (10392) [INFO] * 2025-10-02 01:58:40 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-02 01:58:40 (10409) [INFO] * 2025-10-02 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-02 01:58:40 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-02 01:58:40 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-02 01:58:40 (10379) [INFO] * 2025-10-02 01:58:41 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 01:58:41 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-02 01:58:41 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-02 01:58:41 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-02 01:58:41 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-02 01:58:41 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-02 01:58:41 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-02 01:58:41 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-02 01:58:41 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-02 01:58:41 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-02 01:58:41 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-02 01:58:41 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-02 01:58:41 (10409) [INFO] * 2025-10-02 01:58:41 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-02 01:58:41 (10379) [INFO] * 2025-10-02 01:58:42 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 01:58:42 (10392) [INFO] Determining fastest mirrors * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-02 01:59:13 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-02 01:59:13 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-02 01:59:13 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-02 01:59:13 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-02 01:59:13 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-02 01:59:13 (10392) [INFO] yum --disablerepo= ... * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-02 01:59:13 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-02 01:59:13 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] yum-config-manager --disable * 2025-10-02 01:59:13 (10392) [INFO] or * 2025-10-02 01:59:13 (10392) [INFO] subscription-manager repos --disable= * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-02 01:59:13 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-02 01:59:13 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-02 01:59:13 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-02 01:59:13 (10392) [INFO] compromise: * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-02 01:59:13 (10392) [INFO] * 2025-10-02 01:59:13 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-02 01:59:13 (10409) [INFO] * 2025-10-02 01:59: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-10-02 01:59: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-02 01:59:15 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-02 01:59:15 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-02 01:59:15 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-02 01:59:15 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-02 01:59:15 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-02 01:59:21 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/W_r4BX5mTZ/ea_profile.json * 2025-10-02 02:02:20 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/W_r4BX5mTZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-02 02:02:20 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-03 01:47:44 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-03 01:51:44 (11465) [INFO] Script is up to date. * 2025-10-03 01:55:48 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-03 01:55:48 (10379) [INFO] * 2025-10-03 01:57:06 (10409) [INFO] * 2025-10-03 01:57:06 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-03 01:57:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-03 01:57:06 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-03 01:57:06 (10379) [INFO] * 2025-10-03 01:57:09 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-03 01:57:09 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-03 01:57:09 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-03 01:57:09 (10379) [INFO] * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-03 01:57:45 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-03 01:57:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-03 01:57:45 (10379) [INFO] * 2025-10-03 01:57:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-03 01:57:46 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-03 01:58:16 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-03 01:58:16 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-03 01:58:16 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-03 01:58:16 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-03 01:58:16 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-03 01:58:16 (10392) [INFO] yum --disablerepo= ... * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-03 01:58:16 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-03 01:58:16 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] yum-config-manager --disable * 2025-10-03 01:58:16 (10392) [INFO] or * 2025-10-03 01:58:16 (10392) [INFO] subscription-manager repos --disable= * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-03 01:58:16 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-03 01:58:16 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-03 01:58:16 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-03 01:58:16 (10392) [INFO] compromise: * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-03 01:58:16 (10392) [INFO] * 2025-10-03 01:58:16 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-03 01:58:17 (10409) [INFO] * 2025-10-03 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-03 01:58:17 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-03 01:58:17 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-03 01:58:17 (10379) [INFO] * 2025-10-03 01:58:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-03 01:58:17 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-03 01:58:17 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-03 01:58:17 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-03 01:58:17 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-03 01:58:17 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-03 01:58:17 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-03 01:58:17 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-03 01:58:17 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-03 01:58:17 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-03 01:58:17 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-03 01:58:17 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-03 01:58:17 (10409) [INFO] * 2025-10-03 01:58:17 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-03 01:58:17 (10379) [INFO] * 2025-10-03 01:58:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-03 01:58:18 (10392) [INFO] Determining fastest mirrors * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-03 01:58:49 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-03 01:58:49 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-03 01:58:49 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-03 01:58:49 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-03 01:58:49 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-03 01:58:49 (10392) [INFO] yum --disablerepo= ... * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-03 01:58:49 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-03 01:58:49 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] yum-config-manager --disable * 2025-10-03 01:58:49 (10392) [INFO] or * 2025-10-03 01:58:49 (10392) [INFO] subscription-manager repos --disable= * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-03 01:58:49 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-03 01:58:49 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-03 01:58:49 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-03 01:58:49 (10392) [INFO] compromise: * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-03 01:58:49 (10392) [INFO] * 2025-10-03 01:58:49 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-03 01:58:49 (10409) [INFO] * 2025-10-03 01:58: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-10-03 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-03 01:58:51 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-03 01:58:51 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-03 01:58:51 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-03 01:58:51 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-03 01:58:51 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-03 01:58:57 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sJjmr3e0d7/ea_profile.json * 2025-10-03 02:01:25 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sJjmr3e0d7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-03 02:01:25 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-04 01:45:16 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-04 01:49:17 (11465) [INFO] Script is up to date. * 2025-10-04 01:53:19 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-04 01:53:19 (10379) [INFO] * 2025-10-04 01:54:15 (10409) [INFO] * 2025-10-04 01:54:15 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-04 01:54:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-04 01:54:15 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-04 01:54:15 (10379) [INFO] * 2025-10-04 01:54:19 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-04 01:54:19 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-04 01:54:19 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-04 01:54:19 (10379) [INFO] * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-04 01:54:53 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-04 01:54:53 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-04 01:54:53 (10379) [INFO] * 2025-10-04 01:54:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-04 01:54:54 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-04 01:55:26 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-04 01:55:26 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-04 01:55:26 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-04 01:55:26 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-04 01:55:26 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-04 01:55:26 (10392) [INFO] yum --disablerepo= ... * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-04 01:55:26 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-04 01:55:26 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] yum-config-manager --disable * 2025-10-04 01:55:26 (10392) [INFO] or * 2025-10-04 01:55:26 (10392) [INFO] subscription-manager repos --disable= * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-04 01:55:26 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-04 01:55:26 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-04 01:55:26 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-04 01:55:26 (10392) [INFO] compromise: * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-04 01:55:26 (10392) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-04 01:55:26 (10409) [INFO] * 2025-10-04 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-04 01:55:26 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-04 01:55:26 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-04 01:55:26 (10379) [INFO] * 2025-10-04 01:55:26 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-04 01:55:26 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-04 01:55:26 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-04 01:55:26 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-04 01:55:26 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-04 01:55:26 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-04 01:55:26 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-04 01:55:26 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-04 01:55:26 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-04 01:55:26 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-04 01:55:26 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-04 01:55:27 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-04 01:55:27 (10409) [INFO] * 2025-10-04 01:55:27 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-04 01:55:27 (10379) [INFO] * 2025-10-04 01:55:27 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-04 01:55:27 (10392) [INFO] Determining fastest mirrors * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-04 01:55:58 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-04 01:55:58 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-04 01:55:58 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-04 01:55:58 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-04 01:55:58 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-04 01:55:58 (10392) [INFO] yum --disablerepo= ... * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-04 01:55:58 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-04 01:55:58 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] yum-config-manager --disable * 2025-10-04 01:55:58 (10392) [INFO] or * 2025-10-04 01:55:58 (10392) [INFO] subscription-manager repos --disable= * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-04 01:55:58 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-04 01:55:58 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-04 01:55:58 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-04 01:55:58 (10392) [INFO] compromise: * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-04 01:55:58 (10392) [INFO] * 2025-10-04 01:55:58 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-04 01:55:58 (10409) [INFO] * 2025-10-04 01:55: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-10-04 01:55: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-04 01:56:00 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-04 01:56:00 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-04 01:56:00 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-04 01:56:00 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-04 01:56:00 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-04 01:56:06 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HHF3MkicgO/ea_profile.json * 2025-10-04 01:58:33 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HHF3MkicgO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-04 01:58:33 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-05 01:44:00 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-05 01:48:00 (11465) [INFO] Script is up to date. * 2025-10-05 01:52:03 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-05 01:52:03 (10379) [INFO] * 2025-10-05 01:52:57 (10409) [INFO] * 2025-10-05 01:52:57 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-05 01:52:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-05 01:52:58 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-05 01:52:58 (10379) [INFO] * 2025-10-05 01:53:01 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-05 01:53:01 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-05 01:53:01 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-05 01:53:01 (10379) [INFO] * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-05 01:53:35 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-05 01:53:35 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-05 01:53:35 (10379) [INFO] * 2025-10-05 01:53:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-05 01:53:36 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-05 01:54:06 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-05 01:54:06 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-05 01:54:06 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-05 01:54:06 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-05 01:54:06 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-05 01:54:06 (10392) [INFO] yum --disablerepo= ... * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-05 01:54:06 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-05 01:54:06 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] yum-config-manager --disable * 2025-10-05 01:54:06 (10392) [INFO] or * 2025-10-05 01:54:06 (10392) [INFO] subscription-manager repos --disable= * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-05 01:54:06 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-05 01:54:06 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-05 01:54:06 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-05 01:54:06 (10392) [INFO] compromise: * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-05 01:54:06 (10392) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-05 01:54:06 (10409) [INFO] * 2025-10-05 01:54:06 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-05 01:54:06 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-05 01:54:06 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-05 01:54:06 (10379) [INFO] * 2025-10-05 01:54:06 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-05 01:54:07 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-05 01:54:07 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-05 01:54:07 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-05 01:54:07 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-05 01:54:07 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-05 01:54:07 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-05 01:54:07 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-05 01:54:07 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-05 01:54:07 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-05 01:54:07 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-05 01:54:07 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-05 01:54:07 (10409) [INFO] * 2025-10-05 01:54:07 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-05 01:54:07 (10379) [INFO] * 2025-10-05 01:54:08 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-05 01:54:08 (10392) [INFO] Determining fastest mirrors * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-05 01:54:39 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-05 01:54:39 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-05 01:54:39 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-05 01:54:39 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-05 01:54:39 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-05 01:54:39 (10392) [INFO] yum --disablerepo= ... * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-05 01:54:39 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-05 01:54:39 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] yum-config-manager --disable * 2025-10-05 01:54:39 (10392) [INFO] or * 2025-10-05 01:54:39 (10392) [INFO] subscription-manager repos --disable= * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-05 01:54:39 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-05 01:54:39 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-05 01:54:39 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-05 01:54:39 (10392) [INFO] compromise: * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-05 01:54:39 (10392) [INFO] * 2025-10-05 01:54:39 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-05 01:54:39 (10409) [INFO] * 2025-10-05 01:54: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-10-05 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-05 01:54:40 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-05 01:54:40 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-05 01:54:40 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-05 01:54:40 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-05 01:54:40 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-05 01:54:47 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3NP3tqg_xI/ea_profile.json * 2025-10-05 01:57:47 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3NP3tqg_xI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-05 01:57:47 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-06 01:42:50 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-06 01:46:51 (11465) [INFO] Script is up to date. * 2025-10-06 01:50:54 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-06 01:50:54 (10379) [INFO] * 2025-10-06 01:52:04 (10409) [INFO] * 2025-10-06 01:52:04 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-06 01:52:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-06 01:52:05 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-06 01:52:05 (10379) [INFO] * 2025-10-06 01:52:08 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-06 01:52:08 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-06 01:52:08 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-06 01:52:08 (10379) [INFO] * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-06 01:52:43 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-06 01:52:43 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-06 01:52:43 (10379) [INFO] * 2025-10-06 01:52:43 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-06 01:52:43 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-06 01:53:15 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-06 01:53:15 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-06 01:53:15 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-06 01:53:15 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-06 01:53:15 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-06 01:53:15 (10392) [INFO] yum --disablerepo= ... * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-06 01:53:15 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-06 01:53:15 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] yum-config-manager --disable * 2025-10-06 01:53:15 (10392) [INFO] or * 2025-10-06 01:53:15 (10392) [INFO] subscription-manager repos --disable= * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-06 01:53:15 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-06 01:53:15 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-06 01:53:15 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-06 01:53:15 (10392) [INFO] compromise: * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-06 01:53:15 (10392) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-06 01:53:15 (10409) [INFO] * 2025-10-06 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-06 01:53:15 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-06 01:53:15 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-06 01:53:15 (10379) [INFO] * 2025-10-06 01:53:15 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-06 01:53:16 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-06 01:53:16 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-06 01:53:16 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-06 01:53:16 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-06 01:53:16 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-06 01:53:16 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-06 01:53:16 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-06 01:53:16 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-06 01:53:16 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-06 01:53:16 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-06 01:53:16 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-06 01:53:16 (10409) [INFO] * 2025-10-06 01:53:16 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-06 01:53:16 (10379) [INFO] * 2025-10-06 01:53:16 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-06 01:53:16 (10392) [INFO] Determining fastest mirrors * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-06 01:53:48 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-06 01:53:48 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-06 01:53:48 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-06 01:53:48 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-06 01:53:48 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-06 01:53:48 (10392) [INFO] yum --disablerepo= ... * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-06 01:53:48 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-06 01:53:48 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] yum-config-manager --disable * 2025-10-06 01:53:48 (10392) [INFO] or * 2025-10-06 01:53:48 (10392) [INFO] subscription-manager repos --disable= * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-06 01:53:48 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-06 01:53:48 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-06 01:53:48 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-06 01:53:48 (10392) [INFO] compromise: * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-06 01:53:48 (10392) [INFO] * 2025-10-06 01:53:48 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-06 01:53:48 (10409) [INFO] * 2025-10-06 01:53: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-10-06 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-06 01:53:50 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-06 01:53:50 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-06 01:53:50 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-06 01:53:50 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-06 01:53:50 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-06 01:53:55 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VwKsbC076H/ea_profile.json * 2025-10-06 01:56:24 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VwKsbC076H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-06 01:56:24 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-07 01:42:53 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-07 01:46:53 (11465) [INFO] Script is up to date. * 2025-10-07 01:50:56 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-07 01:50:56 (10379) [INFO] * 2025-10-07 01:52:12 (10409) [INFO] * 2025-10-07 01:52:12 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-07 01:52:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-07 01:52:12 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-07 01:52:12 (10379) [INFO] * 2025-10-07 01:52:15 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-07 01:52:15 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-07 01:52:15 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-07 01:52:15 (10379) [INFO] * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-07 01:52:50 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-07 01:52:50 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-07 01:52:50 (10379) [INFO] * 2025-10-07 01:52:50 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-07 01:52:51 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-07 01:53:21 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-07 01:53:21 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-07 01:53:21 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-07 01:53:21 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-07 01:53:21 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-07 01:53:21 (10392) [INFO] yum --disablerepo= ... * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-07 01:53:21 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-07 01:53:21 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] yum-config-manager --disable * 2025-10-07 01:53:21 (10392) [INFO] or * 2025-10-07 01:53:21 (10392) [INFO] subscription-manager repos --disable= * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-07 01:53:21 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-07 01:53:21 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-07 01:53:21 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-07 01:53:21 (10392) [INFO] compromise: * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-07 01:53:21 (10392) [INFO] * 2025-10-07 01:53:21 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-07 01:53:21 (10409) [INFO] * 2025-10-07 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-07 01:53:21 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-07 01:53:21 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-07 01:53:21 (10379) [INFO] * 2025-10-07 01:53:22 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-07 01:53:22 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-07 01:53:22 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-07 01:53:22 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-07 01:53:22 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-07 01:53:22 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-07 01:53:22 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-07 01:53:22 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-07 01:53:22 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-07 01:53:22 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-07 01:53:22 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-07 01:53:22 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-07 01:53:22 (10409) [INFO] * 2025-10-07 01:53:22 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-07 01:53:22 (10379) [INFO] * 2025-10-07 01:53:22 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-07 01:53:23 (10392) [INFO] Determining fastest mirrors * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-07 01:53:54 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-07 01:53:54 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-07 01:53:54 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-07 01:53:54 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-07 01:53:54 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-07 01:53:54 (10392) [INFO] yum --disablerepo= ... * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-07 01:53:54 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-07 01:53:54 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] yum-config-manager --disable * 2025-10-07 01:53:54 (10392) [INFO] or * 2025-10-07 01:53:54 (10392) [INFO] subscription-manager repos --disable= * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-07 01:53:54 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-07 01:53:54 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-07 01:53:54 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-07 01:53:54 (10392) [INFO] compromise: * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-07 01:53:54 (10392) [INFO] * 2025-10-07 01:53:54 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-07 01:53:54 (10409) [INFO] * 2025-10-07 01:53:54 (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-07 01:53:54 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-07 01:53:55 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-07 01:53:55 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-07 01:53:55 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-07 01:53:55 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-07 01:53:55 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-07 01:54:02 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mHCdQerdJl/ea_profile.json * 2025-10-07 01:56:30 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mHCdQerdJl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-07 01:56:30 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-08 01:42:55 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-08 01:46:55 (11465) [INFO] Script is up to date. * 2025-10-08 01:50:58 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-08 01:50:58 (10379) [INFO] * 2025-10-08 01:52:17 (10409) [INFO] * 2025-10-08 01:52:17 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-08 01:52:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-08 01:52:17 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-08 01:52:17 (10379) [INFO] * 2025-10-08 01:52:20 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-08 01:52:20 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-08 01:52:20 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-08 01:52:20 (10379) [INFO] * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-08 01:52:56 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-08 01:52:56 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-08 01:52:56 (10379) [INFO] * 2025-10-08 01:52:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-08 01:52:56 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-08 01:53:28 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-08 01:53:28 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-08 01:53:28 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-08 01:53:28 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-08 01:53:28 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-08 01:53:28 (10392) [INFO] yum --disablerepo= ... * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-08 01:53:28 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-08 01:53:28 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] yum-config-manager --disable * 2025-10-08 01:53:28 (10392) [INFO] or * 2025-10-08 01:53:28 (10392) [INFO] subscription-manager repos --disable= * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-08 01:53:28 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-08 01:53:28 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-08 01:53:28 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-08 01:53:28 (10392) [INFO] compromise: * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-08 01:53:28 (10392) [INFO] * 2025-10-08 01:53:28 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-08 01:53:28 (10409) [INFO] * 2025-10-08 01:53:28 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-08 01:53:28 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-08 01:53:28 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-08 01:53:28 (10379) [INFO] * 2025-10-08 01:53:29 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-08 01:53:29 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-08 01:53:29 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-08 01:53:29 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-08 01:53:29 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-08 01:53:29 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-08 01:53:29 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-08 01:53:29 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-08 01:53:29 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-08 01:53:29 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-08 01:53:29 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-08 01:53:29 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-08 01:53:29 (10409) [INFO] * 2025-10-08 01:53:29 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-08 01:53:29 (10379) [INFO] * 2025-10-08 01:53:30 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-08 01:53:30 (10392) [INFO] Determining fastest mirrors * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-08 01:54:01 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-08 01:54:01 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-08 01:54:01 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-08 01:54:01 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-08 01:54:01 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-08 01:54:01 (10392) [INFO] yum --disablerepo= ... * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-08 01:54:01 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-08 01:54:01 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] yum-config-manager --disable * 2025-10-08 01:54:01 (10392) [INFO] or * 2025-10-08 01:54:01 (10392) [INFO] subscription-manager repos --disable= * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-08 01:54:01 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-08 01:54:01 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-08 01:54:01 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-08 01:54:01 (10392) [INFO] compromise: * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-08 01:54:01 (10392) [INFO] * 2025-10-08 01:54:01 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-08 01:54:01 (10409) [INFO] * 2025-10-08 01:54:01 (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-08 01:54:01 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-08 01:54:02 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-08 01:54:02 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-08 01:54:02 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-08 01:54:02 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-08 01:54:02 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-08 01:54:08 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2pC37u351Z/ea_profile.json * 2025-10-08 01:56:36 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2pC37u351Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-08 01:56:36 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-09 01:47:54 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-09 01:51:55 (11465) [INFO] Script is up to date. * 2025-10-09 01:55:57 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-09 01:55:57 (10379) [INFO] * 2025-10-09 01:57:12 (10409) [INFO] * 2025-10-09 01:57:12 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-09 01:57:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-09 01:57:13 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-09 01:57:13 (10379) [INFO] * 2025-10-09 01:57:16 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-09 01:57:16 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-09 01:57:16 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-09 01:57:16 (10379) [INFO] * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-09 01:57:50 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-09 01:57:50 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-09 01:57:50 (10379) [INFO] * 2025-10-09 01:57:50 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-09 01:57:50 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-09 01:58:21 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-09 01:58:21 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-09 01:58:21 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-09 01:58:21 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-09 01:58:21 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-09 01:58:21 (10392) [INFO] yum --disablerepo= ... * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-09 01:58:21 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-09 01:58:21 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] yum-config-manager --disable * 2025-10-09 01:58:21 (10392) [INFO] or * 2025-10-09 01:58:21 (10392) [INFO] subscription-manager repos --disable= * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-09 01:58:21 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-09 01:58:21 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-09 01:58:21 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-09 01:58:21 (10392) [INFO] compromise: * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-09 01:58:21 (10392) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-09 01:58:21 (10409) [INFO] * 2025-10-09 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-09 01:58:21 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-09 01:58:21 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-09 01:58:21 (10379) [INFO] * 2025-10-09 01:58:21 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-09 01:58:22 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-09 01:58:22 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-09 01:58:22 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-09 01:58:22 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-09 01:58:22 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-09 01:58:22 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-09 01:58:22 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-09 01:58:22 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-09 01:58:22 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-09 01:58:22 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-09 01:58:22 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-09 01:58:22 (10409) [INFO] * 2025-10-09 01:58:22 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-09 01:58:22 (10379) [INFO] * 2025-10-09 01:58:22 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-09 01:58:23 (10392) [INFO] Determining fastest mirrors * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-09 01:58:53 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-09 01:58:53 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-09 01:58:53 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-09 01:58:53 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-09 01:58:53 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-09 01:58:53 (10392) [INFO] yum --disablerepo= ... * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-09 01:58:53 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-09 01:58:53 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] yum-config-manager --disable * 2025-10-09 01:58:53 (10392) [INFO] or * 2025-10-09 01:58:53 (10392) [INFO] subscription-manager repos --disable= * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-09 01:58:53 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-09 01:58:53 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-09 01:58:53 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-09 01:58:53 (10392) [INFO] compromise: * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-09 01:58:53 (10392) [INFO] * 2025-10-09 01:58:53 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-09 01:58:53 (10409) [INFO] * 2025-10-09 01:58: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-10-09 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-09 01:58:54 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-09 01:58:54 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-09 01:58:54 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-09 01:58:54 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-09 01:58:54 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-09 01:59:00 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/n5A_AriXvP/ea_profile.json * 2025-10-09 02:01:56 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/n5A_AriXvP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-09 02:01:56 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-10 01:43:21 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-10 01:47:21 (11465) [INFO] Script is up to date. * 2025-10-10 01:51:25 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-10 01:51:25 (10379) [INFO] * 2025-10-10 01:52:42 (10409) [INFO] * 2025-10-10 01:52:42 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-10 01:52:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-10 01:52:42 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-10 01:52:42 (10379) [INFO] * 2025-10-10 01:52:46 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-10 01:52:46 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-10 01:52:46 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-10 01:52:46 (10379) [INFO] * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-10 01:53:22 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-10 01:53:22 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-10 01:53:22 (10379) [INFO] * 2025-10-10 01:53:23 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-10 01:53:23 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-10 01:53:54 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-10 01:53:54 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-10 01:53:54 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-10 01:53:54 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-10 01:53:54 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-10 01:53:54 (10392) [INFO] yum --disablerepo= ... * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-10 01:53:54 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-10 01:53:54 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] yum-config-manager --disable * 2025-10-10 01:53:54 (10392) [INFO] or * 2025-10-10 01:53:54 (10392) [INFO] subscription-manager repos --disable= * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-10 01:53:54 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-10 01:53:54 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-10 01:53:54 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-10 01:53:54 (10392) [INFO] compromise: * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-10 01:53:54 (10392) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-10 01:53:54 (10409) [INFO] * 2025-10-10 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-10 01:53:54 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-10 01:53:54 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-10 01:53:54 (10379) [INFO] * 2025-10-10 01:53:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-10 01:53:55 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-10 01:53:55 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-10 01:53:55 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-10 01:53:55 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-10 01:53:55 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-10 01:53:55 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-10 01:53:55 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-10 01:53:55 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-10 01:53:55 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-10 01:53:55 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-10 01:53:55 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-10 01:53:55 (10409) [INFO] * 2025-10-10 01:53:55 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-10 01:53:55 (10379) [INFO] * 2025-10-10 01:53:55 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-10 01:53:56 (10392) [INFO] Determining fastest mirrors * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-10 01:54:26 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-10 01:54:26 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-10 01:54:26 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-10 01:54:26 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-10 01:54:26 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-10 01:54:26 (10392) [INFO] yum --disablerepo= ... * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-10 01:54:26 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-10 01:54:26 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] yum-config-manager --disable * 2025-10-10 01:54:26 (10392) [INFO] or * 2025-10-10 01:54:26 (10392) [INFO] subscription-manager repos --disable= * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-10 01:54:26 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-10 01:54:26 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-10 01:54:26 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-10 01:54:26 (10392) [INFO] compromise: * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-10 01:54:26 (10392) [INFO] * 2025-10-10 01:54:26 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-10 01:54:26 (10409) [INFO] * 2025-10-10 01:54: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-10-10 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-10 01:54:27 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-10 01:54:27 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-10 01:54:28 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-10 01:54:28 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-10 01:54:28 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-10 01:54:33 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/e4nzbMeCKU/ea_profile.json * 2025-10-10 01:56:59 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/e4nzbMeCKU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-10 01:56:59 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-11 01:49:08 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-11 01:53:08 (11465) [INFO] Script is up to date. * 2025-10-11 01:57:12 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-11 01:57:12 (10379) [INFO] * 2025-10-11 01:58:02 (10409) [INFO] * 2025-10-11 01:58:02 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-11 01:58:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-11 01:58:03 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-11 01:58:03 (10379) [INFO] * 2025-10-11 01:58:07 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-11 01:58:07 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-11 01:58:07 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-11 01:58:07 (10379) [INFO] * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-11 01:58:43 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-11 01:58:43 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-11 01:58:43 (10379) [INFO] * 2025-10-11 01:58:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-11 01:58:44 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-11 01:59:16 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-11 01:59:16 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-11 01:59:16 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-11 01:59:16 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-11 01:59:16 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-11 01:59:16 (10392) [INFO] yum --disablerepo= ... * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-11 01:59:16 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-11 01:59:16 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] yum-config-manager --disable * 2025-10-11 01:59:16 (10392) [INFO] or * 2025-10-11 01:59:16 (10392) [INFO] subscription-manager repos --disable= * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-11 01:59:16 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-11 01:59:16 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-11 01:59:16 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-11 01:59:16 (10392) [INFO] compromise: * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-11 01:59:16 (10392) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-11 01:59:16 (10409) [INFO] * 2025-10-11 01:59:16 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-11 01:59:16 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-11 01:59:16 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-11 01:59:16 (10379) [INFO] * 2025-10-11 01:59:16 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-11 01:59:17 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-11 01:59:17 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-11 01:59:17 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-11 01:59:17 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-11 01:59:17 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-11 01:59:17 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-11 01:59:17 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-11 01:59:17 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-11 01:59:17 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-11 01:59:17 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-11 01:59:17 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-11 01:59:17 (10409) [INFO] * 2025-10-11 01:59:17 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-11 01:59:17 (10379) [INFO] * 2025-10-11 01:59:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-11 01:59:18 (10392) [INFO] Determining fastest mirrors * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-11 01:59:48 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-11 01:59:48 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-11 01:59:48 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-11 01:59:48 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-11 01:59:48 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-11 01:59:48 (10392) [INFO] yum --disablerepo= ... * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-11 01:59:48 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-11 01:59:48 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] yum-config-manager --disable * 2025-10-11 01:59:48 (10392) [INFO] or * 2025-10-11 01:59:48 (10392) [INFO] subscription-manager repos --disable= * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-11 01:59:48 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-11 01:59:48 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-11 01:59:48 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-11 01:59:48 (10392) [INFO] compromise: * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-11 01:59:48 (10392) [INFO] * 2025-10-11 01:59:48 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-11 01:59:48 (10409) [INFO] * 2025-10-11 01:59: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-10-11 01:59: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-11 01:59:50 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-11 01:59:50 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-11 01:59:50 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-11 01:59:50 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-11 01:59:50 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-11 01:59:57 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gOT8uS3juO/ea_profile.json * 2025-10-11 02:03:29 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gOT8uS3juO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-11 02:03:29 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-12 01:46:32 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-12 01:50:32 (11465) [INFO] Script is up to date. * 2025-10-12 01:54:35 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-12 01:54:35 (10379) [INFO] * 2025-10-12 01:55:32 (10409) [INFO] * 2025-10-12 01:55:32 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-12 01:55:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-12 01:55:32 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-12 01:55:32 (10379) [INFO] * 2025-10-12 01:55:35 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-12 01:55:35 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-12 01:55:35 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-12 01:55:35 (10379) [INFO] * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-12 01:56:11 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-12 01:56:11 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-12 01:56:11 (10379) [INFO] * 2025-10-12 01:56:11 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-12 01:56:11 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-12 01:56:43 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-12 01:56:43 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-12 01:56:43 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-12 01:56:43 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-12 01:56:43 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-12 01:56:43 (10392) [INFO] yum --disablerepo= ... * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-12 01:56:43 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-12 01:56:43 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] yum-config-manager --disable * 2025-10-12 01:56:43 (10392) [INFO] or * 2025-10-12 01:56:43 (10392) [INFO] subscription-manager repos --disable= * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-12 01:56:43 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-12 01:56:43 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-12 01:56:43 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-12 01:56:43 (10392) [INFO] compromise: * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-12 01:56:43 (10392) [INFO] * 2025-10-12 01:56:43 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-12 01:56:43 (10409) [INFO] * 2025-10-12 01:56: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-12 01:56:43 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-12 01:56:43 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-12 01:56:43 (10379) [INFO] * 2025-10-12 01:56:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-12 01:56:44 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-12 01:56:44 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-12 01:56:44 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-12 01:56:44 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-12 01:56:44 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-12 01:56:44 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-12 01:56:44 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-12 01:56:44 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-12 01:56:44 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-12 01:56:44 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-12 01:56:44 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-12 01:56:44 (10409) [INFO] * 2025-10-12 01:56:44 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-12 01:56:44 (10379) [INFO] * 2025-10-12 01:56:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-12 01:56:45 (10392) [INFO] Determining fastest mirrors * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-12 01:57:16 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-12 01:57:16 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-12 01:57:16 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-12 01:57:16 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-12 01:57:16 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-12 01:57:16 (10392) [INFO] yum --disablerepo= ... * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-12 01:57:16 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-12 01:57:16 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] yum-config-manager --disable * 2025-10-12 01:57:16 (10392) [INFO] or * 2025-10-12 01:57:16 (10392) [INFO] subscription-manager repos --disable= * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-12 01:57:16 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-12 01:57:16 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-12 01:57:16 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-12 01:57:16 (10392) [INFO] compromise: * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-12 01:57:16 (10392) [INFO] * 2025-10-12 01:57:16 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-12 01:57:16 (10409) [INFO] * 2025-10-12 01:57: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-10-12 01:57: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-12 01:57:17 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-12 01:57:17 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-12 01:57:17 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-12 01:57:17 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-12 01:57:17 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-12 01:57:24 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cGgGM89QDX/ea_profile.json * 2025-10-12 01:59:51 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cGgGM89QDX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-12 01:59:51 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-13 01:43:21 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-13 01:47:22 (11465) [INFO] Script is up to date. * 2025-10-13 01:51:25 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-13 01:51:25 (10379) [INFO] * 2025-10-13 01:52:34 (10409) [INFO] * 2025-10-13 01:52:34 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-13 01:52:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-13 01:52:34 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-13 01:52:34 (10379) [INFO] * 2025-10-13 01:52:37 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-13 01:52:37 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-13 01:52:37 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-13 01:52:37 (10379) [INFO] * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-13 01:53:14 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-13 01:53:14 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-13 01:53:14 (10379) [INFO] * 2025-10-13 01:53:14 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-13 01:53:15 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-13 01:53:46 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-13 01:53:46 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-13 01:53:46 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-13 01:53:46 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-13 01:53:46 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-13 01:53:46 (10392) [INFO] yum --disablerepo= ... * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-13 01:53:46 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-13 01:53:46 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] yum-config-manager --disable * 2025-10-13 01:53:46 (10392) [INFO] or * 2025-10-13 01:53:46 (10392) [INFO] subscription-manager repos --disable= * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-13 01:53:46 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-13 01:53:46 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-13 01:53:46 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-13 01:53:46 (10392) [INFO] compromise: * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-13 01:53:46 (10392) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-13 01:53:46 (10409) [INFO] * 2025-10-13 01:53: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-13 01:53:46 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-13 01:53:46 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-13 01:53:46 (10379) [INFO] * 2025-10-13 01:53:46 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-13 01:53:47 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-13 01:53:47 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-13 01:53:47 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-13 01:53:47 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-13 01:53:47 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-13 01:53:47 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-13 01:53:47 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-13 01:53:47 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-13 01:53:47 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-13 01:53:47 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-13 01:53:47 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-13 01:53:47 (10409) [INFO] * 2025-10-13 01:53:47 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-13 01:53:47 (10379) [INFO] * 2025-10-13 01:53:47 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-13 01:53:47 (10392) [INFO] Determining fastest mirrors * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-13 01:54:18 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-13 01:54:18 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-13 01:54:18 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-13 01:54:18 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-13 01:54:18 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-13 01:54:18 (10392) [INFO] yum --disablerepo= ... * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-13 01:54:18 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-13 01:54:18 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] yum-config-manager --disable * 2025-10-13 01:54:18 (10392) [INFO] or * 2025-10-13 01:54:18 (10392) [INFO] subscription-manager repos --disable= * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-13 01:54:18 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-13 01:54:18 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-13 01:54:18 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-13 01:54:18 (10392) [INFO] compromise: * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-13 01:54:18 (10392) [INFO] * 2025-10-13 01:54:18 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-13 01:54:18 (10409) [INFO] * 2025-10-13 01:54:18 (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-13 01:54:18 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-13 01:54:19 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-13 01:54:19 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-13 01:54:19 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-13 01:54:19 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-13 01:54:19 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-13 01:54:25 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2SSMjIBO8N/ea_profile.json * 2025-10-13 01:56:57 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2SSMjIBO8N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-13 01:56:57 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-14 01:43:36 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-14 01:47:36 (11465) [INFO] Script is up to date. * 2025-10-14 01:51:40 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-14 01:51:40 (10379) [INFO] * 2025-10-14 01:52:55 (10409) [INFO] * 2025-10-14 01:52:55 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-14 01:52:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-14 01:52:56 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-14 01:52:56 (10379) [INFO] * 2025-10-14 01:53:00 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-14 01:53:00 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-14 01:53:00 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-14 01:53:00 (10379) [INFO] * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-14 01:53:35 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-14 01:53:35 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-14 01:53:35 (10379) [INFO] * 2025-10-14 01:53:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-14 01:53:36 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-14 01:54:07 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-14 01:54:07 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-14 01:54:07 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-14 01:54:07 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-14 01:54:07 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-14 01:54:07 (10392) [INFO] yum --disablerepo= ... * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-14 01:54:07 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-14 01:54:07 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] yum-config-manager --disable * 2025-10-14 01:54:07 (10392) [INFO] or * 2025-10-14 01:54:07 (10392) [INFO] subscription-manager repos --disable= * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-14 01:54:07 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-14 01:54:07 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-14 01:54:07 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-14 01:54:07 (10392) [INFO] compromise: * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-14 01:54:07 (10392) [INFO] * 2025-10-14 01:54:07 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-14 01:54:07 (10409) [INFO] * 2025-10-14 01:54:07 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-14 01:54:07 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-14 01:54:07 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-14 01:54:07 (10379) [INFO] * 2025-10-14 01:54:08 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-14 01:54:08 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-14 01:54:08 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-14 01:54:08 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-14 01:54:08 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-14 01:54:08 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-14 01:54:08 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-14 01:54:08 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-14 01:54:08 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-14 01:54:08 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-14 01:54:08 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-14 01:54:08 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-14 01:54:08 (10409) [INFO] * 2025-10-14 01:54:08 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-14 01:54:08 (10379) [INFO] * 2025-10-14 01:54:09 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-14 01:54:09 (10392) [INFO] Determining fastest mirrors * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-14 01:54:40 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-14 01:54:40 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-14 01:54:40 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-14 01:54:40 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-14 01:54:40 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-14 01:54:40 (10392) [INFO] yum --disablerepo= ... * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-14 01:54:40 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-14 01:54:40 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] yum-config-manager --disable * 2025-10-14 01:54:40 (10392) [INFO] or * 2025-10-14 01:54:40 (10392) [INFO] subscription-manager repos --disable= * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-14 01:54:40 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-14 01:54:40 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-14 01:54:40 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-14 01:54:40 (10392) [INFO] compromise: * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-14 01:54:40 (10392) [INFO] * 2025-10-14 01:54:40 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-14 01:54:40 (10409) [INFO] * 2025-10-14 01:54: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-10-14 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-14 01:54:42 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-14 01:54:42 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-14 01:54:42 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-14 01:54:42 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-14 01:54:42 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-14 01:54:48 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jMM7SMfYS4/ea_profile.json * 2025-10-14 01:58:19 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jMM7SMfYS4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-14 01:58:19 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-15 01:43:44 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-15 01:47:45 (11465) [INFO] Script is up to date. * 2025-10-15 01:51:47 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-15 01:51:47 (10379) [INFO] * 2025-10-15 01:53:04 (10409) [INFO] * 2025-10-15 01:53:04 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-15 01:53:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-15 01:53:05 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-15 01:53:05 (10379) [INFO] * 2025-10-15 01:53:09 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-15 01:53:09 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-15 01:53:09 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-15 01:53:09 (10379) [INFO] * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-15 01:53:45 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-15 01:53:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-15 01:53:45 (10379) [INFO] * 2025-10-15 01:53:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-15 01:53:46 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-15 01:54:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-15 01:54:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-15 01:54:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-15 01:54:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-15 01:54:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-15 01:54:17 (10392) [INFO] yum --disablerepo= ... * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-15 01:54:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-15 01:54:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] yum-config-manager --disable * 2025-10-15 01:54:17 (10392) [INFO] or * 2025-10-15 01:54:17 (10392) [INFO] subscription-manager repos --disable= * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-15 01:54:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-15 01:54:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-15 01:54:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-15 01:54:17 (10392) [INFO] compromise: * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-15 01:54:17 (10392) [INFO] * 2025-10-15 01:54:17 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-15 01:54:17 (10409) [INFO] * 2025-10-15 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-15 01:54:17 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-15 01:54:17 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-15 01:54:17 (10379) [INFO] * 2025-10-15 01:54:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-15 01:54:18 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-15 01:54:18 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-15 01:54:18 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-15 01:54:18 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-15 01:54:18 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-15 01:54:18 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-15 01:54:18 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-15 01:54:18 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-15 01:54:18 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-15 01:54:18 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-15 01:54:18 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-15 01:54:18 (10409) [INFO] * 2025-10-15 01:54:18 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-15 01:54:18 (10379) [INFO] * 2025-10-15 01:54:19 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-15 01:54:19 (10392) [INFO] Determining fastest mirrors * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-15 01:54:53 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-15 01:54:53 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-15 01:54:53 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-15 01:54:53 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-15 01:54:53 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-15 01:54:53 (10392) [INFO] yum --disablerepo= ... * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-15 01:54:53 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-15 01:54:53 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] yum-config-manager --disable * 2025-10-15 01:54:53 (10392) [INFO] or * 2025-10-15 01:54:53 (10392) [INFO] subscription-manager repos --disable= * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-15 01:54:53 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-15 01:54:53 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-15 01:54:53 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-15 01:54:53 (10392) [INFO] compromise: * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-15 01:54:53 (10392) [INFO] * 2025-10-15 01:54:53 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-15 01:54:53 (10409) [INFO] * 2025-10-15 01:54: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-10-15 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-15 01:54:54 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-15 01:54:54 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-15 01:54:54 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-15 01:54:54 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-15 01:54:54 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-15 01:55:00 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KguW8QLWzw/ea_profile.json * 2025-10-15 01:57:59 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KguW8QLWzw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-15 01:57:59 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-16 00:49:34 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-16 00:53:35 (11465) [INFO] Script is up to date. * 2025-10-16 00:57:38 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-16 00:57:38 (10379) [INFO] * 2025-10-16 00:58:57 (10409) [INFO] * 2025-10-16 00:58:57 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-16 00:58:58 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-16 00:58:58 (10379) [INFO] * 2025-10-16 01:05:55 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-16 01:05:55 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-16 01:05:55 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-16 01:05:55 (10379) [INFO] * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-16 01:06:32 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-16 01:06:32 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-16 01:06:32 (10379) [INFO] * 2025-10-16 01:06:32 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-16 01:06:33 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-16 01:07:07 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-16 01:07:07 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-16 01:07:07 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-16 01:07:07 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-16 01:07:07 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-16 01:07:07 (10392) [INFO] yum --disablerepo= ... * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-16 01:07:07 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-16 01:07:07 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] yum-config-manager --disable * 2025-10-16 01:07:07 (10392) [INFO] or * 2025-10-16 01:07:07 (10392) [INFO] subscription-manager repos --disable= * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-16 01:07:07 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-16 01:07:07 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-16 01:07:07 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-16 01:07:07 (10392) [INFO] compromise: * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-16 01:07:07 (10392) [INFO] * 2025-10-16 01:07:07 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-16 01:07:07 (10409) [INFO] * 2025-10-16 01:07:07 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-16 01:07:07 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-16 01:07:07 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-16 01:07:07 (10379) [INFO] * 2025-10-16 01:07:08 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-16 01:07:08 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-16 01:07:08 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-16 01:07:08 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-16 01:07:08 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-16 01:07:08 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-16 01:07:08 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-16 01:07:08 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-16 01:07:08 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-16 01:07:08 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-16 01:07:08 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-16 01:07:08 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-16 01:07:08 (10409) [INFO] * 2025-10-16 01:07:08 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-16 01:07:08 (10379) [INFO] * 2025-10-16 01:07:09 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-16 01:07:09 (10392) [INFO] Determining fastest mirrors * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-16 01:07:41 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-16 01:07:41 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-16 01:07:41 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-16 01:07:41 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-16 01:07:41 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-16 01:07:41 (10392) [INFO] yum --disablerepo= ... * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-16 01:07:41 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-16 01:07:41 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] yum-config-manager --disable * 2025-10-16 01:07:41 (10392) [INFO] or * 2025-10-16 01:07:41 (10392) [INFO] subscription-manager repos --disable= * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-16 01:07:41 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-16 01:07:41 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-16 01:07:41 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-16 01:07:41 (10392) [INFO] compromise: * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-16 01:07:41 (10392) [INFO] * 2025-10-16 01:07:41 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-16 01:07:41 (10409) [INFO] * 2025-10-16 01:07: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-10-16 01:07: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-16 01:07:43 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-16 01:07:43 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-16 01:07:43 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-16 01:07:43 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-16 01:07:43 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-16 01:07:49 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/EcOXzMhHAp/ea_profile.json * 2025-10-16 01:10:18 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/EcOXzMhHAp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-16 01:10:18 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-17 01:53:37 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-17 01:57:37 (11465) [INFO] Script is up to date. * 2025-10-17 02:01:40 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-17 02:01:40 (10379) [INFO] * 2025-10-17 02:02:58 (10409) [INFO] * 2025-10-17 02:02:58 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-17 02:02:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-17 02:02:59 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-17 02:02:59 (10379) [INFO] * 2025-10-17 02:07:01 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-17 02:07:01 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-17 02:07:01 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-17 02:07:01 (10379) [INFO] * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-17 02:07:34 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-17 02:07:34 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-17 02:07:34 (10379) [INFO] * 2025-10-17 02:07:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-17 02:07:35 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-17 02:08:06 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-17 02:08:06 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-17 02:08:06 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-17 02:08:06 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-17 02:08:06 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-17 02:08:06 (10392) [INFO] yum --disablerepo= ... * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-17 02:08:06 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-17 02:08:06 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] yum-config-manager --disable * 2025-10-17 02:08:06 (10392) [INFO] or * 2025-10-17 02:08:06 (10392) [INFO] subscription-manager repos --disable= * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-17 02:08:06 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-17 02:08:06 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-17 02:08:06 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-17 02:08:06 (10392) [INFO] compromise: * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-17 02:08:06 (10392) [INFO] * 2025-10-17 02:08:06 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-17 02:08:06 (10409) [INFO] * 2025-10-17 02:08:06 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-17 02:08:06 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-17 02:08:06 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-17 02:08:06 (10379) [INFO] * 2025-10-17 02:08:07 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-17 02:08:07 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-17 02:08:07 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-17 02:08:07 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-17 02:08:07 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-17 02:08:07 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-17 02:08:07 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-17 02:08:07 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-17 02:08:07 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-17 02:08:07 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-17 02:08:07 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-17 02:08:07 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-17 02:08:07 (10409) [INFO] * 2025-10-17 02:08:07 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-17 02:08:07 (10379) [INFO] * 2025-10-17 02:08:08 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-17 02:08:08 (10392) [INFO] Determining fastest mirrors * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-17 02:08:39 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-17 02:08:39 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-17 02:08:39 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-17 02:08:39 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-17 02:08:39 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-17 02:08:39 (10392) [INFO] yum --disablerepo= ... * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-17 02:08:39 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-17 02:08:39 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] yum-config-manager --disable * 2025-10-17 02:08:39 (10392) [INFO] or * 2025-10-17 02:08:39 (10392) [INFO] subscription-manager repos --disable= * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-17 02:08:39 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-17 02:08:39 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-17 02:08:39 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-17 02:08:39 (10392) [INFO] compromise: * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-17 02:08:39 (10392) [INFO] * 2025-10-17 02:08:39 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-17 02:08:39 (10409) [INFO] * 2025-10-17 02:08: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-10-17 02:08: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-17 02:08:41 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-17 02:08:41 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-17 02:08:41 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-17 02:08:41 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-17 02:08:41 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-17 02:08:49 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SIL6qgA26Z/ea_profile.json * 2025-10-17 02:11:35 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/SIL6qgA26Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-17 02:11:35 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-18 01:44:38 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-18 01:48:39 (11465) [INFO] Script is up to date. * 2025-10-18 01:52:42 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-18 01:52:42 (10379) [INFO] * 2025-10-18 01:53:31 (10409) [INFO] * 2025-10-18 01:53:31 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-18 01:53:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-18 01:53:32 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-18 01:53:32 (10379) [INFO] * 2025-10-18 02:00:35 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-18 02:00:35 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-18 02:00:35 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-18 02:00:35 (10379) [INFO] * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-18 02:01:11 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-18 02:01:11 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-18 02:01:11 (10379) [INFO] * 2025-10-18 02:01:11 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-18 02:01:12 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-18 02:01:43 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-18 02:01:43 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-18 02:01:43 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-18 02:01:43 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-18 02:01:43 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-18 02:01:43 (10392) [INFO] yum --disablerepo= ... * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-18 02:01:43 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-18 02:01:43 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] yum-config-manager --disable * 2025-10-18 02:01:43 (10392) [INFO] or * 2025-10-18 02:01:43 (10392) [INFO] subscription-manager repos --disable= * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-18 02:01:43 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-18 02:01:43 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-18 02:01:43 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-18 02:01:43 (10392) [INFO] compromise: * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-18 02:01:43 (10392) [INFO] * 2025-10-18 02:01:43 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-18 02:01:43 (10409) [INFO] * 2025-10-18 02:01: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-18 02:01:43 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-18 02:01:43 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-18 02:01:43 (10379) [INFO] * 2025-10-18 02:01:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-18 02:01:44 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-18 02:01:44 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-18 02:01:44 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-18 02:01:44 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-18 02:01:44 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-18 02:01:44 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-18 02:01:44 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-18 02:01:44 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-18 02:01:44 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-18 02:01:44 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-18 02:01:44 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-18 02:01:44 (10409) [INFO] * 2025-10-18 02:01:44 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-18 02:01:44 (10379) [INFO] * 2025-10-18 02:01:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-18 02:01:45 (10392) [INFO] Determining fastest mirrors * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-18 02:02:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-18 02:02:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-18 02:02:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-18 02:02:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-18 02:02:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-18 02:02:17 (10392) [INFO] yum --disablerepo= ... * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-18 02:02:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-18 02:02:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] yum-config-manager --disable * 2025-10-18 02:02:17 (10392) [INFO] or * 2025-10-18 02:02:17 (10392) [INFO] subscription-manager repos --disable= * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-18 02:02:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-18 02:02:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-18 02:02:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-18 02:02:17 (10392) [INFO] compromise: * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-18 02:02:17 (10392) [INFO] * 2025-10-18 02:02:17 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-18 02:02:17 (10409) [INFO] * 2025-10-18 02:02: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-10-18 02:02: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-18 02:02:18 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-18 02:02:18 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-18 02:02:18 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-18 02:02:18 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-18 02:02:18 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-18 02:02:25 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xOrBsuEISn/ea_profile.json * 2025-10-18 02:05:26 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xOrBsuEISn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-18 02:05:26 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-19 01:44:27 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-19 01:48:27 (11465) [INFO] Script is up to date. * 2025-10-19 01:52:30 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-19 01:52:30 (10379) [INFO] * 2025-10-19 01:53:27 (10409) [INFO] * 2025-10-19 01:53:27 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-19 01:53:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-19 01:53:27 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-19 01:53:27 (10379) [INFO] * 2025-10-19 02:00:34 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-19 02:00:34 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-19 02:00:34 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-19 02:00:34 (10379) [INFO] * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-19 02:01:09 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-19 02:01:09 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-19 02:01:09 (10379) [INFO] * 2025-10-19 02:01:09 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-19 02:01:10 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-19 02:01:41 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-19 02:01:41 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-19 02:01:41 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-19 02:01:41 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-19 02:01:41 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-19 02:01:41 (10392) [INFO] yum --disablerepo= ... * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-19 02:01:41 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-19 02:01:41 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] yum-config-manager --disable * 2025-10-19 02:01:41 (10392) [INFO] or * 2025-10-19 02:01:41 (10392) [INFO] subscription-manager repos --disable= * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-19 02:01:41 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-19 02:01:41 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-19 02:01:41 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-19 02:01:41 (10392) [INFO] compromise: * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-19 02:01:41 (10392) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-19 02:01:41 (10409) [INFO] * 2025-10-19 02:01:41 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-19 02:01:41 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-19 02:01:41 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-19 02:01:41 (10379) [INFO] * 2025-10-19 02:01:41 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-19 02:01:42 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-19 02:01:42 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-19 02:01:42 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-19 02:01:42 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-19 02:01:42 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-19 02:01:42 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-19 02:01:42 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-19 02:01:42 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-19 02:01:42 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-19 02:01:42 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-19 02:01:42 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-19 02:01:42 (10409) [INFO] * 2025-10-19 02:01:42 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-19 02:01:42 (10379) [INFO] * 2025-10-19 02:01:42 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-19 02:01:43 (10392) [INFO] Determining fastest mirrors * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-19 02:02:14 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-19 02:02:14 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-19 02:02:14 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-19 02:02:14 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-19 02:02:14 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-19 02:02:14 (10392) [INFO] yum --disablerepo= ... * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-19 02:02:14 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-19 02:02:14 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] yum-config-manager --disable * 2025-10-19 02:02:14 (10392) [INFO] or * 2025-10-19 02:02:14 (10392) [INFO] subscription-manager repos --disable= * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-19 02:02:14 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-19 02:02:14 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-19 02:02:14 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-19 02:02:14 (10392) [INFO] compromise: * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-19 02:02:14 (10392) [INFO] * 2025-10-19 02:02:14 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-19 02:02:14 (10409) [INFO] * 2025-10-19 02:02: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-10-19 02:02: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-19 02:02:16 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-19 02:02:16 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-19 02:02:16 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-19 02:02:16 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-19 02:02:16 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-19 02:02:22 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UlnbAKFgmg/ea_profile.json * 2025-10-19 02:05:21 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UlnbAKFgmg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-19 02:05:21 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-20 01:43:48 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-20 01:47:49 (11465) [INFO] Script is up to date. * 2025-10-20 01:51:52 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-20 01:51:52 (10379) [INFO] * 2025-10-20 01:53:15 (10409) [INFO] * 2025-10-20 01:53:15 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-20 01:53:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-20 01:53:15 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-20 01:53:15 (10379) [INFO] * 2025-10-20 02:00:17 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-20 02:00:17 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-20 02:00:17 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-20 02:00:17 (10379) [INFO] * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-20 02:00:53 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-20 02:00:53 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-20 02:00:53 (10379) [INFO] * 2025-10-20 02:00:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-20 02:00:54 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-20 02:01:25 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-20 02:01:25 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-20 02:01:25 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-20 02:01:25 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-20 02:01:25 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-20 02:01:25 (10392) [INFO] yum --disablerepo= ... * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-20 02:01:25 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-20 02:01:25 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] yum-config-manager --disable * 2025-10-20 02:01:25 (10392) [INFO] or * 2025-10-20 02:01:25 (10392) [INFO] subscription-manager repos --disable= * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-20 02:01:25 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-20 02:01:25 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-20 02:01:25 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-20 02:01:25 (10392) [INFO] compromise: * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-20 02:01:25 (10392) [INFO] * 2025-10-20 02:01:25 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-20 02:01:25 (10409) [INFO] * 2025-10-20 02:01:25 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-20 02:01:25 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-20 02:01:25 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-20 02:01:25 (10379) [INFO] * 2025-10-20 02:01:26 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-20 02:01:26 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-20 02:01:26 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-20 02:01:26 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-20 02:01:26 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-20 02:01:26 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-20 02:01:26 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-20 02:01:26 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-20 02:01:26 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-20 02:01:26 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-20 02:01:26 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-20 02:01:26 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-20 02:01:26 (10409) [INFO] * 2025-10-20 02:01:26 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-20 02:01:26 (10379) [INFO] * 2025-10-20 02:01:27 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-20 02:01:27 (10392) [INFO] Determining fastest mirrors * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-20 02:01:57 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-20 02:01:57 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-20 02:01:57 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-20 02:01:57 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-20 02:01:57 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-20 02:01:57 (10392) [INFO] yum --disablerepo= ... * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-20 02:01:57 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-20 02:01:57 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] yum-config-manager --disable * 2025-10-20 02:01:57 (10392) [INFO] or * 2025-10-20 02:01:57 (10392) [INFO] subscription-manager repos --disable= * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-20 02:01:57 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-20 02:01:57 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-20 02:01:57 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-20 02:01:57 (10392) [INFO] compromise: * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-20 02:01:57 (10392) [INFO] * 2025-10-20 02:01:57 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-20 02:01:57 (10409) [INFO] * 2025-10-20 02:01:57 (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-20 02:01:57 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-20 02:01:59 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-20 02:01:59 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-20 02:01:59 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-20 02:01:59 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-20 02:01:59 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-20 02:02:05 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2d5BicI4Bd/ea_profile.json * 2025-10-20 02:04:34 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2d5BicI4Bd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-20 02:04:34 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-21 01:43:15 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-21 01:47:15 (11465) [INFO] Script is up to date. * 2025-10-21 01:51:18 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-21 01:51:18 (10379) [INFO] * 2025-10-21 01:52:28 (10409) [INFO] * 2025-10-21 01:52:28 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-21 01:52:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-21 01:52:28 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-21 01:52:28 (10379) [INFO] * 2025-10-21 01:59:25 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-21 01:59:25 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-21 01:59:25 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-21 01:59:25 (10379) [INFO] * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-21 02:00:00 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-21 02:00:00 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-21 02:00:00 (10379) [INFO] * 2025-10-21 02:00:01 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-21 02:00:01 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-21 02:00:32 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-21 02:00:32 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-21 02:00:32 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-21 02:00:32 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-21 02:00:32 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-21 02:00:32 (10392) [INFO] yum --disablerepo= ... * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-21 02:00:32 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-21 02:00:32 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] yum-config-manager --disable * 2025-10-21 02:00:32 (10392) [INFO] or * 2025-10-21 02:00:32 (10392) [INFO] subscription-manager repos --disable= * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-21 02:00:32 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-21 02:00:32 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-21 02:00:32 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-21 02:00:32 (10392) [INFO] compromise: * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-21 02:00:32 (10392) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-21 02:00:32 (10409) [INFO] * 2025-10-21 02:00:32 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-21 02:00:32 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-21 02:00:32 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-21 02:00:32 (10379) [INFO] * 2025-10-21 02:00:32 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-21 02:00:32 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-21 02:00:32 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-21 02:00:32 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-21 02:00:32 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-21 02:00:32 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-21 02:00:32 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-21 02:00:32 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-21 02:00:32 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-21 02:00:32 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-21 02:00:32 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-21 02:00:32 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-21 02:00:32 (10409) [INFO] * 2025-10-21 02:00:32 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-21 02:00:32 (10379) [INFO] * 2025-10-21 02:00:33 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-21 02:00:33 (10392) [INFO] Determining fastest mirrors * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-21 02:01:05 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-21 02:01:05 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-21 02:01:05 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-21 02:01:05 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-21 02:01:05 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-21 02:01:05 (10392) [INFO] yum --disablerepo= ... * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-21 02:01:05 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-21 02:01:05 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] yum-config-manager --disable * 2025-10-21 02:01:05 (10392) [INFO] or * 2025-10-21 02:01:05 (10392) [INFO] subscription-manager repos --disable= * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-21 02:01:05 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-21 02:01:05 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-21 02:01:05 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-21 02:01:05 (10392) [INFO] compromise: * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-21 02:01:05 (10392) [INFO] * 2025-10-21 02:01:05 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-21 02:01:05 (10409) [INFO] * 2025-10-21 02:01: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-10-21 02:01: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-21 02:01:06 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-21 02:01:06 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-21 02:01:06 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-21 02:01:06 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-21 02:01:06 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-21 02:01:12 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kR9EHBVo3H/ea_profile.json * 2025-10-21 02:04:03 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kR9EHBVo3H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-21 02:04:03 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-22 01:42:57 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-22 01:46:58 (11465) [INFO] Script is up to date. * 2025-10-22 01:51:01 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-22 01:51:01 (10379) [INFO] * 2025-10-22 01:52:24 (10409) [INFO] * 2025-10-22 01:52:24 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-22 01:52:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-22 01:52:25 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-22 01:52:25 (10379) [INFO] * 2025-10-22 01:59:24 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-22 01:59:24 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-22 01:59:24 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-22 01:59:24 (10379) [INFO] * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-22 02:00:00 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-22 02:00:00 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-22 02:00:00 (10379) [INFO] * 2025-10-22 02:00:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-22 02:00:01 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-22 02:00:32 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-22 02:00:32 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-22 02:00:32 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-22 02:00:32 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-22 02:00:32 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-22 02:00:32 (10392) [INFO] yum --disablerepo= ... * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-22 02:00:32 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-22 02:00:32 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] yum-config-manager --disable * 2025-10-22 02:00:32 (10392) [INFO] or * 2025-10-22 02:00:32 (10392) [INFO] subscription-manager repos --disable= * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-22 02:00:32 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-22 02:00:32 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-22 02:00:32 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-22 02:00:32 (10392) [INFO] compromise: * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-22 02:00:32 (10392) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-22 02:00:32 (10409) [INFO] * 2025-10-22 02:00:32 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-22 02:00:32 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-22 02:00:32 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-22 02:00:32 (10379) [INFO] * 2025-10-22 02:00:32 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-22 02:00:32 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-22 02:00:32 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-22 02:00:32 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-22 02:00:32 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-22 02:00:32 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-22 02:00:32 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-22 02:00:32 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-22 02:00:32 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-22 02:00:32 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-22 02:00:32 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-22 02:00:32 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-22 02:00:32 (10409) [INFO] * 2025-10-22 02:00:32 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-22 02:00:32 (10379) [INFO] * 2025-10-22 02:00:33 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-22 02:00:33 (10392) [INFO] Determining fastest mirrors * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-22 02:01:04 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-22 02:01:04 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-22 02:01:04 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-22 02:01:04 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-22 02:01:04 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-22 02:01:04 (10392) [INFO] yum --disablerepo= ... * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-22 02:01:04 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-22 02:01:04 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] yum-config-manager --disable * 2025-10-22 02:01:04 (10392) [INFO] or * 2025-10-22 02:01:04 (10392) [INFO] subscription-manager repos --disable= * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-22 02:01:04 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-22 02:01:04 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-22 02:01:04 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-22 02:01:04 (10392) [INFO] compromise: * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-22 02:01:04 (10392) [INFO] * 2025-10-22 02:01:04 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-22 02:01:04 (10409) [INFO] * 2025-10-22 02:01:04 (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-22 02:01:04 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-22 02:01:06 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-22 02:01:06 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-22 02:01:06 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-22 02:01:06 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-22 02:01:06 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-22 02:01:12 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VJOa3k1xDx/ea_profile.json * 2025-10-22 02:04:10 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VJOa3k1xDx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-22 02:04:10 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-23 01:47:45 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-23 01:51:45 (11465) [INFO] Script is up to date. * 2025-10-23 01:55:48 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-23 01:55:48 (10379) [INFO] * 2025-10-23 01:57:09 (10409) [INFO] * 2025-10-23 01:57:09 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-23 01:57:09 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-23 01:57:09 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-23 01:57:09 (10379) [INFO] * 2025-10-23 02:04:06 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-23 02:04:06 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-23 02:04:06 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-23 02:04:06 (10379) [INFO] * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-23 02:04:41 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-23 02:04:42 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-23 02:04:42 (10379) [INFO] * 2025-10-23 02:04:42 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-23 02:04:42 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-23 02:05:13 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-23 02:05:13 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-23 02:05:13 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-23 02:05:13 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-23 02:05:13 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-23 02:05:13 (10392) [INFO] yum --disablerepo= ... * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-23 02:05:13 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-23 02:05:13 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] yum-config-manager --disable * 2025-10-23 02:05:13 (10392) [INFO] or * 2025-10-23 02:05:13 (10392) [INFO] subscription-manager repos --disable= * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-23 02:05:13 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-23 02:05:13 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-23 02:05:13 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-23 02:05:13 (10392) [INFO] compromise: * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-23 02:05:13 (10392) [INFO] * 2025-10-23 02:05:13 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-23 02:05:13 (10409) [INFO] * 2025-10-23 02:05: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-23 02:05:13 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-23 02:05:13 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-23 02:05:13 (10379) [INFO] * 2025-10-23 02:05:14 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-23 02:05:14 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-23 02:05:14 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-23 02:05:14 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-23 02:05:14 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-23 02:05:14 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-23 02:05:14 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-23 02:05:14 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-23 02:05:14 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-23 02:05:14 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-23 02:05:14 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-23 02:05:14 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-23 02:05:14 (10409) [INFO] * 2025-10-23 02:05:14 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-23 02:05:14 (10379) [INFO] * 2025-10-23 02:05:14 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-23 02:05:15 (10392) [INFO] Determining fastest mirrors * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-23 02:05:45 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-23 02:05:45 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-23 02:05:45 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-23 02:05:45 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-23 02:05:45 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-23 02:05:45 (10392) [INFO] yum --disablerepo= ... * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-23 02:05:45 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-23 02:05:45 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] yum-config-manager --disable * 2025-10-23 02:05:45 (10392) [INFO] or * 2025-10-23 02:05:45 (10392) [INFO] subscription-manager repos --disable= * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-23 02:05:45 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-23 02:05:45 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-23 02:05:45 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-23 02:05:45 (10392) [INFO] compromise: * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-23 02:05:45 (10392) [INFO] * 2025-10-23 02:05:45 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-23 02:05:45 (10409) [INFO] * 2025-10-23 02:05: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-10-23 02:05: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-23 02:05:47 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-23 02:05:47 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-23 02:05:47 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-23 02:05:47 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-23 02:05:47 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-23 02:05:53 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/82_J4L4ahi/ea_profile.json * 2025-10-23 02:08:21 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/82_J4L4ahi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-23 02:08:21 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-24 01:47:42 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-24 01:51:43 (11465) [INFO] Script is up to date. * 2025-10-24 01:55:46 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-24 01:55:46 (10379) [INFO] * 2025-10-24 01:57:06 (10409) [INFO] * 2025-10-24 01:57:06 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-24 01:57:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-24 01:57:07 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-24 01:57:07 (10379) [INFO] * 2025-10-24 01:57:11 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-24 01:57:11 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-24 01:57:11 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-24 01:57:11 (10379) [INFO] * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-24 01:57:45 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-24 01:57:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-24 01:57:45 (10379) [INFO] * 2025-10-24 01:57:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-24 01:57:46 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-24 01:58:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-24 01:58:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-24 01:58:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-24 01:58:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-24 01:58:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-24 01:58:17 (10392) [INFO] yum --disablerepo= ... * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-24 01:58:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-24 01:58:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] yum-config-manager --disable * 2025-10-24 01:58:17 (10392) [INFO] or * 2025-10-24 01:58:17 (10392) [INFO] subscription-manager repos --disable= * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-24 01:58:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-24 01:58:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-24 01:58:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-24 01:58:17 (10392) [INFO] compromise: * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-24 01:58:17 (10392) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-24 01:58:17 (10409) [INFO] * 2025-10-24 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-24 01:58:17 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-24 01:58:17 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-24 01:58:17 (10379) [INFO] * 2025-10-24 01:58:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-24 01:58:17 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-24 01:58:17 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-24 01:58:17 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-24 01:58:17 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-24 01:58:18 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-24 01:58:18 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-24 01:58:18 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-24 01:58:18 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-24 01:58:18 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-24 01:58:18 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-24 01:58:18 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-24 01:58:18 (10409) [INFO] * 2025-10-24 01:58:18 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-24 01:58:18 (10379) [INFO] * 2025-10-24 01:58:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-24 01:58:19 (10392) [INFO] Determining fastest mirrors * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-24 01:58:50 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-24 01:58:50 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-24 01:58:50 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-24 01:58:50 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-24 01:58:50 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-24 01:58:50 (10392) [INFO] yum --disablerepo= ... * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-24 01:58:50 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-24 01:58:50 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] yum-config-manager --disable * 2025-10-24 01:58:50 (10392) [INFO] or * 2025-10-24 01:58:50 (10392) [INFO] subscription-manager repos --disable= * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-24 01:58:50 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-24 01:58:50 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-24 01:58:50 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-24 01:58:50 (10392) [INFO] compromise: * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-24 01:58:50 (10392) [INFO] * 2025-10-24 01:58:50 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-24 01:58:50 (10409) [INFO] * 2025-10-24 01:58: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-10-24 01:58: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-24 01:58:52 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-24 01:58:52 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-24 01:58:52 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-24 01:58:52 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-24 01:58:52 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-24 01:59:00 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QiZVjTQf5J/ea_profile.json * 2025-10-24 02:01:59 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QiZVjTQf5J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-24 02:01:59 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-25 01:44:17 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-25 01:48:17 (11465) [INFO] Script is up to date. * 2025-10-25 01:52:21 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-25 01:52:21 (10379) [INFO] * 2025-10-25 01:53:20 (10409) [INFO] * 2025-10-25 01:53:20 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-25 01:53:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-25 01:53:20 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-25 01:53:20 (10379) [INFO] * 2025-10-25 02:00:29 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-25 02:00:29 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-25 02:00:29 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-25 02:00:29 (10379) [INFO] * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-25 02:01:03 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-25 02:01:03 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-25 02:01:03 (10379) [INFO] * 2025-10-25 02:01:03 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-25 02:01:04 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-25 02:01:34 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-25 02:01:34 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-25 02:01:34 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-25 02:01:34 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-25 02:01:34 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-25 02:01:34 (10392) [INFO] yum --disablerepo= ... * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-25 02:01:34 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-25 02:01:34 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] yum-config-manager --disable * 2025-10-25 02:01:34 (10392) [INFO] or * 2025-10-25 02:01:34 (10392) [INFO] subscription-manager repos --disable= * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-25 02:01:34 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-25 02:01:34 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-25 02:01:34 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-25 02:01:34 (10392) [INFO] compromise: * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-25 02:01:34 (10392) [INFO] * 2025-10-25 02:01:34 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-25 02:01:34 (10409) [INFO] * 2025-10-25 02:01: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-25 02:01:34 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-25 02:01:34 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-25 02:01:34 (10379) [INFO] * 2025-10-25 02:01:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-25 02:01:35 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-25 02:01:35 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-25 02:01:35 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-25 02:01:35 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-25 02:01:35 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-25 02:01:35 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-25 02:01:35 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-25 02:01:35 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-25 02:01:35 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-25 02:01:35 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-25 02:01:35 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-25 02:01:35 (10409) [INFO] * 2025-10-25 02:01:35 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-25 02:01:35 (10379) [INFO] * 2025-10-25 02:01:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-25 02:01:36 (10392) [INFO] Determining fastest mirrors * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-25 02:02:06 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-25 02:02:06 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-25 02:02:06 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-25 02:02:06 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-25 02:02:06 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-25 02:02:06 (10392) [INFO] yum --disablerepo= ... * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-25 02:02:06 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-25 02:02:06 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] yum-config-manager --disable * 2025-10-25 02:02:06 (10392) [INFO] or * 2025-10-25 02:02:06 (10392) [INFO] subscription-manager repos --disable= * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-25 02:02:06 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-25 02:02:06 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-25 02:02:06 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-25 02:02:06 (10392) [INFO] compromise: * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-25 02:02:06 (10392) [INFO] * 2025-10-25 02:02:06 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-25 02:02:06 (10409) [INFO] * 2025-10-25 02:02: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-10-25 02:02: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-25 02:02:08 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-25 02:02:08 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-25 02:02:08 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-25 02:02:08 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-25 02:02:08 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-25 02:02:13 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UTuYigYCdT/ea_profile.json * 2025-10-25 02:05:13 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UTuYigYCdT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-25 02:05:13 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-26 01:44:19 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-26 01:48:20 (11465) [INFO] Script is up to date. * 2025-10-26 01:52:23 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-26 01:52:23 (10379) [INFO] * 2025-10-26 01:53:25 (10409) [INFO] * 2025-10-26 01:53:25 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-26 01:53:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-26 01:53:25 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-26 01:53:25 (10379) [INFO] * 2025-10-26 02:00:38 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-26 02:00:38 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-26 02:00:38 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-26 02:00:38 (10379) [INFO] * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-26 02:01:13 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-26 02:01:13 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-26 02:01:13 (10379) [INFO] * 2025-10-26 02:01:13 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-26 02:01:13 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-26 02:01:44 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-26 02:01:44 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-26 02:01:44 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-26 02:01:44 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-26 02:01:44 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-26 02:01:44 (10392) [INFO] yum --disablerepo= ... * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-26 02:01:44 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-26 02:01:44 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] yum-config-manager --disable * 2025-10-26 02:01:44 (10392) [INFO] or * 2025-10-26 02:01:44 (10392) [INFO] subscription-manager repos --disable= * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-26 02:01:44 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-26 02:01:44 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-26 02:01:44 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-26 02:01:44 (10392) [INFO] compromise: * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-26 02:01:44 (10392) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-26 02:01:44 (10409) [INFO] * 2025-10-26 02:01: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-26 02:01:44 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-26 02:01:44 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-26 02:01:44 (10379) [INFO] * 2025-10-26 02:01:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-26 02:01:45 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-26 02:01:45 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-26 02:01:45 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-26 02:01:45 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-26 02:01:45 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-26 02:01:45 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-26 02:01:45 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-26 02:01:45 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-26 02:01:45 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-26 02:01:45 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-26 02:01:45 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-26 02:01:45 (10409) [INFO] * 2025-10-26 02:01:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-26 02:01:45 (10379) [INFO] * 2025-10-26 02:01:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-26 02:01:46 (10392) [INFO] Determining fastest mirrors * 2025-10-26 02:02:16 (10392) [INFO] * 2025-10-26 02:02:16 (10392) [INFO] * 2025-10-26 02:02:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-26 02:02:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-26 02:02:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-26 02:02:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-26 02:02:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-26 02:02:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-26 02:02:17 (10392) [INFO] yum --disablerepo= ... * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-26 02:02:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-26 02:02:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] yum-config-manager --disable * 2025-10-26 02:02:17 (10392) [INFO] or * 2025-10-26 02:02:17 (10392) [INFO] subscription-manager repos --disable= * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-26 02:02:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-26 02:02:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-26 02:02:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-26 02:02:17 (10392) [INFO] compromise: * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-26 02:02:17 (10392) [INFO] * 2025-10-26 02:02:17 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-26 02:02:17 (10409) [INFO] * 2025-10-26 02:02: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-10-26 02:02: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-26 02:02:18 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-26 02:02:18 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-26 02:02:18 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-26 02:02:18 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-26 02:02:18 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-26 02:02:26 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GJzlOA8j7a/ea_profile.json * 2025-10-26 02:05:24 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GJzlOA8j7a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-26 02:05:24 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-27 01:43:58 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-27 01:47:59 (11465) [INFO] Script is up to date. * 2025-10-27 01:52:01 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-27 01:52:01 (10379) [INFO] * 2025-10-27 01:53:29 (10409) [INFO] * 2025-10-27 01:53:29 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-27 01:53:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-27 01:53:29 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-27 01:53:29 (10379) [INFO] * 2025-10-27 02:00:32 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-27 02:00:32 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-27 02:00:32 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-27 02:00:32 (10379) [INFO] * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-27 02:01:11 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-27 02:01:11 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-27 02:01:11 (10379) [INFO] * 2025-10-27 02:01:11 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-27 02:01:12 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-27 02:01:42 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-27 02:01:42 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-27 02:01:42 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-27 02:01:42 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-27 02:01:42 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-27 02:01:42 (10392) [INFO] yum --disablerepo= ... * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-27 02:01:42 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-27 02:01:42 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] yum-config-manager --disable * 2025-10-27 02:01:42 (10392) [INFO] or * 2025-10-27 02:01:42 (10392) [INFO] subscription-manager repos --disable= * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-27 02:01:42 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-27 02:01:42 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-27 02:01:42 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-27 02:01:42 (10392) [INFO] compromise: * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-27 02:01:42 (10392) [INFO] * 2025-10-27 02:01:42 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-27 02:01:42 (10409) [INFO] * 2025-10-27 02:01: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-27 02:01:42 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-27 02:01:42 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-27 02:01:42 (10379) [INFO] * 2025-10-27 02:01:43 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-27 02:01:43 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-27 02:01:43 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-27 02:01:43 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-27 02:01:43 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-27 02:01:43 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-27 02:01:43 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-27 02:01:43 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-27 02:01:43 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-27 02:01:43 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-27 02:01:43 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-27 02:01:43 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-27 02:01:43 (10409) [INFO] * 2025-10-27 02:01:43 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-27 02:01:43 (10379) [INFO] * 2025-10-27 02:01:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-27 02:01:44 (10392) [INFO] Determining fastest mirrors * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-27 02:02:15 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-27 02:02:15 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-27 02:02:15 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-27 02:02:15 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-27 02:02:15 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-27 02:02:15 (10392) [INFO] yum --disablerepo= ... * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-27 02:02:15 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-27 02:02:15 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] yum-config-manager --disable * 2025-10-27 02:02:15 (10392) [INFO] or * 2025-10-27 02:02:15 (10392) [INFO] subscription-manager repos --disable= * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-27 02:02:15 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-27 02:02:15 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-27 02:02:15 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-27 02:02:15 (10392) [INFO] compromise: * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-27 02:02:15 (10392) [INFO] * 2025-10-27 02:02:15 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-27 02:02:15 (10409) [INFO] * 2025-10-27 02:02:15 (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-27 02:02:15 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-27 02:02:17 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-27 02:02:17 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-27 02:02:17 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-27 02:02:17 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-27 02:02:17 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-27 02:02:25 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7iie2O3f_5/ea_profile.json * 2025-10-27 02:04:52 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7iie2O3f_5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-27 02:04:52 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-28 01:43:57 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-28 01:47:57 (11465) [INFO] Script is up to date. * 2025-10-28 01:52:01 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-28 01:52:01 (10379) [INFO] * 2025-10-28 01:53:23 (10409) [INFO] * 2025-10-28 01:53:23 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-28 01:53:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-28 01:53:24 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-28 01:53:24 (10379) [INFO] * 2025-10-28 01:53:27 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-28 01:53:27 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-28 01:53:27 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-28 01:53:27 (10379) [INFO] * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-28 01:54:04 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-28 01:54:04 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-28 01:54:04 (10379) [INFO] * 2025-10-28 01:54:04 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-28 01:54:04 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-28 01:54:35 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-28 01:54:35 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-28 01:54:35 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-28 01:54:35 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-28 01:54:35 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-28 01:54:35 (10392) [INFO] yum --disablerepo= ... * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-28 01:54:35 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-28 01:54:35 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] yum-config-manager --disable * 2025-10-28 01:54:35 (10392) [INFO] or * 2025-10-28 01:54:35 (10392) [INFO] subscription-manager repos --disable= * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-28 01:54:35 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-28 01:54:35 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-28 01:54:35 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-28 01:54:35 (10392) [INFO] compromise: * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-28 01:54:35 (10392) [INFO] * 2025-10-28 01:54:35 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-28 01:54:35 (10409) [INFO] * 2025-10-28 01:54: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-28 01:54:35 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-28 01:54:35 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-28 01:54:35 (10379) [INFO] * 2025-10-28 01:54:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-28 01:54:36 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-28 01:54:36 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-28 01:54:36 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-28 01:54:36 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-28 01:54:36 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-28 01:54:36 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-28 01:54:36 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-28 01:54:36 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-28 01:54:36 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-28 01:54:36 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-28 01:54:36 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-28 01:54:36 (10409) [INFO] * 2025-10-28 01:54:36 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-28 01:54:36 (10379) [INFO] * 2025-10-28 01:54:37 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-28 01:54:37 (10392) [INFO] Determining fastest mirrors * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-28 01:55:08 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-28 01:55:08 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-28 01:55:08 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-28 01:55:08 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-28 01:55:08 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-28 01:55:08 (10392) [INFO] yum --disablerepo= ... * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-28 01:55:08 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-28 01:55:08 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] yum-config-manager --disable * 2025-10-28 01:55:08 (10392) [INFO] or * 2025-10-28 01:55:08 (10392) [INFO] subscription-manager repos --disable= * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-28 01:55:08 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-28 01:55:08 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-28 01:55:08 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-28 01:55:08 (10392) [INFO] compromise: * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-28 01:55:08 (10392) [INFO] * 2025-10-28 01:55:08 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-28 01:55:08 (10409) [INFO] * 2025-10-28 01:55:08 (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-28 01:55:08 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-28 01:55:09 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-28 01:55:09 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-28 01:55:09 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-28 01:55:09 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-28 01:55:09 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-28 01:55:16 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wNhZIYRoO1/ea_profile.json * 2025-10-28 01:58:45 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wNhZIYRoO1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-28 01:58:45 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-29 01:42:46 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-29 01:46:46 (11465) [INFO] Script is up to date. * 2025-10-29 01:50:49 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-29 01:50:49 (10379) [INFO] * 2025-10-29 01:52:15 (10409) [INFO] * 2025-10-29 01:52:15 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-29 01:52:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-29 01:52:15 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-29 01:52:15 (10379) [INFO] * 2025-10-29 01:59:11 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-29 01:59:11 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-29 01:59:11 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-29 01:59:11 (10379) [INFO] * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-29 01:59:45 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-29 01:59:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-29 01:59:45 (10379) [INFO] * 2025-10-29 01:59:46 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-29 01:59:46 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-29 02:00:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-29 02:00:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-29 02:00:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-29 02:00:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-29 02:00:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-29 02:00:17 (10392) [INFO] yum --disablerepo= ... * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-29 02:00:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-29 02:00:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] yum-config-manager --disable * 2025-10-29 02:00:17 (10392) [INFO] or * 2025-10-29 02:00:17 (10392) [INFO] subscription-manager repos --disable= * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-29 02:00:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-29 02:00:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-29 02:00:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-29 02:00:17 (10392) [INFO] compromise: * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-29 02:00:17 (10392) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-29 02:00:17 (10409) [INFO] * 2025-10-29 02:00: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-29 02:00:17 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-29 02:00:17 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-29 02:00:17 (10379) [INFO] * 2025-10-29 02:00:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-29 02:00:18 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-29 02:00:18 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-29 02:00:18 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-29 02:00:18 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-29 02:00:18 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-29 02:00:18 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-29 02:00:18 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-29 02:00:18 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-29 02:00:18 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-29 02:00:18 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-29 02:00:18 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-29 02:00:18 (10409) [INFO] * 2025-10-29 02:00:18 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-29 02:00:18 (10379) [INFO] * 2025-10-29 02:00:18 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-29 02:00:18 (10392) [INFO] Determining fastest mirrors * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-29 02:00:49 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-29 02:00:49 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-29 02:00:49 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-29 02:00:49 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-29 02:00:49 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-29 02:00:49 (10392) [INFO] yum --disablerepo= ... * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-29 02:00:49 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-29 02:00:49 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] yum-config-manager --disable * 2025-10-29 02:00:49 (10392) [INFO] or * 2025-10-29 02:00:49 (10392) [INFO] subscription-manager repos --disable= * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-29 02:00:49 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-29 02:00:49 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-29 02:00:49 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-29 02:00:49 (10392) [INFO] compromise: * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-29 02:00:49 (10392) [INFO] * 2025-10-29 02:00:49 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-29 02:00:49 (10409) [INFO] * 2025-10-29 02:00: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-10-29 02:00: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-29 02:00:51 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-29 02:00:51 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-29 02:00:51 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-29 02:00:51 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-29 02:00:51 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-29 02:00:57 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kOxcMA9MIO/ea_profile.json * 2025-10-29 02:03:57 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kOxcMA9MIO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-29 02:03:57 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-30 01:43:02 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-30 01:47:02 (11465) [INFO] Script is up to date. * 2025-10-30 01:51:05 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-30 01:51:05 (10379) [INFO] * 2025-10-30 01:52:27 (10409) [INFO] * 2025-10-30 01:52:27 (6868) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-30 01:52:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-30 01:52:27 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-30 01:52:27 (10379) [INFO] * 2025-10-30 01:59:26 (4432) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-30 01:59:26 (4439) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-30 01:59:26 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-30 01:59:26 (10379) [INFO] * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-30 02:00:03 (6584) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-30 02:00:03 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-30 02:00:03 (10379) [INFO] * 2025-10-30 02:00:03 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-30 02:00:04 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-30 02:00:35 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-30 02:00:35 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-30 02:00:35 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-30 02:00:35 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-30 02:00:35 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-30 02:00:35 (10392) [INFO] yum --disablerepo= ... * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-30 02:00:35 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-30 02:00:35 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] yum-config-manager --disable * 2025-10-30 02:00:35 (10392) [INFO] or * 2025-10-30 02:00:35 (10392) [INFO] subscription-manager repos --disable= * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-30 02:00:35 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-30 02:00:35 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-30 02:00:35 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-30 02:00:35 (10392) [INFO] compromise: * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-30 02:00:35 (10392) [INFO] * 2025-10-30 02:00:35 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-30 02:00:35 (10409) [INFO] * 2025-10-30 02:00: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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-30 02:00:35 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-30 02:00:35 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-30 02:00:35 (10379) [INFO] * 2025-10-30 02:00:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-30 02:00:36 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-30 02:00:36 (10392) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-30 02:00:36 (10392) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-30 02:00:36 (10392) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-30 02:00:36 (10392) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-30 02:00:36 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-30 02:00:36 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-30 02:00:36 (10392) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-30 02:00:36 (10392) [INFO] : wp-toolkit-thirdparties * 2025-10-30 02:00:36 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-30 02:00:36 (10392) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-30 02:00:36 (10409) [INFO] * 2025-10-30 02:00:36 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-30 02:00:36 (10379) [INFO] * 2025-10-30 02:00:37 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-30 02:00:37 (10392) [INFO] Determining fastest mirrors * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-30 02:01:08 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-30 02:01:08 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-30 02:01:08 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-30 02:01:08 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-30 02:01:08 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-30 02:01:08 (10392) [INFO] yum --disablerepo= ... * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-30 02:01:08 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-30 02:01:08 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] yum-config-manager --disable * 2025-10-30 02:01:08 (10392) [INFO] or * 2025-10-30 02:01:08 (10392) [INFO] subscription-manager repos --disable= * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-30 02:01:08 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-30 02:01:08 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-30 02:01:08 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-30 02:01:08 (10392) [INFO] compromise: * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-30 02:01:08 (10392) [INFO] * 2025-10-30 02:01:08 (10392) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-30 02:01:08 (10409) [INFO] * 2025-10-30 02:01:08 (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-30 02:01:08 (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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-30 02:01:10 (3611) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-30 02:01:10 (262) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-30 02:01:10 (4726) [WARN] Your machine has multiple network interface cards (NICs) using kernel-names (ethX). * 2025-10-30 02:01:10 (4732) [INFO] Since the upgrade process cannot guarantee their stability after upgrade, we will need to rename these interfaces before upgrading. * 2025-10-30 02:01:10 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-30 02:01:16 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1wnh6z13uo/ea_profile.json * 2025-10-30 02:04:46 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1wnh6z13uo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-30 02:04:46 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-31 01:43:03 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-31 01:47:03 (11448) [INFO] Newer version of script found. Downloading. * 2025-10-31 01:51:05 (11457) [INFO] Script update to version 72 successful. * 2025-10-31 01:55:08 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-31 01:55:08 (10864) [INFO] * 2025-10-31 01:56:32 (10894) [INFO] * 2025-10-31 01:56:32 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-10-31 01:56:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-10-31 01:56:32 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-31 01:56:32 (10864) [INFO] * 2025-10-31 01:56:59 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-10-31 01:56:59 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-31 01:56:59 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-10-31 01:56:59 (10864) [INFO] * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-10-31 01:57:34 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-10-31 01:57:34 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-10-31 01:57:34 (10864) [INFO] * 2025-10-31 01:57:34 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-31 01:57:35 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-10-31 01:58:06 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-31 01:58:06 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-31 01:58:06 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-31 01:58:06 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-10-31 01:58:06 (10877) [INFO] packages for the previous distribution release still work). * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-31 01:58:06 (10877) [INFO] yum --disablerepo= ... * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-31 01:58:06 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-31 01:58:06 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] yum-config-manager --disable * 2025-10-31 01:58:06 (10877) [INFO] or * 2025-10-31 01:58:06 (10877) [INFO] subscription-manager repos --disable= * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-31 01:58:06 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-31 01:58:06 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-31 01:58:06 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-31 01:58:06 (10877) [INFO] compromise: * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-31 01:58:06 (10877) [INFO] * 2025-10-31 01:58:06 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-31 01:58:06 (10894) [INFO] * 2025-10-31 01:58:06 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-31 01:58:06 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-31 01:58:06 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-10-31 01:58:06 (10864) [INFO] * 2025-10-31 01:58:07 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-31 01:58:07 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-10-31 01:58:07 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-10-31 01:58:07 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-10-31 01:58:07 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-10-31 01:58:07 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-10-31 01:58:07 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-31 01:58:07 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-31 01:58:07 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-10-31 01:58:07 (10877) [INFO] : wp-toolkit-thirdparties * 2025-10-31 01:58:07 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-10-31 01:58:07 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-10-31 01:58:07 (10894) [INFO] * 2025-10-31 01:58:07 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-10-31 01:58:07 (10864) [INFO] * 2025-10-31 01:58:07 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-31 01:58:08 (10877) [INFO] Determining fastest mirrors * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-10-31 01:58:38 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-31 01:58:38 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-31 01:58:38 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-31 01:58:38 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-10-31 01:58:38 (10877) [INFO] packages for the previous distribution release still work). * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-31 01:58:38 (10877) [INFO] yum --disablerepo= ... * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-31 01:58:38 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-31 01:58:38 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] yum-config-manager --disable * 2025-10-31 01:58:38 (10877) [INFO] or * 2025-10-31 01:58:38 (10877) [INFO] subscription-manager repos --disable= * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-31 01:58:38 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-31 01:58:38 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-31 01:58:38 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-31 01:58:38 (10877) [INFO] compromise: * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-31 01:58:38 (10877) [INFO] * 2025-10-31 01:58:38 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-10-31 01:58:38 (10894) [INFO] * 2025-10-31 01:58:38 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-31 01:58:38 (6696) [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 * 2025-10-31 01:58:40 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-10-31 01:58:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-10-31 01:58:40 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-10-31 01:58:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-10-31 01:58:40 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-31 01:58:47 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HqV1OP6uN2/ea_profile.json * 2025-10-31 02:01:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HqV1OP6uN2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-10-31 02:01:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-01 01:49:32 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-01 01:53:32 (11967) [INFO] Script is up to date. * 2025-11-01 01:57:36 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-01 01:57:36 (10864) [INFO] * 2025-11-01 01:58:30 (10894) [INFO] * 2025-11-01 01:58:30 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-01 01:58:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-01 01:58:30 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-01 01:58:30 (10864) [INFO] * 2025-11-01 02:05:27 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-01 02:05:27 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-01 02:05:27 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-01 02:05:27 (10864) [INFO] * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-01 02:06:05 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-01 02:06:05 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-01 02:06:05 (10864) [INFO] * 2025-11-01 02:06:05 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-01 02:06:06 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-01 02:06:37 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-01 02:06:37 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-01 02:06:37 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-01 02:06:37 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-01 02:06:37 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-01 02:06:37 (10877) [INFO] yum --disablerepo= ... * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-01 02:06:37 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-01 02:06:37 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] yum-config-manager --disable * 2025-11-01 02:06:37 (10877) [INFO] or * 2025-11-01 02:06:37 (10877) [INFO] subscription-manager repos --disable= * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-01 02:06:37 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-01 02:06:37 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-01 02:06:37 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-01 02:06:37 (10877) [INFO] compromise: * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-01 02:06:37 (10877) [INFO] * 2025-11-01 02:06:37 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-01 02:06:37 (10894) [INFO] * 2025-11-01 02:06:37 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-01 02:06:37 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-01 02:06:37 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-01 02:06:37 (10864) [INFO] * 2025-11-01 02:06:38 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-01 02:06:38 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-01 02:06:38 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-01 02:06:38 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-01 02:06:38 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-01 02:06:38 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-01 02:06:38 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-01 02:06:38 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-01 02:06:38 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-01 02:06:38 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-01 02:06:38 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-01 02:06:38 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-01 02:06:38 (10894) [INFO] * 2025-11-01 02:06:38 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-01 02:06:38 (10864) [INFO] * 2025-11-01 02:06:39 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-01 02:06:39 (10877) [INFO] Determining fastest mirrors * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-01 02:07:14 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-01 02:07:14 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-01 02:07:14 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-01 02:07:14 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-01 02:07:14 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-01 02:07:14 (10877) [INFO] yum --disablerepo= ... * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-01 02:07:14 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-01 02:07:14 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] yum-config-manager --disable * 2025-11-01 02:07:14 (10877) [INFO] or * 2025-11-01 02:07:14 (10877) [INFO] subscription-manager repos --disable= * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-01 02:07:14 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-01 02:07:14 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-01 02:07:14 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-01 02:07:14 (10877) [INFO] compromise: * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-01 02:07:14 (10877) [INFO] * 2025-11-01 02:07:14 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-01 02:07:15 (10894) [INFO] * 2025-11-01 02:07:15 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-01 02:07:15 (6696) [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 * 2025-11-01 02:07:16 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-01 02:07:16 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-01 02:07:16 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-01 02:07:16 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-01 02:07:16 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-01 02:07:24 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GqpOGb8Jqb/ea_profile.json * 2025-11-01 02:09:54 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GqpOGb8Jqb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-01 02:09:54 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-02 01:44:51 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-02 01:48:51 (11967) [INFO] Script is up to date. * 2025-11-02 01:52:54 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-02 01:52:54 (10864) [INFO] * 2025-11-02 01:53:54 (10894) [INFO] * 2025-11-02 01:53:54 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-02 01:53:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-02 01:53:54 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-02 01:53:54 (10864) [INFO] * 2025-11-02 01:53:58 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-02 01:53:58 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-02 01:53:58 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-02 01:53:58 (10864) [INFO] * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-02 01:54:34 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-02 01:54:34 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-02 01:54:34 (10864) [INFO] * 2025-11-02 01:54:35 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-02 01:54:35 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-02 01:55:06 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-02 01:55:06 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-02 01:55:06 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-02 01:55:06 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-02 01:55:06 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-02 01:55:06 (10877) [INFO] yum --disablerepo= ... * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-02 01:55:06 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-02 01:55:06 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] yum-config-manager --disable * 2025-11-02 01:55:06 (10877) [INFO] or * 2025-11-02 01:55:06 (10877) [INFO] subscription-manager repos --disable= * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-02 01:55:06 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-02 01:55:06 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-02 01:55:06 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-02 01:55:06 (10877) [INFO] compromise: * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-02 01:55:06 (10877) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-02 01:55:06 (10894) [INFO] * 2025-11-02 01:55:06 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-02 01:55:06 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-02 01:55:06 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-02 01:55:06 (10864) [INFO] * 2025-11-02 01:55:06 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-02 01:55:06 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-02 01:55:06 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-02 01:55:06 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-02 01:55:06 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-02 01:55:06 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-02 01:55:06 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-02 01:55:06 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-02 01:55:06 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-02 01:55:06 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-02 01:55:07 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-02 01:55:07 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-02 01:55:07 (10894) [INFO] * 2025-11-02 01:55:07 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-02 01:55:07 (10864) [INFO] * 2025-11-02 01:55:07 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-02 01:55:07 (10877) [INFO] Determining fastest mirrors * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-02 01:55:38 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-02 01:55:38 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-02 01:55:38 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-02 01:55:38 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-02 01:55:38 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-02 01:55:38 (10877) [INFO] yum --disablerepo= ... * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-02 01:55:38 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-02 01:55:38 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] yum-config-manager --disable * 2025-11-02 01:55:38 (10877) [INFO] or * 2025-11-02 01:55:38 (10877) [INFO] subscription-manager repos --disable= * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-02 01:55:38 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-02 01:55:38 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-02 01:55:38 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-02 01:55:38 (10877) [INFO] compromise: * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-02 01:55:38 (10877) [INFO] * 2025-11-02 01:55:38 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-02 01:55:38 (10894) [INFO] * 2025-11-02 01:55:38 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-02 01:55:38 (6696) [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 * 2025-11-02 01:55:40 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-02 01:55:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-02 01:55:40 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-02 01:55:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-02 01:55:40 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-02 01:55:46 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/irjluBW2JH/ea_profile.json * 2025-11-02 01:58:12 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/irjluBW2JH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-02 01:58:13 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-03 01:42:58 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-03 01:46:58 (11967) [INFO] Script is up to date. * 2025-11-03 01:51:02 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-03 01:51:02 (10864) [INFO] * 2025-11-03 01:52:27 (10894) [INFO] * 2025-11-03 01:52:27 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-03 01:52:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-03 01:52:27 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-03 01:52:27 (10864) [INFO] * 2025-11-03 01:52:30 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-03 01:52:30 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-03 01:52:30 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-03 01:52:30 (10864) [INFO] * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-03 01:53:08 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-03 01:53:08 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-03 01:53:08 (10864) [INFO] * 2025-11-03 01:53:08 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-03 01:53:08 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-03 01:53:40 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-03 01:53:40 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-03 01:53:40 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-03 01:53:40 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-03 01:53:40 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-03 01:53:40 (10877) [INFO] yum --disablerepo= ... * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-03 01:53:40 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-03 01:53:40 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] yum-config-manager --disable * 2025-11-03 01:53:40 (10877) [INFO] or * 2025-11-03 01:53:40 (10877) [INFO] subscription-manager repos --disable= * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-03 01:53:40 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-03 01:53:40 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-03 01:53:40 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-03 01:53:40 (10877) [INFO] compromise: * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-03 01:53:40 (10877) [INFO] * 2025-11-03 01:53:40 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-03 01:53:40 (10894) [INFO] * 2025-11-03 01:53:40 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-03 01:53:40 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-03 01:53:40 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-03 01:53:40 (10864) [INFO] * 2025-11-03 01:53:41 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-03 01:53:41 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-03 01:53:41 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-03 01:53:41 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-03 01:53:41 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-03 01:53:41 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-03 01:53:41 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-03 01:53:41 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-03 01:53:41 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-03 01:53:41 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-03 01:53:41 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-03 01:53:41 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-03 01:53:41 (10894) [INFO] * 2025-11-03 01:53:41 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-03 01:53:41 (10864) [INFO] * 2025-11-03 01:53:42 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-03 01:53:42 (10877) [INFO] Determining fastest mirrors * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-03 01:54:13 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-03 01:54:13 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-03 01:54:13 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-03 01:54:13 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-03 01:54:13 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-03 01:54:13 (10877) [INFO] yum --disablerepo= ... * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-03 01:54:13 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-03 01:54:13 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] yum-config-manager --disable * 2025-11-03 01:54:13 (10877) [INFO] or * 2025-11-03 01:54:13 (10877) [INFO] subscription-manager repos --disable= * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-03 01:54:13 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-03 01:54:13 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-03 01:54:13 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-03 01:54:13 (10877) [INFO] compromise: * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-03 01:54:13 (10877) [INFO] * 2025-11-03 01:54:13 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-03 01:54:13 (10894) [INFO] * 2025-11-03 01:54:13 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-03 01:54:13 (6696) [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 * 2025-11-03 01:54:15 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-03 01:54:15 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-03 01:54:15 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-03 01:54:15 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-03 01:54:15 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-03 01:54:20 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bu1RiCNm6m/ea_profile.json * 2025-11-03 01:56:49 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bu1RiCNm6m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-03 01:56:49 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-04 03:22:53 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-04 03:26:53 (11967) [INFO] Script is up to date. * 2025-11-04 03:30:56 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-04 03:30:56 (10864) [INFO] * 2025-11-04 03:32:18 (10894) [INFO] * 2025-11-04 03:32:18 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-04 03:32:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-04 03:32:24 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-04 03:32:24 (10864) [INFO] * 2025-11-04 03:37:02 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-04 03:37:02 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-04 03:37:02 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-04 03:37:02 (10864) [INFO] * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-04 03:37:37 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-04 03:37:37 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-04 03:37:37 (10864) [INFO] * 2025-11-04 03:37:37 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-04 03:37:37 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-04 03:38:09 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-04 03:38:09 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-04 03:38:09 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-04 03:38:09 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-04 03:38:09 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-04 03:38:09 (10877) [INFO] yum --disablerepo= ... * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-04 03:38:09 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-04 03:38:09 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] yum-config-manager --disable * 2025-11-04 03:38:09 (10877) [INFO] or * 2025-11-04 03:38:09 (10877) [INFO] subscription-manager repos --disable= * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-04 03:38:09 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-04 03:38:09 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-04 03:38:09 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-04 03:38:09 (10877) [INFO] compromise: * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-04 03:38:09 (10877) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-04 03:38:09 (10894) [INFO] * 2025-11-04 03:38:09 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-04 03:38:09 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-04 03:38:09 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-04 03:38:09 (10864) [INFO] * 2025-11-04 03:38:09 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-04 03:38:10 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-04 03:38:10 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-04 03:38:10 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-04 03:38:10 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-04 03:38:10 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-04 03:38:10 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-04 03:38:10 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-04 03:38:10 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-04 03:38:10 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-04 03:38:10 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-04 03:38:10 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-04 03:38:10 (10894) [INFO] * 2025-11-04 03:38:10 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-04 03:38:10 (10864) [INFO] * 2025-11-04 03:38:10 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-04 03:38:11 (10877) [INFO] Determining fastest mirrors * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-04 03:38:42 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-04 03:38:42 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-04 03:38:42 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-04 03:38:42 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-04 03:38:42 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-04 03:38:42 (10877) [INFO] yum --disablerepo= ... * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-04 03:38:42 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-04 03:38:42 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] yum-config-manager --disable * 2025-11-04 03:38:42 (10877) [INFO] or * 2025-11-04 03:38:42 (10877) [INFO] subscription-manager repos --disable= * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-04 03:38:42 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-04 03:38:42 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-04 03:38:42 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-04 03:38:42 (10877) [INFO] compromise: * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-04 03:38:42 (10877) [INFO] * 2025-11-04 03:38:42 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-04 03:38:42 (10894) [INFO] * 2025-11-04 03:38:42 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-04 03:38:42 (6696) [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 * 2025-11-04 03:38:43 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-04 03:38:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-04 03:38:43 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-04 03:38:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-04 03:38:43 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-04 03:38:50 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8CMCFU7EO9/ea_profile.json * 2025-11-04 03:41:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/8CMCFU7EO9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-04 03:41:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-05 01:43:40 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-05 01:47:41 (11967) [INFO] Script is up to date. * 2025-11-05 01:51:44 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-05 01:51:44 (10864) [INFO] * 2025-11-05 01:53:03 (10894) [INFO] * 2025-11-05 01:53:03 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-05 01:53:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-05 01:53:05 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-05 01:53:05 (10864) [INFO] * 2025-11-05 02:00:06 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-05 02:00:06 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-05 02:00:06 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-05 02:00:06 (10864) [INFO] * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-05 02:00:42 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-05 02:00:42 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-05 02:00:42 (10864) [INFO] * 2025-11-05 02:00:42 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-05 02:00:43 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-05 02:01:13 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-05 02:01:13 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-05 02:01:13 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-05 02:01:13 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-05 02:01:13 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-05 02:01:13 (10877) [INFO] yum --disablerepo= ... * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-05 02:01:13 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-05 02:01:13 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] yum-config-manager --disable * 2025-11-05 02:01:13 (10877) [INFO] or * 2025-11-05 02:01:13 (10877) [INFO] subscription-manager repos --disable= * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-05 02:01:13 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-05 02:01:13 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-05 02:01:13 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-05 02:01:13 (10877) [INFO] compromise: * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-05 02:01:13 (10877) [INFO] * 2025-11-05 02:01:13 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-05 02:01:14 (10894) [INFO] * 2025-11-05 02:01:14 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-05 02:01:14 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-05 02:01:14 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-05 02:01:14 (10864) [INFO] * 2025-11-05 02:01:14 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-05 02:01:14 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-05 02:01:14 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-05 02:01:14 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-05 02:01:14 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-05 02:01:14 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-05 02:01:14 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-05 02:01:14 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-05 02:01:14 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-05 02:01:14 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-05 02:01:14 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-05 02:01:14 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-05 02:01:15 (10894) [INFO] * 2025-11-05 02:01:15 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-05 02:01:15 (10864) [INFO] * 2025-11-05 02:01:15 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-05 02:01:15 (10877) [INFO] Determining fastest mirrors * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-05 02:01:47 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-05 02:01:47 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-05 02:01:47 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-05 02:01:47 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-05 02:01:47 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-05 02:01:47 (10877) [INFO] yum --disablerepo= ... * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-05 02:01:47 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-05 02:01:47 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] yum-config-manager --disable * 2025-11-05 02:01:47 (10877) [INFO] or * 2025-11-05 02:01:47 (10877) [INFO] subscription-manager repos --disable= * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-05 02:01:47 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-05 02:01:47 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-05 02:01:47 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-05 02:01:47 (10877) [INFO] compromise: * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-05 02:01:47 (10877) [INFO] * 2025-11-05 02:01:47 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-05 02:01:47 (10894) [INFO] * 2025-11-05 02:01:47 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-05 02:01:47 (6696) [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 * 2025-11-05 02:01:48 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-05 02:01:48 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-05 02:01:49 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-05 02:01:49 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-05 02:01:49 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-05 02:01:55 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/FgyuyvHwyU/ea_profile.json * 2025-11-05 02:04:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/FgyuyvHwyU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-05 02:04:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-06 01:53:36 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-06 01:57:36 (11967) [INFO] Script is up to date. * 2025-11-06 02:01:40 (10863) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-06 02:01:40 (10864) [INFO] * 2025-11-06 02:03:06 (10894) [INFO] * 2025-11-06 02:03:06 (7120) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-06 02:03:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-06 02:03:06 (10863) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-06 02:03:06 (10864) [INFO] * 2025-11-06 02:07:05 (4483) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-06 02:07:05 (4490) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-06 02:07:05 (10863) [INFO] Running: /usr/bin/yum list extras * 2025-11-06 02:07:05 (10864) [INFO] * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-06 02:07:42 (6836) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-06 02:07:42 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-06 02:07:42 (10864) [INFO] * 2025-11-06 02:07:43 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-06 02:07:43 (10877) [INFO] Loading mirror speeds from cached hostfile * 2025-11-06 02:08:13 (10877) [INFO] * 2025-11-06 02:08:13 (10877) [INFO] * 2025-11-06 02:08:13 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-06 02:08:13 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-06 02:08:13 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-06 02:08:13 (10877) [INFO] * 2025-11-06 02:08:13 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-06 02:08:13 (10877) [INFO] * 2025-11-06 02:08:13 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-06 02:08:13 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-06 02:08:13 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-06 02:08:13 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-06 02:08:13 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-06 02:08:14 (10877) [INFO] yum --disablerepo= ... * 2025-11-06 02:08:14 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-06 02:08:14 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-06 02:08:14 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-06 02:08:14 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] yum-config-manager --disable * 2025-11-06 02:08:14 (10877) [INFO] or * 2025-11-06 02:08:14 (10877) [INFO] subscription-manager repos --disable= * 2025-11-06 02:08:14 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-06 02:08:14 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-06 02:08:14 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-06 02:08:14 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-06 02:08:14 (10877) [INFO] compromise: * 2025-11-06 02:08:14 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-06 02:08:14 (10877) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-06 02:08:14 (10894) [INFO] * 2025-11-06 02:08:14 (6685) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-06 02:08:14 (6686) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-06 02:08:14 (10863) [INFO] Running: /usr/bin/yum clean all * 2025-11-06 02:08:14 (10864) [INFO] * 2025-11-06 02:08:14 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-06 02:08:14 (10877) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-06 02:08:14 (10877) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-06 02:08:14 (10877) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-06 02:08:14 (10877) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-06 02:08:14 (10877) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-06 02:08:14 (10877) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-06 02:08:14 (10877) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-06 02:08:14 (10877) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-06 02:08:14 (10877) [INFO] : wp-toolkit-thirdparties * 2025-11-06 02:08:14 (10877) [INFO] Cleaning up list of fastest mirrors * 2025-11-06 02:08:14 (10877) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-06 02:08:14 (10894) [INFO] * 2025-11-06 02:08:14 (10863) [INFO] Running: /usr/bin/yum makecache * 2025-11-06 02:08:14 (10864) [INFO] * 2025-11-06 02:08:15 (10877) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-06 02:08:15 (10877) [INFO] Determining fastest mirrors * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] One of the configured repositories failed (Unknown), * 2025-11-06 02:08:46 (10877) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-06 02:08:46 (10877) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-06 02:08:46 (10877) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-06 02:08:46 (10877) [INFO] distribution release than is supported by the repository (and the * 2025-11-06 02:08:46 (10877) [INFO] packages for the previous distribution release still work). * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-06 02:08:46 (10877) [INFO] yum --disablerepo= ... * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-06 02:08:46 (10877) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-06 02:08:46 (10877) [INFO] again or use --enablerepo for temporary usage: * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] yum-config-manager --disable * 2025-11-06 02:08:46 (10877) [INFO] or * 2025-11-06 02:08:46 (10877) [INFO] subscription-manager repos --disable= * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-06 02:08:46 (10877) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-06 02:08:46 (10877) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-06 02:08:46 (10877) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-06 02:08:46 (10877) [INFO] compromise: * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-06 02:08:46 (10877) [INFO] * 2025-11-06 02:08:46 (10877) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-06 02:08:46 (10894) [INFO] * 2025-11-06 02:08:46 (6695) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-06 02:08:46 (6696) [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 * 2025-11-06 02:08:48 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-06 02:08:48 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-06 02:08:48 (4930) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-06 02:08:48 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-06 02:08:48 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-06 02:08:54 (9973) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xZX2to7MVQ/ea_profile.json * 2025-11-06 02:11:30 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/xZX2to7MVQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9975. * 2025-11-06 02:11:30 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-07 01:38:46 (11945) [INFO] Self-update of script version 72 requested. * 2025-11-07 01:42:46 (11950) [INFO] Newer version of script found. Downloading. * 2025-11-07 01:46:48 (11959) [INFO] Script update to version 73 successful. * 2025-11-07 01:50:51 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-07 01:50:51 (10880) [INFO] * 2025-11-07 01:52:14 (10910) [INFO] * 2025-11-07 01:52:14 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-07 01:52:15 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-07 01:52:15 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-07 01:52:15 (10880) [INFO] * 2025-11-07 01:57:01 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-07 01:57:01 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-07 01:57:01 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-07 01:57:01 (10880) [INFO] * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-07 01:57:36 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-07 01:57:36 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-07 01:57:36 (10880) [INFO] * 2025-11-07 01:57:37 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-07 01:57:37 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-07 01:58:09 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-07 01:58:09 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-07 01:58:09 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-07 01:58:09 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-07 01:58:09 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-07 01:58:09 (10893) [INFO] yum --disablerepo= ... * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-07 01:58:09 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-07 01:58:09 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] yum-config-manager --disable * 2025-11-07 01:58:09 (10893) [INFO] or * 2025-11-07 01:58:09 (10893) [INFO] subscription-manager repos --disable= * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-07 01:58:09 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-07 01:58:09 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-07 01:58:09 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-07 01:58:09 (10893) [INFO] compromise: * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-07 01:58:09 (10893) [INFO] * 2025-11-07 01:58:09 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-07 01:58:09 (10910) [INFO] * 2025-11-07 01:58:09 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-07 01:58:09 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-07 01:58:09 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-07 01:58:09 (10880) [INFO] * 2025-11-07 01:58:10 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-07 01:58:10 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-07 01:58:10 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-07 01:58:10 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-07 01:58:10 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-07 01:58:10 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-07 01:58:10 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-07 01:58:10 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-07 01:58:10 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-07 01:58:10 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-07 01:58:10 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-07 01:58:10 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-07 01:58:10 (10910) [INFO] * 2025-11-07 01:58:10 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-07 01:58:10 (10880) [INFO] * 2025-11-07 01:58:11 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-07 01:58:11 (10893) [INFO] Determining fastest mirrors * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-07 01:58:43 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-07 01:58:43 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-07 01:58:43 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-07 01:58:43 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-07 01:58:43 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-07 01:58:43 (10893) [INFO] yum --disablerepo= ... * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-07 01:58:43 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-07 01:58:43 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] yum-config-manager --disable * 2025-11-07 01:58:43 (10893) [INFO] or * 2025-11-07 01:58:43 (10893) [INFO] subscription-manager repos --disable= * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-07 01:58:43 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-07 01:58:43 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-07 01:58:43 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-07 01:58:43 (10893) [INFO] compromise: * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-07 01:58:43 (10893) [INFO] * 2025-11-07 01:58:43 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-07 01:58:43 (10910) [INFO] * 2025-11-07 01:58:43 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-07 01:58:43 (6712) [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 * 2025-11-07 01:58:44 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-07 01:58:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-07 01:58:44 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-07 01:58:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-07 01:58:44 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-07 01:58:51 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GYhLq62Pfb/ea_profile.json * 2025-11-07 02:01:50 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GYhLq62Pfb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-07 02:01:50 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-08 01:41:48 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-08 01:45:48 (11983) [INFO] Script is up to date. * 2025-11-08 01:49:52 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-08 01:49:52 (10880) [INFO] * 2025-11-08 01:50:47 (10910) [INFO] * 2025-11-08 01:50:47 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-08 01:50:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-08 01:50:47 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-08 01:50:47 (10880) [INFO] * 2025-11-08 01:57:45 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-08 01:57:45 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-08 01:57:45 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-08 01:57:45 (10880) [INFO] * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-08 01:58:20 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-08 01:58:20 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-08 01:58:20 (10880) [INFO] * 2025-11-08 01:58:21 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-08 01:58:21 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-08 01:58:52 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-08 01:58:52 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-08 01:58:52 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-08 01:58:52 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-08 01:58:52 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-08 01:58:52 (10893) [INFO] yum --disablerepo= ... * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-08 01:58:52 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-08 01:58:52 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] yum-config-manager --disable * 2025-11-08 01:58:52 (10893) [INFO] or * 2025-11-08 01:58:52 (10893) [INFO] subscription-manager repos --disable= * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-08 01:58:52 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-08 01:58:52 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-08 01:58:52 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-08 01:58:52 (10893) [INFO] compromise: * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-08 01:58:52 (10893) [INFO] * 2025-11-08 01:58:52 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-08 01:58:52 (10910) [INFO] * 2025-11-08 01:58:52 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-08 01:58:52 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-08 01:58:52 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-08 01:58:52 (10880) [INFO] * 2025-11-08 01:58:53 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-08 01:58:53 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-08 01:58:53 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-08 01:58:53 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-08 01:58:53 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-08 01:58:53 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-08 01:58:53 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-08 01:58:53 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-08 01:58:53 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-08 01:58:53 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-08 01:58:53 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-08 01:58:53 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-08 01:58:53 (10910) [INFO] * 2025-11-08 01:58:53 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-08 01:58:53 (10880) [INFO] * 2025-11-08 01:58:54 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-08 01:58:54 (10893) [INFO] Determining fastest mirrors * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-08 01:59:26 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-08 01:59:26 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-08 01:59:26 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-08 01:59:26 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-08 01:59:26 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-08 01:59:26 (10893) [INFO] yum --disablerepo= ... * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-08 01:59:26 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-08 01:59:26 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] yum-config-manager --disable * 2025-11-08 01:59:26 (10893) [INFO] or * 2025-11-08 01:59:26 (10893) [INFO] subscription-manager repos --disable= * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-08 01:59:26 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-08 01:59:26 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-08 01:59:26 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-08 01:59:26 (10893) [INFO] compromise: * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-08 01:59:26 (10893) [INFO] * 2025-11-08 01:59:26 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-08 01:59:26 (10910) [INFO] * 2025-11-08 01:59:26 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-08 01:59:26 (6712) [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 * 2025-11-08 01:59:27 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-08 01:59:27 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-08 01:59:28 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-08 01:59:28 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-08 01:59:28 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-08 01:59:35 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4cPNmeGxTC/ea_profile.json * 2025-11-08 02:02:03 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4cPNmeGxTC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-08 02:02:03 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-09 01:40:06 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-09 01:44:06 (11983) [INFO] Script is up to date. * 2025-11-09 01:48:09 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-09 01:48:09 (10880) [INFO] * 2025-11-09 01:49:05 (10910) [INFO] * 2025-11-09 01:49:05 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-09 01:49:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-09 01:49:06 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-09 01:49:06 (10880) [INFO] * 2025-11-09 01:51:59 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-09 01:51:59 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-09 01:51:59 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-09 01:51:59 (10880) [INFO] * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-09 01:52:35 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-09 01:52:35 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-09 01:52:35 (10880) [INFO] * 2025-11-09 01:52:36 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-09 01:52:36 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-09 01:53:06 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-09 01:53:06 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-09 01:53:06 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-09 01:53:06 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-09 01:53:06 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-09 01:53:06 (10893) [INFO] yum --disablerepo= ... * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-09 01:53:06 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-09 01:53:06 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] yum-config-manager --disable * 2025-11-09 01:53:06 (10893) [INFO] or * 2025-11-09 01:53:06 (10893) [INFO] subscription-manager repos --disable= * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-09 01:53:06 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-09 01:53:06 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-09 01:53:06 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-09 01:53:06 (10893) [INFO] compromise: * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-09 01:53:06 (10893) [INFO] * 2025-11-09 01:53:06 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-09 01:53:06 (10910) [INFO] * 2025-11-09 01:53:06 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-09 01:53:06 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-09 01:53:06 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-09 01:53:06 (10880) [INFO] * 2025-11-09 01:53:07 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-09 01:53:07 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-09 01:53:07 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-09 01:53:07 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-09 01:53:07 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-09 01:53:07 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-09 01:53:07 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-09 01:53:07 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-09 01:53:07 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-09 01:53:07 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-09 01:53:07 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-09 01:53:07 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-09 01:53:08 (10910) [INFO] * 2025-11-09 01:53:08 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-09 01:53:08 (10880) [INFO] * 2025-11-09 01:53:08 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-09 01:53:08 (10893) [INFO] Determining fastest mirrors * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-09 01:53:40 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-09 01:53:40 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-09 01:53:40 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-09 01:53:40 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-09 01:53:40 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-09 01:53:40 (10893) [INFO] yum --disablerepo= ... * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-09 01:53:40 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-09 01:53:40 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] yum-config-manager --disable * 2025-11-09 01:53:40 (10893) [INFO] or * 2025-11-09 01:53:40 (10893) [INFO] subscription-manager repos --disable= * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-09 01:53:40 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-09 01:53:40 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-09 01:53:40 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-09 01:53:40 (10893) [INFO] compromise: * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-09 01:53:40 (10893) [INFO] * 2025-11-09 01:53:40 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-09 01:53:40 (10910) [INFO] * 2025-11-09 01:53:40 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-09 01:53:40 (6712) [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 * 2025-11-09 01:53:42 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-09 01:53:42 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-09 01:53:42 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-09 01:53:42 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-09 01:53:42 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-09 01:53:48 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dXHFYHlcXN/ea_profile.json * 2025-11-09 01:56:16 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dXHFYHlcXN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-09 01:56:16 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-10 01:39:35 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-10 01:43:35 (11983) [INFO] Script is up to date. * 2025-11-10 01:47:38 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-10 01:47:38 (10880) [INFO] * 2025-11-10 01:49:04 (10910) [INFO] * 2025-11-10 01:49:04 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-10 01:49:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-10 01:49:04 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-10 01:49:04 (10880) [INFO] * 2025-11-10 01:57:22 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-10 01:57:22 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-10 01:57:22 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-10 01:57:22 (10880) [INFO] * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-10 01:58:00 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-10 01:58:00 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-10 01:58:00 (10880) [INFO] * 2025-11-10 01:58:01 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-10 01:58:01 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-10 01:58:32 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-10 01:58:32 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-10 01:58:32 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-10 01:58:32 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-10 01:58:32 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-10 01:58:32 (10893) [INFO] yum --disablerepo= ... * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-10 01:58:32 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-10 01:58:32 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] yum-config-manager --disable * 2025-11-10 01:58:32 (10893) [INFO] or * 2025-11-10 01:58:32 (10893) [INFO] subscription-manager repos --disable= * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-10 01:58:32 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-10 01:58:32 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-10 01:58:32 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-10 01:58:32 (10893) [INFO] compromise: * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-10 01:58:32 (10893) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-10 01:58:32 (10910) [INFO] * 2025-11-10 01:58:32 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-10 01:58:32 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-10 01:58:32 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-10 01:58:32 (10880) [INFO] * 2025-11-10 01:58:32 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-10 01:58:32 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-10 01:58:32 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-10 01:58:32 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-10 01:58:32 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-10 01:58:32 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-10 01:58:32 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-10 01:58:32 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-10 01:58:32 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-10 01:58:32 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-10 01:58:33 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-10 01:58:33 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-10 01:58:33 (10910) [INFO] * 2025-11-10 01:58:33 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-10 01:58:33 (10880) [INFO] * 2025-11-10 01:58:33 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-10 01:58:33 (10893) [INFO] Determining fastest mirrors * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-10 01:59:05 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-10 01:59:05 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-10 01:59:05 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-10 01:59:05 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-10 01:59:05 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-10 01:59:05 (10893) [INFO] yum --disablerepo= ... * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-10 01:59:05 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-10 01:59:05 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] yum-config-manager --disable * 2025-11-10 01:59:05 (10893) [INFO] or * 2025-11-10 01:59:05 (10893) [INFO] subscription-manager repos --disable= * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-10 01:59:05 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-10 01:59:05 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-10 01:59:05 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-10 01:59:05 (10893) [INFO] compromise: * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-10 01:59:05 (10893) [INFO] * 2025-11-10 01:59:05 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-10 01:59:05 (10910) [INFO] * 2025-11-10 01:59:05 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-10 01:59:05 (6712) [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 * 2025-11-10 01:59:06 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-10 01:59:06 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-10 01:59:06 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-10 01:59:06 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-10 01:59:06 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-10 01:59:12 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rukwq6zqP4/ea_profile.json * 2025-11-10 02:01:40 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rukwq6zqP4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-10 02:01:40 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-11 02:07:00 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-11 02:11:00 (11983) [INFO] Script is up to date. * 2025-11-11 02:15:04 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-11 02:15:04 (10880) [INFO] * 2025-11-11 02:16:20 (10910) [INFO] * 2025-11-11 02:16:20 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-11 02:16:21 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-11 02:16:21 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-11 02:16:21 (10880) [INFO] * 2025-11-11 02:17:00 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-11 02:17:00 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-11 02:17:00 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-11 02:17:00 (10880) [INFO] * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-11 02:17:35 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-11 02:17:35 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-11 02:17:35 (10880) [INFO] * 2025-11-11 02:17:36 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-11 02:17:36 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-11 02:18:07 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-11 02:18:07 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-11 02:18:07 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-11 02:18:07 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-11 02:18:07 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-11 02:18:07 (10893) [INFO] yum --disablerepo= ... * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-11 02:18:07 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-11 02:18:07 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] yum-config-manager --disable * 2025-11-11 02:18:07 (10893) [INFO] or * 2025-11-11 02:18:07 (10893) [INFO] subscription-manager repos --disable= * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-11 02:18:07 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-11 02:18:07 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-11 02:18:07 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-11 02:18:07 (10893) [INFO] compromise: * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-11 02:18:07 (10893) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-11 02:18:07 (10910) [INFO] * 2025-11-11 02:18:07 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-11 02:18:07 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-11 02:18:07 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-11 02:18:07 (10880) [INFO] * 2025-11-11 02:18:07 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-11 02:18:07 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-11 02:18:07 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-11 02:18:07 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-11 02:18:07 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-11 02:18:07 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-11 02:18:07 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-11 02:18:07 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-11 02:18:07 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-11 02:18:07 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-11 02:18:08 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-11 02:18:08 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-11 02:18:08 (10910) [INFO] * 2025-11-11 02:18:08 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-11 02:18:08 (10880) [INFO] * 2025-11-11 02:18:08 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-11 02:18:08 (10893) [INFO] Determining fastest mirrors * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-11 02:18:40 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-11 02:18:40 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-11 02:18:40 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-11 02:18:40 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-11 02:18:40 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-11 02:18:40 (10893) [INFO] yum --disablerepo= ... * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-11 02:18:40 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-11 02:18:40 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] yum-config-manager --disable * 2025-11-11 02:18:40 (10893) [INFO] or * 2025-11-11 02:18:40 (10893) [INFO] subscription-manager repos --disable= * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-11 02:18:40 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-11 02:18:40 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-11 02:18:40 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-11 02:18:40 (10893) [INFO] compromise: * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-11 02:18:40 (10893) [INFO] * 2025-11-11 02:18:40 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-11 02:18:40 (10910) [INFO] * 2025-11-11 02:18:40 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-11 02:18:40 (6712) [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 * 2025-11-11 02:18:41 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-11 02:18:41 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-11 02:18:41 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-11 02:18:41 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-11 02:18:41 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-11 02:18:47 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/b6olqTIEJL/ea_profile.json * 2025-11-11 02:21:46 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/b6olqTIEJL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-11 02:21:46 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-12 01:39:43 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-12 01:43:43 (11983) [INFO] Script is up to date. * 2025-11-12 01:47:46 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-12 01:47:46 (10880) [INFO] * 2025-11-12 01:49:09 (10910) [INFO] * 2025-11-12 01:49:09 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-12 01:49:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-12 01:49:10 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-12 01:49:10 (10880) [INFO] * 2025-11-12 01:57:21 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-12 01:57:21 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-12 01:57:21 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-12 01:57:21 (10880) [INFO] * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-12 01:57:57 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-12 01:57:57 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-12 01:57:57 (10880) [INFO] * 2025-11-12 01:57:58 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-12 01:57:58 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-12 01:58:29 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-12 01:58:29 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-12 01:58:29 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-12 01:58:29 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-12 01:58:29 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-12 01:58:29 (10893) [INFO] yum --disablerepo= ... * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-12 01:58:29 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-12 01:58:29 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] yum-config-manager --disable * 2025-11-12 01:58:29 (10893) [INFO] or * 2025-11-12 01:58:29 (10893) [INFO] subscription-manager repos --disable= * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-12 01:58:29 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-12 01:58:29 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-12 01:58:29 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-12 01:58:29 (10893) [INFO] compromise: * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-12 01:58:29 (10893) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-12 01:58:29 (10910) [INFO] * 2025-11-12 01:58:29 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-12 01:58:29 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-12 01:58:29 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-12 01:58:29 (10880) [INFO] * 2025-11-12 01:58:29 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-12 01:58:29 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-12 01:58:29 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-12 01:58:29 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-12 01:58:29 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-12 01:58:29 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-12 01:58:29 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-12 01:58:29 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-12 01:58:29 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-12 01:58:29 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-12 01:58:30 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-12 01:58:30 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-12 01:58:30 (10910) [INFO] * 2025-11-12 01:58:30 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-12 01:58:30 (10880) [INFO] * 2025-11-12 01:58:30 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-12 01:58:30 (10893) [INFO] Determining fastest mirrors * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-12 01:59:01 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-12 01:59:01 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-12 01:59:01 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-12 01:59:01 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-12 01:59:01 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-12 01:59:01 (10893) [INFO] yum --disablerepo= ... * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-12 01:59:01 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-12 01:59:01 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] yum-config-manager --disable * 2025-11-12 01:59:01 (10893) [INFO] or * 2025-11-12 01:59:01 (10893) [INFO] subscription-manager repos --disable= * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-12 01:59:01 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-12 01:59:01 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-12 01:59:01 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-12 01:59:01 (10893) [INFO] compromise: * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-12 01:59:01 (10893) [INFO] * 2025-11-12 01:59:01 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-12 01:59:01 (10910) [INFO] * 2025-11-12 01:59:01 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-12 01:59:01 (6712) [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 * 2025-11-12 01:59:03 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-12 01:59:03 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-12 01:59:03 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-12 01:59:03 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-12 01:59:03 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-12 01:59:10 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9dE3hRHsIs/ea_profile.json * 2025-11-12 02:01:37 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9dE3hRHsIs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-12 02:01:37 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-13 01:38:43 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-13 01:42:44 (11983) [INFO] Script is up to date. * 2025-11-13 01:46:46 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-13 01:46:46 (10880) [INFO] * 2025-11-13 01:48:04 (10910) [INFO] * 2025-11-13 01:48:04 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-13 01:48:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-13 01:48:04 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-13 01:48:04 (10880) [INFO] * 2025-11-13 01:48:07 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-13 01:48:07 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-13 01:48:07 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-13 01:48:07 (10880) [INFO] * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-13 01:48:40 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-13 01:48:40 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-13 01:48:40 (10880) [INFO] * 2025-11-13 01:48:40 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-13 01:48:41 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-13 01:49:12 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-13 01:49:12 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-13 01:49:12 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-13 01:49:12 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-13 01:49:12 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-13 01:49:12 (10893) [INFO] yum --disablerepo= ... * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-13 01:49:12 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-13 01:49:12 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] yum-config-manager --disable * 2025-11-13 01:49:12 (10893) [INFO] or * 2025-11-13 01:49:12 (10893) [INFO] subscription-manager repos --disable= * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-13 01:49:12 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-13 01:49:12 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-13 01:49:12 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-13 01:49:12 (10893) [INFO] compromise: * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-13 01:49:12 (10893) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-13 01:49:12 (10910) [INFO] * 2025-11-13 01:49:12 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-13 01:49:12 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-13 01:49:12 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-13 01:49:12 (10880) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-13 01:49:12 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-13 01:49:12 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-13 01:49:12 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-13 01:49:12 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-13 01:49:12 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-13 01:49:12 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-13 01:49:12 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-13 01:49:12 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-13 01:49:12 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-13 01:49:12 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-13 01:49:12 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-13 01:49:12 (10910) [INFO] * 2025-11-13 01:49:12 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-13 01:49:12 (10880) [INFO] * 2025-11-13 01:49:12 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-13 01:49:13 (10893) [INFO] Determining fastest mirrors * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-13 01:49:46 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-13 01:49:46 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-13 01:49:46 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-13 01:49:46 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-13 01:49:46 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-13 01:49:46 (10893) [INFO] yum --disablerepo= ... * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-13 01:49:46 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-13 01:49:46 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] yum-config-manager --disable * 2025-11-13 01:49:46 (10893) [INFO] or * 2025-11-13 01:49:46 (10893) [INFO] subscription-manager repos --disable= * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-13 01:49:46 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-13 01:49:46 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-13 01:49:46 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-13 01:49:46 (10893) [INFO] compromise: * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-13 01:49:46 (10893) [INFO] * 2025-11-13 01:49:46 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-13 01:49:47 (10910) [INFO] * 2025-11-13 01:49:47 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-13 01:49:47 (6712) [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 * 2025-11-13 01:49:48 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-13 01:49:48 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-13 01:49:48 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-13 01:49:48 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-13 01:49:48 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-13 01:49:55 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yos4eTojEC/ea_profile.json * 2025-11-13 01:52:23 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yos4eTojEC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-13 01:52:23 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-14 01:39:58 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-14 01:43:58 (11983) [INFO] Script is up to date. * 2025-11-14 01:48:01 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-14 01:48:01 (10880) [INFO] * 2025-11-14 01:49:16 (10910) [INFO] * 2025-11-14 01:49:16 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-14 01:49:17 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-14 01:49:17 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-14 01:49:17 (10880) [INFO] * 2025-11-14 01:57:21 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-14 01:57:21 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-14 01:57:21 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-14 01:57:21 (10880) [INFO] * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-14 01:57:55 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-14 01:57:55 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-14 01:57:55 (10880) [INFO] * 2025-11-14 01:57:56 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-14 01:57:56 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-14 01:58:26 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-14 01:58:26 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-14 01:58:26 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-14 01:58:26 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-14 01:58:26 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-14 01:58:26 (10893) [INFO] yum --disablerepo= ... * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-14 01:58:26 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-14 01:58:26 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] yum-config-manager --disable * 2025-11-14 01:58:26 (10893) [INFO] or * 2025-11-14 01:58:26 (10893) [INFO] subscription-manager repos --disable= * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-14 01:58:26 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-14 01:58:26 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-14 01:58:26 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-14 01:58:26 (10893) [INFO] compromise: * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-14 01:58:26 (10893) [INFO] * 2025-11-14 01:58:26 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-14 01:58:27 (10910) [INFO] * 2025-11-14 01:58:27 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-14 01:58:27 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-14 01:58:27 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-14 01:58:27 (10880) [INFO] * 2025-11-14 01:58:27 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-14 01:58:27 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-14 01:58:27 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-14 01:58:27 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-14 01:58:27 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-14 01:58:27 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-14 01:58:27 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-14 01:58:27 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-14 01:58:27 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-14 01:58:27 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-14 01:58:27 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-14 01:58:27 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-14 01:58:27 (10910) [INFO] * 2025-11-14 01:58:27 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-14 01:58:27 (10880) [INFO] * 2025-11-14 01:58:28 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-14 01:58:28 (10893) [INFO] Determining fastest mirrors * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-14 01:58:59 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-14 01:58:59 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-14 01:58:59 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-14 01:58:59 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-14 01:58:59 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-14 01:58:59 (10893) [INFO] yum --disablerepo= ... * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-14 01:58:59 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-14 01:58:59 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] yum-config-manager --disable * 2025-11-14 01:58:59 (10893) [INFO] or * 2025-11-14 01:58:59 (10893) [INFO] subscription-manager repos --disable= * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-14 01:58:59 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-14 01:58:59 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-14 01:58:59 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-14 01:58:59 (10893) [INFO] compromise: * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-14 01:58:59 (10893) [INFO] * 2025-11-14 01:58:59 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-14 01:58:59 (10910) [INFO] * 2025-11-14 01:58:59 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-14 01:58:59 (6712) [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 * 2025-11-14 01:59:00 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-14 01:59:00 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-14 01:59:00 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-14 01:59:00 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-14 01:59:00 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-14 01:59:06 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c80njWyeVg/ea_profile.json * 2025-11-14 02:01:42 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c80njWyeVg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-14 02:01:42 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-15 01:39:48 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-15 01:43:48 (11983) [INFO] Script is up to date. * 2025-11-15 01:47:52 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-15 01:47:52 (10880) [INFO] * 2025-11-15 01:48:42 (10910) [INFO] * 2025-11-15 01:48:42 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-15 01:48:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-15 01:48:42 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-15 01:48:42 (10880) [INFO] * 2025-11-15 01:57:19 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-15 01:57:19 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-15 01:57:19 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-15 01:57:19 (10880) [INFO] * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-15 01:57:56 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-15 01:57:56 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-15 01:57:56 (10880) [INFO] * 2025-11-15 01:57:56 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-15 01:57:56 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-15 01:58:27 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-15 01:58:27 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-15 01:58:27 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-15 01:58:27 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-15 01:58:27 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-15 01:58:27 (10893) [INFO] yum --disablerepo= ... * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-15 01:58:27 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-15 01:58:27 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] yum-config-manager --disable * 2025-11-15 01:58:27 (10893) [INFO] or * 2025-11-15 01:58:27 (10893) [INFO] subscription-manager repos --disable= * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-15 01:58:27 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-15 01:58:27 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-15 01:58:27 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-15 01:58:27 (10893) [INFO] compromise: * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-15 01:58:27 (10893) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-15 01:58:27 (10910) [INFO] * 2025-11-15 01:58:27 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-15 01:58:27 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-15 01:58:27 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-15 01:58:27 (10880) [INFO] * 2025-11-15 01:58:27 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-15 01:58:28 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-15 01:58:28 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-15 01:58:28 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-15 01:58:28 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-15 01:58:28 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-15 01:58:28 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-15 01:58:28 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-15 01:58:28 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-15 01:58:28 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-15 01:58:28 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-15 01:58:28 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-15 01:58:28 (10910) [INFO] * 2025-11-15 01:58:28 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-15 01:58:28 (10880) [INFO] * 2025-11-15 01:58:28 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-15 01:58:28 (10893) [INFO] Determining fastest mirrors * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-15 01:58:59 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-15 01:58:59 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-15 01:58:59 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-15 01:58:59 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-15 01:58:59 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-15 01:58:59 (10893) [INFO] yum --disablerepo= ... * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-15 01:58:59 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-15 01:58:59 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] yum-config-manager --disable * 2025-11-15 01:58:59 (10893) [INFO] or * 2025-11-15 01:58:59 (10893) [INFO] subscription-manager repos --disable= * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-15 01:58:59 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-15 01:58:59 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-15 01:58:59 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-15 01:58:59 (10893) [INFO] compromise: * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-15 01:58:59 (10893) [INFO] * 2025-11-15 01:58:59 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-15 01:58:59 (10910) [INFO] * 2025-11-15 01:58:59 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-15 01:58:59 (6712) [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 * 2025-11-15 01:59:01 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-15 01:59:01 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-15 01:59:01 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-15 01:59:01 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-15 01:59:01 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-15 01:59:07 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/U4sv1yTH30/ea_profile.json * 2025-11-15 02:01:35 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/U4sv1yTH30/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-15 02:01:35 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-16 01:40:41 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-16 01:44:41 (11983) [INFO] Script is up to date. * 2025-11-16 01:48:44 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-16 01:48:44 (10880) [INFO] * 2025-11-16 01:49:37 (10910) [INFO] * 2025-11-16 01:49:37 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-16 01:49:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-16 01:49:37 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-16 01:49:37 (10880) [INFO] * 2025-11-16 01:49:41 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-16 01:49:41 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-16 01:49:41 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-16 01:49:41 (10880) [INFO] * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-16 01:50:17 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-16 01:50:17 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-16 01:50:17 (10880) [INFO] * 2025-11-16 01:50:17 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-16 01:50:17 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-16 01:50:48 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-16 01:50:48 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-16 01:50:48 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-16 01:50:48 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-16 01:50:48 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-16 01:50:48 (10893) [INFO] yum --disablerepo= ... * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-16 01:50:48 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-16 01:50:48 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] yum-config-manager --disable * 2025-11-16 01:50:48 (10893) [INFO] or * 2025-11-16 01:50:48 (10893) [INFO] subscription-manager repos --disable= * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-16 01:50:48 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-16 01:50:48 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-16 01:50:48 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-16 01:50:48 (10893) [INFO] compromise: * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-16 01:50:48 (10893) [INFO] * 2025-11-16 01:50:48 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-16 01:50:48 (10910) [INFO] * 2025-11-16 01:50:48 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-16 01:50:48 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-16 01:50:48 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-16 01:50:48 (10880) [INFO] * 2025-11-16 01:50:49 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-16 01:50:49 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-16 01:50:49 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-16 01:50:49 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-16 01:50:49 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-16 01:50:49 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-16 01:50:49 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-16 01:50:49 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-16 01:50:49 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-16 01:50:49 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-16 01:50:49 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-16 01:50:49 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-16 01:50:49 (10910) [INFO] * 2025-11-16 01:50:49 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-16 01:50:49 (10880) [INFO] * 2025-11-16 01:50:50 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-16 01:50:50 (10893) [INFO] Determining fastest mirrors * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-16 01:51:21 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-16 01:51:21 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-16 01:51:21 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-16 01:51:21 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-16 01:51:21 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-16 01:51:21 (10893) [INFO] yum --disablerepo= ... * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-16 01:51:21 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-16 01:51:21 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] yum-config-manager --disable * 2025-11-16 01:51:21 (10893) [INFO] or * 2025-11-16 01:51:21 (10893) [INFO] subscription-manager repos --disable= * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-16 01:51:21 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-16 01:51:21 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-16 01:51:21 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-16 01:51:21 (10893) [INFO] compromise: * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-16 01:51:21 (10893) [INFO] * 2025-11-16 01:51:21 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-16 01:51:21 (10910) [INFO] * 2025-11-16 01:51:21 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-16 01:51:21 (6712) [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 * 2025-11-16 01:51:23 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-16 01:51:23 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-16 01:51:23 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-16 01:51:23 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-16 01:51:23 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-16 01:51:29 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_TJthukQvY/ea_profile.json * 2025-11-16 01:53:57 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_TJthukQvY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-16 01:53:57 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-17 01:38:23 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-17 01:42:23 (11983) [INFO] Script is up to date. * 2025-11-17 01:46:26 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-17 01:46:26 (10880) [INFO] * 2025-11-17 01:47:46 (10910) [INFO] * 2025-11-17 01:47:46 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-17 01:47:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-17 01:47:47 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-17 01:47:47 (10880) [INFO] * 2025-11-17 01:47:50 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-17 01:47:50 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-17 01:47:50 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-17 01:47:50 (10880) [INFO] * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-17 01:48:25 (6852) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-17 01:48:25 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-17 01:48:25 (10880) [INFO] * 2025-11-17 01:48:25 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-17 01:48:26 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-17 01:48:57 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-17 01:48:57 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-17 01:48:57 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-17 01:48:57 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-17 01:48:57 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-17 01:48:57 (10893) [INFO] yum --disablerepo= ... * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-17 01:48:57 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-17 01:48:57 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] yum-config-manager --disable * 2025-11-17 01:48:57 (10893) [INFO] or * 2025-11-17 01:48:57 (10893) [INFO] subscription-manager repos --disable= * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-17 01:48:57 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-17 01:48:57 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-17 01:48:57 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-17 01:48:57 (10893) [INFO] compromise: * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-17 01:48:57 (10893) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-17 01:48:57 (10910) [INFO] * 2025-11-17 01:48:57 (6701) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-17 01:48:57 (6702) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-17 01:48:57 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-17 01:48:57 (10880) [INFO] * 2025-11-17 01:48:57 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-17 01:48:58 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-17 01:48:58 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-17 01:48:58 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-17 01:48:58 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-17 01:48:58 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-17 01:48:58 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-17 01:48:58 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-17 01:48:58 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-17 01:48:58 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-17 01:48:58 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-17 01:48:58 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-17 01:48:58 (10910) [INFO] * 2025-11-17 01:48:58 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-17 01:48:58 (10880) [INFO] * 2025-11-17 01:48:58 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-17 01:48:59 (10893) [INFO] Determining fastest mirrors * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-17 01:49:30 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-17 01:49:30 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-17 01:49:30 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-17 01:49:30 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-17 01:49:30 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-17 01:49:30 (10893) [INFO] yum --disablerepo= ... * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-17 01:49:30 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-17 01:49:30 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] yum-config-manager --disable * 2025-11-17 01:49:30 (10893) [INFO] or * 2025-11-17 01:49:30 (10893) [INFO] subscription-manager repos --disable= * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-17 01:49:30 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-17 01:49:30 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-17 01:49:30 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-17 01:49:30 (10893) [INFO] compromise: * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-17 01:49:30 (10893) [INFO] * 2025-11-17 01:49:30 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-17 01:49:30 (10910) [INFO] * 2025-11-17 01:49:30 (6711) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-17 01:49:30 (6712) [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 * 2025-11-17 01:49:32 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-17 01:49:32 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-17 01:49:32 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-17 01:49:32 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-17 01:49:32 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-17 01:49:38 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gCYXR0LEl5/ea_profile.json * 2025-11-17 01:52:06 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gCYXR0LEl5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-17 01:52:06 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-18 01:38:50 (11961) [INFO] Self-update of script version 73 requested. * 2025-11-18 01:42:50 (11966) [INFO] Newer version of script found. Downloading. * 2025-11-18 01:46:52 (11975) [INFO] Script update to version 74 successful. * 2025-11-18 01:50:55 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-18 01:50:55 (10880) [INFO] * 2025-11-18 01:52:11 (10910) [INFO] * 2025-11-18 01:52:11 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-18 01:52:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-18 01:52:11 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-18 01:52:11 (10880) [INFO] * 2025-11-18 01:52:15 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-18 01:52:15 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-18 01:52:15 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-18 01:52:15 (10880) [INFO] * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-18 01:52:49 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-18 01:52:49 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-18 01:52:49 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-18 01:52:49 (10880) [INFO] * 2025-11-18 01:52:49 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-18 01:52:49 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-18 01:53:20 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-18 01:53:20 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-18 01:53:20 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-18 01:53:20 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-18 01:53:20 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-18 01:53:20 (10893) [INFO] yum --disablerepo= ... * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-18 01:53:20 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-18 01:53:20 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] yum-config-manager --disable * 2025-11-18 01:53:20 (10893) [INFO] or * 2025-11-18 01:53:20 (10893) [INFO] subscription-manager repos --disable= * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-18 01:53:20 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-18 01:53:20 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-18 01:53:20 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-18 01:53:20 (10893) [INFO] compromise: * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-18 01:53:20 (10893) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-18 01:53:20 (10910) [INFO] * 2025-11-18 01:53:20 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-18 01:53:20 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-18 01:53:20 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-18 01:53:20 (10880) [INFO] * 2025-11-18 01:53:20 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-18 01:53:21 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-18 01:53:21 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-18 01:53:21 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-18 01:53:21 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-18 01:53:21 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-18 01:53:21 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-18 01:53:21 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-18 01:53:21 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-18 01:53:21 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-18 01:53:21 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-18 01:53:21 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-18 01:53:21 (10910) [INFO] * 2025-11-18 01:53:21 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-18 01:53:21 (10880) [INFO] * 2025-11-18 01:53:21 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-18 01:53:22 (10893) [INFO] Determining fastest mirrors * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-18 01:53:52 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-18 01:53:52 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-18 01:53:52 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-18 01:53:52 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-18 01:53:52 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-18 01:53:52 (10893) [INFO] yum --disablerepo= ... * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-18 01:53:52 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-18 01:53:52 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] yum-config-manager --disable * 2025-11-18 01:53:52 (10893) [INFO] or * 2025-11-18 01:53:52 (10893) [INFO] subscription-manager repos --disable= * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-18 01:53:52 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-18 01:53:52 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-18 01:53:52 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-18 01:53:52 (10893) [INFO] compromise: * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-18 01:53:52 (10893) [INFO] * 2025-11-18 01:53:52 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-18 01:53:53 (10910) [INFO] * 2025-11-18 01:53:53 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-18 01:53:53 (6726) [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 * 2025-11-18 01:53:54 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-18 01:53:54 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-18 01:53:54 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-18 01:53:54 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-18 01:53:54 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-18 01:54:01 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KJZ3qlfZLK/ea_profile.json * 2025-11-18 01:57:31 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KJZ3qlfZLK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-18 01:57:31 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-19 01:39:21 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-19 01:43:21 (11983) [INFO] Script is up to date. * 2025-11-19 01:47:25 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-19 01:47:25 (10880) [INFO] * 2025-11-19 01:48:45 (10910) [INFO] * 2025-11-19 01:48:45 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-19 01:48:45 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-19 01:48:45 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-19 01:48:45 (10880) [INFO] * 2025-11-19 01:56:21 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-19 01:56:21 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-19 01:56:21 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-19 01:56:21 (10880) [INFO] * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-19 01:56:55 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-19 01:56:55 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-19 01:56:55 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-19 01:56:55 (10880) [INFO] * 2025-11-19 01:56:55 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-19 01:56:56 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-19 01:57:26 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-19 01:57:26 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-19 01:57:26 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-19 01:57:26 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-19 01:57:26 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-19 01:57:26 (10893) [INFO] yum --disablerepo= ... * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-19 01:57:26 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-19 01:57:26 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] yum-config-manager --disable * 2025-11-19 01:57:26 (10893) [INFO] or * 2025-11-19 01:57:26 (10893) [INFO] subscription-manager repos --disable= * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-19 01:57:26 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-19 01:57:26 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-19 01:57:26 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-19 01:57:26 (10893) [INFO] compromise: * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-19 01:57:26 (10893) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-19 01:57:26 (10910) [INFO] * 2025-11-19 01:57:26 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-19 01:57:26 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-19 01:57:26 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-19 01:57:26 (10880) [INFO] * 2025-11-19 01:57:26 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-19 01:57:26 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-19 01:57:26 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-19 01:57:26 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-19 01:57:26 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-19 01:57:26 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-19 01:57:26 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-19 01:57:26 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-19 01:57:26 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-19 01:57:26 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-19 01:57:26 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-19 01:57:26 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-19 01:57:27 (10910) [INFO] * 2025-11-19 01:57:27 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-19 01:57:27 (10880) [INFO] * 2025-11-19 01:57:27 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-19 01:57:27 (10893) [INFO] Determining fastest mirrors * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-19 01:57:59 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-19 01:57:59 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-19 01:57:59 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-19 01:57:59 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-19 01:57:59 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-19 01:57:59 (10893) [INFO] yum --disablerepo= ... * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-19 01:57:59 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-19 01:57:59 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] yum-config-manager --disable * 2025-11-19 01:57:59 (10893) [INFO] or * 2025-11-19 01:57:59 (10893) [INFO] subscription-manager repos --disable= * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-19 01:57:59 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-19 01:57:59 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-19 01:57:59 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-19 01:57:59 (10893) [INFO] compromise: * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-19 01:57:59 (10893) [INFO] * 2025-11-19 01:57:59 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-19 01:57:59 (10910) [INFO] * 2025-11-19 01:57:59 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-19 01:57:59 (6726) [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 * 2025-11-19 01:58:00 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-19 01:58:00 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-19 01:58:00 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-19 01:58:00 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-19 01:58:00 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-19 01:58:06 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jhyqeVkcFr/ea_profile.json * 2025-11-19 02:00:35 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jhyqeVkcFr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-19 02:00:35 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-20 01:39:38 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-20 01:43:38 (11983) [INFO] Script is up to date. * 2025-11-20 01:47:40 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-20 01:47:40 (10880) [INFO] * 2025-11-20 01:48:59 (10910) [INFO] * 2025-11-20 01:48:59 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-20 01:49:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-20 01:49:00 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-20 01:49:00 (10880) [INFO] * 2025-11-20 02:01:02 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-20 02:01:02 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-20 02:01:02 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-20 02:01:02 (10880) [INFO] * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-20 02:01:38 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-20 02:01:38 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-20 02:01:38 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-20 02:01:38 (10880) [INFO] * 2025-11-20 02:01:38 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-20 02:01:39 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-20 02:02:09 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-20 02:02:09 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-20 02:02:09 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-20 02:02:09 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-20 02:02:09 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-20 02:02:09 (10893) [INFO] yum --disablerepo= ... * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-20 02:02:09 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-20 02:02:09 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] yum-config-manager --disable * 2025-11-20 02:02:09 (10893) [INFO] or * 2025-11-20 02:02:09 (10893) [INFO] subscription-manager repos --disable= * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-20 02:02:09 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-20 02:02:09 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-20 02:02:09 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-20 02:02:09 (10893) [INFO] compromise: * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-20 02:02:09 (10893) [INFO] * 2025-11-20 02:02:09 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-20 02:02:09 (10910) [INFO] * 2025-11-20 02:02:09 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-20 02:02:09 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-20 02:02:09 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-20 02:02:09 (10880) [INFO] * 2025-11-20 02:02:10 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-20 02:02:10 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-20 02:02:10 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-20 02:02:10 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-20 02:02:10 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-20 02:02:10 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-20 02:02:10 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-20 02:02:10 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-20 02:02:10 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-20 02:02:10 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-20 02:02:10 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-20 02:02:10 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-20 02:02:10 (10910) [INFO] * 2025-11-20 02:02:10 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-20 02:02:10 (10880) [INFO] * 2025-11-20 02:02:11 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-20 02:02:11 (10893) [INFO] Determining fastest mirrors * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-20 02:02:42 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-20 02:02:42 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-20 02:02:42 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-20 02:02:42 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-20 02:02:42 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-20 02:02:42 (10893) [INFO] yum --disablerepo= ... * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-20 02:02:42 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-20 02:02:42 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] yum-config-manager --disable * 2025-11-20 02:02:42 (10893) [INFO] or * 2025-11-20 02:02:42 (10893) [INFO] subscription-manager repos --disable= * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-20 02:02:42 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-20 02:02:42 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-20 02:02:42 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-20 02:02:42 (10893) [INFO] compromise: * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-20 02:02:42 (10893) [INFO] * 2025-11-20 02:02:42 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-20 02:02:42 (10910) [INFO] * 2025-11-20 02:02:42 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-20 02:02:42 (6726) [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 * 2025-11-20 02:02:44 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-20 02:02:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-20 02:02:44 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-20 02:02:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-20 02:02:44 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-20 02:02:50 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iVrav9UH3N/ea_profile.json * 2025-11-20 02:05:16 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iVrav9UH3N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-20 02:05:16 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-21 01:40:15 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-21 01:44:15 (11983) [INFO] Script is up to date. * 2025-11-21 01:48:18 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-21 01:48:18 (10880) [INFO] * 2025-11-21 01:49:33 (10910) [INFO] * 2025-11-21 01:49:33 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-21 01:49:33 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-21 01:49:33 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-21 01:49:33 (10880) [INFO] * 2025-11-21 02:00:38 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-21 02:00:38 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-21 02:00:38 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-21 02:00:38 (10880) [INFO] * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-21 02:01:16 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-21 02:01:16 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-21 02:01:16 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-21 02:01:16 (10880) [INFO] * 2025-11-21 02:01:16 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-21 02:01:17 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-21 02:01:48 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-21 02:01:48 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-21 02:01:48 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-21 02:01:48 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-21 02:01:48 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-21 02:01:48 (10893) [INFO] yum --disablerepo= ... * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-21 02:01:48 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-21 02:01:48 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] yum-config-manager --disable * 2025-11-21 02:01:48 (10893) [INFO] or * 2025-11-21 02:01:48 (10893) [INFO] subscription-manager repos --disable= * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-21 02:01:48 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-21 02:01:48 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-21 02:01:48 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-21 02:01:48 (10893) [INFO] compromise: * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-21 02:01:48 (10893) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-21 02:01:48 (10910) [INFO] * 2025-11-21 02:01:48 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-21 02:01:48 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-21 02:01:48 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-21 02:01:48 (10880) [INFO] * 2025-11-21 02:01:48 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-21 02:01:49 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-21 02:01:49 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-21 02:01:49 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-21 02:01:49 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-21 02:01:49 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-21 02:01:49 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-21 02:01:49 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-21 02:01:49 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-21 02:01:49 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-21 02:01:49 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-21 02:01:49 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-21 02:01:49 (10910) [INFO] * 2025-11-21 02:01:49 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-21 02:01:49 (10880) [INFO] * 2025-11-21 02:01:49 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-21 02:01:50 (10893) [INFO] Determining fastest mirrors * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-21 02:02:21 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-21 02:02:21 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-21 02:02:21 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-21 02:02:21 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-21 02:02:21 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-21 02:02:21 (10893) [INFO] yum --disablerepo= ... * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-21 02:02:21 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-21 02:02:21 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] yum-config-manager --disable * 2025-11-21 02:02:21 (10893) [INFO] or * 2025-11-21 02:02:21 (10893) [INFO] subscription-manager repos --disable= * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-21 02:02:21 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-21 02:02:21 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-21 02:02:21 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-21 02:02:21 (10893) [INFO] compromise: * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-21 02:02:21 (10893) [INFO] * 2025-11-21 02:02:21 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-21 02:02:22 (10910) [INFO] * 2025-11-21 02:02:22 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-21 02:02:22 (6726) [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 * 2025-11-21 02:02:23 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-21 02:02:23 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-21 02:02:23 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-21 02:02:23 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-21 02:02:23 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-21 02:02:29 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Wn3uvbFyjd/ea_profile.json * 2025-11-21 02:05:57 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Wn3uvbFyjd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-21 02:05:57 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-22 01:40:26 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-22 01:44:27 (11983) [INFO] Script is up to date. * 2025-11-22 01:48:29 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-22 01:48:29 (10880) [INFO] * 2025-11-22 01:49:22 (10910) [INFO] * 2025-11-22 01:49:22 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-22 01:49:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-22 01:49:23 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-22 01:49:23 (10880) [INFO] * 2025-11-22 01:56:21 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-22 01:56:21 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-22 01:56:21 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-22 01:56:21 (10880) [INFO] * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-22 01:56:56 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-22 01:56:56 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-22 01:56:56 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-22 01:56:56 (10880) [INFO] * 2025-11-22 01:56:57 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-22 01:56:57 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-22 01:57:28 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-22 01:57:28 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-22 01:57:28 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-22 01:57:28 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-22 01:57:28 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-22 01:57:28 (10893) [INFO] yum --disablerepo= ... * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-22 01:57:28 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-22 01:57:28 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] yum-config-manager --disable * 2025-11-22 01:57:28 (10893) [INFO] or * 2025-11-22 01:57:28 (10893) [INFO] subscription-manager repos --disable= * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-22 01:57:28 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-22 01:57:28 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-22 01:57:28 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-22 01:57:28 (10893) [INFO] compromise: * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-22 01:57:28 (10893) [INFO] * 2025-11-22 01:57:28 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-22 01:57:28 (10910) [INFO] * 2025-11-22 01:57:28 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-22 01:57:28 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-22 01:57:28 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-22 01:57:28 (10880) [INFO] * 2025-11-22 01:57:29 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-22 01:57:29 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-22 01:57:29 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-22 01:57:29 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-22 01:57:29 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-22 01:57:29 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-22 01:57:29 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-22 01:57:29 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-22 01:57:29 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-22 01:57:29 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-22 01:57:29 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-22 01:57:29 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-22 01:57:29 (10910) [INFO] * 2025-11-22 01:57:29 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-22 01:57:29 (10880) [INFO] * 2025-11-22 01:57:29 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-22 01:57:29 (10893) [INFO] Determining fastest mirrors * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-22 01:58:01 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-22 01:58:01 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-22 01:58:01 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-22 01:58:01 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-22 01:58:01 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-22 01:58:01 (10893) [INFO] yum --disablerepo= ... * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-22 01:58:01 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-22 01:58:01 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] yum-config-manager --disable * 2025-11-22 01:58:01 (10893) [INFO] or * 2025-11-22 01:58:01 (10893) [INFO] subscription-manager repos --disable= * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-22 01:58:01 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-22 01:58:01 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-22 01:58:01 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-22 01:58:01 (10893) [INFO] compromise: * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-22 01:58:01 (10893) [INFO] * 2025-11-22 01:58:01 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-22 01:58:01 (10910) [INFO] * 2025-11-22 01:58:01 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-22 01:58:01 (6726) [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 * 2025-11-22 01:58:02 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-22 01:58:02 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-22 01:58:02 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-22 01:58:02 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-22 01:58:02 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-22 01:58:09 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rAi52GuZO5/ea_profile.json * 2025-11-22 02:00:36 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rAi52GuZO5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-22 02:00:36 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-23 01:40:29 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-23 01:44:29 (11983) [INFO] Script is up to date. * 2025-11-23 01:48:32 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-23 01:48:32 (10880) [INFO] * 2025-11-23 01:49:25 (10910) [INFO] * 2025-11-23 01:49:25 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-23 01:49:25 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-23 01:49:25 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-23 01:49:25 (10880) [INFO] * 2025-11-23 01:56:23 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-23 01:56:23 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-23 01:56:23 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-23 01:56:23 (10880) [INFO] * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-23 01:56:58 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-23 01:56:58 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-23 01:56:58 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-23 01:56:58 (10880) [INFO] * 2025-11-23 01:56:58 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-23 01:56:59 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-23 01:57:30 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-23 01:57:30 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-23 01:57:30 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-23 01:57:30 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-23 01:57:30 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-23 01:57:30 (10893) [INFO] yum --disablerepo= ... * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-23 01:57:30 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-23 01:57:30 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] yum-config-manager --disable * 2025-11-23 01:57:30 (10893) [INFO] or * 2025-11-23 01:57:30 (10893) [INFO] subscription-manager repos --disable= * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-23 01:57:30 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-23 01:57:30 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-23 01:57:30 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-23 01:57:30 (10893) [INFO] compromise: * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-23 01:57:30 (10893) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-23 01:57:30 (10910) [INFO] * 2025-11-23 01:57:30 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-23 01:57:30 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-23 01:57:30 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-23 01:57:30 (10880) [INFO] * 2025-11-23 01:57:30 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-23 01:57:30 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-23 01:57:30 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-23 01:57:30 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-23 01:57:30 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-23 01:57:30 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-23 01:57:30 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-23 01:57:30 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-23 01:57:30 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-23 01:57:30 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-23 01:57:30 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-23 01:57:30 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-23 01:57:30 (10910) [INFO] * 2025-11-23 01:57:30 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-23 01:57:30 (10880) [INFO] * 2025-11-23 01:57:31 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-23 01:57:31 (10893) [INFO] Determining fastest mirrors * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-23 01:58:01 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-23 01:58:01 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-23 01:58:01 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-23 01:58:01 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-23 01:58:01 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-23 01:58:01 (10893) [INFO] yum --disablerepo= ... * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-23 01:58:01 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-23 01:58:01 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] yum-config-manager --disable * 2025-11-23 01:58:01 (10893) [INFO] or * 2025-11-23 01:58:01 (10893) [INFO] subscription-manager repos --disable= * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-23 01:58:01 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-23 01:58:01 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-23 01:58:01 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-23 01:58:01 (10893) [INFO] compromise: * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-23 01:58:01 (10893) [INFO] * 2025-11-23 01:58:01 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-23 01:58:01 (10910) [INFO] * 2025-11-23 01:58:01 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-23 01:58:01 (6726) [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 * 2025-11-23 01:58:03 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-23 01:58:03 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-23 01:58:03 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-23 01:58:03 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-23 01:58:03 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-23 01:58:09 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pbQcIMsam4/ea_profile.json * 2025-11-23 02:00:36 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pbQcIMsam4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-23 02:00:36 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-24 01:39:13 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-24 01:43:13 (11983) [INFO] Script is up to date. * 2025-11-24 01:47:15 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-24 01:47:15 (10880) [INFO] * 2025-11-24 01:48:34 (10910) [INFO] * 2025-11-24 01:48:34 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-24 01:48:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-24 01:48:34 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-24 01:48:34 (10880) [INFO] * 2025-11-24 01:55:32 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-24 01:55:32 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-24 01:55:32 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-24 01:55:32 (10880) [INFO] * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-24 01:56:08 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-24 01:56:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-24 01:56:08 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-24 01:56:08 (10880) [INFO] * 2025-11-24 01:56:09 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-24 01:56:09 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-24 01:56:40 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-24 01:56:40 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-24 01:56:40 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-24 01:56:40 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-24 01:56:40 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-24 01:56:40 (10893) [INFO] yum --disablerepo= ... * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-24 01:56:40 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-24 01:56:40 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] yum-config-manager --disable * 2025-11-24 01:56:40 (10893) [INFO] or * 2025-11-24 01:56:40 (10893) [INFO] subscription-manager repos --disable= * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-24 01:56:40 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-24 01:56:40 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-24 01:56:40 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-24 01:56:40 (10893) [INFO] compromise: * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-24 01:56:40 (10893) [INFO] * 2025-11-24 01:56:40 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-24 01:56:40 (10910) [INFO] * 2025-11-24 01:56:40 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-24 01:56:40 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-24 01:56:40 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-24 01:56:40 (10880) [INFO] * 2025-11-24 01:56:41 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-24 01:56:41 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-24 01:56:41 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-24 01:56:41 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-24 01:56:41 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-24 01:56:41 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-24 01:56:41 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-24 01:56:41 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-24 01:56:41 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-24 01:56:41 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-24 01:56:41 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-24 01:56:41 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-24 01:56:41 (10910) [INFO] * 2025-11-24 01:56:41 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-24 01:56:41 (10880) [INFO] * 2025-11-24 01:56:42 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-24 01:56:42 (10893) [INFO] Determining fastest mirrors * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-24 01:57:12 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-24 01:57:12 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-24 01:57:12 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-24 01:57:12 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-24 01:57:12 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-24 01:57:12 (10893) [INFO] yum --disablerepo= ... * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-24 01:57:12 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-24 01:57:12 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] yum-config-manager --disable * 2025-11-24 01:57:12 (10893) [INFO] or * 2025-11-24 01:57:12 (10893) [INFO] subscription-manager repos --disable= * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-24 01:57:12 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-24 01:57:12 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-24 01:57:12 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-24 01:57:12 (10893) [INFO] compromise: * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-24 01:57:12 (10893) [INFO] * 2025-11-24 01:57:12 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-24 01:57:12 (10910) [INFO] * 2025-11-24 01:57:12 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-24 01:57:12 (6726) [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 * 2025-11-24 01:57:14 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-24 01:57:14 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-24 01:57:14 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-24 01:57:14 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-24 01:57:14 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-24 01:57:21 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9d81hE1xr3/ea_profile.json * 2025-11-24 01:59:50 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9d81hE1xr3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-24 01:59:50 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-25 01:39:40 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-25 01:43:40 (11983) [INFO] Script is up to date. * 2025-11-25 01:47:43 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-25 01:47:43 (10880) [INFO] * 2025-11-25 01:49:00 (10910) [INFO] * 2025-11-25 01:49:00 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-25 01:49:00 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-25 01:49:00 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-25 01:49:00 (10880) [INFO] * 2025-11-25 01:56:01 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-25 01:56:01 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-25 01:56:01 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-25 01:56:01 (10880) [INFO] * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-25 01:56:36 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-25 01:56:36 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-25 01:56:36 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-25 01:56:36 (10880) [INFO] * 2025-11-25 01:56:36 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-25 01:56:36 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-25 01:57:07 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-25 01:57:07 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-25 01:57:07 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-25 01:57:07 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-25 01:57:07 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-25 01:57:07 (10893) [INFO] yum --disablerepo= ... * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-25 01:57:07 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-25 01:57:07 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] yum-config-manager --disable * 2025-11-25 01:57:07 (10893) [INFO] or * 2025-11-25 01:57:07 (10893) [INFO] subscription-manager repos --disable= * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-25 01:57:07 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-25 01:57:07 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-25 01:57:07 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-25 01:57:07 (10893) [INFO] compromise: * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-25 01:57:07 (10893) [INFO] * 2025-11-25 01:57:07 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-25 01:57:07 (10910) [INFO] * 2025-11-25 01:57:07 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-25 01:57:07 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-25 01:57:07 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-25 01:57:07 (10880) [INFO] * 2025-11-25 01:57:08 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-25 01:57:08 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-25 01:57:08 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-25 01:57:08 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-25 01:57:08 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-25 01:57:08 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-25 01:57:08 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-25 01:57:08 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-25 01:57:08 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-25 01:57:08 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-25 01:57:08 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-25 01:57:08 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-25 01:57:08 (10910) [INFO] * 2025-11-25 01:57:08 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-25 01:57:08 (10880) [INFO] * 2025-11-25 01:57:09 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-25 01:57:09 (10893) [INFO] Determining fastest mirrors * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-25 01:57:40 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-25 01:57:40 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-25 01:57:40 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-25 01:57:40 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-25 01:57:40 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-25 01:57:40 (10893) [INFO] yum --disablerepo= ... * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-25 01:57:40 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-25 01:57:40 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] yum-config-manager --disable * 2025-11-25 01:57:40 (10893) [INFO] or * 2025-11-25 01:57:40 (10893) [INFO] subscription-manager repos --disable= * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-25 01:57:40 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-25 01:57:40 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-25 01:57:40 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-25 01:57:40 (10893) [INFO] compromise: * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-25 01:57:40 (10893) [INFO] * 2025-11-25 01:57:40 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-25 01:57:40 (10910) [INFO] * 2025-11-25 01:57:40 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-25 01:57:40 (6726) [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 * 2025-11-25 01:57:42 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-25 01:57:42 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-25 01:57:42 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-25 01:57:42 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-25 01:57:42 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-25 01:57:49 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g4mBZrjlzG/ea_profile.json * 2025-11-25 02:00:47 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/g4mBZrjlzG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-25 02:00:47 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-26 01:39:41 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-26 01:43:42 (11983) [INFO] Script is up to date. * 2025-11-26 01:47:44 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-26 01:47:44 (10880) [INFO] * 2025-11-26 01:49:01 (10910) [INFO] * 2025-11-26 01:49:01 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-26 01:49:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-26 01:49:01 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-26 01:49:01 (10880) [INFO] * 2025-11-27 01:40:53 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-27 01:44:54 (11983) [INFO] Script is up to date. * 2025-11-27 01:48:57 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-27 01:48:57 (10880) [INFO] * 2025-11-27 01:50:12 (10910) [INFO] * 2025-11-27 01:50:12 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-27 01:50:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-27 01:50:12 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-27 01:50:12 (10880) [INFO] * 2025-11-27 01:52:00 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-27 01:52:00 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-27 01:52:00 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-27 01:52:00 (10880) [INFO] * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-27 01:52:37 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-27 01:52:37 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-27 01:52:37 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-27 01:52:37 (10880) [INFO] * 2025-11-27 01:52:37 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-27 01:52:37 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-27 01:53:09 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-27 01:53:09 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-27 01:53:09 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-27 01:53:09 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-27 01:53:09 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-27 01:53:09 (10893) [INFO] yum --disablerepo= ... * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-27 01:53:09 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-27 01:53:09 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] yum-config-manager --disable * 2025-11-27 01:53:09 (10893) [INFO] or * 2025-11-27 01:53:09 (10893) [INFO] subscription-manager repos --disable= * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-27 01:53:09 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-27 01:53:09 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-27 01:53:09 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-27 01:53:09 (10893) [INFO] compromise: * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-27 01:53:09 (10893) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-27 01:53:09 (10910) [INFO] * 2025-11-27 01:53:09 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-27 01:53:09 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-27 01:53:09 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-27 01:53:09 (10880) [INFO] * 2025-11-27 01:53:09 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-27 01:53:09 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-27 01:53:09 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-27 01:53:09 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-27 01:53:09 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-27 01:53:09 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-27 01:53:09 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-27 01:53:09 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-27 01:53:09 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-27 01:53:09 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-27 01:53:09 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-27 01:53:09 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-27 01:53:09 (10910) [INFO] * 2025-11-27 01:53:09 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-27 01:53:09 (10880) [INFO] * 2025-11-27 01:53:10 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-27 01:53:10 (10893) [INFO] Determining fastest mirrors * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-27 01:53:41 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-27 01:53:41 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-27 01:53:41 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-27 01:53:41 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-27 01:53:41 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-27 01:53:41 (10893) [INFO] yum --disablerepo= ... * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-27 01:53:41 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-27 01:53:41 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] yum-config-manager --disable * 2025-11-27 01:53:41 (10893) [INFO] or * 2025-11-27 01:53:41 (10893) [INFO] subscription-manager repos --disable= * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-27 01:53:41 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-27 01:53:41 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-27 01:53:41 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-27 01:53:41 (10893) [INFO] compromise: * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-27 01:53:41 (10893) [INFO] * 2025-11-27 01:53:41 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-27 01:53:42 (10910) [INFO] * 2025-11-27 01:53:42 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-27 01:53:42 (6726) [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 * 2025-11-27 01:53:43 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-27 01:53:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-27 01:53:43 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-27 01:53:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-27 01:53:43 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-27 01:53:50 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/PRxBsO54Ub/ea_profile.json * 2025-11-27 01:56:18 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/PRxBsO54Ub/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-27 01:56:18 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-28 01:39:05 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-28 01:43:05 (11983) [INFO] Script is up to date. * 2025-11-28 01:47:08 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-28 01:47:08 (10880) [INFO] * 2025-11-28 01:48:24 (10910) [INFO] * 2025-11-28 01:48:24 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-28 01:48:24 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-28 01:48:24 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-28 01:48:24 (10880) [INFO] * 2025-11-28 01:55:21 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-28 01:55:21 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-28 01:55:21 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-28 01:55:21 (10880) [INFO] * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-28 01:55:56 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-28 01:55:56 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-28 01:55:56 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-28 01:55:56 (10880) [INFO] * 2025-11-28 01:55:57 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-28 01:55:57 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-28 01:56:30 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-28 01:56:30 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-28 01:56:30 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-28 01:56:30 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-28 01:56:30 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-28 01:56:30 (10893) [INFO] yum --disablerepo= ... * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-28 01:56:30 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-28 01:56:30 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] yum-config-manager --disable * 2025-11-28 01:56:30 (10893) [INFO] or * 2025-11-28 01:56:30 (10893) [INFO] subscription-manager repos --disable= * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-28 01:56:30 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-28 01:56:30 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-28 01:56:30 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-28 01:56:30 (10893) [INFO] compromise: * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-28 01:56:30 (10893) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-28 01:56:30 (10910) [INFO] * 2025-11-28 01:56:30 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-28 01:56:30 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-28 01:56:30 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-28 01:56:30 (10880) [INFO] * 2025-11-28 01:56:30 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-28 01:56:31 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-28 01:56:31 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-28 01:56:31 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-28 01:56:31 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-28 01:56:31 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-28 01:56:31 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-28 01:56:31 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-28 01:56:31 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-28 01:56:31 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-28 01:56:31 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-28 01:56:31 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-11-28 01:56:31 (10910) [INFO] * 2025-11-28 01:56:31 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-28 01:56:31 (10880) [INFO] * 2025-11-28 01:56:31 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-28 01:56:32 (10893) [INFO] Determining fastest mirrors * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-28 01:57:02 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-28 01:57:02 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-28 01:57:02 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-28 01:57:02 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-28 01:57:02 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-28 01:57:02 (10893) [INFO] yum --disablerepo= ... * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-28 01:57:02 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-28 01:57:02 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] yum-config-manager --disable * 2025-11-28 01:57:02 (10893) [INFO] or * 2025-11-28 01:57:02 (10893) [INFO] subscription-manager repos --disable= * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-28 01:57:02 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-28 01:57:02 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-28 01:57:02 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-28 01:57:02 (10893) [INFO] compromise: * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-28 01:57:02 (10893) [INFO] * 2025-11-28 01:57:02 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-28 01:57:02 (10910) [INFO] * 2025-11-28 01:57:02 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-28 01:57:02 (6726) [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 * 2025-11-28 01:57:04 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-28 01:57:04 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-28 01:57:04 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-28 01:57:04 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-28 01:57:04 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-28 01:57:10 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c4MATwBWeW/ea_profile.json * 2025-11-28 02:00:08 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c4MATwBWeW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-28 02:00:08 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-29 01:40:27 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-29 01:44:27 (11983) [INFO] Script is up to date. * 2025-11-29 01:48:30 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-29 01:48:30 (10880) [INFO] * 2025-11-29 01:49:20 (10910) [INFO] * 2025-11-29 01:49:20 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-29 01:49:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-29 01:49:20 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-29 01:49:20 (10880) [INFO] * 2025-11-29 01:56:19 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-29 01:56:19 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-29 01:56:19 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-29 01:56:19 (10880) [INFO] * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-29 01:56:56 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-29 01:56:56 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-29 01:56:56 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-29 01:56:56 (10880) [INFO] * 2025-11-29 01:56:56 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-29 01:56:56 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-29 01:57:27 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-29 01:57:27 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-29 01:57:27 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-29 01:57:27 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-29 01:57:27 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-29 01:57:27 (10893) [INFO] yum --disablerepo= ... * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-29 01:57:27 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-29 01:57:27 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] yum-config-manager --disable * 2025-11-29 01:57:27 (10893) [INFO] or * 2025-11-29 01:57:27 (10893) [INFO] subscription-manager repos --disable= * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-29 01:57:27 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-29 01:57:27 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-29 01:57:27 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-29 01:57:27 (10893) [INFO] compromise: * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-29 01:57:27 (10893) [INFO] * 2025-11-29 01:57:27 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-29 01:57:28 (10910) [INFO] * 2025-11-29 01:57:28 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-29 01:57:28 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-29 01:57:28 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-29 01:57:28 (10880) [INFO] * 2025-11-29 01:57:28 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-29 01:57:28 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-29 01:57:28 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-29 01:57:28 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-29 01:57:28 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-29 01:57:28 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-29 01:57:28 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-29 01:57:28 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-29 01:57:28 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-29 01:57:28 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-29 01:57:29 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-29 01:57:29 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-29 01:57:29 (10910) [INFO] * 2025-11-29 01:57:29 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-29 01:57:29 (10880) [INFO] * 2025-11-29 01:57:29 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-29 01:57:29 (10893) [INFO] Determining fastest mirrors * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-29 01:58:00 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-29 01:58:00 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-29 01:58:00 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-29 01:58:00 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-29 01:58:00 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-29 01:58:00 (10893) [INFO] yum --disablerepo= ... * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-29 01:58:00 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-29 01:58:00 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] yum-config-manager --disable * 2025-11-29 01:58:00 (10893) [INFO] or * 2025-11-29 01:58:00 (10893) [INFO] subscription-manager repos --disable= * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-29 01:58:00 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-29 01:58:00 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-29 01:58:00 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-29 01:58:00 (10893) [INFO] compromise: * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-29 01:58:00 (10893) [INFO] * 2025-11-29 01:58:00 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-29 01:58:00 (10910) [INFO] * 2025-11-29 01:58:00 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-29 01:58:00 (6726) [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 * 2025-11-29 01:58:02 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-29 01:58:02 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-29 01:58:02 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-29 01:58:02 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-29 01:58:02 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-29 01:58:08 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ELdmpUww9t/ea_profile.json * 2025-11-29 02:01:38 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ELdmpUww9t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-29 02:01:38 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-11-30 01:39:48 (11961) [INFO] Self-update of script version 74 requested. * 2025-11-30 01:43:48 (11983) [INFO] Script is up to date. * 2025-11-30 01:47:51 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-11-30 01:47:51 (10880) [INFO] * 2025-11-30 01:48:44 (10910) [INFO] * 2025-11-30 01:48:44 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-11-30 01:48:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-11-30 01:48:44 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-11-30 01:48:44 (10880) [INFO] * 2025-11-30 01:48:47 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-11-30 01:48:47 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-11-30 01:48:47 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-11-30 01:48:47 (10880) [INFO] * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-11-30 01:49:23 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-11-30 01:49:23 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-11-30 01:49:23 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-30 01:49:23 (10880) [INFO] * 2025-11-30 01:49:24 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-30 01:49:24 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-30 01:49:55 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-30 01:49:55 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-30 01:49:55 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-30 01:49:55 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-30 01:49:55 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-30 01:49:55 (10893) [INFO] yum --disablerepo= ... * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-30 01:49:55 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-30 01:49:55 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] yum-config-manager --disable * 2025-11-30 01:49:55 (10893) [INFO] or * 2025-11-30 01:49:55 (10893) [INFO] subscription-manager repos --disable= * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-30 01:49:55 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-30 01:49:55 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-30 01:49:55 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-30 01:49:55 (10893) [INFO] compromise: * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-30 01:49:55 (10893) [INFO] * 2025-11-30 01:49:55 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-30 01:49:55 (10910) [INFO] * 2025-11-30 01:49:55 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-30 01:49:55 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-11-30 01:49:55 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-11-30 01:49:55 (10880) [INFO] * 2025-11-30 01:49:56 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-30 01:49:56 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-11-30 01:49:56 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-11-30 01:49:56 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-11-30 01:49:56 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-11-30 01:49:56 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-11-30 01:49:56 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-11-30 01:49:56 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-11-30 01:49:56 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-11-30 01:49:56 (10893) [INFO] : wp-toolkit-thirdparties * 2025-11-30 01:49:56 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-11-30 01:49:56 (10893) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-11-30 01:49:56 (10910) [INFO] * 2025-11-30 01:49:56 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-11-30 01:49:56 (10880) [INFO] * 2025-11-30 01:49:57 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-11-30 01:49:57 (10893) [INFO] Determining fastest mirrors * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-11-30 01:50:27 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-11-30 01:50:27 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-11-30 01:50:27 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-11-30 01:50:27 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-11-30 01:50:27 (10893) [INFO] packages for the previous distribution release still work). * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-11-30 01:50:27 (10893) [INFO] yum --disablerepo= ... * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-11-30 01:50:27 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-11-30 01:50:27 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] yum-config-manager --disable * 2025-11-30 01:50:27 (10893) [INFO] or * 2025-11-30 01:50:27 (10893) [INFO] subscription-manager repos --disable= * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-11-30 01:50:27 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-11-30 01:50:27 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-11-30 01:50:27 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-11-30 01:50:27 (10893) [INFO] compromise: * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-11-30 01:50:27 (10893) [INFO] * 2025-11-30 01:50:27 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-11-30 01:50:27 (10910) [INFO] * 2025-11-30 01:50:27 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-11-30 01:50:27 (6726) [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 * 2025-11-30 01:50:29 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-11-30 01:50:29 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-11-30 01:50:29 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-11-30 01:50:29 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-11-30 01:50:29 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-11-30 01:50:36 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/aqdD_bIQSu/ea_profile.json * 2025-11-30 01:53:03 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/aqdD_bIQSu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-11-30 01:53:03 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-01 01:38:38 (11961) [INFO] Self-update of script version 74 requested. * 2025-12-01 01:42:38 (11983) [INFO] Script is up to date. * 2025-12-01 01:46:41 (10879) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-01 01:46:41 (10880) [INFO] * 2025-12-01 01:47:53 (10910) [INFO] * 2025-12-01 01:47:53 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-01 01:47:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-01 01:47:54 (10879) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-01 01:47:54 (10880) [INFO] * 2025-12-01 01:54:53 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-01 01:54:53 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-01 01:54:53 (10879) [INFO] Running: /usr/bin/yum list extras * 2025-12-01 01:54:53 (10880) [INFO] * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-01 01:55:28 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-01 01:55:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-01 01:55:28 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-12-01 01:55:28 (10880) [INFO] * 2025-12-01 01:55:29 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-01 01:55:29 (10893) [INFO] Loading mirror speeds from cached hostfile * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-12-01 01:56:01 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-01 01:56:01 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-01 01:56:01 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-01 01:56:01 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-12-01 01:56:01 (10893) [INFO] packages for the previous distribution release still work). * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-01 01:56:01 (10893) [INFO] yum --disablerepo= ... * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-01 01:56:01 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-01 01:56:01 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] yum-config-manager --disable * 2025-12-01 01:56:01 (10893) [INFO] or * 2025-12-01 01:56:01 (10893) [INFO] subscription-manager repos --disable= * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-01 01:56:01 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-01 01:56:01 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-01 01:56:01 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-01 01:56:01 (10893) [INFO] compromise: * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-01 01:56:01 (10893) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-01 01:56:01 (10910) [INFO] * 2025-12-01 01:56:01 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-01 01:56:01 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-01 01:56:01 (10879) [INFO] Running: /usr/bin/yum clean all * 2025-12-01 01:56:01 (10880) [INFO] * 2025-12-01 01:56:01 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-01 01:56:02 (10893) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-01 01:56:02 (10893) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-01 01:56:02 (10893) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-01 01:56:02 (10893) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-01 01:56:02 (10893) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-01 01:56:02 (10893) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-01 01:56:02 (10893) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-01 01:56:02 (10893) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-01 01:56:02 (10893) [INFO] : wp-toolkit-thirdparties * 2025-12-01 01:56:02 (10893) [INFO] Cleaning up list of fastest mirrors * 2025-12-01 01:56:02 (10893) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-12-01 01:56:02 (10910) [INFO] * 2025-12-01 01:56:02 (10879) [INFO] Running: /usr/bin/yum makecache * 2025-12-01 01:56:02 (10880) [INFO] * 2025-12-01 01:56:02 (10893) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-01 01:56:02 (10893) [INFO] Determining fastest mirrors * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] One of the configured repositories failed (Unknown), * 2025-12-01 01:56:33 (10893) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-01 01:56:33 (10893) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-01 01:56:33 (10893) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-01 01:56:33 (10893) [INFO] distribution release than is supported by the repository (and the * 2025-12-01 01:56:33 (10893) [INFO] packages for the previous distribution release still work). * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-01 01:56:33 (10893) [INFO] yum --disablerepo= ... * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-01 01:56:33 (10893) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-01 01:56:33 (10893) [INFO] again or use --enablerepo for temporary usage: * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] yum-config-manager --disable * 2025-12-01 01:56:33 (10893) [INFO] or * 2025-12-01 01:56:33 (10893) [INFO] subscription-manager repos --disable= * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-01 01:56:33 (10893) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-01 01:56:33 (10893) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-01 01:56:33 (10893) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-01 01:56:33 (10893) [INFO] compromise: * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-01 01:56:33 (10893) [INFO] * 2025-12-01 01:56:33 (10893) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-01 01:56:33 (10910) [INFO] * 2025-12-01 01:56:33 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-01 01:56:33 (6726) [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 * 2025-12-01 01:56:35 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-01 01:56:35 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-01 01:56:35 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-01 01:56:35 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-01 01:56:35 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-01 01:56:42 (9989) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cgSQAwg2vy/ea_profile.json * 2025-12-01 01:59:09 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/cgSQAwg2vy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9991. * 2025-12-01 01:59:09 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-02 01:39:37 (11961) [INFO] Self-update of script version 74 requested. * 2025-12-02 01:43:37 (11966) [INFO] Newer version of script found. Downloading. * 2025-12-02 01:47:39 (11975) [INFO] Script update to version 75 successful. * 2025-12-02 01:51:41 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-02 01:51:41 (10879) [INFO] * 2025-12-02 01:52:59 (10909) [INFO] * 2025-12-02 01:52:59 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-02 01:52:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-02 01:52:59 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-02 01:52:59 (10879) [INFO] * 2025-12-02 01:59:59 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-02 01:59:59 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-02 01:59:59 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-02 01:59:59 (10879) [INFO] * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-02 02:00:34 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-02 02:00:34 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-02 02:00:34 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-02 02:00:34 (10879) [INFO] * 2025-12-02 02:00:35 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-02 02:00:35 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-02 02:01:06 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-02 02:01:06 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-02 02:01:06 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-02 02:01:06 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-02 02:01:06 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-02 02:01:06 (10892) [INFO] yum --disablerepo= ... * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-02 02:01:06 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-02 02:01:06 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] yum-config-manager --disable * 2025-12-02 02:01:06 (10892) [INFO] or * 2025-12-02 02:01:06 (10892) [INFO] subscription-manager repos --disable= * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-02 02:01:06 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-02 02:01:06 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-02 02:01:06 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-02 02:01:06 (10892) [INFO] compromise: * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-02 02:01:06 (10892) [INFO] * 2025-12-02 02:01:06 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-02 02:01:06 (10909) [INFO] * 2025-12-02 02:01:06 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-02 02:01:06 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-02 02:01:06 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-02 02:01:06 (10879) [INFO] * 2025-12-02 02:01:07 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-02 02:01:07 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-02 02:01:07 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-02 02:01:07 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-02 02:01:07 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-02 02:01:07 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-02 02:01:07 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-02 02:01:07 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-02 02:01:07 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-02 02:01:07 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-02 02:01:07 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-02 02:01:07 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-02 02:01:07 (10909) [INFO] * 2025-12-02 02:01:07 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-02 02:01:07 (10879) [INFO] * 2025-12-02 02:01:07 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-02 02:01:08 (10892) [INFO] Determining fastest mirrors * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-02 02:01:39 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-02 02:01:39 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-02 02:01:39 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-02 02:01:39 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-02 02:01:39 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-02 02:01:39 (10892) [INFO] yum --disablerepo= ... * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-02 02:01:39 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-02 02:01:39 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] yum-config-manager --disable * 2025-12-02 02:01:39 (10892) [INFO] or * 2025-12-02 02:01:39 (10892) [INFO] subscription-manager repos --disable= * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-02 02:01:39 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-02 02:01:39 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-02 02:01:39 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-02 02:01:39 (10892) [INFO] compromise: * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-02 02:01:39 (10892) [INFO] * 2025-12-02 02:01:39 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-02 02:01:39 (10909) [INFO] * 2025-12-02 02:01:39 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-02 02:01:39 (6726) [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 * 2025-12-02 02:01:40 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-02 02:01:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-02 02:01:40 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-02 02:01:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-02 02:01:40 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-02 02:01:46 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GhVILEWt44/ea_profile.json * 2025-12-02 02:05:46 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GhVILEWt44/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-02 02:05:46 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-03 01:38:33 (11960) [INFO] Self-update of script version 75 requested. * 2025-12-03 01:42:33 (11982) [INFO] Script is up to date. * 2025-12-03 01:46:36 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-03 01:46:36 (10879) [INFO] * 2025-12-03 01:47:54 (10909) [INFO] * 2025-12-03 01:47:54 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-03 01:47:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-03 01:47:54 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-03 01:47:54 (10879) [INFO] * 2025-12-03 01:54:55 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-03 01:54:55 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-03 01:54:55 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-03 01:54:55 (10879) [INFO] * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-03 01:55:30 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-03 01:55:30 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-03 01:55:30 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-03 01:55:30 (10879) [INFO] * 2025-12-03 01:55:31 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-03 01:55:31 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-03 01:56:01 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-03 01:56:01 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-03 01:56:01 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-03 01:56:01 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-03 01:56:01 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-03 01:56:01 (10892) [INFO] yum --disablerepo= ... * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-03 01:56:01 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-03 01:56:01 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] yum-config-manager --disable * 2025-12-03 01:56:01 (10892) [INFO] or * 2025-12-03 01:56:01 (10892) [INFO] subscription-manager repos --disable= * 2025-12-03 01:56:01 (10892) [INFO] * 2025-12-03 01:56:01 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-03 01:56:01 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-03 01:56:01 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-03 01:56:01 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-03 01:56:01 (10892) [INFO] compromise: * 2025-12-03 01:56:02 (10892) [INFO] * 2025-12-03 01:56:02 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-03 01:56:02 (10892) [INFO] * 2025-12-03 01:56:02 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-03 01:56:02 (10909) [INFO] * 2025-12-03 01:56:02 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-03 01:56:02 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-03 01:56:02 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-03 01:56:02 (10879) [INFO] * 2025-12-03 01:56:02 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-03 01:56:02 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-03 01:56:02 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-03 01:56:02 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-03 01:56:02 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-03 01:56:02 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-03 01:56:02 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-03 01:56:02 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-03 01:56:02 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-03 01:56:02 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-03 01:56:02 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-03 01:56:02 (10892) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-12-03 01:56:03 (10909) [INFO] * 2025-12-03 01:56:03 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-03 01:56:03 (10879) [INFO] * 2025-12-03 01:56:03 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-03 01:56:03 (10892) [INFO] Determining fastest mirrors * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-03 01:56:34 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-03 01:56:34 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-03 01:56:34 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-03 01:56:34 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-03 01:56:34 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-03 01:56:34 (10892) [INFO] yum --disablerepo= ... * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-03 01:56:34 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-03 01:56:34 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] yum-config-manager --disable * 2025-12-03 01:56:34 (10892) [INFO] or * 2025-12-03 01:56:34 (10892) [INFO] subscription-manager repos --disable= * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-03 01:56:34 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-03 01:56:34 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-03 01:56:34 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-03 01:56:34 (10892) [INFO] compromise: * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-03 01:56:34 (10892) [INFO] * 2025-12-03 01:56:34 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-03 01:56:34 (10909) [INFO] * 2025-12-03 01:56:34 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-03 01:56:34 (6726) [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 * 2025-12-03 01:56:36 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-03 01:56:36 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-03 01:56:36 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-03 01:56:36 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-03 01:56:36 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-03 01:56:41 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HwM9dTKlEe/ea_profile.json * 2025-12-03 01:59:08 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HwM9dTKlEe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-03 01:59:08 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-04 01:39:16 (11960) [INFO] Self-update of script version 75 requested. * 2025-12-04 01:43:16 (11982) [INFO] Script is up to date. * 2025-12-04 01:47:19 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-04 01:47:19 (10879) [INFO] * 2025-12-04 01:48:36 (10909) [INFO] * 2025-12-04 01:48:36 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-04 01:48:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-04 01:48:36 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-04 01:48:36 (10879) [INFO] * 2025-12-04 01:48:39 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-04 01:48:39 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-04 01:48:39 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-04 01:48:39 (10879) [INFO] * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-04 01:49:14 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-04 01:49:14 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-04 01:49:14 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-04 01:49:14 (10879) [INFO] * 2025-12-04 01:49:14 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-04 01:49:14 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-04 01:49:45 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-04 01:49:45 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-04 01:49:45 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-04 01:49:45 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-04 01:49:45 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-04 01:49:45 (10892) [INFO] yum --disablerepo= ... * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-04 01:49:45 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-04 01:49:45 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] yum-config-manager --disable * 2025-12-04 01:49:45 (10892) [INFO] or * 2025-12-04 01:49:45 (10892) [INFO] subscription-manager repos --disable= * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-04 01:49:45 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-04 01:49:45 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-04 01:49:45 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-04 01:49:45 (10892) [INFO] compromise: * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-04 01:49:45 (10892) [INFO] * 2025-12-04 01:49:45 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-04 01:49:45 (10909) [INFO] * 2025-12-04 01:49:45 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-04 01:49:45 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-04 01:49:45 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-04 01:49:45 (10879) [INFO] * 2025-12-04 01:49:46 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-04 01:49:46 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-04 01:49:46 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-04 01:49:46 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-04 01:49:46 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-04 01:49:46 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-04 01:49:46 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-04 01:49:46 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-04 01:49:46 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-04 01:49:46 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-04 01:49:46 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-04 01:49:46 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-04 01:49:46 (10909) [INFO] * 2025-12-04 01:49:46 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-04 01:49:46 (10879) [INFO] * 2025-12-04 01:49:47 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-04 01:49:47 (10892) [INFO] Determining fastest mirrors * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-04 01:50:18 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-04 01:50:18 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-04 01:50:18 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-04 01:50:18 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-04 01:50:18 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-04 01:50:18 (10892) [INFO] yum --disablerepo= ... * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-04 01:50:18 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-04 01:50:18 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] yum-config-manager --disable * 2025-12-04 01:50:18 (10892) [INFO] or * 2025-12-04 01:50:18 (10892) [INFO] subscription-manager repos --disable= * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-04 01:50:18 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-04 01:50:18 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-04 01:50:18 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-04 01:50:18 (10892) [INFO] compromise: * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-04 01:50:18 (10892) [INFO] * 2025-12-04 01:50:18 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-04 01:50:18 (10909) [INFO] * 2025-12-04 01:50:18 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-04 01:50:18 (6726) [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 * 2025-12-04 01:50:20 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-04 01:50:20 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-04 01:50:20 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-04 01:50:20 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-04 01:50:20 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-04 01:50:26 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6zAvDLiOZL/ea_profile.json * 2025-12-04 01:52:53 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6zAvDLiOZL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-04 01:52:53 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-05 01:40:39 (11960) [INFO] Self-update of script version 75 requested. * 2025-12-05 01:44:39 (11965) [INFO] Newer version of script found. Downloading. * 2025-12-05 01:48:41 (11974) [INFO] Script update to version 76 successful. * 2025-12-05 01:52:43 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-05 01:52:43 (10879) [INFO] * 2025-12-05 01:53:59 (10909) [INFO] * 2025-12-05 01:53:59 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-05 01:53:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-05 01:53:59 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-05 01:53:59 (10879) [INFO] * 2025-12-05 02:01:01 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-05 02:01:01 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-05 02:01:01 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-05 02:01:01 (10879) [INFO] * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-05 02:01:36 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-05 02:01:36 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-05 02:01:36 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-05 02:01:36 (10879) [INFO] * 2025-12-05 02:01:36 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-05 02:01:37 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-05 02:02:07 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-05 02:02:07 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-05 02:02:07 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-05 02:02:07 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-05 02:02:07 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-05 02:02:07 (10892) [INFO] yum --disablerepo= ... * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-05 02:02:07 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-05 02:02:07 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] yum-config-manager --disable * 2025-12-05 02:02:07 (10892) [INFO] or * 2025-12-05 02:02:07 (10892) [INFO] subscription-manager repos --disable= * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-05 02:02:07 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-05 02:02:07 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-05 02:02:07 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-05 02:02:07 (10892) [INFO] compromise: * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-05 02:02:07 (10892) [INFO] * 2025-12-05 02:02:07 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-05 02:02:07 (10909) [INFO] * 2025-12-05 02:02:07 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-05 02:02:07 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-05 02:02:07 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-05 02:02:07 (10879) [INFO] * 2025-12-05 02:02:08 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-05 02:02:08 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-05 02:02:08 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-05 02:02:08 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-05 02:02:08 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-05 02:02:08 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-05 02:02:08 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-05 02:02:08 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-05 02:02:08 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-05 02:02:08 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-05 02:02:08 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-05 02:02:08 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-05 02:02:08 (10909) [INFO] * 2025-12-05 02:02:08 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-05 02:02:08 (10879) [INFO] * 2025-12-05 02:02:09 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-05 02:02:09 (10892) [INFO] Determining fastest mirrors * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-05 02:02:39 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-05 02:02:39 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-05 02:02:39 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-05 02:02:39 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-05 02:02:39 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-05 02:02:39 (10892) [INFO] yum --disablerepo= ... * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-05 02:02:39 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-05 02:02:39 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] yum-config-manager --disable * 2025-12-05 02:02:39 (10892) [INFO] or * 2025-12-05 02:02:39 (10892) [INFO] subscription-manager repos --disable= * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-05 02:02:39 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-05 02:02:39 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-05 02:02:39 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-05 02:02:39 (10892) [INFO] compromise: * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-05 02:02:39 (10892) [INFO] * 2025-12-05 02:02:39 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-05 02:02:39 (10909) [INFO] * 2025-12-05 02:02:39 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-05 02:02:39 (6726) [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 * 2025-12-05 02:02:41 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-05 02:02:41 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-05 02:02:41 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-05 02:02:41 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-05 02:02:41 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-05 02:02:47 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QOWDEsH86G/ea_profile.json * 2025-12-05 02:05:15 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QOWDEsH86G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-05 02:05:15 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-06 01:39:49 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-06 01:43:49 (11982) [INFO] Script is up to date. * 2025-12-06 01:47:53 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-06 01:47:53 (10879) [INFO] * 2025-12-06 01:48:43 (10909) [INFO] * 2025-12-06 01:48:43 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-06 01:48:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-06 01:48:43 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-06 01:48:43 (10879) [INFO] * 2025-12-06 01:55:43 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-06 01:55:43 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-06 01:55:43 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-06 01:55:43 (10879) [INFO] * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-06 01:56:17 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-06 01:56:17 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-06 01:56:17 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-06 01:56:17 (10879) [INFO] * 2025-12-06 01:56:17 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-06 01:56:18 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-06 01:56:48 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-06 01:56:48 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-06 01:56:48 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-06 01:56:48 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-06 01:56:48 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-06 01:56:48 (10892) [INFO] yum --disablerepo= ... * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-06 01:56:48 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-06 01:56:48 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] yum-config-manager --disable * 2025-12-06 01:56:48 (10892) [INFO] or * 2025-12-06 01:56:48 (10892) [INFO] subscription-manager repos --disable= * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-06 01:56:48 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-06 01:56:48 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-06 01:56:48 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-06 01:56:48 (10892) [INFO] compromise: * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-06 01:56:48 (10892) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-06 01:56:48 (10909) [INFO] * 2025-12-06 01:56:48 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-06 01:56:48 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-06 01:56:48 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-06 01:56:48 (10879) [INFO] * 2025-12-06 01:56:48 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-06 01:56:49 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-06 01:56:49 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-06 01:56:49 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-06 01:56:49 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-06 01:56:49 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-06 01:56:49 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-06 01:56:49 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-06 01:56:49 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-06 01:56:49 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-06 01:56:49 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-06 01:56:49 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-06 01:56:49 (10909) [INFO] * 2025-12-06 01:56:49 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-06 01:56:49 (10879) [INFO] * 2025-12-06 01:56:49 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-06 01:56:49 (10892) [INFO] Determining fastest mirrors * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-06 01:57:20 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-06 01:57:20 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-06 01:57:20 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-06 01:57:20 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-06 01:57:20 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-06 01:57:20 (10892) [INFO] yum --disablerepo= ... * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-06 01:57:20 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-06 01:57:20 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] yum-config-manager --disable * 2025-12-06 01:57:20 (10892) [INFO] or * 2025-12-06 01:57:20 (10892) [INFO] subscription-manager repos --disable= * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-06 01:57:20 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-06 01:57:20 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-06 01:57:20 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-06 01:57:20 (10892) [INFO] compromise: * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-06 01:57:20 (10892) [INFO] * 2025-12-06 01:57:20 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-06 01:57:20 (10909) [INFO] * 2025-12-06 01:57:20 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-06 01:57:20 (6726) [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 * 2025-12-06 01:57:22 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-06 01:57:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-06 01:57:22 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-06 01:57:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-06 01:57:22 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-06 01:57:28 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LnF5_QnCrK/ea_profile.json * 2025-12-06 01:59:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LnF5_QnCrK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-06 01:59:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-07 01:39:49 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-07 01:43:50 (11982) [INFO] Script is up to date. * 2025-12-07 01:47:52 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-07 01:47:52 (10879) [INFO] * 2025-12-07 01:48:46 (10909) [INFO] * 2025-12-07 01:48:46 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-07 01:48:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-07 01:48:47 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-07 01:48:47 (10879) [INFO] * 2025-12-07 01:48:50 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-07 01:48:50 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-07 01:48:50 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-07 01:48:50 (10879) [INFO] * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-07 01:49:26 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-07 01:49:26 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-07 01:49:26 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-07 01:49:26 (10879) [INFO] * 2025-12-07 01:49:26 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-07 01:49:27 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-07 01:49:57 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-07 01:49:57 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-07 01:49:57 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-07 01:49:57 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-07 01:49:57 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-07 01:49:57 (10892) [INFO] yum --disablerepo= ... * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-07 01:49:57 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-07 01:49:57 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] yum-config-manager --disable * 2025-12-07 01:49:57 (10892) [INFO] or * 2025-12-07 01:49:57 (10892) [INFO] subscription-manager repos --disable= * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-07 01:49:57 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-07 01:49:57 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-07 01:49:57 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-07 01:49:57 (10892) [INFO] compromise: * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-07 01:49:57 (10892) [INFO] * 2025-12-07 01:49:57 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-07 01:49:58 (10909) [INFO] * 2025-12-07 01:49:58 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-07 01:49:58 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-07 01:49:58 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-07 01:49:58 (10879) [INFO] * 2025-12-07 01:49:58 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-07 01:49:58 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-07 01:49:58 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-07 01:49:58 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-07 01:49:58 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-07 01:49:58 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-07 01:49:58 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-07 01:49:58 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-07 01:49:58 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-07 01:49:58 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-07 01:49:58 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-07 01:49:58 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-07 01:49:58 (10909) [INFO] * 2025-12-07 01:49:58 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-07 01:49:58 (10879) [INFO] * 2025-12-07 01:49:59 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-07 01:49:59 (10892) [INFO] Determining fastest mirrors * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-07 01:50:31 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-07 01:50:31 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-07 01:50:31 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-07 01:50:31 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-07 01:50:31 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-07 01:50:31 (10892) [INFO] yum --disablerepo= ... * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-07 01:50:31 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-07 01:50:31 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] yum-config-manager --disable * 2025-12-07 01:50:31 (10892) [INFO] or * 2025-12-07 01:50:31 (10892) [INFO] subscription-manager repos --disable= * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-07 01:50:31 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-07 01:50:31 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-07 01:50:31 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-07 01:50:31 (10892) [INFO] compromise: * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-07 01:50:31 (10892) [INFO] * 2025-12-07 01:50:31 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-07 01:50:31 (10909) [INFO] * 2025-12-07 01:50:31 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-07 01:50:31 (6726) [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 * 2025-12-07 01:50:32 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-07 01:50:32 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-07 01:50:32 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-07 01:50:32 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-07 01:50:32 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-07 01:50:38 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eMWqbwcMOL/ea_profile.json * 2025-12-07 01:53:05 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eMWqbwcMOL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-07 01:53:05 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-08 01:39:14 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-08 01:43:15 (11982) [INFO] Script is up to date. * 2025-12-08 01:47:17 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-08 01:47:17 (10879) [INFO] * 2025-12-08 01:48:35 (10909) [INFO] * 2025-12-08 01:48:35 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-08 01:48:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-08 01:48:36 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-08 01:48:36 (10879) [INFO] * 2025-12-08 01:48:39 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-08 01:48:39 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-08 01:48:39 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-08 01:48:39 (10879) [INFO] * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-08 01:49:16 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-08 01:49:16 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-08 01:49:16 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-08 01:49:16 (10879) [INFO] * 2025-12-08 01:49:16 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-08 01:49:17 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-08 01:49:48 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-08 01:49:48 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-08 01:49:48 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-08 01:49:48 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-08 01:49:48 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-08 01:49:48 (10892) [INFO] yum --disablerepo= ... * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-08 01:49:48 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-08 01:49:48 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] yum-config-manager --disable * 2025-12-08 01:49:48 (10892) [INFO] or * 2025-12-08 01:49:48 (10892) [INFO] subscription-manager repos --disable= * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-08 01:49:48 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-08 01:49:48 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-08 01:49:48 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-08 01:49:48 (10892) [INFO] compromise: * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-08 01:49:48 (10892) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-08 01:49:48 (10909) [INFO] * 2025-12-08 01:49:48 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-08 01:49:48 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-08 01:49:48 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-08 01:49:48 (10879) [INFO] * 2025-12-08 01:49:48 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-08 01:49:49 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-08 01:49:49 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-08 01:49:49 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-08 01:49:49 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-08 01:49:49 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-08 01:49:49 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-08 01:49:49 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-08 01:49:49 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-08 01:49:49 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-08 01:49:49 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-08 01:49:49 (10892) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-12-08 01:49:49 (10909) [INFO] * 2025-12-08 01:49:49 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-08 01:49:49 (10879) [INFO] * 2025-12-08 01:49:49 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-08 01:49:50 (10892) [INFO] Determining fastest mirrors * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-08 01:50:20 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-08 01:50:20 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-08 01:50:20 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-08 01:50:20 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-08 01:50:20 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-08 01:50:20 (10892) [INFO] yum --disablerepo= ... * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-08 01:50:20 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-08 01:50:20 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] yum-config-manager --disable * 2025-12-08 01:50:20 (10892) [INFO] or * 2025-12-08 01:50:20 (10892) [INFO] subscription-manager repos --disable= * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-08 01:50:20 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-08 01:50:20 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-08 01:50:20 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-08 01:50:20 (10892) [INFO] compromise: * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-08 01:50:20 (10892) [INFO] * 2025-12-08 01:50:20 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-08 01:50:20 (10909) [INFO] * 2025-12-08 01:50:20 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-08 01:50:20 (6726) [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 * 2025-12-08 01:50:22 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-08 01:50:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-08 01:50:22 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-08 01:50:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-08 01:50:22 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-08 01:50:29 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mv1slFxf5U/ea_profile.json * 2025-12-08 01:53:27 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mv1slFxf5U/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-08 01:53:27 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-09 02:13:10 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-09 02:17:11 (11982) [INFO] Script is up to date. * 2025-12-09 02:21:14 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-09 02:21:14 (10879) [INFO] * 2025-12-09 02:22:36 (10909) [INFO] * 2025-12-09 02:22:36 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-09 02:22:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-09 02:22:36 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-09 02:22:36 (10879) [INFO] * 2025-12-09 02:22:40 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-09 02:22:40 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-09 02:22:40 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-09 02:22:40 (10879) [INFO] * 2025-12-09 02:22:51 (264) [ERROR] *** Elevation Blocker detected: *** There are packages installed that do not have associated repositories: online-backup xe-guest-utilities xe-guest-utilities-xenstore * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-09 02:22:53 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-09 02:22:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-09 02:22:53 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-09 02:22:53 (10879) [INFO] * 2025-12-09 02:22:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-09 02:22:53 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-09 02:23:24 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-09 02:23:24 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30773 milliseconds') * 2025-12-09 02:23:24 (10892) [INFO] * EA4: 208.74.123.62 * 2025-12-09 02:23:24 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-12-09 02:23:24 (10892) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-12-09 02:23:24 (10892) [INFO] * epel: dl.fedoraproject.org * 2025-12-09 02:24:34 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') * 2025-12-09 02:24:34 (10892) [INFO] Trying other mirror. * 2025-12-09 02:25:05 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') * 2025-12-09 02:25:05 (10892) [INFO] Trying other mirror. * 2025-12-09 02:28:15 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-12-09 02:28:15 (10892) [INFO] Trying other mirror. * 2025-12-09 02:28:40 (10892) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') * 2025-12-09 02:28:40 (10892) [INFO] Trying other mirror. * 2025-12-09 02:29:25 (10892) [INFO] https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-12-09 02:29:25 (10892) [INFO] Trying other mirror. * 2025-12-09 02:29:34 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') * 2025-12-09 02:29:34 (10892) [INFO] Trying other mirror. * 2025-12-09 02:29:41 (10892) [INFO] https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-12-09 02:29:41 (10892) [INFO] Trying other mirror. * 2025-12-09 02:30:04 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-12-09 02:30:04 (10892) [INFO] Trying other mirror. * 2025-12-09 02:30:48 (10892) [INFO] Metadata Cache Created * 2025-12-09 02:30:48 (10909) [INFO] * 2025-12-09 02:30:48 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30773 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30538 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30534 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/updates/x86_64/repodata/14ff80eeb5b7c2c703cb151b97a17a9cec41fbe5c820b6e73a015d522e02bfe7-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/extras/x86_64/repodata/ae8d9246e7015e7ecb91d202d4d042a7247813edf3da40f32d278a9c6ba754d2-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: (28, 'timed out before SSL handshake') Trying other mirror. * 2025-12-09 02:30:48 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-09 02:30:48 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-09 02:30:48 (10879) [INFO] * 2025-12-09 02:30:49 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-09 02:30:49 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-09 02:30:49 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-09 02:30:49 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-09 02:30:49 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-09 02:30:49 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-09 02:30:49 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-09 02:30:49 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-09 02:30:49 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-09 02:30:49 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-09 02:30:50 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-09 02:30:50 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-09 02:30:50 (10909) [INFO] * 2025-12-09 02:30:50 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-09 02:30:50 (10879) [INFO] * 2025-12-09 02:30:51 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-09 02:30:51 (10892) [INFO] Determining fastest mirrors * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-09 02:31:21 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-09 02:31:21 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-09 02:31:21 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-09 02:31:21 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-09 02:31:21 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-09 02:31:21 (10892) [INFO] yum --disablerepo= ... * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-09 02:31:21 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-09 02:31:21 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] yum-config-manager --disable * 2025-12-09 02:31:21 (10892) [INFO] or * 2025-12-09 02:31:21 (10892) [INFO] subscription-manager repos --disable= * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-09 02:31:21 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-09 02:31:21 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-09 02:31:21 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-09 02:31:21 (10892) [INFO] compromise: * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-09 02:31:21 (10892) [INFO] * 2025-12-09 02:31:21 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-09 02:31:21 (10909) [INFO] * 2025-12-09 02:31:21 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-09 02:31:21 (6726) [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 * 2025-12-09 02:31:23 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-09 02:31:23 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-09 02:31:23 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-09 02:31:23 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-09 02:31:23 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-09 02:31:30 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oUReGAW3Un/ea_profile.json * 2025-12-09 02:39:39 (10011) [INFO] Backed up EA4 profile to /tmp/oUReGAW3Un/ea_profile.json * 2025-12-09 02:39:39 (264) [ERROR] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-12-09 02:40:14 (703) [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. * 2025-12-09 02:40:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-10 01:53:28 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-10 01:57:29 (11982) [INFO] Script is up to date. * 2025-12-10 02:01:32 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-10 02:01:32 (10879) [INFO] * 2025-12-10 02:02:58 (10909) [INFO] * 2025-12-10 02:02:58 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-10 02:02:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-10 02:02:58 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-10 02:02:58 (10879) [INFO] * 2025-12-10 02:12:29 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-10 02:12:29 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-10 02:12:29 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-10 02:12:29 (10879) [INFO] * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-10 02:13:04 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-10 02:13:04 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-10 02:13:04 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-10 02:13:04 (10879) [INFO] * 2025-12-10 02:13:04 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-10 02:13:05 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-10 02:13:36 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-10 02:13:36 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-10 02:13:36 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-10 02:13:36 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-10 02:13:36 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-10 02:13:36 (10892) [INFO] yum --disablerepo= ... * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-10 02:13:36 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-10 02:13:36 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] yum-config-manager --disable * 2025-12-10 02:13:36 (10892) [INFO] or * 2025-12-10 02:13:36 (10892) [INFO] subscription-manager repos --disable= * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-10 02:13:36 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-10 02:13:36 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-10 02:13:36 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-10 02:13:36 (10892) [INFO] compromise: * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-10 02:13:36 (10892) [INFO] * 2025-12-10 02:13:36 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-10 02:13:36 (10909) [INFO] * 2025-12-10 02:13:36 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-10 02:13:36 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-10 02:13:36 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-10 02:13:36 (10879) [INFO] * 2025-12-10 02:13:37 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-10 02:13:37 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-10 02:13:37 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-10 02:13:37 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-10 02:13:37 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-10 02:13:37 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-10 02:13:37 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-10 02:13:37 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-10 02:13:37 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-10 02:13:37 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-10 02:13:37 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-10 02:13:37 (10892) [INFO] Other repos take up 980 k of disk space (use --verbose for details) * 2025-12-10 02:13:37 (10909) [INFO] * 2025-12-10 02:13:37 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-10 02:13:37 (10879) [INFO] * 2025-12-10 02:13:38 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-10 02:13:38 (10892) [INFO] Determining fastest mirrors * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-10 02:14:09 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-10 02:14:09 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-10 02:14:09 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-10 02:14:09 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-10 02:14:09 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-10 02:14:09 (10892) [INFO] yum --disablerepo= ... * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-10 02:14:09 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-10 02:14:09 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] yum-config-manager --disable * 2025-12-10 02:14:09 (10892) [INFO] or * 2025-12-10 02:14:09 (10892) [INFO] subscription-manager repos --disable= * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-10 02:14:09 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-10 02:14:09 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-10 02:14:09 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-10 02:14:09 (10892) [INFO] compromise: * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-10 02:14:09 (10892) [INFO] * 2025-12-10 02:14:09 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-10 02:14:09 (10909) [INFO] * 2025-12-10 02:14:09 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-10 02:14:09 (6726) [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 * 2025-12-10 02:14:11 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-10 02:14:11 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-10 02:14:11 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-10 02:14:11 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-10 02:14:11 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-10 02:14:19 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KtWcOXnJC_/ea_profile.json * 2025-12-10 02:14:37 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/KtWcOXnJC_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-10 02:14:37 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-11 01:42:02 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-11 01:46:03 (11982) [INFO] Script is up to date. * 2025-12-11 01:50:05 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-11 01:50:05 (10879) [INFO] * 2025-12-11 01:51:27 (10909) [INFO] * 2025-12-11 01:51:27 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-11 01:51:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-11 01:51:27 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-11 01:51:27 (10879) [INFO] * 2025-12-11 01:51:30 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-11 01:51:30 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-11 01:51:30 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-11 01:51:30 (10879) [INFO] * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-11 01:52:06 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-11 01:52:06 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-11 01:52:06 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-11 01:52:06 (10879) [INFO] * 2025-12-11 01:52:06 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-11 01:52:06 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-11 01:52:37 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-11 01:52:37 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-11 01:52:37 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-11 01:52:37 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-11 01:52:37 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-11 01:52:37 (10892) [INFO] yum --disablerepo= ... * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-11 01:52:37 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-11 01:52:37 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] yum-config-manager --disable * 2025-12-11 01:52:37 (10892) [INFO] or * 2025-12-11 01:52:37 (10892) [INFO] subscription-manager repos --disable= * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-11 01:52:37 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-11 01:52:37 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-11 01:52:37 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-11 01:52:37 (10892) [INFO] compromise: * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-11 01:52:37 (10892) [INFO] * 2025-12-11 01:52:37 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-11 01:52:37 (10909) [INFO] * 2025-12-11 01:52:37 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-11 01:52:37 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-11 01:52:37 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-11 01:52:37 (10879) [INFO] * 2025-12-11 01:52:38 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-11 01:52:38 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-11 01:52:38 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-11 01:52:38 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-11 01:52:38 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-11 01:52:38 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-11 01:52:38 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-11 01:52:38 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-11 01:52:38 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-11 01:52:38 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-11 01:52:38 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-11 01:52:38 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-11 01:52:38 (10909) [INFO] * 2025-12-11 01:52:38 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-11 01:52:38 (10879) [INFO] * 2025-12-11 01:52:38 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-11 01:52:39 (10892) [INFO] Determining fastest mirrors * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-11 01:53:10 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-11 01:53:10 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-11 01:53:10 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-11 01:53:10 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-11 01:53:10 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-11 01:53:10 (10892) [INFO] yum --disablerepo= ... * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-11 01:53:10 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-11 01:53:10 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] yum-config-manager --disable * 2025-12-11 01:53:10 (10892) [INFO] or * 2025-12-11 01:53:10 (10892) [INFO] subscription-manager repos --disable= * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-11 01:53:10 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-11 01:53:10 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-11 01:53:10 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-11 01:53:10 (10892) [INFO] compromise: * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-11 01:53:10 (10892) [INFO] * 2025-12-11 01:53:10 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-11 01:53:10 (10909) [INFO] * 2025-12-11 01:53:10 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-11 01:53:10 (6726) [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 * 2025-12-11 01:53:12 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-11 01:53:12 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-11 01:53:12 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-11 01:53:12 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-11 01:53:12 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-11 01:53:17 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/W98Nlxmch_/ea_profile.json * 2025-12-11 01:55:45 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/W98Nlxmch_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-11 01:55:45 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-12 01:43:37 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-12 01:47:38 (11982) [INFO] Script is up to date. * 2025-12-12 01:51:41 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-12 01:51:41 (10879) [INFO] * 2025-12-12 01:53:01 (10909) [INFO] * 2025-12-12 01:53:01 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-12 01:53:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-12 01:53:01 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-12 01:53:01 (10879) [INFO] * 2025-12-12 01:53:06 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-12 01:53:06 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-12 01:53:06 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-12 01:53:06 (10879) [INFO] * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-12 01:53:41 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-12 01:53:41 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-12 01:53:41 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-12 01:53:41 (10879) [INFO] * 2025-12-12 01:53:41 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-12 01:53:42 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-12 01:54:13 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-12 01:54:13 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-12 01:54:13 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-12 01:54:13 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-12 01:54:13 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-12 01:54:13 (10892) [INFO] yum --disablerepo= ... * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-12 01:54:13 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-12 01:54:13 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] yum-config-manager --disable * 2025-12-12 01:54:13 (10892) [INFO] or * 2025-12-12 01:54:13 (10892) [INFO] subscription-manager repos --disable= * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-12 01:54:13 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-12 01:54:13 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-12 01:54:13 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-12 01:54:13 (10892) [INFO] compromise: * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-12 01:54:13 (10892) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-12 01:54:13 (10909) [INFO] * 2025-12-12 01:54:13 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-12 01:54:13 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-12 01:54:13 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-12 01:54:13 (10879) [INFO] * 2025-12-12 01:54:13 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-12 01:54:14 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-12 01:54:14 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-12 01:54:14 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-12 01:54:14 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-12 01:54:14 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-12 01:54:14 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-12 01:54:14 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-12 01:54:14 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-12 01:54:14 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-12 01:54:14 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-12 01:54:14 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-12 01:54:14 (10909) [INFO] * 2025-12-12 01:54:14 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-12 01:54:14 (10879) [INFO] * 2025-12-12 01:54:14 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-12 01:54:14 (10892) [INFO] Determining fastest mirrors * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-12 01:54:45 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-12 01:54:45 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-12 01:54:45 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-12 01:54:45 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-12 01:54:45 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-12 01:54:45 (10892) [INFO] yum --disablerepo= ... * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-12 01:54:45 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-12 01:54:45 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] yum-config-manager --disable * 2025-12-12 01:54:45 (10892) [INFO] or * 2025-12-12 01:54:45 (10892) [INFO] subscription-manager repos --disable= * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-12 01:54:45 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-12 01:54:45 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-12 01:54:45 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-12 01:54:45 (10892) [INFO] compromise: * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-12 01:54:45 (10892) [INFO] * 2025-12-12 01:54:45 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-12 01:54:45 (10909) [INFO] * 2025-12-12 01:54:45 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-12 01:54:45 (6726) [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 * 2025-12-12 01:54:47 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-12 01:54:47 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-12 01:54:47 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-12 01:54:47 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-12 01:54:47 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-12 01:54:54 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_kIsOj6D1y/ea_profile.json * 2025-12-12 01:57:51 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/_kIsOj6D1y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-12 01:57:51 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-13 01:44:54 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-13 01:48:55 (11982) [INFO] Script is up to date. * 2025-12-13 01:52:58 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-13 01:52:58 (10879) [INFO] * 2025-12-13 01:53:52 (10909) [INFO] * 2025-12-13 01:53:52 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-13 01:53:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-13 01:53:52 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-13 01:53:52 (10879) [INFO] * 2025-12-13 01:53:56 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-13 01:53:56 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-13 01:53:56 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-13 01:53:56 (10879) [INFO] * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-13 01:54:32 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-13 01:54:32 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-13 01:54:32 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-13 01:54:32 (10879) [INFO] * 2025-12-13 01:54:33 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-13 01:54:33 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-13 01:55:03 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-13 01:55:03 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-13 01:55:03 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-13 01:55:03 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-13 01:55:03 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-13 01:55:03 (10892) [INFO] yum --disablerepo= ... * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-13 01:55:03 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-13 01:55:03 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] yum-config-manager --disable * 2025-12-13 01:55:03 (10892) [INFO] or * 2025-12-13 01:55:03 (10892) [INFO] subscription-manager repos --disable= * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-13 01:55:03 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-13 01:55:03 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-13 01:55:03 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-13 01:55:03 (10892) [INFO] compromise: * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-13 01:55:03 (10892) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-13 01:55:03 (10909) [INFO] * 2025-12-13 01:55:03 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-13 01:55:03 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-13 01:55:03 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-13 01:55:03 (10879) [INFO] * 2025-12-13 01:55:03 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-13 01:55:04 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-13 01:55:04 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-13 01:55:04 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-13 01:55:04 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-13 01:55:04 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-13 01:55:04 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-13 01:55:04 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-13 01:55:04 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-13 01:55:04 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-13 01:55:04 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-13 01:55:04 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-13 01:55:04 (10909) [INFO] * 2025-12-13 01:55:04 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-13 01:55:04 (10879) [INFO] * 2025-12-13 01:55:04 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-13 01:55:04 (10892) [INFO] Determining fastest mirrors * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-13 01:55:35 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-13 01:55:35 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-13 01:55:35 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-13 01:55:35 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-13 01:55:35 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-13 01:55:35 (10892) [INFO] yum --disablerepo= ... * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-13 01:55:35 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-13 01:55:35 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] yum-config-manager --disable * 2025-12-13 01:55:35 (10892) [INFO] or * 2025-12-13 01:55:35 (10892) [INFO] subscription-manager repos --disable= * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-13 01:55:35 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-13 01:55:35 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-13 01:55:35 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-13 01:55:35 (10892) [INFO] compromise: * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-13 01:55:35 (10892) [INFO] * 2025-12-13 01:55:35 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-13 01:55:35 (10909) [INFO] * 2025-12-13 01:55:35 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-13 01:55:35 (6726) [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 * 2025-12-13 01:55:36 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-13 01:55:36 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-13 01:55:36 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-13 01:55:36 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-13 01:55:36 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-13 01:55:44 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kjk6djXmNb/ea_profile.json * 2025-12-13 01:58:42 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kjk6djXmNb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-13 01:58:42 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-14 01:42:42 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-14 01:46:42 (11982) [INFO] Script is up to date. * 2025-12-14 01:50:45 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-14 01:50:45 (10879) [INFO] * 2025-12-14 01:51:41 (10909) [INFO] * 2025-12-14 01:51:41 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-14 01:51:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-14 01:51:41 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-14 01:51:41 (10879) [INFO] * 2025-12-14 01:58:44 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-14 01:58:44 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-14 01:58:44 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-14 01:58:44 (10879) [INFO] * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-14 01:59:20 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-14 01:59:20 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-14 01:59:20 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-14 01:59:20 (10879) [INFO] * 2025-12-14 01:59:20 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-14 01:59:21 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-14 01:59:52 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-14 01:59:52 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-14 01:59:52 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-14 01:59:52 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-14 01:59:52 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-14 01:59:52 (10892) [INFO] yum --disablerepo= ... * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-14 01:59:52 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-14 01:59:52 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] yum-config-manager --disable * 2025-12-14 01:59:52 (10892) [INFO] or * 2025-12-14 01:59:52 (10892) [INFO] subscription-manager repos --disable= * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-14 01:59:52 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-14 01:59:52 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-14 01:59:52 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-14 01:59:52 (10892) [INFO] compromise: * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-14 01:59:52 (10892) [INFO] * 2025-12-14 01:59:52 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-14 01:59:52 (10909) [INFO] * 2025-12-14 01:59:52 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-14 01:59:52 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-14 01:59:52 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-14 01:59:52 (10879) [INFO] * 2025-12-14 01:59:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-14 01:59:53 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-14 01:59:53 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-14 01:59:53 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-14 01:59:53 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-14 01:59:53 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-14 01:59:53 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-14 01:59:53 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-14 01:59:53 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-14 01:59:53 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-14 01:59:53 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-14 01:59:53 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-14 01:59:53 (10909) [INFO] * 2025-12-14 01:59:53 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-14 01:59:53 (10879) [INFO] * 2025-12-14 01:59:54 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-14 01:59:54 (10892) [INFO] Determining fastest mirrors * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-14 02:00:25 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-14 02:00:25 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-14 02:00:25 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-14 02:00:25 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-14 02:00:25 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-14 02:00:25 (10892) [INFO] yum --disablerepo= ... * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-14 02:00:25 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-14 02:00:25 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] yum-config-manager --disable * 2025-12-14 02:00:25 (10892) [INFO] or * 2025-12-14 02:00:25 (10892) [INFO] subscription-manager repos --disable= * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-14 02:00:25 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-14 02:00:25 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-14 02:00:25 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-14 02:00:25 (10892) [INFO] compromise: * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-14 02:00:25 (10892) [INFO] * 2025-12-14 02:00:25 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-14 02:00:25 (10909) [INFO] * 2025-12-14 02:00:25 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-14 02:00:25 (6726) [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 * 2025-12-14 02:00:27 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-14 02:00:27 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-14 02:00:27 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-14 02:00:27 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-14 02:00:27 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-14 02:00:34 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Ebtlg1kbjm/ea_profile.json * 2025-12-14 02:03:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Ebtlg1kbjm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-14 02:03:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-15 01:42:10 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-15 01:46:11 (11982) [INFO] Script is up to date. * 2025-12-15 01:50:14 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-15 01:50:14 (10879) [INFO] * 2025-12-15 01:51:40 (10909) [INFO] * 2025-12-15 01:51:40 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-15 01:51:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-15 01:51:40 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-15 01:51:40 (10879) [INFO] * 2025-12-15 01:58:44 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-15 01:58:44 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-15 01:58:44 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-15 01:58:44 (10879) [INFO] * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-15 02:01:58 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-15 02:01:58 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-15 02:01:58 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-15 02:01:58 (10879) [INFO] * 2025-12-15 02:01:58 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-15 02:01:58 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-15 02:02:29 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-15 02:02:29 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30038 milliseconds with 0 out of 0 bytes received') * 2025-12-15 02:02:29 (10892) [INFO] * EA4: 208.74.123.58 * 2025-12-15 02:02:29 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.58 * 2025-12-15 02:02:29 (10892) [INFO] * cpanel-plugins: 208.74.123.58 * 2025-12-15 02:02:29 (10892) [INFO] * epel: pubmirror1.math.uh.edu * 2025-12-15 02:03:38 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-12-15 02:03:38 (10892) [INFO] Trying other mirror. * 2025-12-15 02:05:39 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-15 02:05:39 (10892) [INFO] Trying other mirror. * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-12-15 02:05:39 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-15 02:05:39 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-15 02:05:39 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-15 02:05:39 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-15 02:05:39 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-15 02:05:39 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-15 02:05:39 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-15 02:05:39 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-12-15 02:05:39 (10892) [INFO] or * 2025-12-15 02:05:39 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-15 02:05:39 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-15 02:05:39 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-15 02:05:39 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-15 02:05:39 (10892) [INFO] compromise: * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-12-15 02:05:39 (10892) [INFO] * 2025-12-15 02:05:39 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-12-15 02:05:39 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-15 02:05:39 (10909) [INFO] * 2025-12-15 02:05:39 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30038 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-15 02:05:39 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-15 02:05:39 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-15 02:05:39 (10879) [INFO] * 2025-12-15 02:05:40 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-15 02:05:40 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-15 02:05:40 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-15 02:05:40 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-15 02:05:40 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-15 02:05:40 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-15 02:05:40 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-15 02:05:40 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-15 02:05:40 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-15 02:05:40 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-15 02:05:40 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-15 02:05:40 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-15 02:05:40 (10909) [INFO] * 2025-12-15 02:05:40 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-15 02:05:40 (10879) [INFO] * 2025-12-15 02:05:40 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-15 02:05:41 (10892) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 24322. * 2025-12-15 02:05:41 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:41 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:41 (10892) [INFO] Memory : 30 M RSS (430 MB VSZ) * 2025-12-15 02:05:41 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:34 ago * 2025-12-15 02:05:41 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:43 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:43 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:43 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:43 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:36 ago * 2025-12-15 02:05:43 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:45 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:45 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:45 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:45 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:38 ago * 2025-12-15 02:05:45 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:47 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:47 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:47 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:47 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:40 ago * 2025-12-15 02:05:47 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:49 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:49 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:49 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:49 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:42 ago * 2025-12-15 02:05:49 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:51 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:51 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:51 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:51 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:44 ago * 2025-12-15 02:05:51 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:53 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:53 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:53 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:53 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:46 ago * 2025-12-15 02:05:53 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:55 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:55 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:55 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:55 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:48 ago * 2025-12-15 02:05:55 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:57 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:57 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:57 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:57 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:50 ago * 2025-12-15 02:05:57 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:05:59 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:05:59 (10892) [INFO] The other application is: yum * 2025-12-15 02:05:59 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:05:59 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:52 ago * 2025-12-15 02:05:59 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:01 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:01 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:01 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:01 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:54 ago * 2025-12-15 02:06:01 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:03 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:03 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:03 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:03 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:56 ago * 2025-12-15 02:06:03 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:05 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:05 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:05 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:05 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 01:58 ago * 2025-12-15 02:06:05 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:07 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:07 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:07 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:07 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 02:00 ago * 2025-12-15 02:06:07 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:09 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:09 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:09 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:09 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 02:02 ago * 2025-12-15 02:06:09 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:11 (10892) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2025-12-15 02:06:11 (10892) [INFO] The other application is: yum * 2025-12-15 02:06:11 (10892) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2025-12-15 02:06:11 (10892) [INFO] Started: Mon Dec 15 02:04:07 2025 - 02:04 ago * 2025-12-15 02:06:11 (10892) [INFO] State : Sleeping, pid: 24322 * 2025-12-15 02:06:13 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-15 02:06:44 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-15 02:06:44 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-15 02:06:44 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-15 02:06:44 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-15 02:06:44 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-15 02:06:44 (10892) [INFO] yum --disablerepo= ... * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-15 02:06:44 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-15 02:06:44 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] yum-config-manager --disable * 2025-12-15 02:06:44 (10892) [INFO] or * 2025-12-15 02:06:44 (10892) [INFO] subscription-manager repos --disable= * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-15 02:06:44 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-15 02:06:44 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-15 02:06:44 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-15 02:06:44 (10892) [INFO] compromise: * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-15 02:06:44 (10892) [INFO] * 2025-12-15 02:06:44 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-15 02:06:44 (10909) [INFO] * 2025-12-15 02:06:44 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-15 02:06:44 (6726) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 24322. Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 30 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:34 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:36 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:38 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:40 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:42 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:44 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:46 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:48 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:50 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:52 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:54 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:56 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 01:58 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 02:00 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 02:02 ago State : Sleeping, pid: 24322 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Mon Dec 15 02:04:07 2025 - 02:04 ago State : Sleeping, pid: 24322 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 * 2025-12-15 02:06:45 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-15 02:06:45 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-15 02:06:45 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-15 02:06:45 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-15 02:06:45 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-16 01:39:10 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-16 01:43:10 (11982) [INFO] Script is up to date. * 2025-12-16 01:47:13 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-16 01:47:13 (10879) [INFO] * 2025-12-16 01:48:37 (10909) [INFO] * 2025-12-16 01:48:37 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-16 01:48:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-16 01:48:37 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-16 01:48:37 (10879) [INFO] * 2025-12-16 01:48:41 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-16 01:48:41 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-16 01:48:41 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-16 01:48:41 (10879) [INFO] * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-16 01:49:11 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-16 01:49:11 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-16 01:49:11 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-16 01:49:11 (10879) [INFO] * 2025-12-16 01:49:12 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-16 01:49:12 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-16 01:49:42 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-16 01:49:42 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30014 milliseconds with 0 out of 0 bytes received') * 2025-12-16 01:49:43 (10892) [INFO] * EA4: 208.74.123.57 * 2025-12-16 01:49:43 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.57 * 2025-12-16 01:49:43 (10892) [INFO] * cpanel-plugins: 208.74.123.57 * 2025-12-16 01:49:43 (10892) [INFO] * epel: pubmirror1.math.uh.edu * 2025-12-16 01:50:55 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30607 milliseconds') * 2025-12-16 01:50:55 (10892) [INFO] Trying other mirror. * 2025-12-16 01:52:56 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-16 01:52:56 (10892) [INFO] Trying other mirror. * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-12-16 01:52:56 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-16 01:52:56 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-16 01:52:56 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-16 01:52:56 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-16 01:52:56 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-16 01:52:56 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-16 01:52:56 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-16 01:52:56 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-12-16 01:52:56 (10892) [INFO] or * 2025-12-16 01:52:56 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-16 01:52:56 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-16 01:52:56 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-16 01:52:56 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-16 01:52:56 (10892) [INFO] compromise: * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-12-16 01:52:56 (10892) [INFO] * 2025-12-16 01:52:56 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-12-16 01:52:56 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-16 01:52:56 (10909) [INFO] * 2025-12-16 01:52:56 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30014 milliseconds with 0 out of 0 bytes received') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30607 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-16 01:52:56 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-16 01:52:56 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-16 01:52:56 (10879) [INFO] * 2025-12-16 01:52:57 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-16 01:52:57 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-16 01:52:57 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-16 01:52:57 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-16 01:52:57 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-16 01:52:57 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-16 01:52:57 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-16 01:52:57 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-16 01:52:57 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-16 01:52:57 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-16 01:52:57 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-16 01:52:57 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-16 01:52:57 (10909) [INFO] * 2025-12-16 01:52:57 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-16 01:52:57 (10879) [INFO] * 2025-12-16 01:52:58 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-16 01:52:58 (10892) [INFO] Determining fastest mirrors * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-16 01:53:30 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-16 01:53:30 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-16 01:53:30 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-16 01:53:30 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-16 01:53:30 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-16 01:53:30 (10892) [INFO] yum --disablerepo= ... * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-16 01:53:30 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-16 01:53:30 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] yum-config-manager --disable * 2025-12-16 01:53:30 (10892) [INFO] or * 2025-12-16 01:53:30 (10892) [INFO] subscription-manager repos --disable= * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-16 01:53:30 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-16 01:53:30 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-16 01:53:30 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-16 01:53:30 (10892) [INFO] compromise: * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-16 01:53:30 (10892) [INFO] * 2025-12-16 01:53:30 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-16 01:53:30 (10909) [INFO] * 2025-12-16 01:53:30 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-16 01:53:30 (6726) [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 * 2025-12-16 01:53:31 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-16 01:53:31 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-16 01:53:31 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-16 01:53:31 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-16 01:53:31 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-16 01:53:38 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YUd9TL1KRw/ea_profile.json * 2025-12-16 01:56:07 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YUd9TL1KRw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-16 01:56:07 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-17 01:41:22 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-17 01:45:22 (11982) [INFO] Script is up to date. * 2025-12-17 01:49:25 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-17 01:49:25 (10879) [INFO] * 2025-12-17 01:50:49 (10909) [INFO] * 2025-12-17 01:50:49 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-17 01:50:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-17 01:50:49 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-17 01:50:49 (10879) [INFO] * 2025-12-17 01:50:53 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-17 01:50:53 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-17 01:50:53 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-17 01:50:53 (10879) [INFO] * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-17 01:51:28 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-17 01:51:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-17 01:51:28 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-17 01:51:28 (10879) [INFO] * 2025-12-17 01:51:28 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-17 01:51:28 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-17 01:51:59 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-17 01:51:59 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-17 01:51:59 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-17 01:51:59 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-17 01:51:59 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-17 01:51:59 (10892) [INFO] yum --disablerepo= ... * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-17 01:51:59 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-17 01:51:59 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] yum-config-manager --disable * 2025-12-17 01:51:59 (10892) [INFO] or * 2025-12-17 01:51:59 (10892) [INFO] subscription-manager repos --disable= * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-17 01:51:59 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-17 01:51:59 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-17 01:51:59 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-17 01:51:59 (10892) [INFO] compromise: * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-17 01:51:59 (10892) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-17 01:51:59 (10909) [INFO] * 2025-12-17 01:51:59 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-17 01:51:59 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-17 01:51:59 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-17 01:51:59 (10879) [INFO] * 2025-12-17 01:51:59 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-17 01:52:00 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-17 01:52:00 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-17 01:52:00 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-17 01:52:00 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-17 01:52:00 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-17 01:52:00 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-17 01:52:00 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-17 01:52:00 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-17 01:52:00 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-17 01:52:00 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-17 01:52:00 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-17 01:52:00 (10909) [INFO] * 2025-12-17 01:52:00 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-17 01:52:00 (10879) [INFO] * 2025-12-17 01:52:00 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-17 01:52:01 (10892) [INFO] Determining fastest mirrors * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-17 01:52:32 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-17 01:52:32 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-17 01:52:32 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-17 01:52:32 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-17 01:52:32 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-17 01:52:32 (10892) [INFO] yum --disablerepo= ... * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-17 01:52:32 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-17 01:52:32 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] yum-config-manager --disable * 2025-12-17 01:52:32 (10892) [INFO] or * 2025-12-17 01:52:32 (10892) [INFO] subscription-manager repos --disable= * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-17 01:52:32 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-17 01:52:32 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-17 01:52:32 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-17 01:52:32 (10892) [INFO] compromise: * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-17 01:52:32 (10892) [INFO] * 2025-12-17 01:52:32 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-17 01:52:32 (10909) [INFO] * 2025-12-17 01:52:32 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-17 01:52:32 (6726) [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 * 2025-12-17 01:52:34 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-17 01:52:34 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-17 01:52:34 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-17 01:52:34 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-17 01:52:34 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-17 01:52:41 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VRaaHB6Mxz/ea_profile.json * 2025-12-17 01:58:12 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VRaaHB6Mxz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-17 01:58:12 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-18 01:40:25 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-18 01:44:26 (11982) [INFO] Script is up to date. * 2025-12-18 01:48:30 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-18 01:48:30 (10879) [INFO] * 2025-12-18 01:49:58 (10909) [INFO] * 2025-12-18 01:49:58 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-18 01:49:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-18 01:49:58 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-18 01:49:58 (10879) [INFO] * 2025-12-18 01:50:04 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-18 01:50:04 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-18 01:50:04 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-18 01:50:04 (10879) [INFO] * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-18 01:53:20 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-18 01:53:20 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-18 01:53:20 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-18 01:53:20 (10879) [INFO] * 2025-12-18 01:53:20 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-18 01:53:20 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-18 01:53:52 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-18 01:53:52 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30784 milliseconds') * 2025-12-18 01:53:52 (10892) [INFO] * EA4: 208.74.123.57 * 2025-12-18 01:53:52 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.57 * 2025-12-18 01:53:52 (10892) [INFO] * cpanel-plugins: 208.74.123.57 * 2025-12-18 01:53:52 (10892) [INFO] * epel: dl.fedoraproject.org * 2025-12-18 01:55:01 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') * 2025-12-18 01:55:01 (10892) [INFO] Trying other mirror. * 2025-12-18 01:57:02 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-18 01:57:02 (10892) [INFO] Trying other mirror. * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-12-18 01:57:02 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-18 01:57:02 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-18 01:57:02 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-18 01:57:02 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-18 01:57:02 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-18 01:57:02 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-18 01:57:02 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-18 01:57:02 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-12-18 01:57:02 (10892) [INFO] or * 2025-12-18 01:57:02 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-18 01:57:02 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-18 01:57:02 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-18 01:57:02 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-18 01:57:02 (10892) [INFO] compromise: * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-12-18 01:57:02 (10892) [INFO] * 2025-12-18 01:57:02 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-12-18 01:57:02 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-18 01:57:03 (10909) [INFO] * 2025-12-18 01:57:03 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30784 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30884 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-18 01:57:03 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-18 01:57:03 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-18 01:57:03 (10879) [INFO] * 2025-12-18 01:57:03 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-18 01:57:03 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-18 01:57:03 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-18 01:57:03 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-18 01:57:03 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-18 01:57:03 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-18 01:57:03 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-18 01:57:03 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-18 01:57:03 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-18 01:57:03 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-18 01:57:04 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-18 01:57:04 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-18 01:57:04 (10909) [INFO] * 2025-12-18 01:57:04 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-18 01:57:04 (10879) [INFO] * 2025-12-18 01:57:04 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-18 01:57:04 (10892) [INFO] Determining fastest mirrors * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-18 01:57:35 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-18 01:57:35 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-18 01:57:35 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-18 01:57:35 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-18 01:57:35 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-18 01:57:35 (10892) [INFO] yum --disablerepo= ... * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-18 01:57:35 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-18 01:57:35 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] yum-config-manager --disable * 2025-12-18 01:57:35 (10892) [INFO] or * 2025-12-18 01:57:35 (10892) [INFO] subscription-manager repos --disable= * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-18 01:57:35 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-18 01:57:35 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-18 01:57:35 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-18 01:57:35 (10892) [INFO] compromise: * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-18 01:57:35 (10892) [INFO] * 2025-12-18 01:57:35 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-18 01:57:35 (10909) [INFO] * 2025-12-18 01:57:35 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-18 01:57:35 (6726) [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 * 2025-12-18 01:57:36 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-18 01:57:36 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-18 01:57:36 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-18 01:57:36 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-18 01:57:36 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-19 01:41:55 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-19 01:45:55 (11982) [INFO] Script is up to date. * 2025-12-19 01:49:58 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-19 01:49:58 (10879) [INFO] * 2025-12-19 01:51:22 (10909) [INFO] * 2025-12-19 01:51:22 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-19 01:51:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-19 01:51:22 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-19 01:51:22 (10879) [INFO] * 2025-12-19 01:58:22 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-19 01:58:22 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-19 01:58:22 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-19 01:58:22 (10879) [INFO] * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-19 01:58:58 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-19 01:58:58 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-19 01:58:58 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-19 01:58:58 (10879) [INFO] * 2025-12-19 01:58:58 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-19 01:58:59 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-19 01:59:30 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-19 01:59:30 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-19 01:59:30 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-19 01:59:30 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-19 01:59:30 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-19 01:59:30 (10892) [INFO] yum --disablerepo= ... * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-19 01:59:30 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-19 01:59:30 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] yum-config-manager --disable * 2025-12-19 01:59:30 (10892) [INFO] or * 2025-12-19 01:59:30 (10892) [INFO] subscription-manager repos --disable= * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-19 01:59:30 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-19 01:59:30 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-19 01:59:30 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-19 01:59:30 (10892) [INFO] compromise: * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-19 01:59:30 (10892) [INFO] * 2025-12-19 01:59:30 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-19 01:59:30 (10909) [INFO] * 2025-12-19 01:59:30 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-19 01:59:30 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-19 01:59:30 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-19 01:59:30 (10879) [INFO] * 2025-12-19 01:59:31 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-19 01:59:31 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-19 01:59:31 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-19 01:59:31 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-19 01:59:31 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-19 01:59:31 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-19 01:59:31 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-19 01:59:31 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-19 01:59:31 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-19 01:59:31 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-19 01:59:31 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-19 01:59:31 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-19 01:59:31 (10909) [INFO] * 2025-12-19 01:59:31 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-19 01:59:31 (10879) [INFO] * 2025-12-19 01:59:31 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-19 01:59:32 (10892) [INFO] Determining fastest mirrors * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-19 02:00:03 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-19 02:00:03 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-19 02:00:03 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-19 02:00:03 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-19 02:00:03 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-19 02:00:03 (10892) [INFO] yum --disablerepo= ... * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-19 02:00:03 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-19 02:00:03 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] yum-config-manager --disable * 2025-12-19 02:00:03 (10892) [INFO] or * 2025-12-19 02:00:03 (10892) [INFO] subscription-manager repos --disable= * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-19 02:00:03 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-19 02:00:03 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-19 02:00:03 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-19 02:00:03 (10892) [INFO] compromise: * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-19 02:00:03 (10892) [INFO] * 2025-12-19 02:00:03 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-19 02:00:03 (10909) [INFO] * 2025-12-19 02:00:03 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-19 02:00:03 (6726) [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 * 2025-12-19 02:00:05 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-19 02:00:05 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-19 02:00:05 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-19 02:00:05 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-19 02:00:05 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-19 02:00:12 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/TE1RXAVZfp/ea_profile.json * 2025-12-19 02:02:39 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/TE1RXAVZfp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-19 02:02:39 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-20 01:51:57 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-20 01:55:58 (11982) [INFO] Script is up to date. * 2025-12-20 02:00:01 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-20 02:00:01 (10879) [INFO] * 2025-12-20 02:01:04 (10909) [INFO] * 2025-12-20 02:01:04 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-20 02:01:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-20 02:01:04 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-20 02:01:04 (10879) [INFO] * 2025-12-20 02:08:05 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-20 02:08:05 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-20 02:08:05 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-20 02:08:05 (10879) [INFO] * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-20 02:08:40 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-20 02:08:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-20 02:08:40 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-20 02:08:40 (10879) [INFO] * 2025-12-20 02:08:41 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-20 02:08:41 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-20 02:09:11 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-20 02:09:11 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-20 02:09:11 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-20 02:09:11 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-20 02:09:11 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-20 02:09:11 (10892) [INFO] yum --disablerepo= ... * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-20 02:09:11 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-20 02:09:11 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] yum-config-manager --disable * 2025-12-20 02:09:11 (10892) [INFO] or * 2025-12-20 02:09:11 (10892) [INFO] subscription-manager repos --disable= * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-20 02:09:11 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-20 02:09:11 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-20 02:09:11 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-20 02:09:11 (10892) [INFO] compromise: * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-20 02:09:11 (10892) [INFO] * 2025-12-20 02:09:11 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-20 02:09:11 (10909) [INFO] * 2025-12-20 02:09:11 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-20 02:09:11 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-20 02:09:11 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-20 02:09:11 (10879) [INFO] * 2025-12-20 02:09:12 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-20 02:09:12 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-20 02:09:12 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-20 02:09:12 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-20 02:09:12 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-20 02:09:12 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-20 02:09:12 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-20 02:09:12 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-20 02:09:12 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-20 02:09:12 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-20 02:09:12 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-20 02:09:12 (10892) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2025-12-20 02:09:12 (10909) [INFO] * 2025-12-20 02:09:12 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-20 02:09:12 (10879) [INFO] * 2025-12-20 02:09:12 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-20 02:09:13 (10892) [INFO] Determining fastest mirrors * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-20 02:09:44 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-20 02:09:44 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-20 02:09:44 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-20 02:09:44 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-20 02:09:44 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-20 02:09:44 (10892) [INFO] yum --disablerepo= ... * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-20 02:09:44 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-20 02:09:44 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] yum-config-manager --disable * 2025-12-20 02:09:44 (10892) [INFO] or * 2025-12-20 02:09:44 (10892) [INFO] subscription-manager repos --disable= * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-20 02:09:44 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-20 02:09:44 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-20 02:09:44 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-20 02:09:44 (10892) [INFO] compromise: * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-20 02:09:44 (10892) [INFO] * 2025-12-20 02:09:44 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-20 02:09:44 (10909) [INFO] * 2025-12-20 02:09:44 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-20 02:09:44 (6726) [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 * 2025-12-20 02:09:45 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-20 02:09:45 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-20 02:09:45 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-20 02:09:45 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-20 02:09:45 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-20 02:09:51 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/CldovoEFYf/ea_profile.json * 2025-12-20 02:11:48 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/CldovoEFYf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-20 02:11:48 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-21 01:44:02 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-21 01:48:03 (11982) [INFO] Script is up to date. * 2025-12-21 01:52:06 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-21 01:52:06 (10879) [INFO] * 2025-12-21 01:53:02 (10909) [INFO] * 2025-12-21 01:53:02 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-21 01:53:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-21 01:53:02 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-21 01:53:02 (10879) [INFO] * 2025-12-21 02:00:05 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-21 02:00:05 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-21 02:00:05 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-21 02:00:05 (10879) [INFO] * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-21 02:00:42 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-21 02:00:42 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-21 02:00:42 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-21 02:00:42 (10879) [INFO] * 2025-12-21 02:00:42 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-21 02:00:42 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-21 02:01:14 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-21 02:01:14 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-21 02:01:14 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-21 02:01:14 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-21 02:01:14 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-21 02:01:14 (10892) [INFO] yum --disablerepo= ... * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-21 02:01:14 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-21 02:01:14 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] yum-config-manager --disable * 2025-12-21 02:01:14 (10892) [INFO] or * 2025-12-21 02:01:14 (10892) [INFO] subscription-manager repos --disable= * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-21 02:01:14 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-21 02:01:14 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-21 02:01:14 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-21 02:01:14 (10892) [INFO] compromise: * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-21 02:01:14 (10892) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-21 02:01:14 (10909) [INFO] * 2025-12-21 02:01:14 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-21 02:01:14 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-21 02:01:14 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-21 02:01:14 (10879) [INFO] * 2025-12-21 02:01:14 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-21 02:01:15 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-21 02:01:15 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-21 02:01:15 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-21 02:01:15 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-21 02:01:15 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-21 02:01:15 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-21 02:01:15 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-21 02:01:15 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-21 02:01:15 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-21 02:01:15 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-21 02:01:15 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-21 02:01:15 (10909) [INFO] * 2025-12-21 02:01:15 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-21 02:01:15 (10879) [INFO] * 2025-12-21 02:01:15 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-21 02:01:16 (10892) [INFO] Determining fastest mirrors * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-21 02:01:47 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-21 02:01:47 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-21 02:01:47 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-21 02:01:47 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-21 02:01:47 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-21 02:01:47 (10892) [INFO] yum --disablerepo= ... * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-21 02:01:47 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-21 02:01:47 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] yum-config-manager --disable * 2025-12-21 02:01:47 (10892) [INFO] or * 2025-12-21 02:01:47 (10892) [INFO] subscription-manager repos --disable= * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-21 02:01:47 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-21 02:01:47 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-21 02:01:47 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-21 02:01:47 (10892) [INFO] compromise: * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-21 02:01:47 (10892) [INFO] * 2025-12-21 02:01:47 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-21 02:01:47 (10909) [INFO] * 2025-12-21 02:01:47 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-21 02:01:47 (6726) [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 * 2025-12-21 02:01:49 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-21 02:01:49 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-21 02:01:49 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-21 02:01:49 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-21 02:01:49 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-21 02:01:56 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rH1K1FqZRY/ea_profile.json * 2025-12-21 02:04:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rH1K1FqZRY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-21 02:04:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-22 01:39:07 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-22 01:43:07 (11982) [INFO] Script is up to date. * 2025-12-22 01:47:10 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-22 01:47:10 (10879) [INFO] * 2025-12-22 01:48:32 (10909) [INFO] * 2025-12-22 01:48:32 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-22 01:48:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-22 01:48:32 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-22 01:48:32 (10879) [INFO] * 2025-12-22 01:48:36 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-22 01:48:36 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-22 01:48:36 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-22 01:48:36 (10879) [INFO] * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-22 01:49:12 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-22 01:49:12 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-22 01:49:12 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-22 01:49:12 (10879) [INFO] * 2025-12-22 01:49:13 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-22 01:49:13 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-22 01:49:44 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-22 01:49:44 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-22 01:49:44 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-22 01:49:44 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-22 01:49:44 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-22 01:49:44 (10892) [INFO] yum --disablerepo= ... * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-22 01:49:44 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-22 01:49:44 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] yum-config-manager --disable * 2025-12-22 01:49:44 (10892) [INFO] or * 2025-12-22 01:49:44 (10892) [INFO] subscription-manager repos --disable= * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-22 01:49:44 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-22 01:49:44 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-22 01:49:44 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-22 01:49:44 (10892) [INFO] compromise: * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-22 01:49:44 (10892) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-22 01:49:44 (10909) [INFO] * 2025-12-22 01:49:44 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-22 01:49:44 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-22 01:49:44 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-22 01:49:44 (10879) [INFO] * 2025-12-22 01:49:44 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-22 01:49:44 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-22 01:49:44 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-22 01:49:44 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-22 01:49:44 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-22 01:49:44 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-22 01:49:44 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-22 01:49:44 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-22 01:49:44 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-22 01:49:44 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-22 01:49:45 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-22 01:49:45 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-22 01:49:45 (10909) [INFO] * 2025-12-22 01:49:45 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-22 01:49:45 (10879) [INFO] * 2025-12-22 01:49:45 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-22 01:49:46 (10892) [INFO] Determining fastest mirrors * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-22 01:50:17 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-22 01:50:17 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-22 01:50:17 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-22 01:50:17 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-22 01:50:17 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-22 01:50:17 (10892) [INFO] yum --disablerepo= ... * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-22 01:50:17 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-22 01:50:17 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] yum-config-manager --disable * 2025-12-22 01:50:17 (10892) [INFO] or * 2025-12-22 01:50:17 (10892) [INFO] subscription-manager repos --disable= * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-22 01:50:17 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-22 01:50:17 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-22 01:50:17 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-22 01:50:17 (10892) [INFO] compromise: * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-22 01:50:17 (10892) [INFO] * 2025-12-22 01:50:17 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-22 01:50:17 (10909) [INFO] * 2025-12-22 01:50:17 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-22 01:50:17 (6726) [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 * 2025-12-22 01:50:19 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-22 01:50:19 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-22 01:50:19 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-22 01:50:19 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-22 01:50:19 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-22 01:50:26 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pFDVpqCuvo/ea_profile.json * 2025-12-22 01:52:54 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pFDVpqCuvo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-22 01:52:54 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-23 01:42:02 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-23 01:46:03 (11982) [INFO] Script is up to date. * 2025-12-23 01:50:06 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-23 01:50:06 (10879) [INFO] * 2025-12-23 01:51:31 (10909) [INFO] * 2025-12-23 01:51:31 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-23 01:51:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-23 01:51:31 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-23 01:51:31 (10879) [INFO] * 2025-12-23 01:58:33 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-23 01:58:33 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-23 01:58:33 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-23 01:58:33 (10879) [INFO] * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-23 01:59:08 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-23 01:59:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-23 01:59:08 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-23 01:59:08 (10879) [INFO] * 2025-12-23 01:59:08 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-23 01:59:08 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-23 01:59:39 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-23 01:59:39 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-23 01:59:39 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-23 01:59:39 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-23 01:59:39 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-23 01:59:39 (10892) [INFO] yum --disablerepo= ... * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-23 01:59:39 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-23 01:59:39 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] yum-config-manager --disable * 2025-12-23 01:59:39 (10892) [INFO] or * 2025-12-23 01:59:39 (10892) [INFO] subscription-manager repos --disable= * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-23 01:59:39 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-23 01:59:39 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-23 01:59:39 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-23 01:59:39 (10892) [INFO] compromise: * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-23 01:59:39 (10892) [INFO] * 2025-12-23 01:59:39 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-23 01:59:39 (10909) [INFO] * 2025-12-23 01:59:39 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-23 01:59:39 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-23 01:59:39 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-23 01:59:39 (10879) [INFO] * 2025-12-23 01:59:40 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-23 01:59:40 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-23 01:59:40 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-23 01:59:40 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-23 01:59:40 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-23 01:59:40 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-23 01:59:40 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-23 01:59:40 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-23 01:59:40 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-23 01:59:40 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-23 01:59:40 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-23 01:59:40 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-23 01:59:40 (10909) [INFO] * 2025-12-23 01:59:40 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-23 01:59:40 (10879) [INFO] * 2025-12-23 01:59:41 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-23 01:59:41 (10892) [INFO] Determining fastest mirrors * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-23 02:00:12 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-23 02:00:12 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-23 02:00:12 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-23 02:00:12 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-23 02:00:12 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-23 02:00:12 (10892) [INFO] yum --disablerepo= ... * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-23 02:00:12 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-23 02:00:12 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] yum-config-manager --disable * 2025-12-23 02:00:12 (10892) [INFO] or * 2025-12-23 02:00:12 (10892) [INFO] subscription-manager repos --disable= * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-23 02:00:12 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-23 02:00:12 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-23 02:00:12 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-23 02:00:12 (10892) [INFO] compromise: * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-23 02:00:12 (10892) [INFO] * 2025-12-23 02:00:12 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-23 02:00:12 (10909) [INFO] * 2025-12-23 02:00:12 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-23 02:00:12 (6726) [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 * 2025-12-23 02:00:14 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-23 02:00:14 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-23 02:00:14 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-23 02:00:14 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-23 02:00:14 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-23 02:00:22 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bBCtvegpKh/ea_profile.json * 2025-12-23 02:03:51 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bBCtvegpKh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-23 02:03:51 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-24 01:38:37 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-24 01:42:38 (11982) [INFO] Script is up to date. * 2025-12-24 01:46:41 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-24 01:46:41 (10879) [INFO] * 2025-12-24 01:47:56 (10909) [INFO] * 2025-12-24 01:47:56 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-24 01:47:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-24 01:47:57 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-24 01:47:57 (10879) [INFO] * 2025-12-24 01:57:27 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-24 01:57:27 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-24 01:57:27 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-24 01:57:27 (10879) [INFO] * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-24 01:58:02 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-24 01:58:02 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-24 01:58:02 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-24 01:58:02 (10879) [INFO] * 2025-12-24 01:58:02 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-24 01:58:03 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-24 01:58:33 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-24 01:58:33 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-24 01:58:33 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-24 01:58:33 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-24 01:58:33 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-24 01:58:33 (10892) [INFO] yum --disablerepo= ... * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-24 01:58:33 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-24 01:58:33 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] yum-config-manager --disable * 2025-12-24 01:58:33 (10892) [INFO] or * 2025-12-24 01:58:33 (10892) [INFO] subscription-manager repos --disable= * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-24 01:58:33 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-24 01:58:33 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-24 01:58:33 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-24 01:58:33 (10892) [INFO] compromise: * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-24 01:58:33 (10892) [INFO] * 2025-12-24 01:58:33 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-24 01:58:33 (10909) [INFO] * 2025-12-24 01:58:33 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-24 01:58:33 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-24 01:58:33 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-24 01:58:33 (10879) [INFO] * 2025-12-24 01:58:34 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-24 01:58:34 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-24 01:58:34 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-24 01:58:34 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-24 01:58:34 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-24 01:58:34 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-24 01:58:34 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-24 01:58:34 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-24 01:58:34 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-24 01:58:34 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-24 01:58:34 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-24 01:58:34 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-24 01:58:34 (10909) [INFO] * 2025-12-24 01:58:34 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-24 01:58:34 (10879) [INFO] * 2025-12-24 01:58:35 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-24 01:58:35 (10892) [INFO] Determining fastest mirrors * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-24 01:59:07 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-24 01:59:07 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-24 01:59:07 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-24 01:59:07 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-24 01:59:07 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-24 01:59:07 (10892) [INFO] yum --disablerepo= ... * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-24 01:59:07 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-24 01:59:07 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] yum-config-manager --disable * 2025-12-24 01:59:07 (10892) [INFO] or * 2025-12-24 01:59:07 (10892) [INFO] subscription-manager repos --disable= * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-24 01:59:07 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-24 01:59:07 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-24 01:59:07 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-24 01:59:07 (10892) [INFO] compromise: * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-24 01:59:07 (10892) [INFO] * 2025-12-24 01:59:07 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-24 01:59:07 (10909) [INFO] * 2025-12-24 01:59:07 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-24 01:59:07 (6726) [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 * 2025-12-24 01:59:08 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-24 01:59:08 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-24 01:59:08 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-24 01:59:08 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-24 01:59:08 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-24 01:59:17 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/epMYqj_0l6/ea_profile.json * 2025-12-24 02:02:30 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/epMYqj_0l6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-24 02:02:30 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-25 01:42:02 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-25 01:46:03 (11982) [INFO] Script is up to date. * 2025-12-25 01:50:06 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-25 01:50:06 (10879) [INFO] * 2025-12-25 01:51:27 (10909) [INFO] * 2025-12-25 01:51:27 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-25 01:51:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-25 01:51:28 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-25 01:51:28 (10879) [INFO] * 2025-12-25 01:56:12 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-25 01:56:12 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-25 01:56:12 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-25 01:56:12 (10879) [INFO] * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-25 01:59:28 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-25 01:59:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-25 01:59:28 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-25 01:59:28 (10879) [INFO] * 2025-12-25 01:59:29 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-25 01:59:29 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-25 02:00:00 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-25 02:00:00 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') * 2025-12-25 02:00:00 (10892) [INFO] * EA4: 208.74.123.61 * 2025-12-25 02:00:00 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2025-12-25 02:00:00 (10892) [INFO] * cpanel-plugins: 208.74.123.61 * 2025-12-25 02:00:00 (10892) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-12-25 02:01:09 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') * 2025-12-25 02:01:09 (10892) [INFO] Trying other mirror. * 2025-12-25 02:01:40 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2025-12-25 02:01:40 (10892) [INFO] Trying other mirror. * 2025-12-25 02:03:42 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-25 02:03:42 (10892) [INFO] Trying other mirror. * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-12-25 02:03:42 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-25 02:03:42 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-25 02:03:42 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-25 02:03:42 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-25 02:03:42 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-25 02:03:42 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-25 02:03:42 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-25 02:03:42 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-12-25 02:03:42 (10892) [INFO] or * 2025-12-25 02:03:42 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-25 02:03:42 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-25 02:03:42 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-25 02:03:42 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-25 02:03:42 (10892) [INFO] compromise: * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-12-25 02:03:42 (10892) [INFO] * 2025-12-25 02:03:42 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-12-25 02:03:42 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-25 02:03:42 (10909) [INFO] * 2025-12-25 02:03:42 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'timed out before SSL handshake') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30535 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-25 02:03:42 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-25 02:03:42 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-25 02:03:42 (10879) [INFO] * 2025-12-25 02:03:43 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-25 02:03:43 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-25 02:03:43 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-25 02:03:43 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-25 02:03:43 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-25 02:03:43 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-25 02:03:43 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-25 02:03:43 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-25 02:03:43 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-25 02:03:43 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-25 02:03:43 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-25 02:03:43 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-25 02:03:43 (10909) [INFO] * 2025-12-25 02:03:43 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-25 02:03:43 (10879) [INFO] * 2025-12-25 02:03:44 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-25 02:03:44 (10892) [INFO] Determining fastest mirrors * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-25 02:04:15 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-25 02:04:15 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-25 02:04:15 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-25 02:04:15 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-25 02:04:15 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-25 02:04:15 (10892) [INFO] yum --disablerepo= ... * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-25 02:04:15 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-25 02:04:15 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] yum-config-manager --disable * 2025-12-25 02:04:15 (10892) [INFO] or * 2025-12-25 02:04:15 (10892) [INFO] subscription-manager repos --disable= * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-25 02:04:15 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-25 02:04:15 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-25 02:04:15 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-25 02:04:15 (10892) [INFO] compromise: * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-25 02:04:15 (10892) [INFO] * 2025-12-25 02:04:15 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-25 02:04:15 (10909) [INFO] * 2025-12-25 02:04:15 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-25 02:04:15 (6726) [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 * 2025-12-25 02:04:17 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-25 02:04:17 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-25 02:04:17 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-25 02:04:17 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-25 02:04:17 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-25 02:11:38 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gjxihvQtJZ/ea_profile.json * 2025-12-26 01:42:42 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-26 01:46:42 (11982) [INFO] Script is up to date. * 2025-12-26 01:50:45 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-26 01:50:45 (10879) [INFO] * 2025-12-26 01:52:12 (10909) [INFO] * 2025-12-26 01:52:12 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-26 01:52:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-26 01:52:13 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-26 01:52:13 (10879) [INFO] * 2025-12-26 01:52:16 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-26 01:52:16 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-26 01:52:16 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-26 01:52:16 (10879) [INFO] * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-26 01:55:32 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-26 01:55:32 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-26 01:55:32 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-26 01:55:32 (10879) [INFO] * 2025-12-26 01:55:32 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-26 01:55:32 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-26 01:56:02 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2025-12-26 01:56:02 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30021 milliseconds with 0 out of 0 bytes received') * 2025-12-26 01:56:02 (10892) [INFO] * EA4: 208.74.123.62 * 2025-12-26 01:56:02 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.62 * 2025-12-26 01:56:02 (10892) [INFO] * cpanel-plugins: 208.74.123.62 * 2025-12-26 01:56:02 (10892) [INFO] * epel: pubmirror1.math.uh.edu * 2025-12-26 01:58:44 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-26 01:58:44 (10892) [INFO] Trying other mirror. * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2025-12-26 01:58:44 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-26 01:58:44 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-26 01:58:44 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-26 01:58:44 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-26 01:58:44 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-26 01:58:44 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-26 01:58:44 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-26 01:58:44 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2025-12-26 01:58:44 (10892) [INFO] or * 2025-12-26 01:58:44 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-26 01:58:44 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-26 01:58:44 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-26 01:58:44 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-26 01:58:44 (10892) [INFO] compromise: * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2025-12-26 01:58:44 (10892) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2025-12-26 01:58:44 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-26 01:58:44 (10909) [INFO] * 2025-12-26 01:58:44 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30021 milliseconds with 0 out of 0 bytes received') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY1MjYwNTk0OjE3NjU1MTk3OTQ6N9KVfAJKAtgZRqqWoOjkq1E9DWRx5P0OZ4mhG3T98iHcQQDTmpd8EC03Qm9uLGF1KkVXzEEoPXWCRAVcxmP5SMSfkTws2zIWDNykC4U99iRGybmYnGphgFHZHTyJP5KS7YkRsXWVezSj1dKwmye3r4sRCubCU4IOgn1qhpZDSyf0pT-2nH_nOjOlGK_r8OeuMl-355GFB0vVvXOxLWsmFNRFiJxWfxqtOcAK0rOFaicIk_ohLQU5C5QSSzHARzFyGt5zSRARxD1AMcBh_HwFd2eKVNXCIq0qhL_QZhGLPSLP0eepWcKs_4dsfV6zHiEC5ujokBlM5ZTi-OnrTkGtvFgfapqEbGn7QMyPw1sZ38cqGQRIqcw3i_UAHdOnhPSSEynGBpCkFFAQ_s86kSv20vyedNPXq33twSqK5GNZc0XctPGrAHO5kuWHtxrkBayOIHsV50i0omhNAMBHThNIDOVijh27SfZGfEPaQDsXHmn5_WWeyoTPwCPRS1bVOQJnbbxf8bbZ7spJH5pnbpAEaljeRx-9SjOj-iRjvXe2uNeD2X-klWjPUNQtfFyvEezV5SXAjmNWf9YGZNGC_l83U6WJHCMUoQdpWb3_Zjt06suEnTLglYl1uPWAA_Zzgqf1qQD3E7X5CWVXABskKj1-7WkQxKiXqTlNqYtAAceF2rQ=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2025-12-26 01:58:44 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-26 01:58:44 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-26 01:58:44 (10879) [INFO] * 2025-12-26 01:58:44 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-26 01:58:45 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-26 01:58:45 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-26 01:58:45 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-26 01:58:45 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-26 01:58:45 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-26 01:58:45 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-26 01:58:45 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-26 01:58:45 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-26 01:58:45 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-26 01:58:45 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-26 01:58:45 (10892) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2025-12-26 01:58:45 (10909) [INFO] * 2025-12-26 01:58:45 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-26 01:58:45 (10879) [INFO] * 2025-12-26 01:58:45 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-26 01:58:46 (10892) [INFO] Determining fastest mirrors * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-26 01:59:16 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-26 01:59:16 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-26 01:59:16 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-26 01:59:16 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-26 01:59:16 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-26 01:59:16 (10892) [INFO] yum --disablerepo= ... * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-26 01:59:16 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-26 01:59:16 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] yum-config-manager --disable * 2025-12-26 01:59:16 (10892) [INFO] or * 2025-12-26 01:59:16 (10892) [INFO] subscription-manager repos --disable= * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-26 01:59:16 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-26 01:59:16 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-26 01:59:16 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-26 01:59:16 (10892) [INFO] compromise: * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-26 01:59:16 (10892) [INFO] * 2025-12-26 01:59:16 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-26 01:59:16 (10909) [INFO] * 2025-12-26 01:59:16 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-26 01:59:16 (6726) [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 * 2025-12-26 01:59:18 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-26 01:59:18 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-26 01:59:18 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-26 01:59:18 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-26 01:59:18 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-26 01:59:24 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XzEg3DrDfP/ea_profile.json * 2025-12-26 02:01:52 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XzEg3DrDfP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-26 02:01:52 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-27 01:42:44 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-27 01:46:44 (11982) [INFO] Script is up to date. * 2025-12-27 01:50:47 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-27 01:50:47 (10879) [INFO] * 2025-12-27 01:51:41 (10909) [INFO] * 2025-12-27 01:51:41 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-27 01:51:41 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-27 01:51:41 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-27 01:51:41 (10879) [INFO] * 2025-12-27 01:58:43 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-27 01:58:43 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-27 01:58:43 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-27 01:58:43 (10879) [INFO] * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-27 01:59:18 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-27 01:59:18 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-27 01:59:18 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-27 01:59:18 (10879) [INFO] * 2025-12-27 01:59:18 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-27 01:59:19 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-27 01:59:49 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-27 01:59:49 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-27 01:59:49 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-27 01:59:49 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-27 01:59:49 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-27 01:59:49 (10892) [INFO] yum --disablerepo= ... * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-27 01:59:49 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-27 01:59:49 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] yum-config-manager --disable * 2025-12-27 01:59:49 (10892) [INFO] or * 2025-12-27 01:59:49 (10892) [INFO] subscription-manager repos --disable= * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-27 01:59:49 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-27 01:59:49 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-27 01:59:49 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-27 01:59:49 (10892) [INFO] compromise: * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-27 01:59:49 (10892) [INFO] * 2025-12-27 01:59:49 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-27 01:59:49 (10909) [INFO] * 2025-12-27 01:59:49 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-27 01:59:49 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-27 01:59:49 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-27 01:59:49 (10879) [INFO] * 2025-12-27 01:59:50 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-27 01:59:50 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-27 01:59:50 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-27 01:59:50 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-27 01:59:50 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-27 01:59:50 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-27 01:59:50 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-27 01:59:50 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-27 01:59:50 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-27 01:59:50 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-27 01:59:50 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-27 01:59:50 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-27 01:59:50 (10909) [INFO] * 2025-12-27 01:59:50 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-27 01:59:50 (10879) [INFO] * 2025-12-27 01:59:51 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-27 01:59:51 (10892) [INFO] Determining fastest mirrors * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-27 02:00:22 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-27 02:00:22 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-27 02:00:22 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-27 02:00:22 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-27 02:00:22 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-27 02:00:22 (10892) [INFO] yum --disablerepo= ... * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-27 02:00:22 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-27 02:00:22 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] yum-config-manager --disable * 2025-12-27 02:00:22 (10892) [INFO] or * 2025-12-27 02:00:22 (10892) [INFO] subscription-manager repos --disable= * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-27 02:00:22 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-27 02:00:22 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-27 02:00:22 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-27 02:00:22 (10892) [INFO] compromise: * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-27 02:00:22 (10892) [INFO] * 2025-12-27 02:00:22 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-27 02:00:22 (10909) [INFO] * 2025-12-27 02:00:22 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-27 02:00:22 (6726) [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 * 2025-12-27 02:00:24 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-27 02:00:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-27 02:00:24 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-27 02:00:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-27 02:00:24 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-27 02:00:33 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3OEVJey2RQ/ea_profile.json * 2025-12-27 02:03:01 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3OEVJey2RQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-27 02:03:01 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-28 01:54:59 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-28 01:59:00 (11982) [INFO] Script is up to date. * 2025-12-28 02:03:03 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-28 02:03:03 (10879) [INFO] * 2025-12-28 02:03:57 (10909) [INFO] * 2025-12-28 02:03:57 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-28 02:03:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-28 02:03:57 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-28 02:03:57 (10879) [INFO] * 2025-12-28 02:04:00 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-28 02:04:00 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-28 02:04:00 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-28 02:04:00 (10879) [INFO] * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-28 02:04:35 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-28 02:04:35 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-28 02:04:35 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-28 02:04:35 (10879) [INFO] * 2025-12-28 02:04:35 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-28 02:04:36 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-28 02:05:06 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-28 02:05:06 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-28 02:05:06 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-28 02:05:06 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-28 02:05:06 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-28 02:05:06 (10892) [INFO] yum --disablerepo= ... * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-28 02:05:06 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-28 02:05:06 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] yum-config-manager --disable * 2025-12-28 02:05:06 (10892) [INFO] or * 2025-12-28 02:05:06 (10892) [INFO] subscription-manager repos --disable= * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-28 02:05:06 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-28 02:05:06 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-28 02:05:06 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-28 02:05:06 (10892) [INFO] compromise: * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-28 02:05:06 (10892) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-28 02:05:06 (10909) [INFO] * 2025-12-28 02:05:06 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-28 02:05:06 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-28 02:05:06 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-28 02:05:06 (10879) [INFO] * 2025-12-28 02:05:06 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-28 02:05:07 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-28 02:05:07 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-28 02:05:07 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-28 02:05:07 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-28 02:05:07 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-28 02:05:07 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-28 02:05:07 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-28 02:05:07 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-28 02:05:07 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-28 02:05:07 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-28 02:05:07 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-28 02:05:07 (10909) [INFO] * 2025-12-28 02:05:07 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-28 02:05:07 (10879) [INFO] * 2025-12-28 02:05:07 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-28 02:05:08 (10892) [INFO] Determining fastest mirrors * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-28 02:05:38 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-28 02:05:38 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-28 02:05:38 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-28 02:05:38 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-28 02:05:38 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-28 02:05:38 (10892) [INFO] yum --disablerepo= ... * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-28 02:05:38 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-28 02:05:38 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] yum-config-manager --disable * 2025-12-28 02:05:38 (10892) [INFO] or * 2025-12-28 02:05:38 (10892) [INFO] subscription-manager repos --disable= * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-28 02:05:38 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-28 02:05:38 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-28 02:05:38 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-28 02:05:38 (10892) [INFO] compromise: * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-28 02:05:38 (10892) [INFO] * 2025-12-28 02:05:38 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-28 02:05:38 (10909) [INFO] * 2025-12-28 02:05:38 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-28 02:05:38 (6726) [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 * 2025-12-28 02:05:40 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-28 02:05:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-28 02:05:40 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-28 02:05:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-28 02:05:40 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-28 02:05:46 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9bHpWR38jf/ea_profile.json * 2025-12-28 02:14:11 (10011) [INFO] Backed up EA4 profile to /tmp/9bHpWR38jf/ea_profile.json * 2025-12-28 02:14:11 (264) [ERROR] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2025-12-28 02:14:46 (703) [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. * 2025-12-28 02:14:46 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-29 01:43:44 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-29 01:47:45 (11982) [INFO] Script is up to date. * 2025-12-29 01:51:47 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-29 01:51:47 (10879) [INFO] * 2025-12-29 01:53:11 (10909) [INFO] * 2025-12-29 01:53:11 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-29 01:53:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-29 01:53:11 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-29 01:53:11 (10879) [INFO] * 2025-12-29 02:02:27 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-29 02:02:27 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-29 02:02:27 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-29 02:02:27 (10879) [INFO] * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-29 02:03:53 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-29 02:03:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-29 02:03:53 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-29 02:03:53 (10879) [INFO] * 2025-12-29 02:03:54 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-29 02:03:54 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-29 02:04:25 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-29 02:04:25 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-29 02:04:25 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-29 02:04:25 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-29 02:04:25 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-29 02:04:25 (10892) [INFO] yum --disablerepo= ... * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-29 02:04:25 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-29 02:04:25 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] yum-config-manager --disable * 2025-12-29 02:04:25 (10892) [INFO] or * 2025-12-29 02:04:25 (10892) [INFO] subscription-manager repos --disable= * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-29 02:04:25 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-29 02:04:25 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-29 02:04:25 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-29 02:04:25 (10892) [INFO] compromise: * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-29 02:04:25 (10892) [INFO] * 2025-12-29 02:04:25 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-29 02:04:25 (10909) [INFO] * 2025-12-29 02:04:25 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-29 02:04:25 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-29 02:04:25 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-29 02:04:25 (10879) [INFO] * 2025-12-29 02:04:26 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-29 02:04:26 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-29 02:04:26 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-29 02:04:26 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-29 02:04:26 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-29 02:04:26 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-29 02:04:26 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-29 02:04:26 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-29 02:04:26 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-29 02:04:26 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-29 02:04:26 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-29 02:04:26 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-29 02:04:26 (10909) [INFO] * 2025-12-29 02:04:26 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-29 02:04:26 (10879) [INFO] * 2025-12-29 02:04:26 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-29 02:04:26 (10892) [INFO] Determining fastest mirrors * 2025-12-29 02:05:14 (10892) [INFO] * EA4: 208.74.123.58 * 2025-12-29 02:05:14 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.58 * 2025-12-29 02:05:14 (10892) [INFO] * cpanel-plugins: 208.74.123.58 * 2025-12-29 02:05:14 (10892) [INFO] * epel: mirror.math.princeton.edu * 2025-12-29 02:06:35 (10892) [INFO] https://repo.alt.tuxcare.com/alt-common/rpm/el/7/stable/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.alt.tuxcare.com/alt-common/rpm/el/7/stable/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30540 milliseconds') * 2025-12-29 02:06:35 (10892) [INFO] Trying other mirror. * 2025-12-29 02:07:29 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30009 milliseconds with 0 out of 0 bytes received') * 2025-12-29 02:07:29 (10892) [INFO] Trying other mirror. * 2025-12-29 02:10:53 (10892) [INFO] http://89.222.122.161/cpanelsync/repos/CentOS/7/EA4/repodata/8c56bd88b9b442d7a5144d302832690c3ec5fda12bc747b95a217500768c3127-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum * 2025-12-29 02:10:53 (10892) [INFO] Trying other mirror. * 2025-12-29 02:11:28 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: (28, 'Connection timed out after 30769 milliseconds') * 2025-12-29 02:11:28 (10892) [INFO] Trying other mirror. * 2025-12-29 02:11:28 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/d6d94c7d406fe7ad4902a97104b39a0d8299451832a97f31d71653ba982c955b-filelists.sqlite.bz2: (28, 'Connection timed out after 30830 milliseconds') * 2025-12-29 02:11:28 (10892) [INFO] Trying other mirror. * 2025-12-29 02:11:58 (10892) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: (28, 'timed out before SSL handshake') * 2025-12-29 02:11:58 (10892) [INFO] Trying other mirror. * 2025-12-29 02:12:22 (10892) [INFO] https://repo.tuxcare.com/centos7-els//updates/x86_64/repodata/f7a940e5d40644d64c1f0ccaa642befc73bdb712645d730f8ba1771c27fefe2e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-12-29 02:12:22 (10892) [INFO] Trying other mirror. * 2025-12-29 02:12:45 (10892) [INFO] https://els-rollout.tuxcare.com/slot-1/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-12-29 02:12:45 (10892) [INFO] Trying other mirror. * 2025-12-29 02:13:08 (10892) [INFO] https://els-rollout.tuxcare.com/slot-2/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-12-29 02:13:08 (10892) [INFO] Trying other mirror. * 2025-12-29 02:13:31 (10892) [INFO] https://els-rollout.tuxcare.com/slot-3/el/7/x86_64//repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable * 2025-12-29 02:13:31 (10892) [INFO] Trying other mirror. * 2025-12-30 01:42:39 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-30 01:46:39 (11982) [INFO] Script is up to date. * 2025-12-30 01:50:42 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-30 01:50:42 (10879) [INFO] * 2025-12-30 01:52:06 (10909) [INFO] * 2025-12-30 01:52:06 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-30 01:52:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-30 01:52:06 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-30 01:52:06 (10879) [INFO] * 2025-12-30 01:52:10 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-30 01:52:10 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-30 01:52:10 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-30 01:52:10 (10879) [INFO] * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-30 01:52:46 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-30 01:52:46 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-30 01:52:46 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-30 01:52:46 (10879) [INFO] * 2025-12-30 01:52:46 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-30 01:52:46 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-30 01:53:17 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-30 01:53:17 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-30 01:53:17 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-30 01:53:17 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-30 01:53:17 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-30 01:53:17 (10892) [INFO] yum --disablerepo= ... * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-30 01:53:17 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-30 01:53:17 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] yum-config-manager --disable * 2025-12-30 01:53:17 (10892) [INFO] or * 2025-12-30 01:53:17 (10892) [INFO] subscription-manager repos --disable= * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-30 01:53:17 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-30 01:53:17 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-30 01:53:17 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-30 01:53:17 (10892) [INFO] compromise: * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-30 01:53:17 (10892) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-30 01:53:17 (10909) [INFO] * 2025-12-30 01:53:17 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-30 01:53:17 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-30 01:53:17 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-30 01:53:17 (10879) [INFO] * 2025-12-30 01:53:17 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-30 01:53:18 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-30 01:53:18 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-30 01:53:18 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-30 01:53:18 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-30 01:53:18 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-30 01:53:18 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-30 01:53:18 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-30 01:53:18 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-30 01:53:18 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-30 01:53:18 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-30 01:53:18 (10892) [INFO] Other repos take up 928 k of disk space (use --verbose for details) * 2025-12-30 01:53:18 (10909) [INFO] * 2025-12-30 01:53:18 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-30 01:53:18 (10879) [INFO] * 2025-12-30 01:53:19 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-30 01:53:19 (10892) [INFO] Determining fastest mirrors * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-30 01:53:50 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-30 01:53:50 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-30 01:53:50 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-30 01:53:50 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-30 01:53:50 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-30 01:53:50 (10892) [INFO] yum --disablerepo= ... * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-30 01:53:50 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-30 01:53:50 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] yum-config-manager --disable * 2025-12-30 01:53:50 (10892) [INFO] or * 2025-12-30 01:53:50 (10892) [INFO] subscription-manager repos --disable= * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-30 01:53:50 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-30 01:53:50 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-30 01:53:50 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-30 01:53:50 (10892) [INFO] compromise: * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-30 01:53:50 (10892) [INFO] * 2025-12-30 01:53:50 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-30 01:53:50 (10909) [INFO] * 2025-12-30 01:53:50 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-30 01:53:50 (6726) [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 * 2025-12-30 01:53:52 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-30 01:53:52 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-30 01:53:52 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-30 01:53:52 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-30 01:53:52 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-30 01:53:58 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1NwiAdvC6x/ea_profile.json * 2025-12-30 01:56:56 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1NwiAdvC6x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-30 01:56:56 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-12-31 01:41:19 (11960) [INFO] Self-update of script version 76 requested. * 2025-12-31 01:45:20 (11982) [INFO] Script is up to date. * 2025-12-31 01:49:23 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-12-31 01:49:23 (10879) [INFO] * 2025-12-31 01:50:41 (10909) [INFO] * 2025-12-31 01:50:41 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2025-12-31 01:50:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2025-12-31 01:50:42 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-12-31 01:50:42 (10879) [INFO] * 2025-12-31 01:57:45 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2025-12-31 01:57:45 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-12-31 01:57:45 (10878) [INFO] Running: /usr/bin/yum list extras * 2025-12-31 01:57:45 (10879) [INFO] * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2025-12-31 01:58:21 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2025-12-31 01:58:21 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2025-12-31 01:58:21 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-31 01:58:21 (10879) [INFO] * 2025-12-31 01:58:21 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-31 01:58:22 (10892) [INFO] Loading mirror speeds from cached hostfile * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-31 01:58:53 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-31 01:58:53 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-31 01:58:53 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-31 01:58:53 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-31 01:58:53 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-31 01:58:53 (10892) [INFO] yum --disablerepo= ... * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-31 01:58:53 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-31 01:58:53 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] yum-config-manager --disable * 2025-12-31 01:58:53 (10892) [INFO] or * 2025-12-31 01:58:53 (10892) [INFO] subscription-manager repos --disable= * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-31 01:58:53 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-31 01:58:53 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-31 01:58:53 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-31 01:58:53 (10892) [INFO] compromise: * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-31 01:58:53 (10892) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-31 01:58:53 (10909) [INFO] * 2025-12-31 01:58:53 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-31 01:58:53 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-12-31 01:58:53 (10878) [INFO] Running: /usr/bin/yum clean all * 2025-12-31 01:58:53 (10879) [INFO] * 2025-12-31 01:58:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-31 01:58:54 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2025-12-31 01:58:54 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2025-12-31 01:58:54 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2025-12-31 01:58:54 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2025-12-31 01:58:54 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2025-12-31 01:58:54 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-12-31 01:58:54 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-12-31 01:58:54 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2025-12-31 01:58:54 (10892) [INFO] : wp-toolkit-thirdparties * 2025-12-31 01:58:54 (10892) [INFO] Cleaning up list of fastest mirrors * 2025-12-31 01:58:54 (10892) [INFO] Other repos take up 936 k of disk space (use --verbose for details) * 2025-12-31 01:58:54 (10909) [INFO] * 2025-12-31 01:58:54 (10878) [INFO] Running: /usr/bin/yum makecache * 2025-12-31 01:58:54 (10879) [INFO] * 2025-12-31 01:58:54 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-12-31 01:58:55 (10892) [INFO] Determining fastest mirrors * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] One of the configured repositories failed (Unknown), * 2025-12-31 01:59:25 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-12-31 01:59:25 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-12-31 01:59:25 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2025-12-31 01:59:25 (10892) [INFO] distribution release than is supported by the repository (and the * 2025-12-31 01:59:25 (10892) [INFO] packages for the previous distribution release still work). * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2025-12-31 01:59:25 (10892) [INFO] yum --disablerepo= ... * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-12-31 01:59:25 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2025-12-31 01:59:25 (10892) [INFO] again or use --enablerepo for temporary usage: * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] yum-config-manager --disable * 2025-12-31 01:59:25 (10892) [INFO] or * 2025-12-31 01:59:25 (10892) [INFO] subscription-manager repos --disable= * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-12-31 01:59:25 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-12-31 01:59:25 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-12-31 01:59:25 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-12-31 01:59:25 (10892) [INFO] compromise: * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-12-31 01:59:25 (10892) [INFO] * 2025-12-31 01:59:25 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2025-12-31 01:59:25 (10909) [INFO] * 2025-12-31 01:59:25 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-12-31 01:59:25 (6726) [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 * 2025-12-31 01:59:27 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2025-12-31 01:59:27 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2025-12-31 01:59:27 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2025-12-31 01:59:27 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2025-12-31 01:59:27 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-12-31 01:59:34 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AnD4dxD0nz/ea_profile.json * 2025-12-31 02:02:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/AnD4dxD0nz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2025-12-31 02:02:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-01 01:42:24 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-01 01:46:24 (11982) [INFO] Script is up to date. * 2026-01-01 01:50:27 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-01 01:50:27 (10879) [INFO] * 2026-01-01 01:51:48 (10909) [INFO] * 2026-01-01 01:51:48 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-01 01:51:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-01 01:51:49 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-01 01:51:49 (10879) [INFO] * 2026-01-01 01:58:55 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-01 01:58:55 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-01 01:58:55 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-01 01:58:55 (10879) [INFO] * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-01 01:59:30 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-01 01:59:30 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-01 01:59:30 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-01 01:59:30 (10879) [INFO] * 2026-01-01 01:59:30 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-01 01:59:30 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-01 02:00:01 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-01 02:00:01 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-01 02:00:01 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-01 02:00:01 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-01 02:00:01 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-01 02:00:01 (10892) [INFO] yum --disablerepo= ... * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-01 02:00:01 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-01 02:00:01 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] yum-config-manager --disable * 2026-01-01 02:00:01 (10892) [INFO] or * 2026-01-01 02:00:01 (10892) [INFO] subscription-manager repos --disable= * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-01 02:00:01 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-01 02:00:01 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-01 02:00:01 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-01 02:00:01 (10892) [INFO] compromise: * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-01 02:00:01 (10892) [INFO] * 2026-01-01 02:00:01 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-01 02:00:01 (10909) [INFO] * 2026-01-01 02:00:01 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-01 02:00:01 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-01 02:00:01 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-01 02:00:01 (10879) [INFO] * 2026-01-01 02:00:02 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-01 02:00:02 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-01 02:00:02 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-01 02:00:02 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-01 02:00:02 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-01 02:00:02 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-01 02:00:02 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-01 02:00:02 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-01 02:00:02 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-01 02:00:02 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-01 02:00:02 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-01 02:00:03 (10892) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-01 02:00:03 (10909) [INFO] * 2026-01-01 02:00:03 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-01 02:00:03 (10879) [INFO] * 2026-01-01 02:00:03 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-01 02:00:04 (10892) [INFO] Determining fastest mirrors * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-01 02:00:34 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-01 02:00:34 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-01 02:00:34 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-01 02:00:34 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-01 02:00:34 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-01 02:00:34 (10892) [INFO] yum --disablerepo= ... * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-01 02:00:34 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-01 02:00:34 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] yum-config-manager --disable * 2026-01-01 02:00:34 (10892) [INFO] or * 2026-01-01 02:00:34 (10892) [INFO] subscription-manager repos --disable= * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-01 02:00:34 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-01 02:00:34 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-01 02:00:34 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-01 02:00:34 (10892) [INFO] compromise: * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-01 02:00:34 (10892) [INFO] * 2026-01-01 02:00:34 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-01 02:00:34 (10909) [INFO] * 2026-01-01 02:00:34 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-01 02:00:34 (6726) [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 * 2026-01-01 02:00:36 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-01 02:00:36 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-01 02:00:36 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-01 02:00:36 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-01 02:00:36 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-01 02:00:43 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iF347TKbxc/ea_profile.json * 2026-01-01 02:03:11 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iF347TKbxc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-01 02:03:11 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-02 01:42:42 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-02 01:46:42 (11982) [INFO] Script is up to date. * 2026-01-02 01:50:45 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-02 01:50:45 (10879) [INFO] * 2026-01-02 01:52:03 (10909) [INFO] * 2026-01-02 01:52:03 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-02 01:52:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-02 01:52:04 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-02 01:52:04 (10879) [INFO] * 2026-01-02 01:53:20 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-02 01:53:20 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-02 01:53:20 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-02 01:53:20 (10879) [INFO] * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-02 01:57:07 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-02 01:57:07 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-02 01:57:07 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-02 01:57:07 (10879) [INFO] * 2026-01-02 01:57:07 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-02 01:57:08 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-02 01:57:38 (10892) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2026-01-02 01:57:38 (10892) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30039 milliseconds with 0 out of 0 bytes received') * 2026-01-02 01:57:38 (10892) [INFO] * EA4: 208.74.123.61 * 2026-01-02 01:57:38 (10892) [INFO] * cpanel-addons-production-feed: 208.74.123.61 * 2026-01-02 01:57:38 (10892) [INFO] * cpanel-plugins: 208.74.123.61 * 2026-01-02 01:57:38 (10892) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2026-01-02 02:00:18 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-02 02:00:18 (10892) [INFO] Trying other mirror. * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2026-01-02 02:00:18 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-02 02:00:18 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-02 02:00:18 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-02 02:00:18 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-02 02:00:18 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-02 02:00:18 (10892) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-02 02:00:18 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-02 02:00:18 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2026-01-02 02:00:18 (10892) [INFO] or * 2026-01-02 02:00:18 (10892) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-02 02:00:18 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-02 02:00:18 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-02 02:00:18 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-02 02:00:18 (10892) [INFO] compromise: * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2026-01-02 02:00:18 (10892) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2026-01-02 02:00:18 (10892) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-02 02:00:18 (10909) [INFO] * 2026-01-02 02:00:18 (6715) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Operation timed out after 30039 milliseconds with 0 out of 0 bytes received') https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-02 02:00:18 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-02 02:00:18 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-02 02:00:18 (10879) [INFO] * 2026-01-02 02:00:18 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-02 02:00:19 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-02 02:00:19 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-02 02:00:19 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-02 02:00:19 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-02 02:00:19 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-02 02:00:19 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-02 02:00:19 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-02 02:00:19 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-02 02:00:19 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-02 02:00:19 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-02 02:00:19 (10892) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-02 02:00:19 (10909) [INFO] * 2026-01-02 02:00:19 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-02 02:00:19 (10879) [INFO] * 2026-01-02 02:00:20 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-02 02:00:20 (10892) [INFO] Determining fastest mirrors * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-02 02:00:51 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-02 02:00:51 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-02 02:00:51 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-02 02:00:51 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-02 02:00:51 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-02 02:00:51 (10892) [INFO] yum --disablerepo= ... * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-02 02:00:51 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-02 02:00:51 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] yum-config-manager --disable * 2026-01-02 02:00:51 (10892) [INFO] or * 2026-01-02 02:00:51 (10892) [INFO] subscription-manager repos --disable= * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-02 02:00:51 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-02 02:00:51 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-02 02:00:51 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-02 02:00:51 (10892) [INFO] compromise: * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-02 02:00:51 (10892) [INFO] * 2026-01-02 02:00:51 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-02 02:00:51 (10909) [INFO] * 2026-01-02 02:00:51 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-02 02:00:51 (6726) [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 * 2026-01-02 02:00:53 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-02 02:00:53 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-02 02:00:53 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-02 02:00:53 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-02 02:00:53 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-02 02:08:47 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QLUS97QOPm/ea_profile.json * 2026-01-02 02:11:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QLUS97QOPm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-02 02:11:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-03 01:40:34 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-03 01:44:35 (11982) [INFO] Script is up to date. * 2026-01-03 01:48:38 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-03 01:48:38 (10879) [INFO] * 2026-01-03 01:49:32 (10909) [INFO] * 2026-01-03 01:49:32 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-03 01:49:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-03 01:49:32 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-03 01:49:32 (10879) [INFO] * 2026-01-03 01:54:19 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-03 01:54:19 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-03 01:54:19 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-03 01:54:19 (10879) [INFO] * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-03 01:54:53 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-03 01:54:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-03 01:54:53 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-03 01:54:53 (10879) [INFO] * 2026-01-03 01:54:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-03 01:54:54 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-03 01:55:25 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-03 01:55:25 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-03 01:55:25 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-03 01:55:25 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-03 01:55:25 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-03 01:55:25 (10892) [INFO] yum --disablerepo= ... * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-03 01:55:25 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-03 01:55:25 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] yum-config-manager --disable * 2026-01-03 01:55:25 (10892) [INFO] or * 2026-01-03 01:55:25 (10892) [INFO] subscription-manager repos --disable= * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-03 01:55:25 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-03 01:55:25 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-03 01:55:25 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-03 01:55:25 (10892) [INFO] compromise: * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-03 01:55:25 (10892) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-03 01:55:25 (10909) [INFO] * 2026-01-03 01:55:25 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-03 01:55:25 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-03 01:55:25 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-03 01:55:25 (10879) [INFO] * 2026-01-03 01:55:25 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-03 01:55:26 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-03 01:55:26 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-03 01:55:26 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-03 01:55:26 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-03 01:55:26 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-03 01:55:26 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-03 01:55:26 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-03 01:55:26 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-03 01:55:26 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-03 01:55:26 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-03 01:55:26 (10892) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-03 01:55:26 (10909) [INFO] * 2026-01-03 01:55:26 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-03 01:55:26 (10879) [INFO] * 2026-01-03 01:55:26 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-03 01:55:27 (10892) [INFO] Determining fastest mirrors * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-03 01:55:58 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-03 01:55:58 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-03 01:55:58 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-03 01:55:58 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-03 01:55:58 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-03 01:55:58 (10892) [INFO] yum --disablerepo= ... * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-03 01:55:58 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-03 01:55:58 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] yum-config-manager --disable * 2026-01-03 01:55:58 (10892) [INFO] or * 2026-01-03 01:55:58 (10892) [INFO] subscription-manager repos --disable= * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-03 01:55:58 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-03 01:55:58 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-03 01:55:58 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-03 01:55:58 (10892) [INFO] compromise: * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-03 01:55:58 (10892) [INFO] * 2026-01-03 01:55:58 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-03 01:55:58 (10909) [INFO] * 2026-01-03 01:55:58 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-03 01:55:58 (6726) [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 * 2026-01-03 01:55:59 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-03 01:55:59 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-03 01:55:59 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-03 01:55:59 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-03 01:55:59 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-03 01:56:07 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kzy4wU6lET/ea_profile.json * 2026-01-03 01:59:05 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kzy4wU6lET/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-03 01:59:05 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-04 01:43:15 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-04 01:47:15 (11982) [INFO] Script is up to date. * 2026-01-04 01:51:19 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-04 01:51:19 (10879) [INFO] * 2026-01-04 01:52:13 (10909) [INFO] * 2026-01-04 01:52:13 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-04 01:52:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-04 01:52:14 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-04 01:52:14 (10879) [INFO] * 2026-01-04 01:52:17 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-04 01:52:17 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-04 01:52:17 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-04 01:52:17 (10879) [INFO] * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-04 01:52:53 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-04 01:52:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-04 01:52:53 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-04 01:52:53 (10879) [INFO] * 2026-01-04 01:52:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-04 01:52:54 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-04 01:53:25 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-04 01:53:25 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-04 01:53:25 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-04 01:53:25 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-04 01:53:25 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-04 01:53:25 (10892) [INFO] yum --disablerepo= ... * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-04 01:53:25 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-04 01:53:25 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] yum-config-manager --disable * 2026-01-04 01:53:25 (10892) [INFO] or * 2026-01-04 01:53:25 (10892) [INFO] subscription-manager repos --disable= * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-04 01:53:25 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-04 01:53:25 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-04 01:53:25 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-04 01:53:25 (10892) [INFO] compromise: * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-04 01:53:25 (10892) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-04 01:53:25 (10909) [INFO] * 2026-01-04 01:53:25 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-04 01:53:25 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-04 01:53:25 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-04 01:53:25 (10879) [INFO] * 2026-01-04 01:53:25 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-04 01:53:26 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-04 01:53:26 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-04 01:53:26 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-04 01:53:26 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-04 01:53:26 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-04 01:53:26 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-04 01:53:26 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-04 01:53:26 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-04 01:53:26 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-04 01:53:26 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-04 01:53:26 (10892) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-04 01:53:26 (10909) [INFO] * 2026-01-04 01:53:26 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-04 01:53:26 (10879) [INFO] * 2026-01-04 01:53:26 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-04 01:53:27 (10892) [INFO] Determining fastest mirrors * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-04 01:53:58 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-04 01:53:58 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-04 01:53:58 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-04 01:53:58 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-04 01:53:58 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-04 01:53:58 (10892) [INFO] yum --disablerepo= ... * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-04 01:53:58 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-04 01:53:58 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] yum-config-manager --disable * 2026-01-04 01:53:58 (10892) [INFO] or * 2026-01-04 01:53:58 (10892) [INFO] subscription-manager repos --disable= * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-04 01:53:58 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-04 01:53:58 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-04 01:53:58 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-04 01:53:58 (10892) [INFO] compromise: * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-04 01:53:58 (10892) [INFO] * 2026-01-04 01:53:58 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-04 01:53:58 (10909) [INFO] * 2026-01-04 01:53:58 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-04 01:53:58 (6726) [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 * 2026-01-04 01:53:59 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-04 01:53:59 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-04 01:53:59 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-04 01:53:59 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-04 01:53:59 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-04 01:54:06 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pm7eW9b3kV/ea_profile.json * 2026-01-04 01:56:34 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/pm7eW9b3kV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-04 01:56:34 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-05 01:44:06 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-05 01:48:07 (11982) [INFO] Script is up to date. * 2026-01-05 01:52:10 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-05 01:52:10 (10879) [INFO] * 2026-01-05 01:53:36 (10909) [INFO] * 2026-01-05 01:53:36 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-05 01:53:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-05 01:53:37 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-05 01:53:37 (10879) [INFO] * 2026-01-05 02:00:41 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-05 02:00:41 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-05 02:00:41 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-05 02:00:41 (10879) [INFO] * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-05 02:06:32 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-05 02:06:32 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-05 02:06:32 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-05 02:06:32 (10879) [INFO] * 2026-01-05 02:06:32 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-05 02:06:33 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-05 02:06:33 (10892) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was * 2026-01-05 02:06:33 (10892) [INFO] 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-05 02:06:33 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-05 02:06:33 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-05 02:06:33 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-05 02:06:33 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-05 02:06:33 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-05 02:06:33 (10892) [INFO] yum --disablerepo= ... * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-05 02:06:33 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-05 02:06:33 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] yum-config-manager --disable * 2026-01-05 02:06:33 (10892) [INFO] or * 2026-01-05 02:06:33 (10892) [INFO] subscription-manager repos --disable= * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-05 02:06:33 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-05 02:06:33 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-05 02:06:33 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-05 02:06:33 (10892) [INFO] compromise: * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-05 02:06:33 (10892) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] Cannot find a valid baseurl for repo: EA4/7/x86_64 * 2026-01-05 02:06:33 (10909) [INFO] * 2026-01-05 02:06:33 (6715) [WARN] Initial run of "yum makecache" failed: Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 find a valid baseurl for repo: EA4/7/x86_64 * 2026-01-05 02:06:33 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-05 02:06:33 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-05 02:06:33 (10879) [INFO] * 2026-01-05 02:06:33 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-05 02:06:34 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-05 02:06:34 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-05 02:06:34 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-05 02:06:34 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-05 02:06:34 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-05 02:06:34 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-05 02:06:34 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-05 02:06:34 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-05 02:06:34 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-05 02:06:34 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-05 02:06:34 (10892) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-05 02:06:34 (10909) [INFO] * 2026-01-05 02:06:34 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-05 02:06:34 (10879) [INFO] * 2026-01-05 02:06:34 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-05 02:06:35 (10892) [INFO] Determining fastest mirrors * 2026-01-05 02:06:35 (10892) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was * 2026-01-05 02:06:35 (10892) [INFO] 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-05 02:06:35 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-05 02:06:35 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-05 02:06:35 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-05 02:06:35 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-05 02:06:35 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-05 02:06:35 (10892) [INFO] yum --disablerepo= ... * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-05 02:06:35 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-05 02:06:35 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] yum-config-manager --disable * 2026-01-05 02:06:35 (10892) [INFO] or * 2026-01-05 02:06:35 (10892) [INFO] subscription-manager repos --disable= * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-05 02:06:35 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-05 02:06:35 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-05 02:06:35 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-05 02:06:35 (10892) [INFO] compromise: * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-05 02:06:35 (10892) [INFO] * 2026-01-05 02:06:35 (10892) [INFO] Cannot find a valid baseurl for repo: EA4/7/x86_64 * 2026-01-05 02:06:35 (10909) [INFO] * 2026-01-05 02:06:35 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-05 02:06:35 (6726) [ERROR] Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by 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 find a valid baseurl for repo: EA4/7/x86_64 * 2026-01-05 02:06:37 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-05 02:06:37 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-05 02:06:37 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-05 02:06:37 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-05 02:06:37 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-06 01:42:26 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-06 01:46:26 (11982) [INFO] Script is up to date. * 2026-01-06 01:50:29 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-06 01:50:29 (10879) [INFO] * 2026-01-06 01:51:54 (10909) [INFO] * 2026-01-06 01:51:54 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-06 01:51:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-06 01:51:55 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-06 01:51:55 (10879) [INFO] * 2026-01-06 01:55:45 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-06 01:55:45 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-06 01:55:45 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-06 01:55:45 (10879) [INFO] * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-06 01:56:21 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-06 01:56:21 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-06 01:56:21 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-06 01:56:21 (10879) [INFO] * 2026-01-06 01:56:22 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-06 01:56:22 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-06 01:56:53 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-06 01:56:53 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-06 01:56:53 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-06 01:56:53 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-06 01:56:53 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-06 01:56:53 (10892) [INFO] yum --disablerepo= ... * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-06 01:56:53 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-06 01:56:53 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] yum-config-manager --disable * 2026-01-06 01:56:53 (10892) [INFO] or * 2026-01-06 01:56:53 (10892) [INFO] subscription-manager repos --disable= * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-06 01:56:53 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-06 01:56:53 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-06 01:56:53 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-06 01:56:53 (10892) [INFO] compromise: * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-06 01:56:53 (10892) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-06 01:56:53 (10909) [INFO] * 2026-01-06 01:56:53 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-06 01:56:53 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-06 01:56:53 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-06 01:56:53 (10879) [INFO] * 2026-01-06 01:56:53 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-06 01:56:54 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-06 01:56:54 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-06 01:56:54 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-06 01:56:54 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-06 01:56:54 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-06 01:56:54 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-06 01:56:54 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-06 01:56:54 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-06 01:56:54 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-06 01:56:54 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-06 01:56:54 (10892) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-06 01:56:54 (10909) [INFO] * 2026-01-06 01:56:54 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-06 01:56:54 (10879) [INFO] * 2026-01-06 01:56:54 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-06 01:56:54 (10892) [INFO] Determining fastest mirrors * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-06 01:57:26 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-06 01:57:26 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-06 01:57:26 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-06 01:57:26 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-06 01:57:26 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-06 01:57:26 (10892) [INFO] yum --disablerepo= ... * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-06 01:57:26 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-06 01:57:26 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] yum-config-manager --disable * 2026-01-06 01:57:26 (10892) [INFO] or * 2026-01-06 01:57:26 (10892) [INFO] subscription-manager repos --disable= * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-06 01:57:26 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-06 01:57:26 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-06 01:57:26 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-06 01:57:26 (10892) [INFO] compromise: * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-06 01:57:26 (10892) [INFO] * 2026-01-06 01:57:26 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-06 01:57:26 (10909) [INFO] * 2026-01-06 01:57:26 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-06 01:57:26 (6726) [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 * 2026-01-06 01:57:28 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-06 01:57:28 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-06 01:57:28 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-06 01:57:28 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-06 01:57:28 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-06 01:57:34 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lEhg7bTHeg/ea_profile.json * 2026-01-06 02:01:48 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lEhg7bTHeg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-06 02:01:48 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-07 01:51:18 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-07 01:55:18 (11982) [INFO] Script is up to date. * 2026-01-07 01:59:21 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-07 01:59:21 (10879) [INFO] * 2026-01-07 02:00:42 (10909) [INFO] * 2026-01-07 02:00:42 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-07 02:00:42 (264) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2026-01-07 02:00:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-07 02:00:42 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-07 02:00:42 (10879) [INFO] * 2026-01-07 02:13:53 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-07 02:13:53 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-07 02:13:53 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-07 02:13:53 (10879) [INFO] * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-07 02:14:28 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-07 02:14:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-07 02:14:28 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-07 02:14:28 (10879) [INFO] * 2026-01-07 02:14:28 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-07 02:14:29 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-07 02:14:59 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-07 02:14:59 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-07 02:14:59 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-07 02:14:59 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-07 02:14:59 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-07 02:14:59 (10892) [INFO] yum --disablerepo= ... * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-07 02:14:59 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-07 02:14:59 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] yum-config-manager --disable * 2026-01-07 02:14:59 (10892) [INFO] or * 2026-01-07 02:14:59 (10892) [INFO] subscription-manager repos --disable= * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-07 02:14:59 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-07 02:14:59 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-07 02:14:59 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-07 02:14:59 (10892) [INFO] compromise: * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-07 02:14:59 (10892) [INFO] * 2026-01-07 02:14:59 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-07 02:14:59 (10909) [INFO] * 2026-01-07 02:14:59 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-07 02:14:59 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-07 02:14:59 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-07 02:14:59 (10879) [INFO] * 2026-01-07 02:15:00 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-07 02:15:00 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-07 02:15:00 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-07 02:15:00 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-07 02:15:00 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-07 02:15:00 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-07 02:15:00 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-07 02:15:00 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-07 02:15:00 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-07 02:15:00 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-07 02:15:00 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-07 02:15:00 (10892) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-07 02:15:00 (10909) [INFO] * 2026-01-07 02:15:00 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-07 02:15:00 (10879) [INFO] * 2026-01-07 02:15:00 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-07 02:15:01 (10892) [INFO] Determining fastest mirrors * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-07 02:15:32 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-07 02:15:32 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-07 02:15:32 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-07 02:15:32 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-07 02:15:32 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-07 02:15:32 (10892) [INFO] yum --disablerepo= ... * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-07 02:15:32 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-07 02:15:32 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] yum-config-manager --disable * 2026-01-07 02:15:32 (10892) [INFO] or * 2026-01-07 02:15:32 (10892) [INFO] subscription-manager repos --disable= * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-07 02:15:32 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-07 02:15:32 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-07 02:15:32 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-07 02:15:32 (10892) [INFO] compromise: * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-07 02:15:32 (10892) [INFO] * 2026-01-07 02:15:32 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-07 02:15:32 (10909) [INFO] * 2026-01-07 02:15:32 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-07 02:15:32 (6726) [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 * 2026-01-07 02:15:33 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-07 02:15:33 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-07 02:15:34 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-07 02:15:34 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-07 02:15:34 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-07 02:15:40 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/204gVnGsfx/ea_profile.json * 2026-01-07 02:18:06 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/204gVnGsfx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-07 02:18:06 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-08 01:42:23 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-08 01:46:24 (11982) [INFO] Script is up to date. * 2026-01-08 01:50:27 (10878) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-08 01:50:27 (10879) [INFO] * 2026-01-08 01:51:47 (10909) [INFO] * 2026-01-08 01:51:47 (7135) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-08 01:51:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-08 01:51:47 (10878) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-08 01:51:47 (10879) [INFO] * 2026-01-08 01:51:51 (4518) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-08 01:51:51 (4525) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-08 01:51:51 (10878) [INFO] Running: /usr/bin/yum list extras * 2026-01-08 01:51:51 (10879) [INFO] * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-08 01:52:28 (6866) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-08 01:52:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-08 01:52:28 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-08 01:52:28 (10879) [INFO] * 2026-01-08 01:52:28 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-08 01:52:29 (10892) [INFO] Loading mirror speeds from cached hostfile * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-08 01:53:00 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-08 01:53:00 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-08 01:53:00 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-08 01:53:00 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-08 01:53:00 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-08 01:53:00 (10892) [INFO] yum --disablerepo= ... * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-08 01:53:00 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-08 01:53:00 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] yum-config-manager --disable * 2026-01-08 01:53:00 (10892) [INFO] or * 2026-01-08 01:53:00 (10892) [INFO] subscription-manager repos --disable= * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-08 01:53:00 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-08 01:53:00 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-08 01:53:00 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-08 01:53:00 (10892) [INFO] compromise: * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-08 01:53:00 (10892) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-08 01:53:00 (10909) [INFO] * 2026-01-08 01:53:00 (6715) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-08 01:53:00 (6716) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-08 01:53:00 (10878) [INFO] Running: /usr/bin/yum clean all * 2026-01-08 01:53:00 (10879) [INFO] * 2026-01-08 01:53:00 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-08 01:53:00 (10892) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-08 01:53:00 (10892) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-08 01:53:00 (10892) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-08 01:53:00 (10892) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-08 01:53:00 (10892) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-08 01:53:00 (10892) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-08 01:53:00 (10892) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-08 01:53:00 (10892) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-08 01:53:00 (10892) [INFO] : wp-toolkit-thirdparties * 2026-01-08 01:53:00 (10892) [INFO] Cleaning up list of fastest mirrors * 2026-01-08 01:53:00 (10892) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-08 01:53:00 (10909) [INFO] * 2026-01-08 01:53:00 (10878) [INFO] Running: /usr/bin/yum makecache * 2026-01-08 01:53:00 (10879) [INFO] * 2026-01-08 01:53:01 (10892) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-08 01:53:01 (10892) [INFO] Determining fastest mirrors * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] One of the configured repositories failed (Unknown), * 2026-01-08 01:53:32 (10892) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-08 01:53:32 (10892) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-08 01:53:32 (10892) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-08 01:53:32 (10892) [INFO] distribution release than is supported by the repository (and the * 2026-01-08 01:53:32 (10892) [INFO] packages for the previous distribution release still work). * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-08 01:53:32 (10892) [INFO] yum --disablerepo= ... * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-08 01:53:32 (10892) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-08 01:53:32 (10892) [INFO] again or use --enablerepo for temporary usage: * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] yum-config-manager --disable * 2026-01-08 01:53:32 (10892) [INFO] or * 2026-01-08 01:53:32 (10892) [INFO] subscription-manager repos --disable= * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-08 01:53:32 (10892) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-08 01:53:32 (10892) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-08 01:53:32 (10892) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-08 01:53:32 (10892) [INFO] compromise: * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-08 01:53:32 (10892) [INFO] * 2026-01-08 01:53:32 (10892) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-08 01:53:32 (10909) [INFO] * 2026-01-08 01:53:32 (6725) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-08 01:53:32 (6726) [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 * 2026-01-08 01:53:33 (3661) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-08 01:53:33 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-08 01:53:33 (4965) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-08 01:53:33 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-08 01:53:33 (2397) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-08 01:53:41 (9988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7Rc1Hz15MP/ea_profile.json * 2026-01-08 01:56:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7Rc1Hz15MP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9990. * 2026-01-08 01:56:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-09 00:39:12 (11960) [INFO] Self-update of script version 76 requested. * 2026-01-09 00:43:12 (11965) [INFO] Newer version of script found. Downloading. * 2026-01-09 00:47:14 (11974) [INFO] Script update to version 77 successful. * 2026-01-09 00:51:17 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-09 00:51:17 (10888) [INFO] * 2026-01-09 00:52:39 (10918) [INFO] * 2026-01-09 00:52:39 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-09 00:52:39 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-09 00:52:39 (10888) [INFO] * 2026-01-09 00:59:42 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-09 00:59:42 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-09 00:59:42 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-09 00:59:42 (10888) [INFO] * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-09 01:00:10 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-09 01:00:10 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-09 01:00:10 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-09 01:00:10 (10888) [INFO] * 2026-01-09 01:00:11 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-09 01:00:11 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-09 01:00:42 (10901) [INFO] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was * 2026-01-09 01:00:42 (10901) [INFO] 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30772 milliseconds') * 2026-01-09 01:00:42 (10901) [INFO] * EA4: 208.74.123.58 * 2026-01-09 01:00:42 (10901) [INFO] * cpanel-addons-production-feed: 208.74.123.58 * 2026-01-09 01:00:42 (10901) [INFO] * cpanel-plugins: 208.74.123.58 * 2026-01-09 01:00:42 (10901) [INFO] * epel: pubmirror1.math.uh.edu * 2026-01-09 01:01:51 (10901) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'timed out before SSL handshake') * 2026-01-09 01:01:51 (10901) [INFO] Trying other mirror. * 2026-01-09 01:02:21 (10901) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') * 2026-01-09 01:02:21 (10901) [INFO] Trying other mirror. * 2026-01-09 01:02:52 (10901) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30777 milliseconds') * 2026-01-09 01:02:52 (10901) [INFO] Trying other mirror. * 2026-01-09 01:03:23 (10901) [INFO] https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') * 2026-01-09 01:03:23 (10901) [INFO] Trying other mirror. * 2026-01-09 01:05:24 (10901) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-09 01:05:24 (10901) [INFO] Trying other mirror. * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), * 2026-01-09 01:05:24 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-09 01:05:24 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-09 01:05:24 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-09 01:05:24 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-09 01:05:24 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-09 01:05:24 (10901) [INFO] yum --disablerepo=imunify360-ea-php-hardened ... * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-09 01:05:24 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-09 01:05:24 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] yum-config-manager --disable imunify360-ea-php-hardened * 2026-01-09 01:05:24 (10901) [INFO] or * 2026-01-09 01:05:24 (10901) [INFO] subscription-manager repos --disable=imunify360-ea-php-hardened * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-09 01:05:24 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-09 01:05:24 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-09 01:05:24 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-09 01:05:24 (10901) [INFO] compromise: * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true * 2026-01-09 01:05:24 (10901) [INFO] * 2026-01-09 01:05:24 (10901) [INFO] failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. * 2026-01-09 01:05:24 (10901) [INFO] https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-09 01:05:24 (10918) [INFO] * 2026-01-09 01:05:24 (6724) [WARN] Initial run of "yum makecache" failed: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=stock&content=centos: (28, 'Connection timed out after 30772 milliseconds') https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'timed out before SSL handshake') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30769 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30777 milliseconds') Trying other mirror. https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://vault.centos.org/7.9.2009/os/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30533 milliseconds') Trying other mirror. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU%3D/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized Trying other mirror. One of the configured repositories failed (Imunify360 ea-php Hardened repository for CentOS 7 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=imunify360-ea-php-hardened ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable imunify360-ea-php-hardened or subscription-manager repos --disable=imunify360-ea-php-hardened 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=imunify360-ea-php-hardened.skip_if_unavailable=true failure: repodata/repomd.xml from imunify360-ea-php-hardened: [Errno 256] No more mirrors to try. https://repo.alt.cloudlinux.com/el/U1NKZXZRRlh1NDNDMGdVSjpvazo6MjE0NzQ4MzY0NzoxNzY2ODI2MTc3OjE3NjcwODUzNzc6FOMZ5i_KdLAXwVFNEFGUKpDMA7VmNqaLYmunMhdBGoEwIUPAKrktZH2rdwk-NLy3CeG9y9kJs7CGr6uOuflP747j9zBNpBmUB70Oh6-PwwdKKAwZQerl2NM0UnnIEdDU9CaRUa8EzUyFRhlHc9SA8EwnOL8p056EQ6bTcYgkRJv5n5VvLHOvlN0z710t0KuGqPgjwAAmtpfxvLLfYHiaTdOoK8kDQacGu03nYYD5YwP1gsgosSjNGknMQ9KqUPB7g_-D7wbMOlq_0cGfci2UlCgd5n0NT3duTZLe4WSMowMNK1GFMeiFhhDA9fAAB1MziaWaG7VH_5y89a--gqGzGTC4V3wTTUqTiwmmqWXSvYXxZB_TSbK3JQfYjMIwFO82ccIGPnLPN08qbt1xZN7uleaEHWp-hzBcV98UZyJ9wRrpI0mdLvqbrm-T_93w6bvHkOfxNTi-e1Ke-vmaligyeUwUX99600-yEtCklSJL4EE2NrO0LbVZfZmsk-4uXkKWDhLcSpNNChYqoZV7Z6q0TLwlPTydixJFptvJboCxRIxqPT8A8MtATAmWy7-7eCHv83CZJ5Ef6xC4dzjbEbjlQOKXgNvpDkYsqvlUzEIJEXlfFQah81VLn-BW24voOnD6F14fmr3ss1AmlpHcEBSKKEU8rb--zWxIhWyvP_A5UdU=/ea-php/7/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized * 2026-01-09 01:05:24 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-09 01:05:24 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-09 01:05:24 (10888) [INFO] * 2026-01-09 01:05:25 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-09 01:05:25 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-09 01:05:25 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-09 01:05:25 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-09 01:05:25 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-09 01:05:25 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-09 01:05:25 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-09 01:05:25 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-09 01:05:25 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-09 01:05:25 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-09 01:05:25 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-09 01:05:25 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-09 01:05:25 (10918) [INFO] * 2026-01-09 01:05:25 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-09 01:05:25 (10888) [INFO] * 2026-01-09 01:05:26 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-09 01:05:26 (10901) [INFO] Determining fastest mirrors * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-09 01:05:57 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-09 01:05:57 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-09 01:05:57 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-09 01:05:57 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-09 01:05:57 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-09 01:05:57 (10901) [INFO] yum --disablerepo= ... * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-09 01:05:57 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-09 01:05:57 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] yum-config-manager --disable * 2026-01-09 01:05:57 (10901) [INFO] or * 2026-01-09 01:05:57 (10901) [INFO] subscription-manager repos --disable= * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-09 01:05:57 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-09 01:05:57 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-09 01:05:57 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-09 01:05:57 (10901) [INFO] compromise: * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-09 01:05:57 (10901) [INFO] * 2026-01-09 01:05:57 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-09 01:05:57 (10918) [INFO] * 2026-01-09 01:05:57 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-09 01:05:57 (6735) [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 * 2026-01-09 01:05:59 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-09 01:05:59 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-09 01:05:59 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-09 01:05:59 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-09 01:05:59 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-10 01:43:00 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-10 01:47:00 (11991) [INFO] Script is up to date. * 2026-01-10 01:51:03 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-10 01:51:03 (10888) [INFO] * 2026-01-10 01:51:58 (10918) [INFO] * 2026-01-10 01:51:58 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-10 01:51:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-10 01:51:58 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-10 01:51:58 (10888) [INFO] * 2026-01-10 01:57:04 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-10 01:57:04 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-10 01:57:04 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-10 01:57:04 (10888) [INFO] * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-10 01:57:40 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-10 01:57:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-10 01:57:40 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-10 01:57:40 (10888) [INFO] * 2026-01-10 01:57:40 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-10 01:57:40 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-10 01:58:11 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-10 01:58:11 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-10 01:58:11 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-10 01:58:11 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-10 01:58:11 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-10 01:58:11 (10901) [INFO] yum --disablerepo= ... * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-10 01:58:11 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-10 01:58:11 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] yum-config-manager --disable * 2026-01-10 01:58:11 (10901) [INFO] or * 2026-01-10 01:58:11 (10901) [INFO] subscription-manager repos --disable= * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-10 01:58:11 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-10 01:58:11 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-10 01:58:11 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-10 01:58:11 (10901) [INFO] compromise: * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-10 01:58:11 (10901) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-10 01:58:11 (10918) [INFO] * 2026-01-10 01:58:11 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-10 01:58:11 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-10 01:58:11 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-10 01:58:11 (10888) [INFO] * 2026-01-10 01:58:11 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-10 01:58:12 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-10 01:58:12 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-10 01:58:12 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-10 01:58:12 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-10 01:58:12 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-10 01:58:12 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-10 01:58:12 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-10 01:58:12 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-10 01:58:12 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-10 01:58:12 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-10 01:58:12 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-10 01:58:12 (10918) [INFO] * 2026-01-10 01:58:12 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-10 01:58:12 (10888) [INFO] * 2026-01-10 01:58:12 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-10 01:58:13 (10901) [INFO] Determining fastest mirrors * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-10 01:58:44 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-10 01:58:44 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-10 01:58:44 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-10 01:58:44 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-10 01:58:44 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-10 01:58:44 (10901) [INFO] yum --disablerepo= ... * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-10 01:58:44 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-10 01:58:44 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] yum-config-manager --disable * 2026-01-10 01:58:44 (10901) [INFO] or * 2026-01-10 01:58:44 (10901) [INFO] subscription-manager repos --disable= * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-10 01:58:44 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-10 01:58:44 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-10 01:58:44 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-10 01:58:44 (10901) [INFO] compromise: * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-10 01:58:44 (10901) [INFO] * 2026-01-10 01:58:44 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-10 01:58:44 (10918) [INFO] * 2026-01-10 01:58:44 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-10 01:58:44 (6735) [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 * 2026-01-10 01:58:46 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-10 01:58:46 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-10 01:58:46 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-10 01:58:46 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-10 01:58:46 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-10 01:58:52 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/92nD_wVGEi/ea_profile.json * 2026-01-10 02:02:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/92nD_wVGEi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-10 02:02:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-11 01:43:40 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-11 01:47:41 (11991) [INFO] Script is up to date. * 2026-01-11 01:51:43 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-11 01:51:43 (10888) [INFO] * 2026-01-11 01:52:36 (10918) [INFO] * 2026-01-11 01:52:36 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-11 01:52:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-11 01:52:36 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-11 01:52:36 (10888) [INFO] * 2026-01-11 01:59:38 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-11 01:59:38 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-11 01:59:38 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-11 01:59:38 (10888) [INFO] * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-11 02:00:13 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-11 02:00:13 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-11 02:00:13 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-11 02:00:13 (10888) [INFO] * 2026-01-11 02:00:14 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-11 02:00:14 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-11 02:00:44 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-11 02:00:44 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-11 02:00:44 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-11 02:00:44 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-11 02:00:44 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-11 02:00:44 (10901) [INFO] yum --disablerepo= ... * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-11 02:00:44 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-11 02:00:44 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] yum-config-manager --disable * 2026-01-11 02:00:44 (10901) [INFO] or * 2026-01-11 02:00:44 (10901) [INFO] subscription-manager repos --disable= * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-11 02:00:44 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-11 02:00:44 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-11 02:00:44 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-11 02:00:44 (10901) [INFO] compromise: * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-11 02:00:44 (10901) [INFO] * 2026-01-11 02:00:44 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-11 02:00:44 (10918) [INFO] * 2026-01-11 02:00:44 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-11 02:00:44 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-11 02:00:44 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-11 02:00:44 (10888) [INFO] * 2026-01-11 02:00:45 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-11 02:00:45 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-11 02:00:45 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-11 02:00:45 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-11 02:00:45 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-11 02:00:45 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-11 02:00:45 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-11 02:00:45 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-11 02:00:45 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-11 02:00:45 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-11 02:00:45 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-11 02:00:45 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-11 02:00:45 (10918) [INFO] * 2026-01-11 02:00:45 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-11 02:00:45 (10888) [INFO] * 2026-01-11 02:00:46 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-11 02:00:46 (10901) [INFO] Determining fastest mirrors * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-11 02:01:17 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-11 02:01:17 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-11 02:01:17 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-11 02:01:17 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-11 02:01:17 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-11 02:01:17 (10901) [INFO] yum --disablerepo= ... * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-11 02:01:17 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-11 02:01:17 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] yum-config-manager --disable * 2026-01-11 02:01:17 (10901) [INFO] or * 2026-01-11 02:01:17 (10901) [INFO] subscription-manager repos --disable= * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-11 02:01:17 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-11 02:01:17 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-11 02:01:17 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-11 02:01:17 (10901) [INFO] compromise: * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-11 02:01:17 (10901) [INFO] * 2026-01-11 02:01:17 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-11 02:01:17 (10918) [INFO] * 2026-01-11 02:01:17 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-11 02:01:17 (6735) [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 * 2026-01-11 02:01:19 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-11 02:01:19 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-11 02:01:19 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-11 02:01:19 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-11 02:01:19 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-11 02:01:24 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6T2URUvZt6/ea_profile.json * 2026-01-11 02:04:23 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6T2URUvZt6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-11 02:04:23 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-12 01:38:37 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-12 01:42:38 (11991) [INFO] Script is up to date. * 2026-01-12 01:46:41 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-12 01:46:41 (10888) [INFO] * 2026-01-12 01:47:57 (10918) [INFO] * 2026-01-12 01:47:57 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-12 01:47:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-12 01:47:58 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-12 01:47:58 (10888) [INFO] * 2026-01-12 01:48:01 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-12 01:48:01 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-12 01:48:01 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-12 01:48:01 (10888) [INFO] * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-12 01:48:37 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-12 01:48:37 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-12 01:48:37 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-12 01:48:37 (10888) [INFO] * 2026-01-12 01:48:37 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-12 01:48:38 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-12 01:49:09 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-12 01:49:09 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-12 01:49:09 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-12 01:49:09 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-12 01:49:09 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-12 01:49:09 (10901) [INFO] yum --disablerepo= ... * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-12 01:49:09 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-12 01:49:09 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] yum-config-manager --disable * 2026-01-12 01:49:09 (10901) [INFO] or * 2026-01-12 01:49:09 (10901) [INFO] subscription-manager repos --disable= * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-12 01:49:09 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-12 01:49:09 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-12 01:49:09 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-12 01:49:09 (10901) [INFO] compromise: * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-12 01:49:09 (10901) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-12 01:49:09 (10918) [INFO] * 2026-01-12 01:49:09 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-12 01:49:09 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-12 01:49:09 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-12 01:49:09 (10888) [INFO] * 2026-01-12 01:49:09 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-12 01:49:10 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-12 01:49:10 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-12 01:49:10 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-12 01:49:10 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-12 01:49:10 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-12 01:49:10 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-12 01:49:10 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-12 01:49:10 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-12 01:49:10 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-12 01:49:10 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-12 01:49:10 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-12 01:49:10 (10918) [INFO] * 2026-01-12 01:49:10 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-12 01:49:10 (10888) [INFO] * 2026-01-12 01:49:10 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-12 01:49:11 (10901) [INFO] Determining fastest mirrors * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-12 01:49:42 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-12 01:49:42 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-12 01:49:42 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-12 01:49:42 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-12 01:49:42 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-12 01:49:42 (10901) [INFO] yum --disablerepo= ... * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-12 01:49:42 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-12 01:49:42 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] yum-config-manager --disable * 2026-01-12 01:49:42 (10901) [INFO] or * 2026-01-12 01:49:42 (10901) [INFO] subscription-manager repos --disable= * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-12 01:49:42 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-12 01:49:42 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-12 01:49:42 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-12 01:49:42 (10901) [INFO] compromise: * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-12 01:49:42 (10901) [INFO] * 2026-01-12 01:49:42 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-12 01:49:42 (10918) [INFO] * 2026-01-12 01:49:42 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-12 01:49:42 (6735) [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 * 2026-01-12 01:49:43 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-12 01:49:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-12 01:49:43 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-12 01:49:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-12 01:49:43 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-12 01:49:50 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OOPogw6E98/ea_profile.json * 2026-01-12 01:52:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OOPogw6E98/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-12 01:52:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-13 02:17:28 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-13 02:21:28 (11991) [INFO] Script is up to date. * 2026-01-13 02:25:31 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-13 02:25:31 (10888) [INFO] * 2026-01-13 02:26:39 (10918) [INFO] * 2026-01-13 02:26:39 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-13 02:26:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-13 02:26:39 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-13 02:26:39 (10888) [INFO] * 2026-01-13 02:26:43 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-13 02:26:43 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-13 02:26:43 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-13 02:26:43 (10888) [INFO] * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-13 02:27:17 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-13 02:27:17 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-13 02:27:17 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-13 02:27:17 (10888) [INFO] * 2026-01-13 02:27:17 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-13 02:27:17 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-13 02:27:48 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-13 02:27:48 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-13 02:27:48 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-13 02:27:48 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-13 02:27:48 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-13 02:27:48 (10901) [INFO] yum --disablerepo= ... * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-13 02:27:48 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-13 02:27:48 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] yum-config-manager --disable * 2026-01-13 02:27:48 (10901) [INFO] or * 2026-01-13 02:27:48 (10901) [INFO] subscription-manager repos --disable= * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-13 02:27:48 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-13 02:27:48 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-13 02:27:48 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-13 02:27:48 (10901) [INFO] compromise: * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-13 02:27:48 (10901) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-13 02:27:48 (10918) [INFO] * 2026-01-13 02:27:48 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-13 02:27:48 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-13 02:27:48 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-13 02:27:48 (10888) [INFO] * 2026-01-13 02:27:48 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-13 02:27:49 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-13 02:27:49 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-13 02:27:49 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-13 02:27:49 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-13 02:27:49 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-13 02:27:49 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-13 02:27:49 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-13 02:27:49 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-13 02:27:49 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-13 02:27:49 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-13 02:27:49 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-13 02:27:49 (10918) [INFO] * 2026-01-13 02:27:49 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-13 02:27:49 (10888) [INFO] * 2026-01-13 02:27:49 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-13 02:27:50 (10901) [INFO] Determining fastest mirrors * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-13 02:28:21 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-13 02:28:21 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-13 02:28:21 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-13 02:28:21 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-13 02:28:21 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-13 02:28:21 (10901) [INFO] yum --disablerepo= ... * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-13 02:28:21 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-13 02:28:21 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] yum-config-manager --disable * 2026-01-13 02:28:21 (10901) [INFO] or * 2026-01-13 02:28:21 (10901) [INFO] subscription-manager repos --disable= * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-13 02:28:21 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-13 02:28:21 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-13 02:28:21 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-13 02:28:21 (10901) [INFO] compromise: * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-13 02:28:21 (10901) [INFO] * 2026-01-13 02:28:21 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-13 02:28:21 (10918) [INFO] * 2026-01-13 02:28:21 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-13 02:28:21 (6735) [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 * 2026-01-13 02:28:22 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-13 02:28:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-13 02:28:22 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-13 02:28:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-13 02:28:22 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-13 02:28:29 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/X7y4YgdPCX/ea_profile.json * 2026-01-13 02:31:27 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/X7y4YgdPCX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-13 02:31:27 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-14 01:49:20 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-14 01:53:21 (11991) [INFO] Script is up to date. * 2026-01-14 01:57:24 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-14 01:57:24 (10888) [INFO] * 2026-01-14 01:58:40 (10918) [INFO] * 2026-01-14 01:58:40 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-14 01:58:40 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-14 01:58:40 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-14 01:58:40 (10888) [INFO] * 2026-01-14 02:05:42 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-14 02:05:42 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-14 02:05:42 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-14 02:05:42 (10888) [INFO] * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-14 02:06:18 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-14 02:06:18 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-14 02:06:18 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-14 02:06:18 (10888) [INFO] * 2026-01-14 02:06:19 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-14 02:06:19 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-14 02:06:50 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-14 02:06:50 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-14 02:06:50 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-14 02:06:50 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-14 02:06:50 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-14 02:06:50 (10901) [INFO] yum --disablerepo= ... * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-14 02:06:50 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-14 02:06:50 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] yum-config-manager --disable * 2026-01-14 02:06:50 (10901) [INFO] or * 2026-01-14 02:06:50 (10901) [INFO] subscription-manager repos --disable= * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-14 02:06:50 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-14 02:06:50 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-14 02:06:50 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-14 02:06:50 (10901) [INFO] compromise: * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-14 02:06:50 (10901) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-14 02:06:50 (10918) [INFO] * 2026-01-14 02:06:50 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-14 02:06:50 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-14 02:06:50 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-14 02:06:50 (10888) [INFO] * 2026-01-14 02:06:50 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-14 02:06:51 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-14 02:06:51 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-14 02:06:51 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-14 02:06:51 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-14 02:06:51 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-14 02:06:51 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-14 02:06:51 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-14 02:06:51 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-14 02:06:51 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-14 02:06:51 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-14 02:06:51 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-14 02:06:51 (10918) [INFO] * 2026-01-14 02:06:51 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-14 02:06:51 (10888) [INFO] * 2026-01-14 02:06:51 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-14 02:06:51 (10901) [INFO] Determining fastest mirrors * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-14 02:07:23 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-14 02:07:23 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-14 02:07:23 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-14 02:07:23 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-14 02:07:23 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-14 02:07:23 (10901) [INFO] yum --disablerepo= ... * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-14 02:07:23 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-14 02:07:23 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] yum-config-manager --disable * 2026-01-14 02:07:23 (10901) [INFO] or * 2026-01-14 02:07:23 (10901) [INFO] subscription-manager repos --disable= * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-14 02:07:23 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-14 02:07:23 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-14 02:07:23 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-14 02:07:23 (10901) [INFO] compromise: * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-14 02:07:23 (10901) [INFO] * 2026-01-14 02:07:23 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-14 02:07:23 (10918) [INFO] * 2026-01-14 02:07:23 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-14 02:07:23 (6735) [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 * 2026-01-14 02:07:24 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-14 02:07:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-14 02:07:24 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-14 02:07:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-14 02:07:24 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-14 02:07:30 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/E372BP_Ysk/ea_profile.json * 2026-01-14 02:17:56 (10020) [INFO] Backed up EA4 profile to /tmp/E372BP_Ysk/ea_profile.json * 2026-01-14 02:17:57 (264) [ERROR] *** Elevation Blocker detected: *** One or more EasyApache 4 package(s) are not compatible with AlmaLinux 8. Please remove these packages before continuing the update. - alt-common-release - alt-curl - alt-curlssl11 - alt-freetds - alt-freetds11 - alt-hyperscanpd - alt-libcurlssl - alt-libcurlssl11 - alt-libicu - alt-libidn2 - alt-libssh2 - alt-libssh211 - alt-libwebp - alt-openldap11 - alt-pcre2 - alt-php-config - alt-php-hyperscan - alt-php-internal - alt-php-internal-cli - alt-php-internal-common - alt-php-internal-intl - alt-php-internal-mbstring - alt-php-internal-mysqlnd - alt-php-internal-pdo - alt-php-internal-process - alt-python-internal - alt-python-internal-libs - alt-python-internal-pip-wheel - alt-python-internal-setuptools-wheel - alt-python311 - alt-python311-libs - alt-python311-pip-wheel - alt-python311-setuptools-wheel - alt-python35 - alt-python35-PyYAML - alt-python35-aiohttp - alt-python35-async-timeout - alt-python35-attrs - alt-python35-cached-property - alt-python35-cerberus - alt-python35-certifi - alt-python35-chardet - alt-python35-click - alt-python35-daemon - alt-python35-funcsigs - alt-python35-humanize - alt-python35-idna - alt-python35-idna-ssl - alt-python35-libs - alt-python35-lockfile - alt-python35-mock - alt-python35-multidict - alt-python35-pam - alt-python35-pbr - alt-python35-peewee - alt-python35-peewee-migrate - alt-python35-pip - alt-python35-psutil - alt-python35-pyjwt - alt-python35-pysocks - alt-python35-sentry-sdk - alt-python35-setuptools - alt-python35-six - alt-python35-urllib3 - alt-python35-yarl - alt-python38 - alt-python38-PyYAML - alt-python38-aiodns - alt-python38-aiohttp - alt-python38-async-lru - alt-python38-async-timeout - alt-python38-attrs - alt-python38-blinker - alt-python38-cached-property - alt-python38-cerberus - alt-python38-certifi - alt-python38-cffi - alt-python38-chardet - alt-python38-click - alt-python38-daemon - alt-python38-distro - alt-python38-funcsigs - alt-python38-humanize - alt-python38-idna - alt-python38-libs - alt-python38-lockfile - alt-python38-mock - alt-python38-multidict - alt-python38-pam - alt-python38-pbr - alt-python38-peewee - alt-python38-peewee-migrate - alt-python38-pip-wheel - alt-python38-ply - alt-python38-psutil - alt-python38-pycares - alt-python38-pycparser - alt-python38-pyjwt - alt-python38-pysocks - alt-python38-sdnotify - alt-python38-sentry-sdk - alt-python38-setuptools - alt-python38-setuptools-wheel - alt-python38-six - alt-python38-typing-extensions - alt-python38-urllib3 - alt-python38-yarl - alt-sqlite - alt-t1lib - ea-ruby24-ruby - ea-ruby24-ruby-devel - ea-ruby24-ruby-irb - ea-ruby24-ruby-libs - ea-ruby24-rubygem-bigdecimal - ea-ruby24-rubygem-did-you-mean - ea-ruby24-rubygem-io-console - ea-ruby24-rubygem-json - ea-ruby24-rubygem-openssl - ea-ruby24-rubygem-psych - ea-ruby24-rubygem-rdoc - ea-ruby24-rubygems * 2026-01-14 02:18:30 (703) [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. * 2026-01-14 02:18:30 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-15 01:53:29 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-15 01:57:29 (11991) [INFO] Script is up to date. * 2026-01-15 02:01:32 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-15 02:01:32 (10888) [INFO] * 2026-01-15 02:02:51 (10918) [INFO] * 2026-01-15 02:02:51 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-15 02:02:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-15 02:02:52 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-15 02:02:52 (10888) [INFO] * 2026-01-15 02:10:01 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-15 02:10:01 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-15 02:10:01 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-15 02:10:01 (10888) [INFO] * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-15 02:10:34 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-15 02:10:34 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-15 02:10:34 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-15 02:10:34 (10888) [INFO] * 2026-01-15 02:10:35 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-15 02:10:35 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-15 02:11:07 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-15 02:11:07 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-15 02:11:07 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-15 02:11:07 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-15 02:11:07 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-15 02:11:07 (10901) [INFO] yum --disablerepo= ... * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-15 02:11:07 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-15 02:11:07 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] yum-config-manager --disable * 2026-01-15 02:11:07 (10901) [INFO] or * 2026-01-15 02:11:07 (10901) [INFO] subscription-manager repos --disable= * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-15 02:11:07 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-15 02:11:07 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-15 02:11:07 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-15 02:11:07 (10901) [INFO] compromise: * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-15 02:11:07 (10901) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-15 02:11:07 (10918) [INFO] * 2026-01-15 02:11:07 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-15 02:11:07 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-15 02:11:07 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-15 02:11:07 (10888) [INFO] * 2026-01-15 02:11:07 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-15 02:11:08 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-15 02:11:08 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-15 02:11:08 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-15 02:11:08 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-15 02:11:08 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-15 02:11:08 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-15 02:11:08 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-15 02:11:08 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-15 02:11:08 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-15 02:11:08 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-15 02:11:08 (10901) [INFO] Other repos take up 984 k of disk space (use --verbose for details) * 2026-01-15 02:11:08 (10918) [INFO] * 2026-01-15 02:11:08 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-15 02:11:08 (10888) [INFO] * 2026-01-15 02:11:08 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-15 02:11:08 (10901) [INFO] Determining fastest mirrors * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-15 02:11:39 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-15 02:11:39 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-15 02:11:39 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-15 02:11:39 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-15 02:11:39 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-15 02:11:39 (10901) [INFO] yum --disablerepo= ... * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-15 02:11:39 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-15 02:11:39 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] yum-config-manager --disable * 2026-01-15 02:11:39 (10901) [INFO] or * 2026-01-15 02:11:39 (10901) [INFO] subscription-manager repos --disable= * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-15 02:11:39 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-15 02:11:39 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-15 02:11:39 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-15 02:11:39 (10901) [INFO] compromise: * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-15 02:11:39 (10901) [INFO] * 2026-01-15 02:11:39 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-15 02:11:39 (10918) [INFO] * 2026-01-15 02:11:39 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-15 02:11:39 (6735) [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 * 2026-01-15 02:11:40 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-15 02:11:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-15 02:11:40 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-15 02:11:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-15 02:11:40 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-15 02:11:47 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ibFndq8BMV/ea_profile.json * 2026-01-15 02:14:45 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ibFndq8BMV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-15 02:14:45 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-16 01:44:05 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-16 01:48:05 (11991) [INFO] Script is up to date. * 2026-01-16 01:52:09 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-16 01:52:09 (10888) [INFO] * 2026-01-16 01:53:22 (10918) [INFO] * 2026-01-16 01:53:22 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-16 01:53:22 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-16 01:53:22 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-16 01:53:22 (10888) [INFO] * 2026-01-16 02:00:26 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-16 02:00:26 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-16 02:00:26 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-16 02:00:26 (10888) [INFO] * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-16 02:01:01 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-16 02:01:01 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-16 02:01:01 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-16 02:01:01 (10888) [INFO] * 2026-01-16 02:01:01 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-16 02:01:02 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-16 02:01:33 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-16 02:01:33 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-16 02:01:33 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-16 02:01:33 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-16 02:01:33 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-16 02:01:33 (10901) [INFO] yum --disablerepo= ... * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-16 02:01:33 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-16 02:01:33 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] yum-config-manager --disable * 2026-01-16 02:01:33 (10901) [INFO] or * 2026-01-16 02:01:33 (10901) [INFO] subscription-manager repos --disable= * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-16 02:01:33 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-16 02:01:33 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-16 02:01:33 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-16 02:01:33 (10901) [INFO] compromise: * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-16 02:01:33 (10901) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-16 02:01:33 (10918) [INFO] * 2026-01-16 02:01:33 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-16 02:01:33 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-16 02:01:33 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-16 02:01:33 (10888) [INFO] * 2026-01-16 02:01:33 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-16 02:01:34 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-16 02:01:34 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-16 02:01:34 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-16 02:01:34 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-16 02:01:34 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-16 02:01:34 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-16 02:01:34 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-16 02:01:34 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-16 02:01:34 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-16 02:01:34 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-16 02:01:34 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-16 02:01:34 (10918) [INFO] * 2026-01-16 02:01:34 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-16 02:01:34 (10888) [INFO] * 2026-01-16 02:01:34 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-16 02:01:35 (10901) [INFO] Determining fastest mirrors * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-16 02:02:05 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-16 02:02:05 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-16 02:02:05 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-16 02:02:05 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-16 02:02:05 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-16 02:02:05 (10901) [INFO] yum --disablerepo= ... * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-16 02:02:05 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-16 02:02:05 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] yum-config-manager --disable * 2026-01-16 02:02:05 (10901) [INFO] or * 2026-01-16 02:02:05 (10901) [INFO] subscription-manager repos --disable= * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-16 02:02:05 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-16 02:02:05 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-16 02:02:05 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-16 02:02:05 (10901) [INFO] compromise: * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-16 02:02:05 (10901) [INFO] * 2026-01-16 02:02:05 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-16 02:02:05 (10918) [INFO] * 2026-01-16 02:02:05 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-16 02:02:05 (6735) [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 * 2026-01-16 02:02:06 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-16 02:02:06 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-16 02:02:06 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-16 02:02:06 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-16 02:02:06 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-16 02:02:12 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4OufQ4wV8D/ea_profile.json * 2026-01-16 02:04:39 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4OufQ4wV8D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-16 02:04:39 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-17 01:45:40 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-17 01:49:40 (11991) [INFO] Script is up to date. * 2026-01-17 01:53:43 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-17 01:53:43 (10888) [INFO] * 2026-01-17 01:54:36 (10918) [INFO] * 2026-01-17 01:54:36 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-17 01:54:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-17 01:54:36 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-17 01:54:36 (10888) [INFO] * 2026-01-17 02:01:39 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-17 02:01:39 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-17 02:01:39 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-17 02:01:39 (10888) [INFO] * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-17 02:02:15 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-17 02:02:15 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-17 02:02:15 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-17 02:02:15 (10888) [INFO] * 2026-01-17 02:02:16 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-17 02:02:16 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-17 02:02:47 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-17 02:02:47 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-17 02:02:47 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-17 02:02:47 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-17 02:02:47 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-17 02:02:47 (10901) [INFO] yum --disablerepo= ... * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-17 02:02:47 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-17 02:02:47 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] yum-config-manager --disable * 2026-01-17 02:02:47 (10901) [INFO] or * 2026-01-17 02:02:47 (10901) [INFO] subscription-manager repos --disable= * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-17 02:02:47 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-17 02:02:47 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-17 02:02:47 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-17 02:02:47 (10901) [INFO] compromise: * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-17 02:02:47 (10901) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-17 02:02:47 (10918) [INFO] * 2026-01-17 02:02:47 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-17 02:02:47 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-17 02:02:47 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-17 02:02:47 (10888) [INFO] * 2026-01-17 02:02:47 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-17 02:02:48 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-17 02:02:48 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-17 02:02:48 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-17 02:02:48 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-17 02:02:48 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-17 02:02:48 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-17 02:02:48 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-17 02:02:48 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-17 02:02:48 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-17 02:02:48 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-17 02:02:48 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-17 02:02:48 (10918) [INFO] * 2026-01-17 02:02:48 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-17 02:02:48 (10888) [INFO] * 2026-01-17 02:02:48 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-17 02:02:49 (10901) [INFO] Determining fastest mirrors * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-17 02:03:20 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-17 02:03:20 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-17 02:03:20 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-17 02:03:20 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-17 02:03:20 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-17 02:03:20 (10901) [INFO] yum --disablerepo= ... * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-17 02:03:20 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-17 02:03:20 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] yum-config-manager --disable * 2026-01-17 02:03:20 (10901) [INFO] or * 2026-01-17 02:03:20 (10901) [INFO] subscription-manager repos --disable= * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-17 02:03:20 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-17 02:03:20 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-17 02:03:20 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-17 02:03:20 (10901) [INFO] compromise: * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-17 02:03:20 (10901) [INFO] * 2026-01-17 02:03:20 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-17 02:03:20 (10918) [INFO] * 2026-01-17 02:03:20 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-17 02:03:20 (6735) [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 * 2026-01-17 02:03:22 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-17 02:03:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-17 02:03:22 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-17 02:03:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-17 02:03:22 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-17 02:03:29 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wKlbAAlJrG/ea_profile.json * 2026-01-17 02:05:56 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wKlbAAlJrG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-17 02:05:56 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-18 01:40:21 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-18 01:44:21 (11991) [INFO] Script is up to date. * 2026-01-18 01:48:24 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-18 01:48:24 (10888) [INFO] * 2026-01-18 01:49:12 (10918) [INFO] * 2026-01-18 01:49:12 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-18 01:49:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-18 01:49:12 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-18 01:49:12 (10888) [INFO] * 2026-01-18 01:59:40 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-18 01:59:40 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-18 01:59:40 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-18 01:59:40 (10888) [INFO] * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-18 02:00:16 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-18 02:00:16 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-18 02:00:16 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-18 02:00:16 (10888) [INFO] * 2026-01-18 02:00:16 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-18 02:00:17 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-18 02:00:48 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-18 02:00:48 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-18 02:00:48 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-18 02:00:48 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-18 02:00:48 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-18 02:00:48 (10901) [INFO] yum --disablerepo= ... * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-18 02:00:48 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-18 02:00:48 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] yum-config-manager --disable * 2026-01-18 02:00:48 (10901) [INFO] or * 2026-01-18 02:00:48 (10901) [INFO] subscription-manager repos --disable= * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-18 02:00:48 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-18 02:00:48 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-18 02:00:48 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-18 02:00:48 (10901) [INFO] compromise: * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-18 02:00:48 (10901) [INFO] * 2026-01-18 02:00:48 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-18 02:00:48 (10918) [INFO] * 2026-01-18 02:00:48 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-18 02:00:48 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-18 02:00:48 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-18 02:00:48 (10888) [INFO] * 2026-01-18 02:00:49 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-18 02:00:49 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-18 02:00:49 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-18 02:00:49 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-18 02:00:49 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-18 02:00:49 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-18 02:00:49 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-18 02:00:49 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-18 02:00:49 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-18 02:00:49 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-18 02:00:49 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-18 02:00:49 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-18 02:00:49 (10918) [INFO] * 2026-01-18 02:00:49 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-18 02:00:49 (10888) [INFO] * 2026-01-18 02:00:49 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-18 02:00:50 (10901) [INFO] Determining fastest mirrors * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-18 02:01:21 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-18 02:01:21 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-18 02:01:21 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-18 02:01:21 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-18 02:01:21 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-18 02:01:21 (10901) [INFO] yum --disablerepo= ... * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-18 02:01:21 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-18 02:01:21 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] yum-config-manager --disable * 2026-01-18 02:01:21 (10901) [INFO] or * 2026-01-18 02:01:21 (10901) [INFO] subscription-manager repos --disable= * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-18 02:01:21 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-18 02:01:21 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-18 02:01:21 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-18 02:01:21 (10901) [INFO] compromise: * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-18 02:01:21 (10901) [INFO] * 2026-01-18 02:01:21 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-18 02:01:21 (10918) [INFO] * 2026-01-18 02:01:21 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-18 02:01:21 (6735) [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 * 2026-01-18 02:01:23 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-18 02:01:23 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-18 02:01:23 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-18 02:01:23 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-18 02:01:23 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-18 02:01:30 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ajT3YwrsPO/ea_profile.json * 2026-01-18 02:04:28 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ajT3YwrsPO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-18 02:04:28 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-19 01:38:42 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-19 01:42:42 (11991) [INFO] Script is up to date. * 2026-01-19 01:46:46 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-19 01:46:46 (10888) [INFO] * 2026-01-19 01:48:05 (10918) [INFO] * 2026-01-19 01:48:05 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-19 01:48:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-19 01:48:06 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-19 01:48:06 (10888) [INFO] * 2026-01-19 01:48:09 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-19 01:48:09 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-19 01:48:09 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-19 01:48:09 (10888) [INFO] * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-19 01:48:45 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-19 01:48:45 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-19 01:48:45 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-19 01:48:45 (10888) [INFO] * 2026-01-19 01:48:45 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-19 01:48:46 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-19 01:49:16 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-19 01:49:16 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-19 01:49:16 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-19 01:49:16 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-19 01:49:16 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-19 01:49:16 (10901) [INFO] yum --disablerepo= ... * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-19 01:49:16 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-19 01:49:16 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] yum-config-manager --disable * 2026-01-19 01:49:16 (10901) [INFO] or * 2026-01-19 01:49:16 (10901) [INFO] subscription-manager repos --disable= * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-19 01:49:16 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-19 01:49:16 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-19 01:49:16 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-19 01:49:16 (10901) [INFO] compromise: * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-19 01:49:16 (10901) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-19 01:49:16 (10918) [INFO] * 2026-01-19 01:49:16 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-19 01:49:16 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-19 01:49:16 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-19 01:49:16 (10888) [INFO] * 2026-01-19 01:49:16 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-19 01:49:17 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-19 01:49:17 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-19 01:49:17 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-19 01:49:17 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-19 01:49:17 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-19 01:49:17 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-19 01:49:17 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-19 01:49:17 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-19 01:49:17 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-19 01:49:17 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-19 01:49:17 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-19 01:49:17 (10918) [INFO] * 2026-01-19 01:49:17 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-19 01:49:17 (10888) [INFO] * 2026-01-19 01:49:17 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-19 01:49:18 (10901) [INFO] Determining fastest mirrors * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-19 01:49:48 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-19 01:49:48 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-19 01:49:48 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-19 01:49:48 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-19 01:49:48 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-19 01:49:48 (10901) [INFO] yum --disablerepo= ... * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-19 01:49:48 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-19 01:49:48 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] yum-config-manager --disable * 2026-01-19 01:49:48 (10901) [INFO] or * 2026-01-19 01:49:48 (10901) [INFO] subscription-manager repos --disable= * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-19 01:49:48 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-19 01:49:48 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-19 01:49:48 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-19 01:49:48 (10901) [INFO] compromise: * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-19 01:49:48 (10901) [INFO] * 2026-01-19 01:49:48 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-19 01:49:48 (10918) [INFO] * 2026-01-19 01:49:48 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-19 01:49:48 (6735) [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 * 2026-01-19 01:49:50 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-19 01:49:50 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-19 01:49:50 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-19 01:49:50 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-19 01:49:50 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-19 01:49:56 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XY1H0EfBxr/ea_profile.json * 2026-01-19 01:52:54 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XY1H0EfBxr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-19 01:52:54 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-20 01:45:05 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-20 01:49:05 (11991) [INFO] Script is up to date. * 2026-01-20 01:53:09 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-20 01:53:09 (10888) [INFO] * 2026-01-20 01:54:23 (10918) [INFO] * 2026-01-20 01:54:23 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-20 01:54:23 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-20 01:54:23 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-20 01:54:23 (10888) [INFO] * 2026-01-20 02:01:26 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-20 02:01:26 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-20 02:01:26 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-20 02:01:26 (10888) [INFO] * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-20 02:01:59 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-20 02:01:59 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-20 02:01:59 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-20 02:01:59 (10888) [INFO] * 2026-01-20 02:02:00 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-20 02:02:00 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-20 02:02:30 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-20 02:02:30 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-20 02:02:30 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-20 02:02:30 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-20 02:02:30 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-20 02:02:30 (10901) [INFO] yum --disablerepo= ... * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-20 02:02:30 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-20 02:02:30 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] yum-config-manager --disable * 2026-01-20 02:02:30 (10901) [INFO] or * 2026-01-20 02:02:30 (10901) [INFO] subscription-manager repos --disable= * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-20 02:02:30 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-20 02:02:30 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-20 02:02:30 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-20 02:02:30 (10901) [INFO] compromise: * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-20 02:02:30 (10901) [INFO] * 2026-01-20 02:02:30 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-20 02:02:30 (10918) [INFO] * 2026-01-20 02:02:30 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-20 02:02:30 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-20 02:02:30 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-20 02:02:30 (10888) [INFO] * 2026-01-20 02:02:31 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-20 02:02:31 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-20 02:02:31 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-20 02:02:31 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-20 02:02:31 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-20 02:02:31 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-20 02:02:31 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-20 02:02:31 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-20 02:02:31 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-20 02:02:31 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-20 02:02:31 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-20 02:02:31 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-20 02:02:31 (10918) [INFO] * 2026-01-20 02:02:31 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-20 02:02:31 (10888) [INFO] * 2026-01-20 02:02:32 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-20 02:02:32 (10901) [INFO] Determining fastest mirrors * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-20 02:03:03 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-20 02:03:03 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-20 02:03:03 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-20 02:03:03 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-20 02:03:03 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-20 02:03:03 (10901) [INFO] yum --disablerepo= ... * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-20 02:03:03 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-20 02:03:03 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] yum-config-manager --disable * 2026-01-20 02:03:03 (10901) [INFO] or * 2026-01-20 02:03:03 (10901) [INFO] subscription-manager repos --disable= * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-20 02:03:03 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-20 02:03:03 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-20 02:03:03 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-20 02:03:03 (10901) [INFO] compromise: * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-20 02:03:03 (10901) [INFO] * 2026-01-20 02:03:03 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-20 02:03:03 (10918) [INFO] * 2026-01-20 02:03:03 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-20 02:03:03 (6735) [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 * 2026-01-20 02:03:05 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-20 02:03:05 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-20 02:03:05 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-20 02:03:05 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-20 02:03:05 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-20 02:03:12 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/WJ_XNE1iPo/ea_profile.json * 2026-01-20 02:06:10 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/WJ_XNE1iPo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-20 02:06:10 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-21 01:40:34 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-21 01:44:35 (11991) [INFO] Script is up to date. * 2026-01-21 01:48:38 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-21 01:48:38 (10888) [INFO] * 2026-01-21 01:49:52 (10918) [INFO] * 2026-01-21 01:49:52 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-21 01:49:52 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-21 01:49:52 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-21 01:49:52 (10888) [INFO] * 2026-01-21 01:56:55 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-21 01:56:55 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-21 01:56:55 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-21 01:56:55 (10888) [INFO] * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-21 01:57:29 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-21 01:57:29 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-21 01:57:29 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-21 01:57:29 (10888) [INFO] * 2026-01-21 01:57:29 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-21 01:57:29 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-21 01:57:59 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-21 01:57:59 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-21 01:57:59 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-21 01:57:59 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-21 01:57:59 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-21 01:57:59 (10901) [INFO] yum --disablerepo= ... * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-21 01:57:59 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-21 01:57:59 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] yum-config-manager --disable * 2026-01-21 01:57:59 (10901) [INFO] or * 2026-01-21 01:57:59 (10901) [INFO] subscription-manager repos --disable= * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-21 01:57:59 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-21 01:57:59 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-21 01:57:59 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-21 01:57:59 (10901) [INFO] compromise: * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-21 01:57:59 (10901) [INFO] * 2026-01-21 01:57:59 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-21 01:57:59 (10918) [INFO] * 2026-01-21 01:57:59 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-21 01:57:59 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-21 01:57:59 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-21 01:57:59 (10888) [INFO] * 2026-01-21 01:58:00 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-21 01:58:00 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-21 01:58:00 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-21 01:58:00 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-21 01:58:00 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-21 01:58:00 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-21 01:58:00 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-21 01:58:00 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-21 01:58:00 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-21 01:58:00 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-21 01:58:00 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-21 01:58:00 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-21 01:58:00 (10918) [INFO] * 2026-01-21 01:58:00 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-21 01:58:00 (10888) [INFO] * 2026-01-21 01:58:01 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-21 01:58:01 (10901) [INFO] Determining fastest mirrors * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-21 01:58:33 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-21 01:58:33 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-21 01:58:33 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-21 01:58:33 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-21 01:58:33 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-21 01:58:33 (10901) [INFO] yum --disablerepo= ... * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-21 01:58:33 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-21 01:58:33 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] yum-config-manager --disable * 2026-01-21 01:58:33 (10901) [INFO] or * 2026-01-21 01:58:33 (10901) [INFO] subscription-manager repos --disable= * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-21 01:58:33 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-21 01:58:33 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-21 01:58:33 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-21 01:58:33 (10901) [INFO] compromise: * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-21 01:58:33 (10901) [INFO] * 2026-01-21 01:58:33 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-21 01:58:33 (10918) [INFO] * 2026-01-21 01:58:33 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-21 01:58:33 (6735) [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 * 2026-01-21 01:58:34 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-21 01:58:34 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-21 01:58:34 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-21 01:58:34 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-21 01:58:34 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-21 01:58:42 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Wk7o6WOESS/ea_profile.json * 2026-01-21 02:01:10 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Wk7o6WOESS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-21 02:01:10 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-22 01:38:38 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-22 01:42:39 (11991) [INFO] Script is up to date. * 2026-01-22 01:46:42 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-22 01:46:42 (10888) [INFO] * 2026-01-22 01:47:57 (10918) [INFO] * 2026-01-22 01:47:57 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-22 01:47:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-22 01:47:58 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-22 01:47:58 (10888) [INFO] * 2026-01-22 01:56:22 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-22 01:56:22 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-22 01:56:22 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-22 01:56:22 (10888) [INFO] * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-22 01:56:57 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-22 01:56:57 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-22 01:56:57 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-22 01:56:57 (10888) [INFO] * 2026-01-22 01:56:57 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-22 01:56:58 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-22 01:57:29 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-22 01:57:29 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-22 01:57:29 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-22 01:57:29 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-22 01:57:29 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-22 01:57:29 (10901) [INFO] yum --disablerepo= ... * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-22 01:57:29 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-22 01:57:29 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] yum-config-manager --disable * 2026-01-22 01:57:29 (10901) [INFO] or * 2026-01-22 01:57:29 (10901) [INFO] subscription-manager repos --disable= * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-22 01:57:29 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-22 01:57:29 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-22 01:57:29 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-22 01:57:29 (10901) [INFO] compromise: * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-22 01:57:29 (10901) [INFO] * 2026-01-22 01:57:29 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-22 01:57:29 (10918) [INFO] * 2026-01-22 01:57:29 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-22 01:57:29 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-22 01:57:29 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-22 01:57:29 (10888) [INFO] * 2026-01-22 01:57:30 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-22 01:57:30 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-22 01:57:30 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-22 01:57:30 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-22 01:57:30 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-22 01:57:30 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-22 01:57:30 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-22 01:57:30 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-22 01:57:30 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-22 01:57:30 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-22 01:57:30 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-22 01:57:30 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-22 01:57:30 (10918) [INFO] * 2026-01-22 01:57:30 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-22 01:57:30 (10888) [INFO] * 2026-01-22 01:57:31 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-22 01:57:31 (10901) [INFO] Determining fastest mirrors * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-22 01:58:02 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-22 01:58:02 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-22 01:58:02 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-22 01:58:02 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-22 01:58:02 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-22 01:58:02 (10901) [INFO] yum --disablerepo= ... * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-22 01:58:02 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-22 01:58:02 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] yum-config-manager --disable * 2026-01-22 01:58:02 (10901) [INFO] or * 2026-01-22 01:58:02 (10901) [INFO] subscription-manager repos --disable= * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-22 01:58:02 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-22 01:58:02 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-22 01:58:02 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-22 01:58:02 (10901) [INFO] compromise: * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-22 01:58:02 (10901) [INFO] * 2026-01-22 01:58:02 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-22 01:58:02 (10918) [INFO] * 2026-01-22 01:58:02 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-22 01:58:02 (6735) [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 * 2026-01-22 01:58:03 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-22 01:58:03 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-22 01:58:03 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-22 01:58:03 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-22 01:58:03 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-22 01:58:12 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/x6XemtTqhr/ea_profile.json * 2026-01-22 02:00:40 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/x6XemtTqhr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-22 02:00:40 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-23 01:39:09 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-23 01:43:10 (11991) [INFO] Script is up to date. * 2026-01-23 01:47:13 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-23 01:47:13 (10888) [INFO] * 2026-01-23 01:48:30 (10918) [INFO] * 2026-01-23 01:48:30 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-23 01:48:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-23 01:48:31 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-23 01:48:31 (10888) [INFO] * 2026-01-23 01:48:34 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-23 01:48:34 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-23 01:48:34 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-23 01:48:34 (10888) [INFO] * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-23 01:49:08 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-23 01:49:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-23 01:49:08 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-23 01:49:08 (10888) [INFO] * 2026-01-23 01:49:08 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-23 01:49:08 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-23 01:49:39 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-23 01:49:39 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-23 01:49:39 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-23 01:49:39 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-23 01:49:39 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-23 01:49:39 (10901) [INFO] yum --disablerepo= ... * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-23 01:49:39 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-23 01:49:39 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] yum-config-manager --disable * 2026-01-23 01:49:39 (10901) [INFO] or * 2026-01-23 01:49:39 (10901) [INFO] subscription-manager repos --disable= * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-23 01:49:39 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-23 01:49:39 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-23 01:49:39 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-23 01:49:39 (10901) [INFO] compromise: * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-23 01:49:39 (10901) [INFO] * 2026-01-23 01:49:39 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-23 01:49:39 (10918) [INFO] * 2026-01-23 01:49:39 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-23 01:49:39 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-23 01:49:39 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-23 01:49:39 (10888) [INFO] * 2026-01-23 01:49:40 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-23 01:49:40 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-23 01:49:40 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-23 01:49:40 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-23 01:49:40 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-23 01:49:40 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-23 01:49:40 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-23 01:49:40 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-23 01:49:40 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-23 01:49:40 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-23 01:49:40 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-23 01:49:40 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-23 01:49:40 (10918) [INFO] * 2026-01-23 01:49:40 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-23 01:49:40 (10888) [INFO] * 2026-01-23 01:49:41 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-23 01:49:41 (10901) [INFO] Determining fastest mirrors * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-23 01:50:12 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-23 01:50:12 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-23 01:50:12 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-23 01:50:12 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-23 01:50:12 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-23 01:50:12 (10901) [INFO] yum --disablerepo= ... * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-23 01:50:12 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-23 01:50:12 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] yum-config-manager --disable * 2026-01-23 01:50:12 (10901) [INFO] or * 2026-01-23 01:50:12 (10901) [INFO] subscription-manager repos --disable= * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-23 01:50:12 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-23 01:50:12 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-23 01:50:12 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-23 01:50:12 (10901) [INFO] compromise: * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-23 01:50:12 (10901) [INFO] * 2026-01-23 01:50:12 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-23 01:50:12 (10918) [INFO] * 2026-01-23 01:50:12 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-23 01:50:12 (6735) [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 * 2026-01-23 01:50:13 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-23 01:50:13 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-23 01:50:13 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-23 01:50:13 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-23 01:50:13 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-23 01:50:19 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lPuAv_765n/ea_profile.json * 2026-01-23 01:53:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lPuAv_765n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-23 01:53:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-24 01:39:47 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-24 01:43:48 (11991) [INFO] Script is up to date. * 2026-01-24 01:47:51 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-24 01:47:51 (10888) [INFO] * 2026-01-24 01:48:43 (10918) [INFO] * 2026-01-24 01:48:43 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-24 01:48:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-24 01:48:44 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-24 01:48:44 (10888) [INFO] * 2026-01-24 01:55:46 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-24 01:55:46 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-24 01:55:46 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-24 01:55:46 (10888) [INFO] * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-24 01:56:20 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-24 01:56:20 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-24 01:56:20 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-24 01:56:20 (10888) [INFO] * 2026-01-24 01:56:21 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-24 01:56:21 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-24 01:56:52 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-24 01:56:52 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-24 01:56:52 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-24 01:56:52 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-24 01:56:52 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-24 01:56:52 (10901) [INFO] yum --disablerepo= ... * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-24 01:56:52 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-24 01:56:52 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] yum-config-manager --disable * 2026-01-24 01:56:52 (10901) [INFO] or * 2026-01-24 01:56:52 (10901) [INFO] subscription-manager repos --disable= * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-24 01:56:52 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-24 01:56:52 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-24 01:56:52 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-24 01:56:52 (10901) [INFO] compromise: * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-24 01:56:52 (10901) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-24 01:56:52 (10918) [INFO] * 2026-01-24 01:56:52 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-24 01:56:52 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-24 01:56:52 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-24 01:56:52 (10888) [INFO] * 2026-01-24 01:56:52 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-24 01:56:52 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-24 01:56:52 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-24 01:56:52 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-24 01:56:52 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-24 01:56:52 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-24 01:56:52 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-24 01:56:52 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-24 01:56:52 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-24 01:56:52 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-24 01:56:52 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-24 01:56:53 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-24 01:56:53 (10918) [INFO] * 2026-01-24 01:56:53 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-24 01:56:53 (10888) [INFO] * 2026-01-24 01:56:53 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-24 01:56:53 (10901) [INFO] Determining fastest mirrors * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-24 01:57:24 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-24 01:57:24 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-24 01:57:24 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-24 01:57:24 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-24 01:57:24 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-24 01:57:24 (10901) [INFO] yum --disablerepo= ... * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-24 01:57:24 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-24 01:57:24 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] yum-config-manager --disable * 2026-01-24 01:57:24 (10901) [INFO] or * 2026-01-24 01:57:24 (10901) [INFO] subscription-manager repos --disable= * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-24 01:57:24 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-24 01:57:24 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-24 01:57:24 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-24 01:57:24 (10901) [INFO] compromise: * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-24 01:57:24 (10901) [INFO] * 2026-01-24 01:57:24 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-24 01:57:24 (10918) [INFO] * 2026-01-24 01:57:24 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-24 01:57:24 (6735) [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 * 2026-01-24 01:57:26 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-24 01:57:26 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-24 01:57:26 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-24 01:57:26 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-24 01:57:26 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-24 01:57:33 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tkFIQj5TVE/ea_profile.json * 2026-01-24 01:59:58 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tkFIQj5TVE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-24 01:59:58 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-25 01:40:53 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-25 01:44:53 (11991) [INFO] Script is up to date. * 2026-01-25 01:48:57 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-25 01:48:57 (10888) [INFO] * 2026-01-25 01:49:50 (10918) [INFO] * 2026-01-25 01:49:50 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-25 01:49:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-25 01:49:50 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-25 01:49:50 (10888) [INFO] * 2026-01-25 01:56:53 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-25 01:56:53 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-25 01:56:53 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-25 01:56:53 (10888) [INFO] * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-25 01:57:28 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-25 01:57:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-25 01:57:28 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-25 01:57:28 (10888) [INFO] * 2026-01-25 01:57:29 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-25 01:57:29 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-25 01:57:59 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-25 01:57:59 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-25 01:57:59 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-25 01:57:59 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-25 01:57:59 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-25 01:57:59 (10901) [INFO] yum --disablerepo= ... * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-25 01:57:59 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-25 01:57:59 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] yum-config-manager --disable * 2026-01-25 01:57:59 (10901) [INFO] or * 2026-01-25 01:57:59 (10901) [INFO] subscription-manager repos --disable= * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-25 01:57:59 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-25 01:57:59 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-25 01:57:59 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-25 01:57:59 (10901) [INFO] compromise: * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-25 01:57:59 (10901) [INFO] * 2026-01-25 01:57:59 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-25 01:57:59 (10918) [INFO] * 2026-01-25 01:57:59 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-25 01:57:59 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-25 01:57:59 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-25 01:57:59 (10888) [INFO] * 2026-01-25 01:58:00 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-25 01:58:00 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-25 01:58:00 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-25 01:58:00 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-25 01:58:00 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-25 01:58:00 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-25 01:58:00 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-25 01:58:00 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-25 01:58:00 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-25 01:58:00 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-25 01:58:00 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-25 01:58:00 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-25 01:58:00 (10918) [INFO] * 2026-01-25 01:58:00 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-25 01:58:00 (10888) [INFO] * 2026-01-25 01:58:01 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-25 01:58:01 (10901) [INFO] Determining fastest mirrors * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-25 01:58:32 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-25 01:58:32 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-25 01:58:32 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-25 01:58:32 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-25 01:58:32 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-25 01:58:32 (10901) [INFO] yum --disablerepo= ... * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-25 01:58:32 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-25 01:58:32 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] yum-config-manager --disable * 2026-01-25 01:58:32 (10901) [INFO] or * 2026-01-25 01:58:32 (10901) [INFO] subscription-manager repos --disable= * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-25 01:58:32 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-25 01:58:32 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-25 01:58:32 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-25 01:58:32 (10901) [INFO] compromise: * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-25 01:58:32 (10901) [INFO] * 2026-01-25 01:58:32 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-25 01:58:32 (10918) [INFO] * 2026-01-25 01:58:32 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-25 01:58:32 (6735) [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 * 2026-01-25 01:58:33 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-25 01:58:33 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-25 01:58:33 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-25 01:58:33 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-25 01:58:33 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-25 01:58:39 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rFQDyJvUze/ea_profile.json * 2026-01-25 02:01:06 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/rFQDyJvUze/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-25 02:01:06 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-26 01:38:39 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-26 01:42:39 (11991) [INFO] Script is up to date. * 2026-01-26 01:46:42 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-26 01:46:42 (10888) [INFO] * 2026-01-26 01:48:02 (10918) [INFO] * 2026-01-26 01:48:02 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-26 01:48:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-26 01:48:02 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-26 01:48:02 (10888) [INFO] * 2026-01-26 01:58:43 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-26 01:58:43 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-26 01:58:43 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-26 01:58:43 (10888) [INFO] * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-26 01:59:19 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-26 01:59:19 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-26 01:59:19 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-26 01:59:19 (10888) [INFO] * 2026-01-26 01:59:19 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-26 01:59:19 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-26 01:59:50 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-26 01:59:50 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-26 01:59:50 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-26 01:59:50 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-26 01:59:50 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-26 01:59:50 (10901) [INFO] yum --disablerepo= ... * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-26 01:59:50 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-26 01:59:50 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] yum-config-manager --disable * 2026-01-26 01:59:50 (10901) [INFO] or * 2026-01-26 01:59:50 (10901) [INFO] subscription-manager repos --disable= * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-26 01:59:50 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-26 01:59:50 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-26 01:59:50 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-26 01:59:50 (10901) [INFO] compromise: * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-26 01:59:50 (10901) [INFO] * 2026-01-26 01:59:50 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-26 01:59:50 (10918) [INFO] * 2026-01-26 01:59:50 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-26 01:59:50 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-26 01:59:50 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-26 01:59:50 (10888) [INFO] * 2026-01-26 01:59:51 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-26 01:59:51 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-26 01:59:51 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-26 01:59:51 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-26 01:59:51 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-26 01:59:51 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-26 01:59:51 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-26 01:59:51 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-26 01:59:51 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-26 01:59:51 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-26 01:59:51 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-26 01:59:51 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-26 01:59:51 (10918) [INFO] * 2026-01-26 01:59:51 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-26 01:59:51 (10888) [INFO] * 2026-01-26 01:59:52 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-26 01:59:52 (10901) [INFO] Determining fastest mirrors * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-26 02:00:22 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-26 02:00:22 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-26 02:00:22 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-26 02:00:22 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-26 02:00:22 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-26 02:00:22 (10901) [INFO] yum --disablerepo= ... * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-26 02:00:22 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-26 02:00:22 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] yum-config-manager --disable * 2026-01-26 02:00:22 (10901) [INFO] or * 2026-01-26 02:00:22 (10901) [INFO] subscription-manager repos --disable= * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-26 02:00:22 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-26 02:00:22 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-26 02:00:22 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-26 02:00:22 (10901) [INFO] compromise: * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-26 02:00:22 (10901) [INFO] * 2026-01-26 02:00:22 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-26 02:00:23 (10918) [INFO] * 2026-01-26 02:00:23 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-26 02:00:23 (6735) [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 * 2026-01-26 02:00:24 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-26 02:00:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-26 02:00:24 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-26 02:00:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-26 02:00:24 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-26 02:00:31 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sQ3bqi3g3n/ea_profile.json * 2026-01-26 02:02:58 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sQ3bqi3g3n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-26 02:02:58 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-27 01:42:09 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-27 01:46:09 (11991) [INFO] Script is up to date. * 2026-01-27 01:50:13 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-27 01:50:13 (10888) [INFO] * 2026-01-27 01:51:31 (10918) [INFO] * 2026-01-27 01:51:31 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-27 01:51:31 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-27 01:51:31 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-27 01:51:31 (10888) [INFO] * 2026-01-27 01:52:02 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-27 01:52:02 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-27 01:52:02 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-27 01:52:02 (10888) [INFO] * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-27 01:52:38 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-27 01:52:38 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-27 01:52:38 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-27 01:52:38 (10888) [INFO] * 2026-01-27 01:52:39 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-27 01:52:39 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-27 01:53:09 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-27 01:53:09 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-27 01:53:09 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-27 01:53:09 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-27 01:53:09 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-27 01:53:09 (10901) [INFO] yum --disablerepo= ... * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-27 01:53:09 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-27 01:53:09 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] yum-config-manager --disable * 2026-01-27 01:53:09 (10901) [INFO] or * 2026-01-27 01:53:09 (10901) [INFO] subscription-manager repos --disable= * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-27 01:53:09 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-27 01:53:09 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-27 01:53:09 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-27 01:53:09 (10901) [INFO] compromise: * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-27 01:53:09 (10901) [INFO] * 2026-01-27 01:53:09 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-27 01:53:09 (10918) [INFO] * 2026-01-27 01:53:09 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-27 01:53:09 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-27 01:53:09 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-27 01:53:10 (10888) [INFO] * 2026-01-27 01:53:10 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-27 01:53:10 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-27 01:53:10 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-27 01:53:10 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-27 01:53:10 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-27 01:53:10 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-27 01:53:10 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-27 01:53:10 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-27 01:53:10 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-27 01:53:10 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-27 01:53:10 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-27 01:53:10 (10901) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-01-27 01:53:11 (10918) [INFO] * 2026-01-27 01:53:11 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-27 01:53:11 (10888) [INFO] * 2026-01-27 01:53:11 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-27 01:53:11 (10901) [INFO] Determining fastest mirrors * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-27 01:53:42 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-27 01:53:42 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-27 01:53:42 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-27 01:53:42 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-27 01:53:42 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-27 01:53:42 (10901) [INFO] yum --disablerepo= ... * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-27 01:53:42 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-27 01:53:42 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] yum-config-manager --disable * 2026-01-27 01:53:42 (10901) [INFO] or * 2026-01-27 01:53:42 (10901) [INFO] subscription-manager repos --disable= * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-27 01:53:42 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-27 01:53:42 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-27 01:53:42 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-27 01:53:42 (10901) [INFO] compromise: * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-27 01:53:42 (10901) [INFO] * 2026-01-27 01:53:42 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-27 01:53:42 (10918) [INFO] * 2026-01-27 01:53:42 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-27 01:53:42 (6735) [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 * 2026-01-27 01:53:43 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-27 01:53:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-27 01:53:43 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-27 01:53:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-27 01:53:43 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-27 01:53:50 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jjYVOfnwkN/ea_profile.json * 2026-01-27 01:56:47 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jjYVOfnwkN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-27 01:56:47 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-28 01:43:22 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-28 01:47:22 (11991) [INFO] Script is up to date. * 2026-01-28 01:51:25 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-28 01:51:25 (10888) [INFO] * 2026-01-28 01:52:43 (10918) [INFO] * 2026-01-28 01:52:43 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-28 01:52:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-28 01:52:43 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-28 01:52:43 (10888) [INFO] * 2026-01-28 01:58:58 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-28 01:58:58 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-28 01:58:58 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-28 01:58:58 (10888) [INFO] * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-28 01:59:34 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-28 01:59:34 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-28 01:59:34 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-28 01:59:34 (10888) [INFO] * 2026-01-28 01:59:34 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-28 01:59:35 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-28 02:00:05 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-28 02:00:05 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-28 02:00:05 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-28 02:00:05 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-28 02:00:05 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-28 02:00:05 (10901) [INFO] yum --disablerepo= ... * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-28 02:00:05 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-28 02:00:05 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] yum-config-manager --disable * 2026-01-28 02:00:05 (10901) [INFO] or * 2026-01-28 02:00:05 (10901) [INFO] subscription-manager repos --disable= * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-28 02:00:05 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-28 02:00:05 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-28 02:00:05 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-28 02:00:05 (10901) [INFO] compromise: * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-28 02:00:05 (10901) [INFO] * 2026-01-28 02:00:05 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-28 02:00:05 (10918) [INFO] * 2026-01-28 02:00:05 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-28 02:00:05 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-28 02:00:05 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-28 02:00:05 (10888) [INFO] * 2026-01-28 02:00:06 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-28 02:00:06 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-28 02:00:06 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-28 02:00:06 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-28 02:00:06 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-28 02:00:06 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-28 02:00:06 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-28 02:00:06 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-28 02:00:06 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-28 02:00:06 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-28 02:00:06 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-28 02:00:06 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-28 02:00:06 (10918) [INFO] * 2026-01-28 02:00:06 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-28 02:00:06 (10888) [INFO] * 2026-01-28 02:00:07 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-28 02:00:07 (10901) [INFO] Determining fastest mirrors * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-28 02:00:39 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-28 02:00:39 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-28 02:00:39 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-28 02:00:39 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-28 02:00:39 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-28 02:00:39 (10901) [INFO] yum --disablerepo= ... * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-28 02:00:39 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-28 02:00:39 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] yum-config-manager --disable * 2026-01-28 02:00:39 (10901) [INFO] or * 2026-01-28 02:00:39 (10901) [INFO] subscription-manager repos --disable= * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-28 02:00:39 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-28 02:00:39 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-28 02:00:39 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-28 02:00:39 (10901) [INFO] compromise: * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-28 02:00:39 (10901) [INFO] * 2026-01-28 02:00:39 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-28 02:00:39 (10918) [INFO] * 2026-01-28 02:00:39 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-28 02:00:39 (6735) [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 * 2026-01-28 02:00:40 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-28 02:00:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-28 02:00:40 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-28 02:00:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-28 02:00:40 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-28 02:00:47 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VRpnEqk0ez/ea_profile.json * 2026-01-28 02:03:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VRpnEqk0ez/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-28 02:03:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-29 01:41:19 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-29 01:45:19 (11991) [INFO] Script is up to date. * 2026-01-29 01:49:22 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-29 01:49:22 (10888) [INFO] * 2026-01-29 01:50:41 (10918) [INFO] * 2026-01-29 01:50:41 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-29 01:50:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-29 01:50:42 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-29 01:50:42 (10888) [INFO] * 2026-01-29 01:56:58 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-29 01:56:58 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-29 01:56:58 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-29 01:56:58 (10888) [INFO] * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-29 01:57:33 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-29 01:57:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-29 01:57:33 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-29 01:57:33 (10888) [INFO] * 2026-01-29 01:57:34 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-29 01:57:34 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-29 01:58:04 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-29 01:58:04 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-29 01:58:04 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-29 01:58:04 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-29 01:58:04 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-29 01:58:04 (10901) [INFO] yum --disablerepo= ... * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-29 01:58:04 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-29 01:58:04 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] yum-config-manager --disable * 2026-01-29 01:58:04 (10901) [INFO] or * 2026-01-29 01:58:04 (10901) [INFO] subscription-manager repos --disable= * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-29 01:58:04 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-29 01:58:04 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-29 01:58:04 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-29 01:58:04 (10901) [INFO] compromise: * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-29 01:58:04 (10901) [INFO] * 2026-01-29 01:58:04 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-29 01:58:04 (10918) [INFO] * 2026-01-29 01:58:04 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-29 01:58:04 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-29 01:58:04 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-29 01:58:04 (10888) [INFO] * 2026-01-29 01:58:05 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-29 01:58:05 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-29 01:58:05 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-29 01:58:05 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-29 01:58:05 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-29 01:58:05 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-29 01:58:05 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-29 01:58:05 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-29 01:58:05 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-29 01:58:05 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-29 01:58:05 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-29 01:58:05 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-29 01:58:05 (10918) [INFO] * 2026-01-29 01:58:05 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-29 01:58:05 (10888) [INFO] * 2026-01-29 01:58:06 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-29 01:58:06 (10901) [INFO] Determining fastest mirrors * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-29 01:58:37 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-29 01:58:37 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-29 01:58:37 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-29 01:58:37 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-29 01:58:37 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-29 01:58:37 (10901) [INFO] yum --disablerepo= ... * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-29 01:58:37 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-29 01:58:37 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] yum-config-manager --disable * 2026-01-29 01:58:37 (10901) [INFO] or * 2026-01-29 01:58:37 (10901) [INFO] subscription-manager repos --disable= * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-29 01:58:37 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-29 01:58:37 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-29 01:58:37 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-29 01:58:37 (10901) [INFO] compromise: * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-29 01:58:37 (10901) [INFO] * 2026-01-29 01:58:37 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-29 01:58:37 (10918) [INFO] * 2026-01-29 01:58:37 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-29 01:58:37 (6735) [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 * 2026-01-29 01:58:39 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-29 01:58:39 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-29 01:58:39 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-29 01:58:39 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-29 01:58:39 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-29 01:58:45 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/klBXxAt_DX/ea_profile.json * 2026-01-29 02:01:11 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/klBXxAt_DX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-29 02:01:11 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-30 01:38:33 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-30 01:42:34 (11991) [INFO] Script is up to date. * 2026-01-30 01:46:36 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-30 01:46:36 (10888) [INFO] * 2026-01-30 01:47:49 (10918) [INFO] * 2026-01-30 01:47:49 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-30 01:47:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-30 01:47:50 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-30 01:47:50 (10888) [INFO] * 2026-01-30 01:58:18 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-30 01:58:18 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-30 01:58:18 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-30 01:58:18 (10888) [INFO] * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-30 01:58:53 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-30 01:58:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-30 01:58:53 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-30 01:58:53 (10888) [INFO] * 2026-01-30 01:58:53 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-30 01:58:54 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-30 01:59:24 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-30 01:59:24 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-30 01:59:24 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-30 01:59:24 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-30 01:59:24 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-30 01:59:24 (10901) [INFO] yum --disablerepo= ... * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-30 01:59:24 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-30 01:59:24 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] yum-config-manager --disable * 2026-01-30 01:59:24 (10901) [INFO] or * 2026-01-30 01:59:24 (10901) [INFO] subscription-manager repos --disable= * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-30 01:59:24 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-30 01:59:24 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-30 01:59:24 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-30 01:59:24 (10901) [INFO] compromise: * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-30 01:59:24 (10901) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-30 01:59:24 (10918) [INFO] * 2026-01-30 01:59:24 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-30 01:59:24 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-30 01:59:24 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-30 01:59:24 (10888) [INFO] * 2026-01-30 01:59:24 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-30 01:59:25 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-30 01:59:25 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-30 01:59:25 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-30 01:59:25 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-30 01:59:25 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-30 01:59:25 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-30 01:59:25 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-30 01:59:25 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-30 01:59:25 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-30 01:59:25 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-30 01:59:25 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-01-30 01:59:25 (10918) [INFO] * 2026-01-30 01:59:25 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-30 01:59:25 (10888) [INFO] * 2026-01-30 01:59:25 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-30 01:59:26 (10901) [INFO] Determining fastest mirrors * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-30 01:59:56 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-30 01:59:56 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-30 01:59:56 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-30 01:59:56 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-30 01:59:56 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-30 01:59:56 (10901) [INFO] yum --disablerepo= ... * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-30 01:59:56 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-30 01:59:56 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] yum-config-manager --disable * 2026-01-30 01:59:56 (10901) [INFO] or * 2026-01-30 01:59:56 (10901) [INFO] subscription-manager repos --disable= * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-30 01:59:56 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-30 01:59:56 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-30 01:59:56 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-30 01:59:56 (10901) [INFO] compromise: * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-30 01:59:56 (10901) [INFO] * 2026-01-30 01:59:56 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-30 01:59:56 (10918) [INFO] * 2026-01-30 01:59:56 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-30 01:59:56 (6735) [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 * 2026-01-30 01:59:57 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-30 01:59:57 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-30 01:59:57 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-30 01:59:57 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-30 01:59:57 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-30 02:00:04 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wYfXRTYsuu/ea_profile.json * 2026-01-30 02:02:32 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/wYfXRTYsuu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-30 02:02:32 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-01-31 01:39:49 (11969) [INFO] Self-update of script version 77 requested. * 2026-01-31 01:43:49 (11991) [INFO] Script is up to date. * 2026-01-31 01:47:52 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-01-31 01:47:52 (10888) [INFO] * 2026-01-31 01:48:43 (10918) [INFO] * 2026-01-31 01:48:43 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-01-31 01:48:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-01-31 01:48:43 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-01-31 01:48:43 (10888) [INFO] * 2026-01-31 01:54:59 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-01-31 01:54:59 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-01-31 01:54:59 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-01-31 01:54:59 (10888) [INFO] * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-01-31 01:55:33 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-01-31 01:55:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-01-31 01:55:33 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-31 01:55:33 (10888) [INFO] * 2026-01-31 01:55:34 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-31 01:55:34 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-31 01:56:04 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-31 01:56:04 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-31 01:56:04 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-31 01:56:04 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-31 01:56:04 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-31 01:56:04 (10901) [INFO] yum --disablerepo= ... * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-31 01:56:04 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-31 01:56:04 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] yum-config-manager --disable * 2026-01-31 01:56:04 (10901) [INFO] or * 2026-01-31 01:56:04 (10901) [INFO] subscription-manager repos --disable= * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-31 01:56:04 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-31 01:56:04 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-31 01:56:04 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-31 01:56:04 (10901) [INFO] compromise: * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-31 01:56:04 (10901) [INFO] * 2026-01-31 01:56:04 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-31 01:56:04 (10918) [INFO] * 2026-01-31 01:56:04 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-31 01:56:04 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-01-31 01:56:04 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-01-31 01:56:04 (10888) [INFO] * 2026-01-31 01:56:05 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-31 01:56:05 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-01-31 01:56:05 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-01-31 01:56:05 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-01-31 01:56:05 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-01-31 01:56:05 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-01-31 01:56:05 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-01-31 01:56:05 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-01-31 01:56:05 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-01-31 01:56:05 (10901) [INFO] : wp-toolkit-thirdparties * 2026-01-31 01:56:05 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-01-31 01:56:05 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-01-31 01:56:05 (10918) [INFO] * 2026-01-31 01:56:05 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-01-31 01:56:05 (10888) [INFO] * 2026-01-31 01:56:05 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-01-31 01:56:06 (10901) [INFO] Determining fastest mirrors * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-01-31 01:56:36 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-01-31 01:56:36 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-01-31 01:56:36 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-01-31 01:56:36 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-01-31 01:56:36 (10901) [INFO] packages for the previous distribution release still work). * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-01-31 01:56:36 (10901) [INFO] yum --disablerepo= ... * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-01-31 01:56:36 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-01-31 01:56:36 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] yum-config-manager --disable * 2026-01-31 01:56:36 (10901) [INFO] or * 2026-01-31 01:56:36 (10901) [INFO] subscription-manager repos --disable= * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-01-31 01:56:36 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-01-31 01:56:36 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-01-31 01:56:36 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-01-31 01:56:36 (10901) [INFO] compromise: * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-01-31 01:56:36 (10901) [INFO] * 2026-01-31 01:56:36 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-01-31 01:56:36 (10918) [INFO] * 2026-01-31 01:56:36 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-01-31 01:56:36 (6735) [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 * 2026-01-31 01:56:38 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-01-31 01:56:38 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-01-31 01:56:38 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-01-31 01:56:38 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-01-31 01:56:38 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-01-31 01:56:45 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4ZdcWwDV3Q/ea_profile.json * 2026-01-31 01:59:13 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4ZdcWwDV3Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-01-31 01:59:13 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-01 01:40:25 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-01 01:44:26 (11991) [INFO] Script is up to date. * 2026-02-01 01:48:28 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-01 01:48:28 (10888) [INFO] * 2026-02-01 01:49:15 (10918) [INFO] * 2026-02-01 01:49:15 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-01 01:49:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-01 01:49:16 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-01 01:49:16 (10888) [INFO] * 2026-02-01 01:56:45 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-01 01:56:45 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-01 01:56:45 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-01 01:56:45 (10888) [INFO] * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-01 01:57:21 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-01 01:57:21 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-01 01:57:21 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-01 01:57:21 (10888) [INFO] * 2026-02-01 01:57:22 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-01 01:57:22 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-01 01:57:53 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-01 01:57:53 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-01 01:57:53 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-01 01:57:53 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-01 01:57:53 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-01 01:57:53 (10901) [INFO] yum --disablerepo= ... * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-01 01:57:53 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-01 01:57:53 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] yum-config-manager --disable * 2026-02-01 01:57:53 (10901) [INFO] or * 2026-02-01 01:57:53 (10901) [INFO] subscription-manager repos --disable= * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-01 01:57:53 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-01 01:57:53 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-01 01:57:53 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-01 01:57:53 (10901) [INFO] compromise: * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-01 01:57:53 (10901) [INFO] * 2026-02-01 01:57:53 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-01 01:57:53 (10918) [INFO] * 2026-02-01 01:57:53 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-01 01:57:53 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-01 01:57:53 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-01 01:57:53 (10888) [INFO] * 2026-02-01 01:57:54 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-01 01:57:54 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-01 01:57:54 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-01 01:57:54 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-01 01:57:54 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-01 01:57:54 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-01 01:57:54 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-01 01:57:54 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-01 01:57:54 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-01 01:57:54 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-01 01:57:54 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-01 01:57:54 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-01 01:57:54 (10918) [INFO] * 2026-02-01 01:57:54 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-01 01:57:54 (10888) [INFO] * 2026-02-01 01:57:55 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-01 01:57:55 (10901) [INFO] Determining fastest mirrors * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-01 01:58:26 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-01 01:58:26 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-01 01:58:26 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-01 01:58:26 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-01 01:58:26 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-01 01:58:26 (10901) [INFO] yum --disablerepo= ... * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-01 01:58:26 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-01 01:58:26 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] yum-config-manager --disable * 2026-02-01 01:58:26 (10901) [INFO] or * 2026-02-01 01:58:26 (10901) [INFO] subscription-manager repos --disable= * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-01 01:58:26 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-01 01:58:26 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-01 01:58:26 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-01 01:58:26 (10901) [INFO] compromise: * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-01 01:58:26 (10901) [INFO] * 2026-02-01 01:58:26 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-01 01:58:26 (10918) [INFO] * 2026-02-01 01:58:26 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-01 01:58:26 (6735) [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 * 2026-02-01 01:58:28 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-01 01:58:28 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-01 01:58:28 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-01 01:58:28 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-01 01:58:28 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-01 01:58:34 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yqIGG2YCxa/ea_profile.json * 2026-02-01 02:01:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/yqIGG2YCxa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-01 02:01:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-02 01:39:09 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-02 01:43:09 (11991) [INFO] Script is up to date. * 2026-02-02 01:47:12 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-02 01:47:12 (10888) [INFO] * 2026-02-02 01:48:28 (10918) [INFO] * 2026-02-02 01:48:28 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-02 01:48:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-02 01:48:29 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-02 01:48:29 (10888) [INFO] * 2026-02-02 01:54:45 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-02 01:54:45 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-02 01:54:45 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-02 01:54:45 (10888) [INFO] * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-02 01:55:21 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-02 01:55:21 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-02 01:55:21 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-02 01:55:21 (10888) [INFO] * 2026-02-02 01:55:21 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-02 01:55:22 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-02 01:55:53 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-02 01:55:53 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-02 01:55:53 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-02 01:55:53 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-02 01:55:53 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-02 01:55:53 (10901) [INFO] yum --disablerepo= ... * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-02 01:55:53 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-02 01:55:53 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] yum-config-manager --disable * 2026-02-02 01:55:53 (10901) [INFO] or * 2026-02-02 01:55:53 (10901) [INFO] subscription-manager repos --disable= * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-02 01:55:53 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-02 01:55:53 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-02 01:55:53 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-02 01:55:53 (10901) [INFO] compromise: * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-02 01:55:53 (10901) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-02 01:55:53 (10918) [INFO] * 2026-02-02 01:55:53 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-02 01:55:53 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-02 01:55:53 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-02 01:55:53 (10888) [INFO] * 2026-02-02 01:55:53 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-02 01:55:53 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-02 01:55:53 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-02 01:55:53 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-02 01:55:53 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-02 01:55:53 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-02 01:55:53 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-02 01:55:53 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-02 01:55:53 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-02 01:55:53 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-02 01:55:54 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-02 01:55:54 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-02 01:55:54 (10918) [INFO] * 2026-02-02 01:55:54 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-02 01:55:54 (10888) [INFO] * 2026-02-02 01:55:54 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-02 01:55:54 (10901) [INFO] Determining fastest mirrors * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-02 01:56:24 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-02 01:56:24 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-02 01:56:24 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-02 01:56:24 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-02 01:56:24 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-02 01:56:24 (10901) [INFO] yum --disablerepo= ... * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-02 01:56:24 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-02 01:56:24 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] yum-config-manager --disable * 2026-02-02 01:56:24 (10901) [INFO] or * 2026-02-02 01:56:24 (10901) [INFO] subscription-manager repos --disable= * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-02 01:56:24 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-02 01:56:24 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-02 01:56:24 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-02 01:56:24 (10901) [INFO] compromise: * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-02 01:56:24 (10901) [INFO] * 2026-02-02 01:56:24 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-02 01:56:24 (10918) [INFO] * 2026-02-02 01:56:24 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-02 01:56:24 (6735) [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 * 2026-02-02 01:56:26 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-02 01:56:26 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-02 01:56:26 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-02 01:56:26 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-02 01:56:26 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-02 01:56:32 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qCk2Xyj2Wf/ea_profile.json * 2026-02-02 01:59:30 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qCk2Xyj2Wf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-02 01:59:30 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-03 01:39:42 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-03 01:43:43 (11991) [INFO] Script is up to date. * 2026-02-03 01:47:46 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-03 01:47:46 (10888) [INFO] * 2026-02-03 01:49:02 (10918) [INFO] * 2026-02-03 01:49:02 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-03 01:49:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-03 01:49:02 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-03 01:49:02 (10888) [INFO] * 2026-02-03 01:55:19 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-03 01:55:19 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-03 01:55:19 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-03 01:55:19 (10888) [INFO] * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-03 01:55:53 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-03 01:55:53 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-03 01:55:53 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-03 01:55:53 (10888) [INFO] * 2026-02-03 01:55:53 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-03 01:55:54 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-03 01:56:24 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-03 01:56:24 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-03 01:56:24 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-03 01:56:24 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-03 01:56:24 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-03 01:56:24 (10901) [INFO] yum --disablerepo= ... * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-03 01:56:24 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-03 01:56:24 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] yum-config-manager --disable * 2026-02-03 01:56:24 (10901) [INFO] or * 2026-02-03 01:56:24 (10901) [INFO] subscription-manager repos --disable= * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-03 01:56:24 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-03 01:56:24 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-03 01:56:24 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-03 01:56:24 (10901) [INFO] compromise: * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-03 01:56:24 (10901) [INFO] * 2026-02-03 01:56:24 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-03 01:56:25 (10918) [INFO] * 2026-02-03 01:56:25 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-03 01:56:25 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-03 01:56:25 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-03 01:56:25 (10888) [INFO] * 2026-02-03 01:56:25 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-03 01:56:25 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-03 01:56:25 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-03 01:56:25 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-03 01:56:25 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-03 01:56:25 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-03 01:56:25 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-03 01:56:25 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-03 01:56:25 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-03 01:56:25 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-03 01:56:26 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-03 01:56:26 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-03 01:56:26 (10918) [INFO] * 2026-02-03 01:56:26 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-03 01:56:26 (10888) [INFO] * 2026-02-03 01:56:26 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-03 01:56:26 (10901) [INFO] Determining fastest mirrors * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-03 01:56:57 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-03 01:56:57 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-03 01:56:57 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-03 01:56:57 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-03 01:56:57 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-03 01:56:57 (10901) [INFO] yum --disablerepo= ... * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-03 01:56:57 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-03 01:56:57 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] yum-config-manager --disable * 2026-02-03 01:56:57 (10901) [INFO] or * 2026-02-03 01:56:57 (10901) [INFO] subscription-manager repos --disable= * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-03 01:56:57 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-03 01:56:57 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-03 01:56:57 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-03 01:56:57 (10901) [INFO] compromise: * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-03 01:56:57 (10901) [INFO] * 2026-02-03 01:56:57 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-03 01:56:57 (10918) [INFO] * 2026-02-03 01:56:57 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-03 01:56:57 (6735) [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 * 2026-02-03 01:56:58 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-03 01:56:58 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-03 01:56:58 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-03 01:56:58 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-03 01:56:58 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-03 01:57:05 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lQRQq6QcaL/ea_profile.json * 2026-02-03 02:00:34 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/lQRQq6QcaL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-03 02:00:34 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-04 01:51:03 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-04 01:55:03 (11991) [INFO] Script is up to date. * 2026-02-04 01:59:06 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-04 01:59:06 (10888) [INFO] * 2026-02-04 02:00:26 (10918) [INFO] * 2026-02-04 02:00:26 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-04 02:00:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-04 02:00:27 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-04 02:00:27 (10888) [INFO] * 2026-02-04 02:06:48 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-04 02:06:48 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-04 02:06:48 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-04 02:06:48 (10888) [INFO] * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-04 02:07:22 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-04 02:07:22 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-04 02:07:22 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-04 02:07:22 (10888) [INFO] * 2026-02-04 02:07:23 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-04 02:07:23 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-04 02:07:53 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-04 02:07:53 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-04 02:07:53 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-04 02:07:53 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-04 02:07:53 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-04 02:07:53 (10901) [INFO] yum --disablerepo= ... * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-04 02:07:53 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-04 02:07:53 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] yum-config-manager --disable * 2026-02-04 02:07:53 (10901) [INFO] or * 2026-02-04 02:07:53 (10901) [INFO] subscription-manager repos --disable= * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-04 02:07:53 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-04 02:07:53 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-04 02:07:53 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-04 02:07:53 (10901) [INFO] compromise: * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-04 02:07:53 (10901) [INFO] * 2026-02-04 02:07:53 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-04 02:07:53 (10918) [INFO] * 2026-02-04 02:07:53 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-04 02:07:53 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-04 02:07:53 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-04 02:07:53 (10888) [INFO] * 2026-02-04 02:07:54 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-04 02:07:54 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-04 02:07:54 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-04 02:07:54 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-04 02:07:54 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-04 02:07:54 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-04 02:07:54 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-04 02:07:54 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-04 02:07:54 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-04 02:07:54 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-04 02:07:54 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-04 02:07:54 (10901) [INFO] Other repos take up 988 k of disk space (use --verbose for details) * 2026-02-04 02:07:54 (10918) [INFO] * 2026-02-04 02:07:54 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-04 02:07:54 (10888) [INFO] * 2026-02-04 02:07:55 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-04 02:07:55 (10901) [INFO] Determining fastest mirrors * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-04 02:08:25 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-04 02:08:25 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-04 02:08:25 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-04 02:08:25 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-04 02:08:25 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-04 02:08:25 (10901) [INFO] yum --disablerepo= ... * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-04 02:08:25 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-04 02:08:25 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] yum-config-manager --disable * 2026-02-04 02:08:25 (10901) [INFO] or * 2026-02-04 02:08:25 (10901) [INFO] subscription-manager repos --disable= * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-04 02:08:25 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-04 02:08:25 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-04 02:08:25 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-04 02:08:25 (10901) [INFO] compromise: * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-04 02:08:25 (10901) [INFO] * 2026-02-04 02:08:25 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-04 02:08:25 (10918) [INFO] * 2026-02-04 02:08:25 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-04 02:08:25 (6735) [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 * 2026-02-04 02:08:27 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-04 02:08:27 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-04 02:08:27 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-04 02:08:27 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-04 02:08:27 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-04 02:08:35 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ODhooGnQSE/ea_profile.json * 2026-02-04 02:11:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ODhooGnQSE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-04 02:11:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-05 01:38:35 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-05 01:42:35 (11991) [INFO] Script is up to date. * 2026-02-05 01:46:39 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-05 01:46:39 (10888) [INFO] * 2026-02-05 01:47:56 (10918) [INFO] * 2026-02-05 01:47:56 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-05 01:47:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-05 01:47:56 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-05 01:47:57 (10888) [INFO] * 2026-02-05 01:48:00 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-05 01:48:00 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-05 01:48:00 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-05 01:48:00 (10888) [INFO] * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-05 01:48:34 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-05 01:48:34 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-05 01:48:34 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-05 01:48:34 (10888) [INFO] * 2026-02-05 01:48:34 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-05 01:48:35 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-05 01:49:06 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-05 01:49:06 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-05 01:49:06 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-05 01:49:06 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-05 01:49:06 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-05 01:49:06 (10901) [INFO] yum --disablerepo= ... * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-05 01:49:06 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-05 01:49:06 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] yum-config-manager --disable * 2026-02-05 01:49:06 (10901) [INFO] or * 2026-02-05 01:49:06 (10901) [INFO] subscription-manager repos --disable= * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-05 01:49:06 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-05 01:49:06 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-05 01:49:06 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-05 01:49:06 (10901) [INFO] compromise: * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-05 01:49:06 (10901) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-05 01:49:06 (10918) [INFO] * 2026-02-05 01:49:06 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-05 01:49:06 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-05 01:49:06 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-05 01:49:06 (10888) [INFO] * 2026-02-05 01:49:06 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-05 01:49:06 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-05 01:49:06 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-05 01:49:06 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-05 01:49:06 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-05 01:49:06 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-05 01:49:06 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-05 01:49:06 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-05 01:49:06 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-05 01:49:06 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-05 01:49:06 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-05 01:49:06 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-05 01:49:06 (10918) [INFO] * 2026-02-05 01:49:06 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-05 01:49:06 (10888) [INFO] * 2026-02-05 01:49:07 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-05 01:49:07 (10901) [INFO] Determining fastest mirrors * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-05 01:49:38 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-05 01:49:38 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-05 01:49:38 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-05 01:49:38 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-05 01:49:38 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-05 01:49:38 (10901) [INFO] yum --disablerepo= ... * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-05 01:49:38 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-05 01:49:38 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] yum-config-manager --disable * 2026-02-05 01:49:38 (10901) [INFO] or * 2026-02-05 01:49:38 (10901) [INFO] subscription-manager repos --disable= * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-05 01:49:38 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-05 01:49:38 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-05 01:49:38 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-05 01:49:38 (10901) [INFO] compromise: * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-05 01:49:38 (10901) [INFO] * 2026-02-05 01:49:38 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-05 01:49:38 (10918) [INFO] * 2026-02-05 01:49:38 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-05 01:49:38 (6735) [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 * 2026-02-05 01:49:40 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-05 01:49:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-05 01:49:40 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-05 01:49:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-05 01:49:40 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-05 01:49:46 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/l1jNhacFSZ/ea_profile.json * 2026-02-05 01:52:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/l1jNhacFSZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-05 01:52:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-06 01:38:42 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-06 01:42:43 (11991) [INFO] Script is up to date. * 2026-02-06 01:46:46 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-06 01:46:46 (10888) [INFO] * 2026-02-06 01:48:08 (10918) [INFO] * 2026-02-06 01:48:08 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-06 01:48:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-06 01:48:08 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-06 01:48:08 (10888) [INFO] * 2026-02-06 01:51:17 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-06 01:51:17 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-06 01:51:17 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-06 01:51:17 (10888) [INFO] * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-06 01:51:52 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-06 01:51:52 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-06 01:51:52 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-06 01:51:52 (10888) [INFO] * 2026-02-06 01:51:53 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-06 01:51:53 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-06 01:52:23 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-06 01:52:23 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-06 01:52:23 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-06 01:52:23 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-06 01:52:23 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-06 01:52:23 (10901) [INFO] yum --disablerepo= ... * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-06 01:52:23 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-06 01:52:23 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] yum-config-manager --disable * 2026-02-06 01:52:23 (10901) [INFO] or * 2026-02-06 01:52:23 (10901) [INFO] subscription-manager repos --disable= * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-06 01:52:23 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-06 01:52:23 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-06 01:52:23 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-06 01:52:23 (10901) [INFO] compromise: * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-06 01:52:23 (10901) [INFO] * 2026-02-06 01:52:23 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-06 01:52:23 (10918) [INFO] * 2026-02-06 01:52:23 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-06 01:52:23 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-06 01:52:23 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-06 01:52:23 (10888) [INFO] * 2026-02-06 01:52:24 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-06 01:52:24 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-06 01:52:24 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-06 01:52:24 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-06 01:52:24 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-06 01:52:24 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-06 01:52:24 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-06 01:52:24 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-06 01:52:24 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-06 01:52:24 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-06 01:52:24 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-06 01:52:24 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-06 01:52:24 (10918) [INFO] * 2026-02-06 01:52:24 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-06 01:52:24 (10888) [INFO] * 2026-02-06 01:52:25 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-06 01:52:25 (10901) [INFO] Determining fastest mirrors * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-06 01:52:56 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-06 01:52:56 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-06 01:52:56 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-06 01:52:56 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-06 01:52:56 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-06 01:52:56 (10901) [INFO] yum --disablerepo= ... * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-06 01:52:56 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-06 01:52:56 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] yum-config-manager --disable * 2026-02-06 01:52:56 (10901) [INFO] or * 2026-02-06 01:52:56 (10901) [INFO] subscription-manager repos --disable= * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-06 01:52:56 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-06 01:52:56 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-06 01:52:56 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-06 01:52:56 (10901) [INFO] compromise: * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-06 01:52:56 (10901) [INFO] * 2026-02-06 01:52:56 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-06 01:52:56 (10918) [INFO] * 2026-02-06 01:52:56 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-06 01:52:56 (6735) [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 * 2026-02-06 01:52:58 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-06 01:52:58 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-06 01:52:58 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-06 01:52:58 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-06 01:52:58 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-06 01:53:03 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kGvdTHoXcu/ea_profile.json * 2026-02-06 01:56:00 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/kGvdTHoXcu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-06 01:56:00 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-07 01:43:05 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-07 01:47:06 (11991) [INFO] Script is up to date. * 2026-02-07 01:51:09 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-07 01:51:09 (10888) [INFO] * 2026-02-07 01:51:58 (10918) [INFO] * 2026-02-07 01:51:58 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-07 01:51:58 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-07 01:51:58 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-07 01:51:58 (10888) [INFO] * 2026-02-07 01:58:15 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-07 01:58:15 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-07 01:58:16 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-07 01:58:16 (10888) [INFO] * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-07 01:58:50 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-07 01:58:50 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-07 01:58:50 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-07 01:58:50 (10888) [INFO] * 2026-02-07 01:58:51 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-07 01:58:51 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-07 01:59:22 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-07 01:59:22 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-07 01:59:22 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-07 01:59:22 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-07 01:59:22 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-07 01:59:22 (10901) [INFO] yum --disablerepo= ... * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-07 01:59:22 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-07 01:59:22 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] yum-config-manager --disable * 2026-02-07 01:59:22 (10901) [INFO] or * 2026-02-07 01:59:22 (10901) [INFO] subscription-manager repos --disable= * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-07 01:59:22 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-07 01:59:22 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-07 01:59:22 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-07 01:59:22 (10901) [INFO] compromise: * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-07 01:59:22 (10901) [INFO] * 2026-02-07 01:59:22 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-07 01:59:22 (10918) [INFO] * 2026-02-07 01:59:22 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-07 01:59:22 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-07 01:59:22 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-07 01:59:22 (10888) [INFO] * 2026-02-07 01:59:23 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-07 01:59:23 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-07 01:59:23 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-07 01:59:23 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-07 01:59:23 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-07 01:59:23 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-07 01:59:23 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-07 01:59:23 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-07 01:59:23 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-07 01:59:23 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-07 01:59:23 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-07 01:59:23 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-07 01:59:24 (10918) [INFO] * 2026-02-07 01:59:24 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-07 01:59:24 (10888) [INFO] * 2026-02-07 01:59:24 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-07 01:59:24 (10901) [INFO] Determining fastest mirrors * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-07 01:59:55 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-07 01:59:55 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-07 01:59:55 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-07 01:59:55 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-07 01:59:55 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-07 01:59:55 (10901) [INFO] yum --disablerepo= ... * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-07 01:59:55 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-07 01:59:55 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] yum-config-manager --disable * 2026-02-07 01:59:55 (10901) [INFO] or * 2026-02-07 01:59:55 (10901) [INFO] subscription-manager repos --disable= * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-07 01:59:55 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-07 01:59:55 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-07 01:59:55 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-07 01:59:55 (10901) [INFO] compromise: * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-07 01:59:55 (10901) [INFO] * 2026-02-07 01:59:55 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-07 01:59:55 (10918) [INFO] * 2026-02-07 01:59:55 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-07 01:59:55 (6735) [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 * 2026-02-07 01:59:57 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-07 01:59:57 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-07 01:59:57 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-07 01:59:57 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-07 01:59:57 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-07 02:00:05 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4w9ueH8n2m/ea_profile.json * 2026-02-07 02:03:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/4w9ueH8n2m/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-07 02:03:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-08 01:40:00 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-08 01:44:00 (11991) [INFO] Script is up to date. * 2026-02-08 01:48:03 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-08 01:48:03 (10888) [INFO] * 2026-02-08 01:48:55 (10918) [INFO] * 2026-02-08 01:48:55 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-08 01:48:55 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-08 01:48:55 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-08 01:48:55 (10888) [INFO] * 2026-02-08 01:55:11 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-08 01:55:11 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-08 01:55:11 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-08 01:55:11 (10888) [INFO] * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-08 01:55:48 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-08 01:55:48 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-08 01:55:48 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-08 01:55:48 (10888) [INFO] * 2026-02-08 01:55:48 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-08 01:55:48 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-08 01:56:19 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-08 01:56:19 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-08 01:56:19 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-08 01:56:19 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-08 01:56:19 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-08 01:56:19 (10901) [INFO] yum --disablerepo= ... * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-08 01:56:19 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-08 01:56:19 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] yum-config-manager --disable * 2026-02-08 01:56:19 (10901) [INFO] or * 2026-02-08 01:56:19 (10901) [INFO] subscription-manager repos --disable= * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-08 01:56:19 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-08 01:56:19 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-08 01:56:19 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-08 01:56:19 (10901) [INFO] compromise: * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-08 01:56:19 (10901) [INFO] * 2026-02-08 01:56:19 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-08 01:56:19 (10918) [INFO] * 2026-02-08 01:56:19 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-08 01:56:19 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-08 01:56:19 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-08 01:56:19 (10888) [INFO] * 2026-02-08 01:56:20 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-08 01:56:20 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-08 01:56:20 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-08 01:56:20 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-08 01:56:20 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-08 01:56:20 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-08 01:56:20 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-08 01:56:20 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-08 01:56:20 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-08 01:56:20 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-08 01:56:20 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-08 01:56:20 (10901) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-08 01:56:20 (10918) [INFO] * 2026-02-08 01:56:20 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-08 01:56:20 (10888) [INFO] * 2026-02-08 01:56:21 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-08 01:56:21 (10901) [INFO] Determining fastest mirrors * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-08 01:56:52 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-08 01:56:52 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-08 01:56:52 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-08 01:56:52 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-08 01:56:52 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-08 01:56:52 (10901) [INFO] yum --disablerepo= ... * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-08 01:56:52 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-08 01:56:52 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] yum-config-manager --disable * 2026-02-08 01:56:52 (10901) [INFO] or * 2026-02-08 01:56:52 (10901) [INFO] subscription-manager repos --disable= * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-08 01:56:52 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-08 01:56:52 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-08 01:56:52 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-08 01:56:52 (10901) [INFO] compromise: * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-08 01:56:52 (10901) [INFO] * 2026-02-08 01:56:52 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-08 01:56:52 (10918) [INFO] * 2026-02-08 01:56:52 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-08 01:56:52 (6735) [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 * 2026-02-08 01:56:54 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-08 01:56:54 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-08 01:56:54 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-08 01:56:54 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-08 01:56:54 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-08 01:57:00 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Zcj_0nCyN1/ea_profile.json * 2026-02-08 01:59:58 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Zcj_0nCyN1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-08 01:59:58 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-09 01:39:12 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-09 01:43:13 (11991) [INFO] Script is up to date. * 2026-02-09 01:47:16 (10887) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-09 01:47:16 (10888) [INFO] * 2026-02-09 01:48:37 (10918) [INFO] * 2026-02-09 01:48:37 (7144) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-09 01:48:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-09 01:48:38 (10887) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-09 01:48:38 (10888) [INFO] * 2026-02-09 01:48:41 (4527) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-09 01:48:41 (4534) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-09 01:48:41 (10887) [INFO] Running: /usr/bin/yum list extras * 2026-02-09 01:48:41 (10888) [INFO] * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-09 01:49:17 (6875) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-09 01:49:17 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-09 01:49:17 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-09 01:49:17 (10888) [INFO] * 2026-02-09 01:49:17 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-09 01:49:18 (10901) [INFO] Loading mirror speeds from cached hostfile * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-09 01:49:49 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-09 01:49:49 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-09 01:49:49 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-09 01:49:49 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-09 01:49:49 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-09 01:49:49 (10901) [INFO] yum --disablerepo= ... * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-09 01:49:49 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-09 01:49:49 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] yum-config-manager --disable * 2026-02-09 01:49:49 (10901) [INFO] or * 2026-02-09 01:49:49 (10901) [INFO] subscription-manager repos --disable= * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-09 01:49:49 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-09 01:49:49 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-09 01:49:49 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-09 01:49:49 (10901) [INFO] compromise: * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-09 01:49:49 (10901) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-09 01:49:49 (10918) [INFO] * 2026-02-09 01:49:49 (6724) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-09 01:49:49 (6725) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-09 01:49:49 (10887) [INFO] Running: /usr/bin/yum clean all * 2026-02-09 01:49:49 (10888) [INFO] * 2026-02-09 01:49:49 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-09 01:49:50 (10901) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-09 01:49:50 (10901) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-09 01:49:50 (10901) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-09 01:49:50 (10901) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-09 01:49:50 (10901) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-09 01:49:50 (10901) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-09 01:49:50 (10901) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-09 01:49:50 (10901) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-09 01:49:50 (10901) [INFO] : wp-toolkit-thirdparties * 2026-02-09 01:49:50 (10901) [INFO] Cleaning up list of fastest mirrors * 2026-02-09 01:49:50 (10901) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-09 01:49:50 (10918) [INFO] * 2026-02-09 01:49:50 (10887) [INFO] Running: /usr/bin/yum makecache * 2026-02-09 01:49:50 (10888) [INFO] * 2026-02-09 01:49:50 (10901) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-09 01:49:51 (10901) [INFO] Determining fastest mirrors * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] One of the configured repositories failed (Unknown), * 2026-02-09 01:50:21 (10901) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-09 01:50:21 (10901) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-09 01:50:21 (10901) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-09 01:50:21 (10901) [INFO] distribution release than is supported by the repository (and the * 2026-02-09 01:50:21 (10901) [INFO] packages for the previous distribution release still work). * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-09 01:50:21 (10901) [INFO] yum --disablerepo= ... * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-09 01:50:21 (10901) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-09 01:50:21 (10901) [INFO] again or use --enablerepo for temporary usage: * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] yum-config-manager --disable * 2026-02-09 01:50:21 (10901) [INFO] or * 2026-02-09 01:50:21 (10901) [INFO] subscription-manager repos --disable= * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-09 01:50:21 (10901) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-09 01:50:21 (10901) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-09 01:50:21 (10901) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-09 01:50:21 (10901) [INFO] compromise: * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-09 01:50:21 (10901) [INFO] * 2026-02-09 01:50:21 (10901) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-09 01:50:21 (10918) [INFO] * 2026-02-09 01:50:21 (6734) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-09 01:50:21 (6735) [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 * 2026-02-09 01:50:23 (3670) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-09 01:50:23 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-09 01:50:23 (4974) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-09 01:50:23 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-09 01:50:23 (2406) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-09 01:50:29 (9997) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1xmhefIfcB/ea_profile.json * 2026-02-09 01:52:57 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1xmhefIfcB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9999. * 2026-02-09 01:52:57 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-10 01:39:01 (11969) [INFO] Self-update of script version 77 requested. * 2026-02-10 01:43:01 (11974) [INFO] Newer version of script found. Downloading. * 2026-02-10 01:47:02 (11983) [INFO] Script update to version 78 successful. * 2026-02-10 01:51:05 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-10 01:51:05 (10883) [INFO] * 2026-02-10 01:52:18 (10913) [INFO] * 2026-02-10 01:52:18 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-10 01:52:19 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-10 01:52:19 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-10 01:52:19 (10883) [INFO] * 2026-02-10 01:58:33 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-10 01:58:33 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-10 01:58:33 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-10 01:58:33 (10883) [INFO] * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-10 01:59:08 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-10 01:59:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-10 01:59:08 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-10 01:59:08 (10883) [INFO] * 2026-02-10 01:59:08 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-10 01:59:08 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-10 01:59:39 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-10 01:59:39 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-10 01:59:39 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-10 01:59:39 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-10 01:59:39 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-10 01:59:39 (10896) [INFO] yum --disablerepo= ... * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-10 01:59:39 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-10 01:59:39 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] yum-config-manager --disable * 2026-02-10 01:59:39 (10896) [INFO] or * 2026-02-10 01:59:39 (10896) [INFO] subscription-manager repos --disable= * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-10 01:59:39 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-10 01:59:39 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-10 01:59:39 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-10 01:59:39 (10896) [INFO] compromise: * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-10 01:59:39 (10896) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-10 01:59:39 (10913) [INFO] * 2026-02-10 01:59:39 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-10 01:59:39 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-10 01:59:39 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-10 01:59:39 (10883) [INFO] * 2026-02-10 01:59:39 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-10 01:59:40 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-10 01:59:40 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-10 01:59:40 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-10 01:59:40 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-10 01:59:40 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-10 01:59:40 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-10 01:59:40 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-10 01:59:40 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-10 01:59:40 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-10 01:59:40 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-10 01:59:40 (10896) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-10 01:59:40 (10913) [INFO] * 2026-02-10 01:59:40 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-10 01:59:40 (10883) [INFO] * 2026-02-10 01:59:40 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-10 01:59:41 (10896) [INFO] Determining fastest mirrors * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-10 02:00:11 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-10 02:00:11 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-10 02:00:11 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-10 02:00:11 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-10 02:00:11 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-10 02:00:11 (10896) [INFO] yum --disablerepo= ... * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-10 02:00:11 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-10 02:00:11 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] yum-config-manager --disable * 2026-02-10 02:00:11 (10896) [INFO] or * 2026-02-10 02:00:11 (10896) [INFO] subscription-manager repos --disable= * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-10 02:00:11 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-10 02:00:11 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-10 02:00:11 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-10 02:00:11 (10896) [INFO] compromise: * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-10 02:00:11 (10896) [INFO] * 2026-02-10 02:00:11 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-10 02:00:11 (10913) [INFO] * 2026-02-10 02:00:11 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-10 02:00:11 (6727) [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 * 2026-02-10 02:00:13 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-10 02:00:13 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-10 02:00:13 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-10 02:00:13 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-10 02:00:13 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-10 02:00:19 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GllwLFkEMs/ea_profile.json * 2026-02-10 02:02:46 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GllwLFkEMs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-10 02:02:46 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-11 01:38:33 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-11 01:42:34 (11986) [INFO] Script is up to date. * 2026-02-11 01:46:37 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-11 01:46:37 (10883) [INFO] * 2026-02-11 01:47:56 (10913) [INFO] * 2026-02-11 01:47:56 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-11 01:47:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-11 01:47:57 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-11 01:47:57 (10883) [INFO] * 2026-02-11 01:48:00 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-11 01:48:00 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-11 01:48:00 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-11 01:48:00 (10883) [INFO] * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-11 01:48:35 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-11 01:48:35 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-11 01:48:35 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-11 01:48:35 (10883) [INFO] * 2026-02-11 01:48:36 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-11 01:48:36 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-11 01:49:07 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-11 01:49:07 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-11 01:49:07 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-11 01:49:07 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-11 01:49:07 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-11 01:49:07 (10896) [INFO] yum --disablerepo= ... * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-11 01:49:07 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-11 01:49:07 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] yum-config-manager --disable * 2026-02-11 01:49:07 (10896) [INFO] or * 2026-02-11 01:49:07 (10896) [INFO] subscription-manager repos --disable= * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-11 01:49:07 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-11 01:49:07 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-11 01:49:07 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-11 01:49:07 (10896) [INFO] compromise: * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-11 01:49:07 (10896) [INFO] * 2026-02-11 01:49:07 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-11 01:49:07 (10913) [INFO] * 2026-02-11 01:49:07 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-11 01:49:07 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-11 01:49:07 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-11 01:49:07 (10883) [INFO] * 2026-02-11 01:49:08 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-11 01:49:08 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-11 01:49:08 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-11 01:49:08 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-11 01:49:08 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-11 01:49:08 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-11 01:49:08 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-11 01:49:08 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-11 01:49:08 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-11 01:49:08 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-11 01:49:08 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-11 01:49:08 (10896) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-11 01:49:09 (10913) [INFO] * 2026-02-11 01:49:09 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-11 01:49:09 (10883) [INFO] * 2026-02-11 01:49:09 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-11 01:49:09 (10896) [INFO] Determining fastest mirrors * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-11 01:49:40 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-11 01:49:40 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-11 01:49:40 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-11 01:49:40 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-11 01:49:40 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-11 01:49:40 (10896) [INFO] yum --disablerepo= ... * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-11 01:49:40 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-11 01:49:40 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] yum-config-manager --disable * 2026-02-11 01:49:40 (10896) [INFO] or * 2026-02-11 01:49:40 (10896) [INFO] subscription-manager repos --disable= * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-11 01:49:40 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-11 01:49:40 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-11 01:49:40 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-11 01:49:40 (10896) [INFO] compromise: * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-11 01:49:40 (10896) [INFO] * 2026-02-11 01:49:40 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-11 01:49:40 (10913) [INFO] * 2026-02-11 01:49:40 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-11 01:49:40 (6727) [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 * 2026-02-11 01:49:42 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-11 01:49:42 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-11 01:49:42 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-11 01:49:42 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-11 01:49:42 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-11 01:49:48 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sICIryoebv/ea_profile.json * 2026-02-11 01:52:16 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/sICIryoebv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-11 01:52:16 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-12 01:39:43 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-12 01:43:43 (11986) [INFO] Script is up to date. * 2026-02-12 01:47:47 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-12 01:47:47 (10883) [INFO] * 2026-02-12 01:49:05 (10913) [INFO] * 2026-02-12 01:49:05 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-12 01:49:06 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-12 01:49:06 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-12 01:49:06 (10883) [INFO] * 2026-02-12 01:51:19 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-12 01:51:19 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-12 01:51:19 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-12 01:51:19 (10883) [INFO] * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-12 01:51:55 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-12 01:51:55 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-12 01:51:55 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-12 01:51:55 (10883) [INFO] * 2026-02-12 01:51:55 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-12 01:51:56 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-12 01:52:27 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-12 01:52:27 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-12 01:52:27 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-12 01:52:27 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-12 01:52:27 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-12 01:52:27 (10896) [INFO] yum --disablerepo= ... * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-12 01:52:27 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-12 01:52:27 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] yum-config-manager --disable * 2026-02-12 01:52:27 (10896) [INFO] or * 2026-02-12 01:52:27 (10896) [INFO] subscription-manager repos --disable= * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-12 01:52:27 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-12 01:52:27 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-12 01:52:27 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-12 01:52:27 (10896) [INFO] compromise: * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-12 01:52:27 (10896) [INFO] * 2026-02-12 01:52:27 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-12 01:52:27 (10913) [INFO] * 2026-02-12 01:52:27 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-12 01:52:27 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-12 01:52:27 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-12 01:52:27 (10883) [INFO] * 2026-02-12 01:52:28 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-12 01:52:28 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-12 01:52:28 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-12 01:52:28 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-12 01:52:28 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-12 01:52:28 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-12 01:52:28 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-12 01:52:28 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-12 01:52:28 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-12 01:52:28 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-12 01:52:28 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-12 01:52:28 (10896) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-12 01:52:28 (10913) [INFO] * 2026-02-12 01:52:28 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-12 01:52:28 (10883) [INFO] * 2026-02-12 01:52:28 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-12 01:52:28 (10896) [INFO] Determining fastest mirrors * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-12 01:52:59 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-12 01:52:59 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-12 01:52:59 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-12 01:52:59 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-12 01:52:59 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-12 01:52:59 (10896) [INFO] yum --disablerepo= ... * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-12 01:52:59 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-12 01:52:59 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] yum-config-manager --disable * 2026-02-12 01:52:59 (10896) [INFO] or * 2026-02-12 01:52:59 (10896) [INFO] subscription-manager repos --disable= * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-12 01:52:59 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-12 01:52:59 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-12 01:52:59 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-12 01:52:59 (10896) [INFO] compromise: * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-12 01:52:59 (10896) [INFO] * 2026-02-12 01:52:59 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-12 01:52:59 (10913) [INFO] * 2026-02-12 01:52:59 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-12 01:52:59 (6727) [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 * 2026-02-12 01:53:01 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-12 01:53:01 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-12 01:53:01 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-12 01:53:01 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-12 01:53:01 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-12 01:53:08 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mEiMw6LnDq/ea_profile.json * 2026-02-12 01:56:06 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mEiMw6LnDq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-12 01:56:06 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-13 01:42:25 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-13 01:46:25 (11986) [INFO] Script is up to date. * 2026-02-13 01:50:28 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-13 01:50:28 (10883) [INFO] * 2026-02-13 01:51:45 (10913) [INFO] * 2026-02-13 01:51:45 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-13 01:51:46 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-13 01:51:46 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-13 01:51:46 (10883) [INFO] * 2026-02-13 01:58:03 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-13 01:58:03 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-13 01:58:03 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-13 01:58:03 (10883) [INFO] * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-13 01:58:38 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-13 01:58:38 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-13 01:58:38 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-13 01:58:38 (10883) [INFO] * 2026-02-13 01:58:38 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-13 01:58:39 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-13 01:59:10 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-13 01:59:10 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-13 01:59:10 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-13 01:59:10 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-13 01:59:10 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-13 01:59:10 (10896) [INFO] yum --disablerepo= ... * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-13 01:59:10 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-13 01:59:10 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] yum-config-manager --disable * 2026-02-13 01:59:10 (10896) [INFO] or * 2026-02-13 01:59:10 (10896) [INFO] subscription-manager repos --disable= * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-13 01:59:10 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-13 01:59:10 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-13 01:59:10 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-13 01:59:10 (10896) [INFO] compromise: * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-13 01:59:10 (10896) [INFO] * 2026-02-13 01:59:10 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-13 01:59:10 (10913) [INFO] * 2026-02-13 01:59:10 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-13 01:59:10 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-13 01:59:10 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-13 01:59:10 (10883) [INFO] * 2026-02-13 01:59:11 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-13 01:59:11 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-13 01:59:11 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-13 01:59:11 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-13 01:59:11 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-13 01:59:11 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-13 01:59:11 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-13 01:59:11 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-13 01:59:11 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-13 01:59:11 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-13 01:59:11 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-13 01:59:11 (10896) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-13 01:59:11 (10913) [INFO] * 2026-02-13 01:59:11 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-13 01:59:11 (10883) [INFO] * 2026-02-13 01:59:11 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-13 01:59:12 (10896) [INFO] Determining fastest mirrors * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-13 01:59:42 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-13 01:59:42 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-13 01:59:42 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-13 01:59:42 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-13 01:59:42 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-13 01:59:42 (10896) [INFO] yum --disablerepo= ... * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-13 01:59:42 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-13 01:59:42 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] yum-config-manager --disable * 2026-02-13 01:59:42 (10896) [INFO] or * 2026-02-13 01:59:42 (10896) [INFO] subscription-manager repos --disable= * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-13 01:59:42 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-13 01:59:42 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-13 01:59:42 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-13 01:59:42 (10896) [INFO] compromise: * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-13 01:59:42 (10896) [INFO] * 2026-02-13 01:59:42 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-13 01:59:42 (10913) [INFO] * 2026-02-13 01:59:42 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-13 01:59:42 (6727) [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 * 2026-02-13 01:59:44 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-13 01:59:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-13 01:59:44 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-13 01:59:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-13 01:59:44 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-13 01:59:51 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MLlSZqPJHj/ea_profile.json * 2026-02-13 02:02:49 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MLlSZqPJHj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-13 02:02:49 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-14 01:39:55 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-14 01:43:55 (11986) [INFO] Script is up to date. * 2026-02-14 01:47:59 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-14 01:47:59 (10883) [INFO] * 2026-02-14 01:48:51 (10913) [INFO] * 2026-02-14 01:48:51 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-14 01:48:51 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-14 01:48:51 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-14 01:48:51 (10883) [INFO] * 2026-02-14 01:55:09 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-14 01:55:09 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-14 01:55:09 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-14 01:55:09 (10883) [INFO] * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-14 01:55:43 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-14 01:55:43 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-14 01:55:43 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-14 01:55:43 (10883) [INFO] * 2026-02-14 01:55:43 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-14 01:55:43 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-14 01:56:14 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-14 01:56:14 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-14 01:56:14 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-14 01:56:14 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-14 01:56:14 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-14 01:56:14 (10896) [INFO] yum --disablerepo= ... * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-14 01:56:14 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-14 01:56:14 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] yum-config-manager --disable * 2026-02-14 01:56:14 (10896) [INFO] or * 2026-02-14 01:56:14 (10896) [INFO] subscription-manager repos --disable= * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-14 01:56:14 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-14 01:56:14 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-14 01:56:14 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-14 01:56:14 (10896) [INFO] compromise: * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-14 01:56:14 (10896) [INFO] * 2026-02-14 01:56:14 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-14 01:56:14 (10913) [INFO] * 2026-02-14 01:56:14 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-14 01:56:14 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-14 01:56:14 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-14 01:56:14 (10883) [INFO] * 2026-02-14 01:56:15 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-14 01:56:15 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-14 01:56:15 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-14 01:56:15 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-14 01:56:15 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-14 01:56:15 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-14 01:56:15 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-14 01:56:15 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-14 01:56:15 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-14 01:56:15 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-14 01:56:15 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-14 01:56:15 (10896) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-14 01:56:15 (10913) [INFO] * 2026-02-14 01:56:15 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-14 01:56:15 (10883) [INFO] * 2026-02-14 01:56:15 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-14 01:56:16 (10896) [INFO] Determining fastest mirrors * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-14 01:56:47 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-14 01:56:47 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-14 01:56:47 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-14 01:56:47 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-14 01:56:47 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-14 01:56:47 (10896) [INFO] yum --disablerepo= ... * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-14 01:56:47 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-14 01:56:47 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] yum-config-manager --disable * 2026-02-14 01:56:47 (10896) [INFO] or * 2026-02-14 01:56:47 (10896) [INFO] subscription-manager repos --disable= * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-14 01:56:47 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-14 01:56:47 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-14 01:56:47 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-14 01:56:47 (10896) [INFO] compromise: * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-14 01:56:47 (10896) [INFO] * 2026-02-14 01:56:47 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-14 01:56:47 (10913) [INFO] * 2026-02-14 01:56:47 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-14 01:56:47 (6727) [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 * 2026-02-14 01:56:49 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-14 01:56:49 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-14 01:56:49 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-14 01:56:49 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-14 01:56:49 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-14 01:56:55 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NlLqhmNhxe/ea_profile.json * 2026-02-14 01:59:22 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NlLqhmNhxe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-14 01:59:22 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-15 01:39:56 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-15 01:43:57 (11986) [INFO] Script is up to date. * 2026-02-15 01:48:00 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-15 01:48:00 (10883) [INFO] * 2026-02-15 01:48:53 (10913) [INFO] * 2026-02-15 01:48:53 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-15 01:48:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-15 01:48:53 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-15 01:48:53 (10883) [INFO] * 2026-02-15 01:55:11 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-15 01:55:11 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-15 01:55:11 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-15 01:55:11 (10883) [INFO] * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-15 01:55:47 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-15 01:55:47 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-15 01:55:47 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-15 01:55:47 (10883) [INFO] * 2026-02-15 01:55:48 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-15 01:55:48 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-15 01:56:19 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-15 01:56:19 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-15 01:56:19 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-15 01:56:19 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-15 01:56:19 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-15 01:56:19 (10896) [INFO] yum --disablerepo= ... * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-15 01:56:19 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-15 01:56:19 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] yum-config-manager --disable * 2026-02-15 01:56:19 (10896) [INFO] or * 2026-02-15 01:56:19 (10896) [INFO] subscription-manager repos --disable= * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-15 01:56:19 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-15 01:56:19 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-15 01:56:19 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-15 01:56:19 (10896) [INFO] compromise: * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-15 01:56:19 (10896) [INFO] * 2026-02-15 01:56:19 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-15 01:56:20 (10913) [INFO] * 2026-02-15 01:56:20 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-15 01:56:20 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-15 01:56:20 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-15 01:56:20 (10883) [INFO] * 2026-02-15 01:56:20 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-15 01:56:20 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-15 01:56:20 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-15 01:56:20 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-15 01:56:20 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-15 01:56:20 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-15 01:56:20 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-15 01:56:20 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-15 01:56:20 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-15 01:56:20 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-15 01:56:20 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-15 01:56:20 (10896) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-15 01:56:20 (10913) [INFO] * 2026-02-15 01:56:20 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-15 01:56:20 (10883) [INFO] * 2026-02-15 01:56:21 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-15 01:56:21 (10896) [INFO] Determining fastest mirrors * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-15 01:56:52 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-15 01:56:52 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-15 01:56:52 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-15 01:56:52 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-15 01:56:52 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-15 01:56:52 (10896) [INFO] yum --disablerepo= ... * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-15 01:56:52 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-15 01:56:52 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] yum-config-manager --disable * 2026-02-15 01:56:52 (10896) [INFO] or * 2026-02-15 01:56:52 (10896) [INFO] subscription-manager repos --disable= * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-15 01:56:52 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-15 01:56:52 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-15 01:56:52 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-15 01:56:52 (10896) [INFO] compromise: * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-15 01:56:52 (10896) [INFO] * 2026-02-15 01:56:52 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-15 01:56:52 (10913) [INFO] * 2026-02-15 01:56:52 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-15 01:56:52 (6727) [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 * 2026-02-15 01:56:54 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-15 01:56:54 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-15 01:56:54 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-15 01:56:54 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-15 01:56:54 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-15 01:57:01 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QrlRPSGgNN/ea_profile.json * 2026-02-15 01:59:29 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QrlRPSGgNN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-15 01:59:29 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-16 01:38:40 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-16 01:42:40 (11986) [INFO] Script is up to date. * 2026-02-16 01:46:43 (10882) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-16 01:46:43 (10883) [INFO] * 2026-02-16 01:48:04 (10913) [INFO] * 2026-02-16 01:48:04 (7136) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-16 01:48:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-16 01:48:04 (10882) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-16 01:48:04 (10883) [INFO] * 2026-02-16 01:55:07 (4519) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-16 01:55:07 (4526) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-16 01:55:08 (10882) [INFO] Running: /usr/bin/yum list extras * 2026-02-16 01:55:08 (10883) [INFO] * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-16 01:55:44 (6867) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-16 01:55:44 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-16 01:55:44 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-16 01:55:44 (10883) [INFO] * 2026-02-16 01:55:44 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-16 01:55:44 (10896) [INFO] Loading mirror speeds from cached hostfile * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-16 01:56:15 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-16 01:56:15 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-16 01:56:15 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-16 01:56:15 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-16 01:56:15 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-16 01:56:15 (10896) [INFO] yum --disablerepo= ... * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-16 01:56:15 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-16 01:56:15 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] yum-config-manager --disable * 2026-02-16 01:56:15 (10896) [INFO] or * 2026-02-16 01:56:15 (10896) [INFO] subscription-manager repos --disable= * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-16 01:56:15 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-16 01:56:15 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-16 01:56:15 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-16 01:56:15 (10896) [INFO] compromise: * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-16 01:56:15 (10896) [INFO] * 2026-02-16 01:56:15 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-16 01:56:15 (10913) [INFO] * 2026-02-16 01:56:15 (6716) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-16 01:56:15 (6717) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-16 01:56:15 (10882) [INFO] Running: /usr/bin/yum clean all * 2026-02-16 01:56:15 (10883) [INFO] * 2026-02-16 01:56:16 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-16 01:56:16 (10896) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-16 01:56:16 (10896) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-16 01:56:16 (10896) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-16 01:56:16 (10896) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-16 01:56:16 (10896) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-16 01:56:16 (10896) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-16 01:56:16 (10896) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-16 01:56:16 (10896) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-16 01:56:16 (10896) [INFO] : wp-toolkit-thirdparties * 2026-02-16 01:56:16 (10896) [INFO] Cleaning up list of fastest mirrors * 2026-02-16 01:56:16 (10896) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-16 01:56:16 (10913) [INFO] * 2026-02-16 01:56:16 (10882) [INFO] Running: /usr/bin/yum makecache * 2026-02-16 01:56:16 (10883) [INFO] * 2026-02-16 01:56:17 (10896) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-16 01:56:17 (10896) [INFO] Determining fastest mirrors * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] One of the configured repositories failed (Unknown), * 2026-02-16 01:56:49 (10896) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-16 01:56:49 (10896) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-16 01:56:49 (10896) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-16 01:56:49 (10896) [INFO] distribution release than is supported by the repository (and the * 2026-02-16 01:56:49 (10896) [INFO] packages for the previous distribution release still work). * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-16 01:56:49 (10896) [INFO] yum --disablerepo= ... * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-16 01:56:49 (10896) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-16 01:56:49 (10896) [INFO] again or use --enablerepo for temporary usage: * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] yum-config-manager --disable * 2026-02-16 01:56:49 (10896) [INFO] or * 2026-02-16 01:56:49 (10896) [INFO] subscription-manager repos --disable= * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-16 01:56:49 (10896) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-16 01:56:49 (10896) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-16 01:56:49 (10896) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-16 01:56:49 (10896) [INFO] compromise: * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-16 01:56:49 (10896) [INFO] * 2026-02-16 01:56:49 (10896) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-16 01:56:49 (10913) [INFO] * 2026-02-16 01:56:49 (6726) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-16 01:56:49 (6727) [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 * 2026-02-16 01:56:50 (3662) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-16 01:56:50 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-16 01:56:50 (4966) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-16 01:56:50 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-16 01:56:50 (2398) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-16 01:56:57 (9992) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NrNrth9I5b/ea_profile.json * 2026-02-16 01:59:26 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/NrNrth9I5b/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9994. * 2026-02-16 01:59:26 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-17 01:44:41 (11964) [INFO] Self-update of script version 78 requested. * 2026-02-17 01:48:41 (11969) [INFO] Newer version of script found. Downloading. * 2026-02-17 01:52:43 (11978) [INFO] Script update to version 79 successful. * 2026-02-17 01:56:47 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-17 01:56:47 (10960) [INFO] * 2026-02-17 01:58:05 (10990) [INFO] * 2026-02-17 01:58:05 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-17 01:58:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-17 01:58:05 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-17 01:58:05 (10960) [INFO] * 2026-02-17 02:02:04 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-17 02:02:04 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-17 02:02:04 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-17 02:02:04 (10960) [INFO] * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-17 02:02:39 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-17 02:02:39 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-17 02:02:39 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-17 02:02:39 (10960) [INFO] * 2026-02-17 02:02:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-17 02:02:40 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-17 02:03:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-17 02:03:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-17 02:03:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-17 02:03:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-17 02:03:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-17 02:03:11 (10973) [INFO] yum --disablerepo= ... * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-17 02:03:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-17 02:03:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] yum-config-manager --disable * 2026-02-17 02:03:11 (10973) [INFO] or * 2026-02-17 02:03:11 (10973) [INFO] subscription-manager repos --disable= * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-17 02:03:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-17 02:03:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-17 02:03:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-17 02:03:11 (10973) [INFO] compromise: * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-17 02:03:11 (10973) [INFO] * 2026-02-17 02:03:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-17 02:03:11 (10990) [INFO] * 2026-02-17 02:03:11 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-17 02:03:11 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-17 02:03:11 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-17 02:03:11 (10960) [INFO] * 2026-02-17 02:03:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-17 02:03:12 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-17 02:03:12 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-17 02:03:12 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-17 02:03:12 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-17 02:03:12 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-17 02:03:12 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-17 02:03:12 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-17 02:03:12 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-17 02:03:12 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-17 02:03:12 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-17 02:03:12 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-17 02:03:12 (10990) [INFO] * 2026-02-17 02:03:12 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-17 02:03:12 (10960) [INFO] * 2026-02-17 02:03:13 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-17 02:03:13 (10973) [INFO] Determining fastest mirrors * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-17 02:03:43 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-17 02:03:43 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-17 02:03:43 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-17 02:03:43 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-17 02:03:43 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-17 02:03:43 (10973) [INFO] yum --disablerepo= ... * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-17 02:03:43 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-17 02:03:43 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] yum-config-manager --disable * 2026-02-17 02:03:43 (10973) [INFO] or * 2026-02-17 02:03:43 (10973) [INFO] subscription-manager repos --disable= * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-17 02:03:43 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-17 02:03:43 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-17 02:03:43 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-17 02:03:43 (10973) [INFO] compromise: * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-17 02:03:43 (10973) [INFO] * 2026-02-17 02:03:43 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-17 02:03:43 (10990) [INFO] * 2026-02-17 02:03:43 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-17 02:03:43 (6792) [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 * 2026-02-17 02:03:45 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-17 02:03:45 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-17 02:03:45 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-17 02:03:45 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-17 02:03:45 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-17 02:03:51 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YnFg11w8Wm/ea_profile.json * 2026-02-17 02:06:50 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YnFg11w8Wm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-17 02:06:50 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-18 01:39:10 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-18 01:43:10 (12063) [INFO] Script is up to date. * 2026-02-18 01:47:14 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-18 01:47:14 (10960) [INFO] * 2026-02-18 01:48:27 (10990) [INFO] * 2026-02-18 01:48:27 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-18 01:48:27 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-18 01:48:27 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-18 01:48:27 (10960) [INFO] * 2026-02-18 01:48:31 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-18 01:48:31 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-18 01:48:31 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-18 01:48:31 (10960) [INFO] * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-18 01:49:05 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-18 01:49:05 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-18 01:49:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-18 01:49:05 (10960) [INFO] * 2026-02-18 01:49:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-18 01:49:06 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-18 01:49:37 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-18 01:49:37 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-18 01:49:37 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-18 01:49:37 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-18 01:49:37 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-18 01:49:37 (10973) [INFO] yum --disablerepo= ... * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-18 01:49:37 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-18 01:49:37 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] yum-config-manager --disable * 2026-02-18 01:49:37 (10973) [INFO] or * 2026-02-18 01:49:37 (10973) [INFO] subscription-manager repos --disable= * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-18 01:49:37 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-18 01:49:37 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-18 01:49:37 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-18 01:49:37 (10973) [INFO] compromise: * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-18 01:49:37 (10973) [INFO] * 2026-02-18 01:49:37 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-18 01:49:37 (10990) [INFO] * 2026-02-18 01:49:37 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-18 01:49:37 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-18 01:49:37 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-18 01:49:37 (10960) [INFO] * 2026-02-18 01:49:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-18 01:49:38 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-18 01:49:38 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-18 01:49:38 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-18 01:49:38 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-18 01:49:38 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-18 01:49:38 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-18 01:49:38 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-18 01:49:38 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-18 01:49:38 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-18 01:49:38 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-18 01:49:38 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-18 01:49:38 (10990) [INFO] * 2026-02-18 01:49:38 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-18 01:49:38 (10960) [INFO] * 2026-02-18 01:49:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-18 01:49:38 (10973) [INFO] Determining fastest mirrors * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-18 01:50:09 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-18 01:50:09 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-18 01:50:09 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-18 01:50:09 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-18 01:50:09 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-18 01:50:09 (10973) [INFO] yum --disablerepo= ... * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-18 01:50:09 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-18 01:50:09 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] yum-config-manager --disable * 2026-02-18 01:50:09 (10973) [INFO] or * 2026-02-18 01:50:09 (10973) [INFO] subscription-manager repos --disable= * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-18 01:50:09 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-18 01:50:09 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-18 01:50:09 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-18 01:50:09 (10973) [INFO] compromise: * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-18 01:50:09 (10973) [INFO] * 2026-02-18 01:50:09 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-18 01:50:09 (10990) [INFO] * 2026-02-18 01:50:09 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-18 01:50:09 (6792) [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 * 2026-02-18 01:50:11 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-18 01:50:11 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-18 01:50:11 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-18 01:50:11 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-18 01:50:11 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-18 01:50:17 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JvOvcLKj45/ea_profile.json * 2026-02-18 01:53:45 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/JvOvcLKj45/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-18 01:53:45 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-19 01:39:06 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-19 01:43:06 (12063) [INFO] Script is up to date. * 2026-02-19 01:47:09 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-19 01:47:09 (10960) [INFO] * 2026-02-19 01:48:30 (10990) [INFO] * 2026-02-19 01:48:30 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-19 01:48:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-19 01:48:30 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-19 01:48:30 (10960) [INFO] * 2026-02-19 01:55:32 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-19 01:55:32 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-19 01:55:32 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-19 01:55:32 (10960) [INFO] * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-19 01:56:05 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-19 01:56:05 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-19 01:56:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-19 01:56:05 (10960) [INFO] * 2026-02-19 01:56:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-19 01:56:06 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-19 01:56:36 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-19 01:56:36 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-19 01:56:36 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-19 01:56:36 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-19 01:56:36 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-19 01:56:36 (10973) [INFO] yum --disablerepo= ... * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-19 01:56:36 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-19 01:56:36 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] yum-config-manager --disable * 2026-02-19 01:56:36 (10973) [INFO] or * 2026-02-19 01:56:36 (10973) [INFO] subscription-manager repos --disable= * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-19 01:56:36 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-19 01:56:36 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-19 01:56:36 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-19 01:56:36 (10973) [INFO] compromise: * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-19 01:56:36 (10973) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-19 01:56:36 (10990) [INFO] * 2026-02-19 01:56:36 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-19 01:56:36 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-19 01:56:36 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-19 01:56:36 (10960) [INFO] * 2026-02-19 01:56:36 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-19 01:56:37 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-19 01:56:37 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-19 01:56:37 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-19 01:56:37 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-19 01:56:37 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-19 01:56:37 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-19 01:56:37 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-19 01:56:37 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-19 01:56:37 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-19 01:56:37 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-19 01:56:37 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-19 01:56:37 (10990) [INFO] * 2026-02-19 01:56:37 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-19 01:56:37 (10960) [INFO] * 2026-02-19 01:56:37 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-19 01:56:38 (10973) [INFO] Determining fastest mirrors * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-19 01:57:08 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-19 01:57:08 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-19 01:57:08 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-19 01:57:08 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-19 01:57:08 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-19 01:57:08 (10973) [INFO] yum --disablerepo= ... * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-19 01:57:08 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-19 01:57:08 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] yum-config-manager --disable * 2026-02-19 01:57:08 (10973) [INFO] or * 2026-02-19 01:57:08 (10973) [INFO] subscription-manager repos --disable= * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-19 01:57:08 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-19 01:57:08 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-19 01:57:08 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-19 01:57:08 (10973) [INFO] compromise: * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-19 01:57:08 (10973) [INFO] * 2026-02-19 01:57:08 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-19 01:57:09 (10990) [INFO] * 2026-02-19 01:57:09 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-19 01:57:09 (6792) [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 * 2026-02-19 01:57:10 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-19 01:57:10 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-19 01:57:10 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-19 01:57:10 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-19 01:57:10 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-19 01:57:17 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/WB1NAmMq_6/ea_profile.json * 2026-02-19 01:59:44 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/WB1NAmMq_6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-19 01:59:44 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-20 01:39:39 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-20 01:43:40 (12063) [INFO] Script is up to date. * 2026-02-20 01:47:43 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-20 01:47:43 (10960) [INFO] * 2026-02-20 01:49:02 (10990) [INFO] * 2026-02-20 01:49:02 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-20 01:49:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-20 01:49:03 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-20 01:49:03 (10960) [INFO] * 2026-02-20 02:00:43 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-20 02:00:43 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-20 02:00:43 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-20 02:00:43 (10960) [INFO] * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-20 02:01:18 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-20 02:01:18 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-20 02:01:18 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-20 02:01:18 (10960) [INFO] * 2026-02-20 02:01:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-20 02:01:19 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-20 02:01:49 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-20 02:01:49 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-20 02:01:49 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-20 02:01:49 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-20 02:01:49 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-20 02:01:49 (10973) [INFO] yum --disablerepo= ... * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-20 02:01:49 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-20 02:01:49 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] yum-config-manager --disable * 2026-02-20 02:01:49 (10973) [INFO] or * 2026-02-20 02:01:49 (10973) [INFO] subscription-manager repos --disable= * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-20 02:01:49 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-20 02:01:49 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-20 02:01:49 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-20 02:01:49 (10973) [INFO] compromise: * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-20 02:01:49 (10973) [INFO] * 2026-02-20 02:01:49 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-20 02:01:49 (10990) [INFO] * 2026-02-20 02:01:49 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-20 02:01:49 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-20 02:01:49 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-20 02:01:49 (10960) [INFO] * 2026-02-20 02:01:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-20 02:01:50 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-20 02:01:50 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-20 02:01:50 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-20 02:01:50 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-20 02:01:50 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-20 02:01:50 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-20 02:01:50 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-20 02:01:50 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-20 02:01:50 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-20 02:01:50 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-20 02:01:50 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-20 02:01:50 (10990) [INFO] * 2026-02-20 02:01:50 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-20 02:01:50 (10960) [INFO] * 2026-02-20 02:01:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-20 02:01:51 (10973) [INFO] Determining fastest mirrors * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-20 02:02:22 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-20 02:02:22 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-20 02:02:22 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-20 02:02:22 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-20 02:02:22 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-20 02:02:22 (10973) [INFO] yum --disablerepo= ... * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-20 02:02:22 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-20 02:02:22 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] yum-config-manager --disable * 2026-02-20 02:02:22 (10973) [INFO] or * 2026-02-20 02:02:22 (10973) [INFO] subscription-manager repos --disable= * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-20 02:02:22 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-20 02:02:22 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-20 02:02:22 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-20 02:02:22 (10973) [INFO] compromise: * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-20 02:02:22 (10973) [INFO] * 2026-02-20 02:02:22 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-20 02:02:22 (10990) [INFO] * 2026-02-20 02:02:22 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-20 02:02:22 (6792) [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 * 2026-02-20 02:02:24 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-20 02:02:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-20 02:02:24 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-20 02:02:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-20 02:02:24 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-20 02:02:30 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9xNOsAL5Wg/ea_profile.json * 2026-02-20 02:04:59 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/9xNOsAL5Wg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-20 02:04:59 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-21 01:39:51 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-21 01:43:52 (12063) [INFO] Script is up to date. * 2026-02-21 01:47:55 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-21 01:47:55 (10960) [INFO] * 2026-02-21 01:48:49 (10990) [INFO] * 2026-02-21 01:48:49 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-21 01:48:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-21 01:48:49 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-21 01:48:49 (10960) [INFO] * 2026-02-21 02:00:12 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-21 02:00:12 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-21 02:00:12 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-21 02:00:12 (10960) [INFO] * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-21 02:00:48 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-21 02:00:48 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-21 02:00:48 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-21 02:00:48 (10960) [INFO] * 2026-02-21 02:00:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-21 02:00:49 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-21 02:01:19 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-21 02:01:19 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-21 02:01:19 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-21 02:01:19 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-21 02:01:19 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-21 02:01:19 (10973) [INFO] yum --disablerepo= ... * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-21 02:01:19 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-21 02:01:19 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] yum-config-manager --disable * 2026-02-21 02:01:19 (10973) [INFO] or * 2026-02-21 02:01:19 (10973) [INFO] subscription-manager repos --disable= * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-21 02:01:19 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-21 02:01:19 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-21 02:01:19 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-21 02:01:19 (10973) [INFO] compromise: * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-21 02:01:19 (10973) [INFO] * 2026-02-21 02:01:19 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-21 02:01:19 (10990) [INFO] * 2026-02-21 02:01:19 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-21 02:01:19 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-21 02:01:19 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-21 02:01:19 (10960) [INFO] * 2026-02-21 02:01:20 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-21 02:01:20 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-21 02:01:20 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-21 02:01:20 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-21 02:01:20 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-21 02:01:20 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-21 02:01:20 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-21 02:01:20 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-21 02:01:20 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-21 02:01:20 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-21 02:01:20 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-21 02:01:20 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-21 02:01:20 (10990) [INFO] * 2026-02-21 02:01:20 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-21 02:01:20 (10960) [INFO] * 2026-02-21 02:01:21 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-21 02:01:21 (10973) [INFO] Determining fastest mirrors * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-21 02:01:52 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-21 02:01:52 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-21 02:01:52 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-21 02:01:52 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-21 02:01:52 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-21 02:01:52 (10973) [INFO] yum --disablerepo= ... * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-21 02:01:52 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-21 02:01:52 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] yum-config-manager --disable * 2026-02-21 02:01:52 (10973) [INFO] or * 2026-02-21 02:01:52 (10973) [INFO] subscription-manager repos --disable= * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-21 02:01:52 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-21 02:01:52 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-21 02:01:52 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-21 02:01:52 (10973) [INFO] compromise: * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-21 02:01:52 (10973) [INFO] * 2026-02-21 02:01:52 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-21 02:01:52 (10990) [INFO] * 2026-02-21 02:01:52 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-21 02:01:52 (6792) [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 * 2026-02-21 02:01:53 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-21 02:01:53 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-21 02:01:53 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-21 02:01:53 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-21 02:01:53 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-21 02:02:00 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c4lbCxw4Te/ea_profile.json * 2026-02-21 02:04:28 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/c4lbCxw4Te/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-21 02:04:28 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-22 01:40:00 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-22 01:44:01 (12063) [INFO] Script is up to date. * 2026-02-22 01:48:04 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-22 01:48:04 (10960) [INFO] * 2026-02-22 01:48:54 (10990) [INFO] * 2026-02-22 01:48:54 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-22 01:48:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-22 01:48:54 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-22 01:48:54 (10960) [INFO] * 2026-02-22 01:48:57 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-22 01:48:57 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-22 01:48:57 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-22 01:48:57 (10960) [INFO] * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-22 01:49:33 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-22 01:49:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-22 01:49:33 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-22 01:49:33 (10960) [INFO] * 2026-02-22 01:49:34 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-22 01:49:34 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-22 01:50:05 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-22 01:50:05 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-22 01:50:05 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-22 01:50:05 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-22 01:50:05 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-22 01:50:05 (10973) [INFO] yum --disablerepo= ... * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-22 01:50:05 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-22 01:50:05 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] yum-config-manager --disable * 2026-02-22 01:50:05 (10973) [INFO] or * 2026-02-22 01:50:05 (10973) [INFO] subscription-manager repos --disable= * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-22 01:50:05 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-22 01:50:05 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-22 01:50:05 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-22 01:50:05 (10973) [INFO] compromise: * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-22 01:50:05 (10973) [INFO] * 2026-02-22 01:50:05 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-22 01:50:05 (10990) [INFO] * 2026-02-22 01:50:05 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-22 01:50:05 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-22 01:50:05 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-22 01:50:05 (10960) [INFO] * 2026-02-22 01:50:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-22 01:50:06 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-22 01:50:06 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-22 01:50:06 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-22 01:50:06 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-22 01:50:06 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-22 01:50:06 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-22 01:50:06 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-22 01:50:06 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-22 01:50:06 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-22 01:50:06 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-22 01:50:06 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-22 01:50:06 (10990) [INFO] * 2026-02-22 01:50:06 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-22 01:50:06 (10960) [INFO] * 2026-02-22 01:50:07 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-22 01:50:07 (10973) [INFO] Determining fastest mirrors * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-22 01:50:39 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-22 01:50:39 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-22 01:50:39 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-22 01:50:39 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-22 01:50:39 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-22 01:50:39 (10973) [INFO] yum --disablerepo= ... * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-22 01:50:39 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-22 01:50:39 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] yum-config-manager --disable * 2026-02-22 01:50:39 (10973) [INFO] or * 2026-02-22 01:50:39 (10973) [INFO] subscription-manager repos --disable= * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-22 01:50:39 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-22 01:50:39 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-22 01:50:39 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-22 01:50:39 (10973) [INFO] compromise: * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-22 01:50:39 (10973) [INFO] * 2026-02-22 01:50:39 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-22 01:50:39 (10990) [INFO] * 2026-02-22 01:50:39 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-22 01:50:39 (6792) [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 * 2026-02-22 01:50:40 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-22 01:50:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-22 01:50:40 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-22 01:50:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-22 01:50:40 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-22 01:50:47 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MdLaiyINlY/ea_profile.json * 2026-02-22 01:53:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MdLaiyINlY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-22 01:53:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-23 01:38:40 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-23 01:43:40 (12063) [INFO] Script is up to date. * 2026-02-23 01:48:43 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-23 01:48:43 (10960) [INFO] * 2026-02-23 01:50:03 (10990) [INFO] * 2026-02-23 01:50:03 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-23 01:50:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-23 01:50:03 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-23 01:50:03 (10960) [INFO] * 2026-02-23 01:52:31 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-23 01:52:31 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-23 01:52:31 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-23 01:52:31 (10960) [INFO] * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-23 01:53:07 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-23 01:53:07 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-23 01:53:07 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-23 01:53:07 (10960) [INFO] * 2026-02-23 01:53:07 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-23 01:53:07 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-23 01:53:38 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-23 01:53:38 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-23 01:53:38 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-23 01:53:38 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-23 01:53:38 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-23 01:53:38 (10973) [INFO] yum --disablerepo= ... * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-23 01:53:38 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-23 01:53:38 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] yum-config-manager --disable * 2026-02-23 01:53:38 (10973) [INFO] or * 2026-02-23 01:53:38 (10973) [INFO] subscription-manager repos --disable= * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-23 01:53:38 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-23 01:53:38 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-23 01:53:38 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-23 01:53:38 (10973) [INFO] compromise: * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-23 01:53:38 (10973) [INFO] * 2026-02-23 01:53:38 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-23 01:53:38 (10990) [INFO] * 2026-02-23 01:53:38 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-23 01:53:38 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-23 01:53:38 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-23 01:53:38 (10960) [INFO] * 2026-02-23 01:53:39 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-23 01:53:39 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-23 01:53:39 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-23 01:53:39 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-23 01:53:39 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-23 01:53:39 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-23 01:53:39 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-23 01:53:39 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-23 01:53:39 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-23 01:53:39 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-23 01:53:39 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-23 01:53:39 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-23 01:53:39 (10990) [INFO] * 2026-02-23 01:53:39 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-23 01:53:39 (10960) [INFO] * 2026-02-23 01:53:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-23 01:53:40 (10973) [INFO] Determining fastest mirrors * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-23 01:54:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-23 01:54:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-23 01:54:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-23 01:54:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-23 01:54:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-23 01:54:11 (10973) [INFO] yum --disablerepo= ... * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-23 01:54:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-23 01:54:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] yum-config-manager --disable * 2026-02-23 01:54:11 (10973) [INFO] or * 2026-02-23 01:54:11 (10973) [INFO] subscription-manager repos --disable= * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-23 01:54:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-23 01:54:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-23 01:54:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-23 01:54:11 (10973) [INFO] compromise: * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-23 01:54:11 (10973) [INFO] * 2026-02-23 01:54:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-23 01:54:11 (10990) [INFO] * 2026-02-23 01:54:11 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-23 01:54:11 (6792) [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 * 2026-02-23 01:54:13 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-23 01:54:13 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-23 01:54:13 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-23 01:54:13 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-23 01:54:13 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-23 01:54:18 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/14M3qH0POq/ea_profile.json * 2026-02-23 01:56:45 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/14M3qH0POq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-23 01:56:45 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-24 01:44:20 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-24 01:48:21 (12063) [INFO] Script is up to date. * 2026-02-24 01:52:25 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-24 01:52:25 (10960) [INFO] * 2026-02-24 01:53:41 (10990) [INFO] * 2026-02-24 01:53:41 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-24 01:53:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-24 01:53:42 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-24 01:53:42 (10960) [INFO] * 2026-02-24 02:02:28 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-24 02:02:28 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-24 02:02:28 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-24 02:02:28 (10960) [INFO] * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-24 02:03:05 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-24 02:03:05 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-24 02:03:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-24 02:03:05 (10960) [INFO] * 2026-02-24 02:03:05 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-24 02:03:06 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-24 02:03:37 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-24 02:03:37 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-24 02:03:37 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-24 02:03:37 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-24 02:03:37 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-24 02:03:37 (10973) [INFO] yum --disablerepo= ... * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-24 02:03:37 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-24 02:03:37 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] yum-config-manager --disable * 2026-02-24 02:03:37 (10973) [INFO] or * 2026-02-24 02:03:37 (10973) [INFO] subscription-manager repos --disable= * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-24 02:03:37 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-24 02:03:37 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-24 02:03:37 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-24 02:03:37 (10973) [INFO] compromise: * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-24 02:03:37 (10973) [INFO] * 2026-02-24 02:03:37 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-24 02:03:37 (10990) [INFO] * 2026-02-24 02:03:37 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-24 02:03:37 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-24 02:03:37 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-24 02:03:37 (10960) [INFO] * 2026-02-24 02:03:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-24 02:03:38 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-24 02:03:38 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-24 02:03:38 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-24 02:03:38 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-24 02:03:38 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-24 02:03:38 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-24 02:03:38 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-24 02:03:38 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-24 02:03:38 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-24 02:03:38 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-24 02:03:38 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-24 02:03:38 (10990) [INFO] * 2026-02-24 02:03:38 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-24 02:03:38 (10960) [INFO] * 2026-02-24 02:03:39 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-24 02:03:39 (10973) [INFO] Determining fastest mirrors * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-24 02:04:10 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-24 02:04:10 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-24 02:04:10 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-24 02:04:10 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-24 02:04:10 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-24 02:04:10 (10973) [INFO] yum --disablerepo= ... * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-24 02:04:10 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-24 02:04:10 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] yum-config-manager --disable * 2026-02-24 02:04:10 (10973) [INFO] or * 2026-02-24 02:04:10 (10973) [INFO] subscription-manager repos --disable= * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-24 02:04:10 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-24 02:04:10 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-24 02:04:10 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-24 02:04:10 (10973) [INFO] compromise: * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-24 02:04:10 (10973) [INFO] * 2026-02-24 02:04:10 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-24 02:04:10 (10990) [INFO] * 2026-02-24 02:04:10 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-24 02:04:10 (6792) [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 * 2026-02-24 02:04:12 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-24 02:04:12 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-24 02:04:12 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-24 02:04:12 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-24 02:04:12 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-24 02:04:19 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QAMd1aIzEN/ea_profile.json * 2026-02-24 02:06:46 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/QAMd1aIzEN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-24 02:06:46 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-25 01:39:40 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-25 01:44:41 (12063) [INFO] Script is up to date. * 2026-02-25 01:49:44 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-25 01:49:44 (10960) [INFO] * 2026-02-25 01:51:02 (10990) [INFO] * 2026-02-25 01:51:02 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-25 01:51:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-25 01:51:03 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-25 01:51:03 (10960) [INFO] * 2026-02-25 01:58:06 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-25 01:58:06 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-25 01:58:06 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-25 01:58:06 (10960) [INFO] * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-25 01:58:41 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-25 01:58:41 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-25 01:58:41 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-25 01:58:41 (10960) [INFO] * 2026-02-25 01:58:42 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-25 01:58:42 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-25 01:59:13 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-25 01:59:13 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-25 01:59:13 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-25 01:59:13 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-25 01:59:13 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-25 01:59:13 (10973) [INFO] yum --disablerepo= ... * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-25 01:59:13 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-25 01:59:13 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] yum-config-manager --disable * 2026-02-25 01:59:13 (10973) [INFO] or * 2026-02-25 01:59:13 (10973) [INFO] subscription-manager repos --disable= * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-25 01:59:13 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-25 01:59:13 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-25 01:59:13 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-25 01:59:13 (10973) [INFO] compromise: * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-25 01:59:13 (10973) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-25 01:59:13 (10990) [INFO] * 2026-02-25 01:59:13 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-25 01:59:13 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-25 01:59:13 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-25 01:59:13 (10960) [INFO] * 2026-02-25 01:59:13 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-25 01:59:13 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-25 01:59:13 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-25 01:59:13 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-25 01:59:13 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-25 01:59:13 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-25 01:59:13 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-25 01:59:13 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-25 01:59:13 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-25 01:59:13 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-25 01:59:14 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-25 01:59:14 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-25 01:59:14 (10990) [INFO] * 2026-02-25 01:59:14 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-25 01:59:14 (10960) [INFO] * 2026-02-25 01:59:14 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-25 01:59:14 (10973) [INFO] Determining fastest mirrors * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-25 01:59:45 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-25 01:59:45 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-25 01:59:45 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-25 01:59:45 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-25 01:59:45 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-25 01:59:45 (10973) [INFO] yum --disablerepo= ... * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-25 01:59:45 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-25 01:59:45 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] yum-config-manager --disable * 2026-02-25 01:59:45 (10973) [INFO] or * 2026-02-25 01:59:45 (10973) [INFO] subscription-manager repos --disable= * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-25 01:59:45 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-25 01:59:45 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-25 01:59:45 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-25 01:59:45 (10973) [INFO] compromise: * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-25 01:59:45 (10973) [INFO] * 2026-02-25 01:59:45 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-25 01:59:45 (10990) [INFO] * 2026-02-25 01:59:45 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-25 01:59:45 (6792) [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 * 2026-02-25 01:59:47 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-25 01:59:47 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-25 01:59:47 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-25 01:59:47 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-25 01:59:47 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-25 01:59:55 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kc1srP4DtG/ea_profile.json * 2026-02-25 02:03:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Kc1srP4DtG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-25 02:03:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-26 01:39:08 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-26 01:43:09 (12063) [INFO] Script is up to date. * 2026-02-26 01:47:12 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-26 01:47:12 (10960) [INFO] * 2026-02-26 01:48:28 (10990) [INFO] * 2026-02-26 01:48:28 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-26 01:48:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-26 01:48:28 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-26 01:48:28 (10960) [INFO] * 2026-02-26 01:48:32 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-26 01:48:32 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-26 01:48:32 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-26 01:48:32 (10960) [INFO] * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-26 01:49:08 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-26 01:49:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-26 01:49:08 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-26 01:49:08 (10960) [INFO] * 2026-02-26 01:49:08 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-26 01:49:09 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-26 01:49:39 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-26 01:49:39 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-26 01:49:39 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-26 01:49:39 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-26 01:49:39 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-26 01:49:39 (10973) [INFO] yum --disablerepo= ... * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-26 01:49:39 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-26 01:49:39 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] yum-config-manager --disable * 2026-02-26 01:49:39 (10973) [INFO] or * 2026-02-26 01:49:39 (10973) [INFO] subscription-manager repos --disable= * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-26 01:49:39 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-26 01:49:39 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-26 01:49:39 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-26 01:49:39 (10973) [INFO] compromise: * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-26 01:49:39 (10973) [INFO] * 2026-02-26 01:49:39 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-26 01:49:40 (10990) [INFO] * 2026-02-26 01:49:40 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-26 01:49:40 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-26 01:49:40 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-26 01:49:40 (10960) [INFO] * 2026-02-26 01:49:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-26 01:49:40 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-26 01:49:40 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-26 01:49:40 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-26 01:49:40 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-26 01:49:40 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-26 01:49:40 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-26 01:49:40 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-26 01:49:40 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-26 01:49:40 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-26 01:49:40 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-26 01:49:40 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-26 01:49:40 (10990) [INFO] * 2026-02-26 01:49:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-26 01:49:40 (10960) [INFO] * 2026-02-26 01:49:41 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-26 01:49:41 (10973) [INFO] Determining fastest mirrors * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-26 01:50:12 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-26 01:50:12 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-26 01:50:12 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-26 01:50:12 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-26 01:50:12 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-26 01:50:12 (10973) [INFO] yum --disablerepo= ... * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-26 01:50:12 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-26 01:50:12 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] yum-config-manager --disable * 2026-02-26 01:50:12 (10973) [INFO] or * 2026-02-26 01:50:12 (10973) [INFO] subscription-manager repos --disable= * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-26 01:50:12 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-26 01:50:12 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-26 01:50:12 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-26 01:50:12 (10973) [INFO] compromise: * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-26 01:50:12 (10973) [INFO] * 2026-02-26 01:50:12 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-26 01:50:12 (10990) [INFO] * 2026-02-26 01:50:12 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-26 01:50:12 (6792) [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 * 2026-02-26 01:50:13 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-26 01:50:13 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-26 01:50:13 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-26 01:50:13 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-26 01:50:13 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-26 01:50:20 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6Wp6YOF15_/ea_profile.json * 2026-02-26 01:52:48 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6Wp6YOF15_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-26 01:52:48 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-27 01:38:38 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-27 01:43:38 (12063) [INFO] Script is up to date. * 2026-02-27 01:48:41 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-27 01:48:41 (10960) [INFO] * 2026-02-27 01:49:58 (10990) [INFO] * 2026-02-27 01:49:58 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-27 01:49:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-27 01:49:59 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-27 01:49:59 (10960) [INFO] * 2026-02-27 01:56:58 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-27 01:56:58 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-27 01:56:58 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-27 01:56:58 (10960) [INFO] * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-27 01:57:33 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-27 01:57:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-27 01:57:33 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-27 01:57:33 (10960) [INFO] * 2026-02-27 01:57:33 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-27 01:57:33 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-27 01:58:04 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-27 01:58:04 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-27 01:58:04 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-27 01:58:04 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-27 01:58:04 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-27 01:58:04 (10973) [INFO] yum --disablerepo= ... * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-27 01:58:04 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-27 01:58:04 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] yum-config-manager --disable * 2026-02-27 01:58:04 (10973) [INFO] or * 2026-02-27 01:58:04 (10973) [INFO] subscription-manager repos --disable= * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-27 01:58:04 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-27 01:58:04 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-27 01:58:04 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-27 01:58:04 (10973) [INFO] compromise: * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-27 01:58:04 (10973) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-27 01:58:04 (10990) [INFO] * 2026-02-27 01:58:04 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-27 01:58:04 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-27 01:58:04 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-27 01:58:04 (10960) [INFO] * 2026-02-27 01:58:04 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-27 01:58:05 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-27 01:58:05 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-27 01:58:05 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-27 01:58:05 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-27 01:58:05 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-27 01:58:05 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-27 01:58:05 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-27 01:58:05 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-27 01:58:05 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-27 01:58:05 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-27 01:58:05 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-02-27 01:58:05 (10990) [INFO] * 2026-02-27 01:58:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-27 01:58:05 (10960) [INFO] * 2026-02-27 01:58:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-27 01:58:06 (10973) [INFO] Determining fastest mirrors * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-27 01:58:37 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-27 01:58:37 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-27 01:58:37 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-27 01:58:37 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-27 01:58:37 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-27 01:58:37 (10973) [INFO] yum --disablerepo= ... * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-27 01:58:37 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-27 01:58:37 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] yum-config-manager --disable * 2026-02-27 01:58:37 (10973) [INFO] or * 2026-02-27 01:58:37 (10973) [INFO] subscription-manager repos --disable= * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-27 01:58:37 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-27 01:58:37 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-27 01:58:37 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-27 01:58:37 (10973) [INFO] compromise: * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-27 01:58:37 (10973) [INFO] * 2026-02-27 01:58:37 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-27 01:58:37 (10990) [INFO] * 2026-02-27 01:58:37 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-27 01:58:37 (6792) [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 * 2026-02-27 01:58:39 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-27 01:58:39 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-27 01:58:39 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-27 01:58:39 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-27 01:58:39 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-27 01:58:45 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jXSyGgxfn8/ea_profile.json * 2026-02-27 02:01:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jXSyGgxfn8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-27 02:01:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-02-28 01:41:23 (12041) [INFO] Self-update of script version 79 requested. * 2026-02-28 01:46:24 (12063) [INFO] Script is up to date. * 2026-02-28 01:51:27 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-02-28 01:51:27 (10960) [INFO] * 2026-02-28 01:52:20 (10990) [INFO] * 2026-02-28 01:52:20 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-02-28 01:52:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-02-28 01:52:20 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-02-28 01:52:20 (10960) [INFO] * 2026-02-28 01:59:22 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-02-28 01:59:22 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-02-28 01:59:22 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-02-28 01:59:22 (10960) [INFO] * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-02-28 01:59:58 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-02-28 01:59:58 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-02-28 01:59:58 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-28 01:59:58 (10960) [INFO] * 2026-02-28 01:59:58 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-28 01:59:58 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-28 02:00:30 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-28 02:00:30 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-28 02:00:30 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-28 02:00:30 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-28 02:00:30 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-28 02:00:30 (10973) [INFO] yum --disablerepo= ... * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-28 02:00:30 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-28 02:00:30 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] yum-config-manager --disable * 2026-02-28 02:00:30 (10973) [INFO] or * 2026-02-28 02:00:30 (10973) [INFO] subscription-manager repos --disable= * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-28 02:00:30 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-28 02:00:30 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-28 02:00:30 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-28 02:00:30 (10973) [INFO] compromise: * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-28 02:00:30 (10973) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-28 02:00:30 (10990) [INFO] * 2026-02-28 02:00:30 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-28 02:00:30 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-02-28 02:00:30 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-02-28 02:00:30 (10960) [INFO] * 2026-02-28 02:00:30 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-28 02:00:30 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-02-28 02:00:30 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-02-28 02:00:30 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-02-28 02:00:30 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-02-28 02:00:30 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-02-28 02:00:30 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-02-28 02:00:30 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-02-28 02:00:30 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-02-28 02:00:30 (10973) [INFO] : wp-toolkit-thirdparties * 2026-02-28 02:00:31 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-02-28 02:00:31 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-02-28 02:00:31 (10990) [INFO] * 2026-02-28 02:00:31 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-02-28 02:00:31 (10960) [INFO] * 2026-02-28 02:00:31 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-02-28 02:00:32 (10973) [INFO] Determining fastest mirrors * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-02-28 02:01:03 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-02-28 02:01:03 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-02-28 02:01:03 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-02-28 02:01:03 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-02-28 02:01:03 (10973) [INFO] packages for the previous distribution release still work). * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-02-28 02:01:03 (10973) [INFO] yum --disablerepo= ... * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-02-28 02:01:03 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-02-28 02:01:03 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] yum-config-manager --disable * 2026-02-28 02:01:03 (10973) [INFO] or * 2026-02-28 02:01:03 (10973) [INFO] subscription-manager repos --disable= * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-02-28 02:01:03 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-02-28 02:01:03 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-02-28 02:01:03 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-02-28 02:01:03 (10973) [INFO] compromise: * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-02-28 02:01:03 (10973) [INFO] * 2026-02-28 02:01:03 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-02-28 02:01:03 (10990) [INFO] * 2026-02-28 02:01:03 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-02-28 02:01:03 (6792) [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 * 2026-02-28 02:01:04 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-02-28 02:01:04 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-02-28 02:01:04 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-02-28 02:01:04 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-02-28 02:01:04 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-02-28 02:01:11 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1IqzMS0vWO/ea_profile.json * 2026-02-28 02:03:37 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/1IqzMS0vWO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-02-28 02:03:38 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-01 01:41:00 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-01 01:45:00 (12063) [INFO] Script is up to date. * 2026-03-01 01:49:04 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-01 01:49:04 (10960) [INFO] * 2026-03-01 01:49:55 (10990) [INFO] * 2026-03-01 01:49:55 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-01 01:49:56 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-01 01:49:56 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-01 01:49:56 (10960) [INFO] * 2026-03-01 01:56:55 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-01 01:56:55 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-01 01:56:55 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-01 01:56:55 (10960) [INFO] * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-01 01:57:31 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-01 01:57:31 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-01 01:57:31 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-01 01:57:31 (10960) [INFO] * 2026-03-01 01:57:31 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-01 01:57:32 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-01 01:58:02 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-01 01:58:02 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-01 01:58:02 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-01 01:58:02 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-01 01:58:02 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-01 01:58:02 (10973) [INFO] yum --disablerepo= ... * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-01 01:58:02 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-01 01:58:02 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] yum-config-manager --disable * 2026-03-01 01:58:02 (10973) [INFO] or * 2026-03-01 01:58:02 (10973) [INFO] subscription-manager repos --disable= * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-01 01:58:02 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-01 01:58:02 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-01 01:58:02 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-01 01:58:02 (10973) [INFO] compromise: * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-01 01:58:02 (10973) [INFO] * 2026-03-01 01:58:02 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-01 01:58:02 (10990) [INFO] * 2026-03-01 01:58:02 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-01 01:58:02 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-01 01:58:02 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-01 01:58:02 (10960) [INFO] * 2026-03-01 01:58:03 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-01 01:58:03 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-01 01:58:03 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-01 01:58:03 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-01 01:58:03 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-01 01:58:03 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-01 01:58:03 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-01 01:58:03 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-01 01:58:03 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-01 01:58:03 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-01 01:58:03 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-01 01:58:03 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-01 01:58:03 (10990) [INFO] * 2026-03-01 01:58:03 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-01 01:58:03 (10960) [INFO] * 2026-03-01 01:58:04 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-01 01:58:04 (10973) [INFO] Determining fastest mirrors * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-01 01:58:36 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-01 01:58:36 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-01 01:58:36 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-01 01:58:36 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-01 01:58:36 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-01 01:58:36 (10973) [INFO] yum --disablerepo= ... * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-01 01:58:36 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-01 01:58:36 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] yum-config-manager --disable * 2026-03-01 01:58:36 (10973) [INFO] or * 2026-03-01 01:58:36 (10973) [INFO] subscription-manager repos --disable= * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-01 01:58:36 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-01 01:58:36 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-01 01:58:36 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-01 01:58:36 (10973) [INFO] compromise: * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-01 01:58:36 (10973) [INFO] * 2026-03-01 01:58:36 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-01 01:58:36 (10990) [INFO] * 2026-03-01 01:58:36 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-01 01:58:36 (6792) [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 * 2026-03-01 01:58:38 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-01 01:58:38 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-01 01:58:38 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-01 01:58:38 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-01 01:58:38 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-01 01:58:45 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dK8AWXRxpp/ea_profile.json * 2026-03-01 02:01:11 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/dK8AWXRxpp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-01 02:01:11 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-02 01:38:42 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-02 01:43:42 (12063) [INFO] Script is up to date. * 2026-03-02 01:48:46 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-02 01:48:46 (10960) [INFO] * 2026-03-02 01:50:07 (10990) [INFO] * 2026-03-02 01:50:07 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-02 01:50:07 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-02 01:50:07 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-02 01:50:07 (10960) [INFO] * 2026-03-02 01:57:28 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-02 01:57:28 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-02 01:57:28 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-02 01:57:28 (10960) [INFO] * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-02 01:58:03 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-02 01:58:03 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-02 01:58:03 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-02 01:58:03 (10960) [INFO] * 2026-03-02 01:58:04 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-02 01:58:04 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-02 01:58:35 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-02 01:58:35 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-02 01:58:35 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-02 01:58:35 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-02 01:58:35 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-02 01:58:35 (10973) [INFO] yum --disablerepo= ... * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-02 01:58:35 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-02 01:58:35 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] yum-config-manager --disable * 2026-03-02 01:58:35 (10973) [INFO] or * 2026-03-02 01:58:35 (10973) [INFO] subscription-manager repos --disable= * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-02 01:58:35 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-02 01:58:35 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-02 01:58:35 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-02 01:58:35 (10973) [INFO] compromise: * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-02 01:58:35 (10973) [INFO] * 2026-03-02 01:58:35 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-02 01:58:35 (10990) [INFO] * 2026-03-02 01:58:35 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-02 01:58:35 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-02 01:58:35 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-02 01:58:35 (10960) [INFO] * 2026-03-02 01:58:36 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-02 01:58:36 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-02 01:58:36 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-02 01:58:36 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-02 01:58:36 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-02 01:58:36 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-02 01:58:36 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-02 01:58:36 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-02 01:58:36 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-02 01:58:36 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-02 01:58:36 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-02 01:58:36 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-02 01:58:36 (10990) [INFO] * 2026-03-02 01:58:36 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-02 01:58:36 (10960) [INFO] * 2026-03-02 01:58:37 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-02 01:58:37 (10973) [INFO] Determining fastest mirrors * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-02 01:59:07 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-02 01:59:07 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-02 01:59:07 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-02 01:59:07 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-02 01:59:07 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-02 01:59:07 (10973) [INFO] yum --disablerepo= ... * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-02 01:59:07 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-02 01:59:07 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] yum-config-manager --disable * 2026-03-02 01:59:07 (10973) [INFO] or * 2026-03-02 01:59:07 (10973) [INFO] subscription-manager repos --disable= * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-02 01:59:07 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-02 01:59:07 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-02 01:59:07 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-02 01:59:07 (10973) [INFO] compromise: * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-02 01:59:07 (10973) [INFO] * 2026-03-02 01:59:07 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-02 01:59:07 (10990) [INFO] * 2026-03-02 01:59:07 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-02 01:59:07 (6792) [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 * 2026-03-02 01:59:09 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-02 01:59:09 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-02 01:59:09 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-02 01:59:09 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-02 01:59:09 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-02 01:59:15 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0qzyFjjw1x/ea_profile.json * 2026-03-02 02:01:42 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0qzyFjjw1x/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-02 02:01:42 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-03 02:55:18 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-03 03:00:18 (12063) [INFO] Script is up to date. * 2026-03-03 03:05:22 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-03 03:05:22 (10960) [INFO] * 2026-03-03 03:06:42 (10990) [INFO] * 2026-03-03 03:06:42 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-03 03:06:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-03 03:06:43 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-03 03:06:43 (10960) [INFO] * 2026-03-03 03:13:45 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-03 03:13:45 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-03 03:13:45 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-03 03:13:45 (10960) [INFO] * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-03 03:14:19 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-03 03:14:19 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-03 03:14:19 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-03 03:14:19 (10960) [INFO] * 2026-03-03 03:14:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-03 03:14:20 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-03 03:14:50 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-03 03:14:50 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-03 03:14:50 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-03 03:14:50 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-03 03:14:50 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-03 03:14:50 (10973) [INFO] yum --disablerepo= ... * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-03 03:14:50 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-03 03:14:50 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] yum-config-manager --disable * 2026-03-03 03:14:50 (10973) [INFO] or * 2026-03-03 03:14:50 (10973) [INFO] subscription-manager repos --disable= * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-03 03:14:50 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-03 03:14:50 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-03 03:14:50 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-03 03:14:50 (10973) [INFO] compromise: * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-03 03:14:50 (10973) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-03 03:14:50 (10990) [INFO] * 2026-03-03 03:14:50 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-03 03:14:50 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-03 03:14:50 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-03 03:14:50 (10960) [INFO] * 2026-03-03 03:14:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-03 03:14:51 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-03 03:14:51 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-03 03:14:51 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-03 03:14:51 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-03 03:14:51 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-03 03:14:51 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-03 03:14:51 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-03 03:14:51 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-03 03:14:51 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-03 03:14:51 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-03 03:14:51 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-03 03:14:51 (10990) [INFO] * 2026-03-03 03:14:51 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-03 03:14:51 (10960) [INFO] * 2026-03-03 03:14:51 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-03 03:14:52 (10973) [INFO] Determining fastest mirrors * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-03 03:15:23 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-03 03:15:23 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-03 03:15:23 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-03 03:15:23 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-03 03:15:23 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-03 03:15:23 (10973) [INFO] yum --disablerepo= ... * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-03 03:15:23 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-03 03:15:23 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] yum-config-manager --disable * 2026-03-03 03:15:23 (10973) [INFO] or * 2026-03-03 03:15:23 (10973) [INFO] subscription-manager repos --disable= * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-03 03:15:23 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-03 03:15:23 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-03 03:15:23 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-03 03:15:23 (10973) [INFO] compromise: * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-03 03:15:23 (10973) [INFO] * 2026-03-03 03:15:23 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-03 03:15:23 (10990) [INFO] * 2026-03-03 03:15:23 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-03 03:15:23 (6792) [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 * 2026-03-03 03:15:25 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-03 03:15:25 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-03 03:15:25 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-03 03:15:25 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-03 03:15:25 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-03 03:15:31 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zZ9NJgUqE4/ea_profile.json * 2026-03-03 03:17:58 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zZ9NJgUqE4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-03 03:17:58 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-04 01:38:35 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-04 01:42:35 (12063) [INFO] Script is up to date. * 2026-03-04 01:46:38 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-04 01:46:38 (10960) [INFO] * 2026-03-04 01:47:54 (10990) [INFO] * 2026-03-04 01:47:54 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-04 01:47:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-04 01:47:54 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-04 01:47:54 (10960) [INFO] * 2026-03-04 01:54:58 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-04 01:54:58 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-04 01:54:58 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-04 01:54:58 (10960) [INFO] * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-04 01:55:33 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-04 01:55:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-04 01:55:33 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-04 01:55:33 (10960) [INFO] * 2026-03-04 01:55:33 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-04 01:55:34 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-04 01:56:04 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-04 01:56:04 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-04 01:56:04 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-04 01:56:04 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-04 01:56:04 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-04 01:56:04 (10973) [INFO] yum --disablerepo= ... * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-04 01:56:04 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-04 01:56:04 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] yum-config-manager --disable * 2026-03-04 01:56:04 (10973) [INFO] or * 2026-03-04 01:56:04 (10973) [INFO] subscription-manager repos --disable= * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-04 01:56:04 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-04 01:56:04 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-04 01:56:04 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-04 01:56:04 (10973) [INFO] compromise: * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-04 01:56:04 (10973) [INFO] * 2026-03-04 01:56:04 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-04 01:56:04 (10990) [INFO] * 2026-03-04 01:56:04 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-04 01:56:04 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-04 01:56:04 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-04 01:56:04 (10960) [INFO] * 2026-03-04 01:56:05 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-04 01:56:05 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-04 01:56:05 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-04 01:56:05 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-04 01:56:05 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-04 01:56:05 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-04 01:56:05 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-04 01:56:05 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-04 01:56:05 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-04 01:56:05 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-04 01:56:05 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-04 01:56:05 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-04 01:56:05 (10990) [INFO] * 2026-03-04 01:56:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-04 01:56:05 (10960) [INFO] * 2026-03-04 01:56:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-04 01:56:06 (10973) [INFO] Determining fastest mirrors * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-04 01:56:37 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-04 01:56:37 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-04 01:56:37 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-04 01:56:37 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-04 01:56:37 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-04 01:56:37 (10973) [INFO] yum --disablerepo= ... * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-04 01:56:37 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-04 01:56:37 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] yum-config-manager --disable * 2026-03-04 01:56:37 (10973) [INFO] or * 2026-03-04 01:56:37 (10973) [INFO] subscription-manager repos --disable= * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-04 01:56:37 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-04 01:56:37 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-04 01:56:37 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-04 01:56:37 (10973) [INFO] compromise: * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-04 01:56:37 (10973) [INFO] * 2026-03-04 01:56:37 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-04 01:56:37 (10990) [INFO] * 2026-03-04 01:56:37 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-04 01:56:37 (6792) [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 * 2026-03-04 01:56:39 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-04 01:56:39 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-04 01:56:39 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-04 01:56:39 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-04 01:56:39 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-04 01:56:45 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uAhCRFpPh3/ea_profile.json * 2026-03-04 01:59:12 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uAhCRFpPh3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-04 01:59:12 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-05 01:44:19 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-05 01:48:19 (12063) [INFO] Script is up to date. * 2026-03-05 01:52:23 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-05 01:52:23 (10960) [INFO] * 2026-03-05 01:53:43 (10990) [INFO] * 2026-03-05 01:53:43 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-05 01:53:43 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-05 01:53:43 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-05 01:53:43 (10960) [INFO] * 2026-03-05 02:00:45 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-05 02:00:45 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-05 02:00:45 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-05 02:00:45 (10960) [INFO] * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-05 02:01:21 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-05 02:01:21 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-05 02:01:21 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-05 02:01:21 (10960) [INFO] * 2026-03-05 02:01:22 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-05 02:01:22 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-05 02:01:54 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-05 02:01:54 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-05 02:01:54 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-05 02:01:54 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-05 02:01:54 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-05 02:01:54 (10973) [INFO] yum --disablerepo= ... * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-05 02:01:54 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-05 02:01:54 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] yum-config-manager --disable * 2026-03-05 02:01:54 (10973) [INFO] or * 2026-03-05 02:01:54 (10973) [INFO] subscription-manager repos --disable= * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-05 02:01:54 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-05 02:01:54 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-05 02:01:54 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-05 02:01:54 (10973) [INFO] compromise: * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-05 02:01:54 (10973) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-05 02:01:54 (10990) [INFO] * 2026-03-05 02:01:54 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-05 02:01:54 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-05 02:01:54 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-05 02:01:54 (10960) [INFO] * 2026-03-05 02:01:54 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-05 02:01:55 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-05 02:01:55 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-05 02:01:55 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-05 02:01:55 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-05 02:01:55 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-05 02:01:55 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-05 02:01:55 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-05 02:01:55 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-05 02:01:55 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-05 02:01:55 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-05 02:01:55 (10973) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-03-05 02:01:55 (10990) [INFO] * 2026-03-05 02:01:55 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-05 02:01:55 (10960) [INFO] * 2026-03-05 02:01:55 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-05 02:01:56 (10973) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 1337. * 2026-03-05 02:01:56 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:01:56 (10973) [INFO] The other application is: yum * 2026-03-05 02:01:56 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:01:56 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:49 ago * 2026-03-05 02:01:56 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:01:58 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:01:58 (10973) [INFO] The other application is: yum * 2026-03-05 02:01:58 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:01:58 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:51 ago * 2026-03-05 02:01:58 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:00 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:00 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:00 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:00 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:53 ago * 2026-03-05 02:02:00 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:02 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:02 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:02 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:02 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:55 ago * 2026-03-05 02:02:02 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:04 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:04 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:04 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:04 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:57 ago * 2026-03-05 02:02:04 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:06 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:06 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:06 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:06 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 00:59 ago * 2026-03-05 02:02:06 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:08 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:08 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:08 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:08 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:01 ago * 2026-03-05 02:02:08 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:10 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:10 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:10 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:10 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:03 ago * 2026-03-05 02:02:10 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:12 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:12 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:12 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:12 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:05 ago * 2026-03-05 02:02:12 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:14 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:14 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:14 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:14 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:07 ago * 2026-03-05 02:02:14 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:16 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:16 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:16 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:16 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:09 ago * 2026-03-05 02:02:16 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:18 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:18 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:18 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:18 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:11 ago * 2026-03-05 02:02:18 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:20 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:20 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:20 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:20 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:13 ago * 2026-03-05 02:02:20 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:22 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:22 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:22 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:22 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:15 ago * 2026-03-05 02:02:22 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:24 (10973) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2026-03-05 02:02:24 (10973) [INFO] The other application is: yum * 2026-03-05 02:02:24 (10973) [INFO] Memory : 31 M RSS (430 MB VSZ) * 2026-03-05 02:02:24 (10973) [INFO] Started: Thu Mar 5 02:01:07 2026 - 01:17 ago * 2026-03-05 02:02:24 (10973) [INFO] State : Sleeping, pid: 1337 * 2026-03-05 02:02:26 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-05 02:02:57 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-05 02:02:57 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-05 02:02:57 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-05 02:02:57 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-05 02:02:57 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-05 02:02:57 (10973) [INFO] yum --disablerepo= ... * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-05 02:02:57 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-05 02:02:57 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] yum-config-manager --disable * 2026-03-05 02:02:57 (10973) [INFO] or * 2026-03-05 02:02:57 (10973) [INFO] subscription-manager repos --disable= * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-05 02:02:57 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-05 02:02:57 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-05 02:02:57 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-05 02:02:57 (10973) [INFO] compromise: * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-05 02:02:57 (10973) [INFO] * 2026-03-05 02:02:57 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-05 02:02:57 (10990) [INFO] * 2026-03-05 02:02:57 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-05 02:02:57 (6792) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 1337. Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:49 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:51 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:53 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:55 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:57 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 00:59 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:01 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:03 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:05 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:07 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:09 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:11 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:13 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:15 ago State : Sleeping, pid: 1337 Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 31 M RSS (430 MB VSZ) Started: Thu Mar 5 02:01:07 2026 - 01:17 ago State : Sleeping, pid: 1337 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 * 2026-03-05 02:02:59 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-05 02:02:59 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-05 02:02:59 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-05 02:02:59 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-05 02:02:59 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-05 02:03:07 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Qq4QIgdAH2/ea_profile.json * 2026-03-05 02:05:35 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Qq4QIgdAH2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-05 02:05:35 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-06 01:38:36 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-06 01:43:36 (12063) [INFO] Script is up to date. * 2026-03-06 01:48:40 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-06 01:48:40 (10960) [INFO] * 2026-03-06 01:49:57 (10990) [INFO] * 2026-03-06 01:49:57 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-06 01:49:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-06 01:49:57 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-06 01:49:57 (10960) [INFO] * 2026-03-06 01:50:00 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-06 01:50:00 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-06 01:50:00 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-06 01:50:00 (10960) [INFO] * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-06 01:50:36 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-06 01:50:36 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-06 01:50:36 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-06 01:50:36 (10960) [INFO] * 2026-03-06 01:50:36 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-06 01:50:37 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-06 01:51:07 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-06 01:51:07 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-06 01:51:07 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-06 01:51:07 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-06 01:51:07 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-06 01:51:07 (10973) [INFO] yum --disablerepo= ... * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-06 01:51:07 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-06 01:51:07 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] yum-config-manager --disable * 2026-03-06 01:51:07 (10973) [INFO] or * 2026-03-06 01:51:07 (10973) [INFO] subscription-manager repos --disable= * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-06 01:51:07 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-06 01:51:07 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-06 01:51:07 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-06 01:51:07 (10973) [INFO] compromise: * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-06 01:51:07 (10973) [INFO] * 2026-03-06 01:51:07 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-06 01:51:07 (10990) [INFO] * 2026-03-06 01:51:07 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-06 01:51:07 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-06 01:51:07 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-06 01:51:07 (10960) [INFO] * 2026-03-06 01:51:08 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-06 01:51:08 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-06 01:51:08 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-06 01:51:08 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-06 01:51:08 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-06 01:51:08 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-06 01:51:08 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-06 01:51:08 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-06 01:51:08 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-06 01:51:08 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-06 01:51:08 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-06 01:51:08 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-06 01:51:08 (10990) [INFO] * 2026-03-06 01:51:08 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-06 01:51:08 (10960) [INFO] * 2026-03-06 01:51:09 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-06 01:51:09 (10973) [INFO] Determining fastest mirrors * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-06 01:51:40 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-06 01:51:40 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-06 01:51:40 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-06 01:51:40 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-06 01:51:40 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-06 01:51:40 (10973) [INFO] yum --disablerepo= ... * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-06 01:51:40 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-06 01:51:40 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] yum-config-manager --disable * 2026-03-06 01:51:40 (10973) [INFO] or * 2026-03-06 01:51:40 (10973) [INFO] subscription-manager repos --disable= * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-06 01:51:40 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-06 01:51:40 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-06 01:51:40 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-06 01:51:40 (10973) [INFO] compromise: * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-06 01:51:40 (10973) [INFO] * 2026-03-06 01:51:40 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-06 01:51:40 (10990) [INFO] * 2026-03-06 01:51:40 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-06 01:51:40 (6792) [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 * 2026-03-06 01:51:41 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-06 01:51:41 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-06 01:51:41 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-06 01:51:41 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-06 01:51:41 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-06 01:51:48 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Gn2Gj8PVlZ/ea_profile.json * 2026-03-06 01:54:15 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Gn2Gj8PVlZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-06 01:54:15 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-07 01:39:56 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-07 01:44:56 (12063) [INFO] Script is up to date. * 2026-03-07 01:50:00 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-07 01:50:00 (10960) [INFO] * 2026-03-07 01:50:53 (10990) [INFO] * 2026-03-07 01:50:53 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-07 01:50:54 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-07 01:50:54 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-07 01:50:54 (10960) [INFO] * 2026-03-07 01:57:55 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-07 01:57:55 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-07 01:57:55 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-07 01:57:55 (10960) [INFO] * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-07 01:58:31 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-07 01:58:31 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-07 01:58:31 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-07 01:58:31 (10960) [INFO] * 2026-03-07 01:58:31 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-07 01:58:32 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-07 01:59:02 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-07 01:59:02 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-07 01:59:02 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-07 01:59:02 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-07 01:59:02 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-07 01:59:02 (10973) [INFO] yum --disablerepo= ... * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-07 01:59:02 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-07 01:59:02 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] yum-config-manager --disable * 2026-03-07 01:59:02 (10973) [INFO] or * 2026-03-07 01:59:02 (10973) [INFO] subscription-manager repos --disable= * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-07 01:59:02 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-07 01:59:02 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-07 01:59:02 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-07 01:59:02 (10973) [INFO] compromise: * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-07 01:59:02 (10973) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-07 01:59:02 (10990) [INFO] * 2026-03-07 01:59:02 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-07 01:59:02 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-07 01:59:02 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-07 01:59:02 (10960) [INFO] * 2026-03-07 01:59:02 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-07 01:59:03 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-07 01:59:03 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-07 01:59:03 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-07 01:59:03 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-07 01:59:03 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-07 01:59:03 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-07 01:59:03 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-07 01:59:03 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-07 01:59:03 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-07 01:59:03 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-07 01:59:03 (10973) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-03-07 01:59:03 (10990) [INFO] * 2026-03-07 01:59:03 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-07 01:59:03 (10960) [INFO] * 2026-03-07 01:59:03 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-07 01:59:04 (10973) [INFO] Determining fastest mirrors * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-07 01:59:35 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-07 01:59:35 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-07 01:59:35 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-07 01:59:35 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-07 01:59:35 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-07 01:59:35 (10973) [INFO] yum --disablerepo= ... * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-07 01:59:35 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-07 01:59:35 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] yum-config-manager --disable * 2026-03-07 01:59:35 (10973) [INFO] or * 2026-03-07 01:59:35 (10973) [INFO] subscription-manager repos --disable= * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-07 01:59:35 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-07 01:59:35 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-07 01:59:35 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-07 01:59:35 (10973) [INFO] compromise: * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-07 01:59:35 (10973) [INFO] * 2026-03-07 01:59:35 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-07 01:59:35 (10990) [INFO] * 2026-03-07 01:59:35 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-07 01:59:35 (6792) [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 * 2026-03-07 01:59:36 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-07 01:59:36 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-07 01:59:36 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-07 01:59:36 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-07 01:59:36 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-07 01:59:44 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fMkS3EusSx/ea_profile.json * 2026-03-07 02:02:11 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/fMkS3EusSx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-07 02:02:11 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-08 01:41:03 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-08 01:45:03 (12063) [INFO] Script is up to date. * 2026-03-08 01:49:05 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-08 01:49:05 (10960) [INFO] * 2026-03-08 01:50:01 (10990) [INFO] * 2026-03-08 01:50:01 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-08 01:50:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-08 01:50:02 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-08 01:50:02 (10960) [INFO] * 2026-03-08 01:57:04 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-08 01:57:04 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-08 01:57:04 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-08 01:57:04 (10960) [INFO] * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-08 01:57:40 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-08 01:57:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-08 01:57:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-08 01:57:40 (10960) [INFO] * 2026-03-08 01:57:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-08 01:57:41 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-08 01:58:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-08 01:58:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-08 01:58:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-08 01:58:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-08 01:58:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-08 01:58:11 (10973) [INFO] yum --disablerepo= ... * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-08 01:58:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-08 01:58:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] yum-config-manager --disable * 2026-03-08 01:58:11 (10973) [INFO] or * 2026-03-08 01:58:11 (10973) [INFO] subscription-manager repos --disable= * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-08 01:58:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-08 01:58:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-08 01:58:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-08 01:58:11 (10973) [INFO] compromise: * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-08 01:58:11 (10973) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-08 01:58:11 (10990) [INFO] * 2026-03-08 01:58:11 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-08 01:58:11 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-08 01:58:11 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-08 01:58:11 (10960) [INFO] * 2026-03-08 01:58:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-08 01:58:12 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-08 01:58:12 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-08 01:58:12 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-08 01:58:12 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-08 01:58:12 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-08 01:58:12 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-08 01:58:12 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-08 01:58:12 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-08 01:58:12 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-08 01:58:12 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-08 01:58:12 (10973) [INFO] Other repos take up 952 k of disk space (use --verbose for details) * 2026-03-08 01:58:12 (10990) [INFO] * 2026-03-08 01:58:12 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-08 01:58:12 (10960) [INFO] * 2026-03-08 01:58:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-08 01:58:12 (10973) [INFO] Determining fastest mirrors * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-08 01:58:43 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-08 01:58:43 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-08 01:58:43 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-08 01:58:43 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-08 01:58:43 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-08 01:58:43 (10973) [INFO] yum --disablerepo= ... * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-08 01:58:43 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-08 01:58:43 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] yum-config-manager --disable * 2026-03-08 01:58:43 (10973) [INFO] or * 2026-03-08 01:58:43 (10973) [INFO] subscription-manager repos --disable= * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-08 01:58:43 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-08 01:58:43 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-08 01:58:43 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-08 01:58:43 (10973) [INFO] compromise: * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-08 01:58:43 (10973) [INFO] * 2026-03-08 01:58:43 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-08 01:58:43 (10990) [INFO] * 2026-03-08 01:58:43 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-08 01:58:43 (6792) [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 * 2026-03-08 01:58:44 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-08 01:58:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-08 01:58:44 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-08 01:58:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-08 01:58:44 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-08 01:58:51 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6YeI0zPa4_/ea_profile.json * 2026-03-08 03:01:18 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6YeI0zPa4_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-08 03:01:18 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-09 01:39:09 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-09 01:43:09 (12063) [INFO] Script is up to date. * 2026-03-09 01:47:12 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-09 01:47:12 (10960) [INFO] * 2026-03-09 01:48:33 (10990) [INFO] * 2026-03-09 01:48:33 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-09 01:48:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-09 01:48:34 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-09 01:48:34 (10960) [INFO] * 2026-03-09 01:55:32 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-09 01:55:32 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-09 01:55:32 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-09 01:55:32 (10960) [INFO] * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-09 01:56:08 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-09 01:56:08 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-09 01:56:08 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-09 01:56:08 (10960) [INFO] * 2026-03-09 01:56:08 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-09 01:56:09 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-09 01:56:40 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-09 01:56:40 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-09 01:56:40 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-09 01:56:40 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-09 01:56:40 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-09 01:56:40 (10973) [INFO] yum --disablerepo= ... * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-09 01:56:40 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-09 01:56:40 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] yum-config-manager --disable * 2026-03-09 01:56:40 (10973) [INFO] or * 2026-03-09 01:56:40 (10973) [INFO] subscription-manager repos --disable= * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-09 01:56:40 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-09 01:56:40 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-09 01:56:40 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-09 01:56:40 (10973) [INFO] compromise: * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-09 01:56:40 (10973) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-09 01:56:40 (10990) [INFO] * 2026-03-09 01:56:40 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-09 01:56:40 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-09 01:56:40 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-09 01:56:40 (10960) [INFO] * 2026-03-09 01:56:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-09 01:56:41 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-09 01:56:41 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-09 01:56:41 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-09 01:56:41 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-09 01:56:41 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-09 01:56:41 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-09 01:56:41 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-09 01:56:41 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-09 01:56:41 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-09 01:56:41 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-09 01:56:41 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-09 01:56:41 (10990) [INFO] * 2026-03-09 01:56:41 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-09 01:56:41 (10960) [INFO] * 2026-03-09 01:56:41 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-09 01:56:41 (10973) [INFO] Determining fastest mirrors * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-09 01:57:12 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-09 01:57:12 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-09 01:57:12 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-09 01:57:12 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-09 01:57:12 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-09 01:57:12 (10973) [INFO] yum --disablerepo= ... * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-09 01:57:12 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-09 01:57:12 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] yum-config-manager --disable * 2026-03-09 01:57:12 (10973) [INFO] or * 2026-03-09 01:57:12 (10973) [INFO] subscription-manager repos --disable= * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-09 01:57:12 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-09 01:57:12 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-09 01:57:12 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-09 01:57:12 (10973) [INFO] compromise: * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-09 01:57:12 (10973) [INFO] * 2026-03-09 01:57:12 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-09 01:57:12 (10990) [INFO] * 2026-03-09 01:57:12 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-09 01:57:12 (6792) [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 * 2026-03-09 01:57:14 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-09 01:57:14 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-09 01:57:14 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-09 01:57:14 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-09 01:57:14 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-09 01:57:20 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7PAyWIMhN6/ea_profile.json * 2026-03-09 02:00:18 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/7PAyWIMhN6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-09 02:00:18 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-10 01:38:41 (12041) [INFO] Self-update of script version 79 requested. * 2026-03-10 01:43:41 (12046) [INFO] Newer version of script found. Downloading. * 2026-03-10 01:48:43 (12055) [INFO] Script update to version 80 successful. * 2026-03-10 01:53:45 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-10 01:53:45 (10960) [INFO] * 2026-03-10 01:54:59 (10990) [INFO] * 2026-03-10 01:54:59 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-10 01:54:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-10 01:54:59 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-10 01:54:59 (10960) [INFO] * 2026-03-10 01:55:03 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-10 01:55:03 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-10 01:55:03 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-10 01:55:03 (10960) [INFO] * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-10 01:55:37 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-10 01:55:37 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-10 01:55:37 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-10 01:55:37 (10960) [INFO] * 2026-03-10 01:55:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-10 01:55:38 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-10 01:56:09 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-10 01:56:09 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-10 01:56:09 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-10 01:56:09 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-10 01:56:09 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-10 01:56:09 (10973) [INFO] yum --disablerepo= ... * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-10 01:56:09 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-10 01:56:09 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] yum-config-manager --disable * 2026-03-10 01:56:09 (10973) [INFO] or * 2026-03-10 01:56:09 (10973) [INFO] subscription-manager repos --disable= * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-10 01:56:09 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-10 01:56:09 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-10 01:56:09 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-10 01:56:09 (10973) [INFO] compromise: * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-10 01:56:09 (10973) [INFO] * 2026-03-10 01:56:09 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-10 01:56:09 (10990) [INFO] * 2026-03-10 01:56:09 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-10 01:56:09 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-10 01:56:09 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-10 01:56:09 (10960) [INFO] * 2026-03-10 01:56:10 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-10 01:56:10 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-10 01:56:10 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-10 01:56:10 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-10 01:56:10 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-10 01:56:10 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-10 01:56:10 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-10 01:56:10 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-10 01:56:10 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-10 01:56:10 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-10 01:56:10 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-10 01:56:10 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-10 01:56:10 (10990) [INFO] * 2026-03-10 01:56:10 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-10 01:56:10 (10960) [INFO] * 2026-03-10 01:56:10 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-10 01:56:11 (10973) [INFO] Determining fastest mirrors * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-10 01:56:42 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-10 01:56:42 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-10 01:56:42 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-10 01:56:42 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-10 01:56:42 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-10 01:56:42 (10973) [INFO] yum --disablerepo= ... * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-10 01:56:42 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-10 01:56:42 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] yum-config-manager --disable * 2026-03-10 01:56:42 (10973) [INFO] or * 2026-03-10 01:56:42 (10973) [INFO] subscription-manager repos --disable= * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-10 01:56:42 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-10 01:56:42 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-10 01:56:42 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-10 01:56:42 (10973) [INFO] compromise: * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-10 01:56:42 (10973) [INFO] * 2026-03-10 01:56:42 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-10 01:56:42 (10990) [INFO] * 2026-03-10 01:56:42 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-10 01:56:42 (6792) [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 * 2026-03-10 01:56:44 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-10 01:56:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-10 01:56:44 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-10 01:56:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-10 01:56:44 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-10 01:56:49 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/H5ZjadpbG7/ea_profile.json * 2026-03-10 01:59:49 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/H5ZjadpbG7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-10 01:59:49 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-11 01:49:52 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-11 01:53:52 (12063) [INFO] Script is up to date. * 2026-03-11 01:57:55 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-11 01:57:55 (10960) [INFO] * 2026-03-11 01:59:13 (10990) [INFO] * 2026-03-11 01:59:13 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-11 01:59:13 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-11 01:59:13 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-11 01:59:13 (10960) [INFO] * 2026-03-11 02:06:12 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-11 02:06:12 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-11 02:06:12 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-11 02:06:12 (10960) [INFO] * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-11 02:06:48 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-11 02:06:48 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-11 02:06:48 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-11 02:06:48 (10960) [INFO] * 2026-03-11 02:06:49 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-11 02:06:49 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-11 02:07:21 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-11 02:07:21 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-11 02:07:21 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-11 02:07:21 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-11 02:07:21 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-11 02:07:21 (10973) [INFO] yum --disablerepo= ... * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-11 02:07:21 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-11 02:07:21 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] yum-config-manager --disable * 2026-03-11 02:07:21 (10973) [INFO] or * 2026-03-11 02:07:21 (10973) [INFO] subscription-manager repos --disable= * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-11 02:07:21 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-11 02:07:21 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-11 02:07:21 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-11 02:07:21 (10973) [INFO] compromise: * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-11 02:07:21 (10973) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-11 02:07:21 (10990) [INFO] * 2026-03-11 02:07:21 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-11 02:07:21 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-11 02:07:21 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-11 02:07:21 (10960) [INFO] * 2026-03-11 02:07:21 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-11 02:07:21 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-11 02:07:21 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-11 02:07:21 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-11 02:07:21 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-11 02:07:21 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-11 02:07:21 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-11 02:07:21 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-11 02:07:21 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-11 02:07:21 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-11 02:07:21 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-11 02:07:21 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-11 02:07:21 (10990) [INFO] * 2026-03-11 02:07:21 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-11 02:07:21 (10960) [INFO] * 2026-03-11 02:07:22 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-11 02:07:22 (10973) [INFO] Determining fastest mirrors * 2026-03-11 02:07:53 (10973) [INFO] * 2026-03-11 02:07:53 (10973) [INFO] * 2026-03-11 02:07:53 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-11 02:07:54 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-11 02:07:54 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-11 02:07:54 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-11 02:07:54 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-11 02:07:54 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-11 02:07:54 (10973) [INFO] yum --disablerepo= ... * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-11 02:07:54 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-11 02:07:54 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] yum-config-manager --disable * 2026-03-11 02:07:54 (10973) [INFO] or * 2026-03-11 02:07:54 (10973) [INFO] subscription-manager repos --disable= * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-11 02:07:54 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-11 02:07:54 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-11 02:07:54 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-11 02:07:54 (10973) [INFO] compromise: * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-11 02:07:54 (10973) [INFO] * 2026-03-11 02:07:54 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-11 02:07:54 (10990) [INFO] * 2026-03-11 02:07:54 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-11 02:07:54 (6792) [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 * 2026-03-11 02:07:55 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-11 02:07:55 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-11 02:07:55 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-11 02:07:55 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-11 02:07:55 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-11 02:08:05 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OxeOIQj0El/ea_profile.json * 2026-03-11 02:11:02 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/OxeOIQj0El/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-11 02:11:02 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-12 01:38:37 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-12 01:43:37 (12063) [INFO] Script is up to date. * 2026-03-12 01:48:40 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-12 01:48:40 (10960) [INFO] * 2026-03-12 01:49:59 (10990) [INFO] * 2026-03-12 01:49:59 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-12 01:49:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-12 01:49:59 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-12 01:49:59 (10960) [INFO] * 2026-03-12 01:57:02 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-12 01:57:02 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-12 01:57:02 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-12 01:57:02 (10960) [INFO] * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-12 01:57:37 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-12 01:57:37 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-12 01:57:37 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-12 01:57:37 (10960) [INFO] * 2026-03-12 01:57:37 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-12 01:57:38 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-12 01:58:09 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-12 01:58:09 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-12 01:58:09 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-12 01:58:09 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-12 01:58:09 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-12 01:58:09 (10973) [INFO] yum --disablerepo= ... * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-12 01:58:09 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-12 01:58:09 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] yum-config-manager --disable * 2026-03-12 01:58:09 (10973) [INFO] or * 2026-03-12 01:58:09 (10973) [INFO] subscription-manager repos --disable= * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-12 01:58:09 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-12 01:58:09 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-12 01:58:09 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-12 01:58:09 (10973) [INFO] compromise: * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-12 01:58:09 (10973) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-12 01:58:09 (10990) [INFO] * 2026-03-12 01:58:09 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-12 01:58:09 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-12 01:58:09 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-12 01:58:09 (10960) [INFO] * 2026-03-12 01:58:09 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-12 01:58:10 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-12 01:58:10 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-12 01:58:10 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-12 01:58:10 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-12 01:58:10 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-12 01:58:10 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-12 01:58:10 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-12 01:58:10 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-12 01:58:10 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-12 01:58:10 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-12 01:58:10 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-12 01:58:10 (10990) [INFO] * 2026-03-12 01:58:10 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-12 01:58:10 (10960) [INFO] * 2026-03-12 01:58:10 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-12 01:58:11 (10973) [INFO] Determining fastest mirrors * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-12 01:58:42 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-12 01:58:42 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-12 01:58:42 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-12 01:58:42 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-12 01:58:42 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-12 01:58:42 (10973) [INFO] yum --disablerepo= ... * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-12 01:58:42 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-12 01:58:42 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] yum-config-manager --disable * 2026-03-12 01:58:42 (10973) [INFO] or * 2026-03-12 01:58:42 (10973) [INFO] subscription-manager repos --disable= * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-12 01:58:42 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-12 01:58:42 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-12 01:58:42 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-12 01:58:42 (10973) [INFO] compromise: * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-12 01:58:42 (10973) [INFO] * 2026-03-12 01:58:42 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-12 01:58:42 (10990) [INFO] * 2026-03-12 01:58:42 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-12 01:58:42 (6792) [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 * 2026-03-12 01:58:43 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-12 01:58:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-12 01:58:43 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-12 01:58:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-12 01:58:43 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-12 01:58:50 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UqvIIsNslV/ea_profile.json * 2026-03-12 02:01:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/UqvIIsNslV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-12 02:01:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-13 01:41:42 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-13 01:46:42 (12063) [INFO] Script is up to date. * 2026-03-13 01:51:46 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-13 01:51:46 (10960) [INFO] * 2026-03-13 01:53:04 (10990) [INFO] * 2026-03-13 01:53:04 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-13 01:53:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-13 01:53:04 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-13 01:53:04 (10960) [INFO] * 2026-03-13 02:00:06 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-13 02:00:06 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-13 02:00:06 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-13 02:00:06 (10960) [INFO] * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-13 02:00:41 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-13 02:00:41 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-13 02:00:41 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-13 02:00:41 (10960) [INFO] * 2026-03-13 02:00:42 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-13 02:00:42 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-13 02:01:13 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-13 02:01:13 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-13 02:01:13 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-13 02:01:13 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-13 02:01:13 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-13 02:01:13 (10973) [INFO] yum --disablerepo= ... * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-13 02:01:13 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-13 02:01:13 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] yum-config-manager --disable * 2026-03-13 02:01:13 (10973) [INFO] or * 2026-03-13 02:01:13 (10973) [INFO] subscription-manager repos --disable= * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-13 02:01:13 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-13 02:01:13 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-13 02:01:13 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-13 02:01:13 (10973) [INFO] compromise: * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-13 02:01:13 (10973) [INFO] * 2026-03-13 02:01:13 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-13 02:01:13 (10990) [INFO] * 2026-03-13 02:01:13 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-13 02:01:13 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-13 02:01:13 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-13 02:01:13 (10960) [INFO] * 2026-03-13 02:01:14 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-13 02:01:14 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-13 02:01:14 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-13 02:01:14 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-13 02:01:14 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-13 02:01:14 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-13 02:01:14 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-13 02:01:14 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-13 02:01:14 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-13 02:01:14 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-13 02:01:14 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-13 02:01:14 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-13 02:01:14 (10990) [INFO] * 2026-03-13 02:01:14 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-13 02:01:14 (10960) [INFO] * 2026-03-13 02:01:15 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-13 02:01:15 (10973) [INFO] Determining fastest mirrors * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-13 02:01:46 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-13 02:01:46 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-13 02:01:46 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-13 02:01:46 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-13 02:01:46 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-13 02:01:46 (10973) [INFO] yum --disablerepo= ... * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-13 02:01:46 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-13 02:01:46 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] yum-config-manager --disable * 2026-03-13 02:01:46 (10973) [INFO] or * 2026-03-13 02:01:46 (10973) [INFO] subscription-manager repos --disable= * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-13 02:01:46 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-13 02:01:46 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-13 02:01:46 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-13 02:01:46 (10973) [INFO] compromise: * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-13 02:01:46 (10973) [INFO] * 2026-03-13 02:01:46 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-13 02:01:46 (10990) [INFO] * 2026-03-13 02:01:46 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-13 02:01:46 (6792) [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 * 2026-03-13 02:01:48 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-13 02:01:48 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-13 02:01:48 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-13 02:01:48 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-13 02:01:48 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-13 02:01:54 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MvRMQPz_QE/ea_profile.json * 2026-03-13 02:04:52 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/MvRMQPz_QE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-13 02:04:52 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-14 01:39:53 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-14 01:44:54 (12063) [INFO] Script is up to date. * 2026-03-14 01:49:57 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-14 01:49:57 (10960) [INFO] * 2026-03-14 01:50:48 (10990) [INFO] * 2026-03-14 01:50:48 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-14 01:50:48 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-14 01:50:48 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-14 01:50:48 (10960) [INFO] * 2026-03-14 01:57:50 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-14 01:57:50 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-14 01:57:50 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-14 01:57:50 (10960) [INFO] * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-14 01:58:26 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-14 01:58:26 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-14 01:58:26 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-14 01:58:26 (10960) [INFO] * 2026-03-14 01:58:26 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-14 01:58:27 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-14 01:58:58 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-14 01:58:58 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-14 01:58:58 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-14 01:58:58 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-14 01:58:58 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-14 01:58:58 (10973) [INFO] yum --disablerepo= ... * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-14 01:58:58 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-14 01:58:58 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] yum-config-manager --disable * 2026-03-14 01:58:58 (10973) [INFO] or * 2026-03-14 01:58:58 (10973) [INFO] subscription-manager repos --disable= * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-14 01:58:58 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-14 01:58:58 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-14 01:58:58 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-14 01:58:58 (10973) [INFO] compromise: * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-14 01:58:58 (10973) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-14 01:58:58 (10990) [INFO] * 2026-03-14 01:58:58 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-14 01:58:58 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-14 01:58:58 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-14 01:58:58 (10960) [INFO] * 2026-03-14 01:58:58 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-14 01:58:59 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-14 01:58:59 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-14 01:58:59 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-14 01:58:59 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-14 01:58:59 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-14 01:58:59 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-14 01:58:59 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-14 01:58:59 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-14 01:58:59 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-14 01:58:59 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-14 01:58:59 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-14 01:58:59 (10990) [INFO] * 2026-03-14 01:58:59 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-14 01:58:59 (10960) [INFO] * 2026-03-14 01:58:59 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-14 01:59:00 (10973) [INFO] Determining fastest mirrors * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-14 01:59:30 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-14 01:59:30 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-14 01:59:30 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-14 01:59:30 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-14 01:59:30 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-14 01:59:30 (10973) [INFO] yum --disablerepo= ... * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-14 01:59:30 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-14 01:59:30 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] yum-config-manager --disable * 2026-03-14 01:59:30 (10973) [INFO] or * 2026-03-14 01:59:30 (10973) [INFO] subscription-manager repos --disable= * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-14 01:59:30 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-14 01:59:30 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-14 01:59:30 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-14 01:59:30 (10973) [INFO] compromise: * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-14 01:59:30 (10973) [INFO] * 2026-03-14 01:59:30 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-14 01:59:30 (10990) [INFO] * 2026-03-14 01:59:30 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-14 01:59:30 (6792) [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 * 2026-03-14 01:59:31 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-14 01:59:31 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-14 01:59:31 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-14 01:59:31 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-14 01:59:31 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-14 01:59:40 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oHu7l2lljw/ea_profile.json * 2026-03-14 02:03:08 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/oHu7l2lljw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-14 02:03:08 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-15 01:42:42 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-15 01:47:42 (12063) [INFO] Script is up to date. * 2026-03-15 01:52:44 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-15 01:52:44 (10960) [INFO] * 2026-03-15 01:53:37 (10990) [INFO] * 2026-03-15 01:53:37 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-15 01:53:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-15 01:53:38 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-15 01:53:38 (10960) [INFO] * 2026-03-15 02:00:38 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-15 02:00:38 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-15 02:00:38 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-15 02:00:38 (10960) [INFO] * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-15 02:01:15 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-15 02:01:15 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-15 02:01:15 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-15 02:01:15 (10960) [INFO] * 2026-03-15 02:01:15 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-15 02:01:15 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-15 02:01:46 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-15 02:01:46 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-15 02:01:46 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-15 02:01:46 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-15 02:01:46 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-15 02:01:46 (10973) [INFO] yum --disablerepo= ... * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-15 02:01:46 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-15 02:01:46 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] yum-config-manager --disable * 2026-03-15 02:01:46 (10973) [INFO] or * 2026-03-15 02:01:46 (10973) [INFO] subscription-manager repos --disable= * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-15 02:01:46 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-15 02:01:46 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-15 02:01:46 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-15 02:01:46 (10973) [INFO] compromise: * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-15 02:01:46 (10973) [INFO] * 2026-03-15 02:01:46 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-15 02:01:46 (10990) [INFO] * 2026-03-15 02:01:46 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-15 02:01:46 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-15 02:01:46 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-15 02:01:46 (10960) [INFO] * 2026-03-15 02:01:47 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-15 02:01:47 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-15 02:01:47 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-15 02:01:47 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-15 02:01:47 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-15 02:01:47 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-15 02:01:47 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-15 02:01:47 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-15 02:01:47 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-15 02:01:47 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-15 02:01:47 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-15 02:01:47 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-15 02:01:47 (10990) [INFO] * 2026-03-15 02:01:47 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-15 02:01:47 (10960) [INFO] * 2026-03-15 02:01:47 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-15 02:01:48 (10973) [INFO] Determining fastest mirrors * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-15 02:02:18 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-15 02:02:18 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-15 02:02:18 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-15 02:02:18 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-15 02:02:18 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-15 02:02:18 (10973) [INFO] yum --disablerepo= ... * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-15 02:02:18 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-15 02:02:18 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] yum-config-manager --disable * 2026-03-15 02:02:18 (10973) [INFO] or * 2026-03-15 02:02:18 (10973) [INFO] subscription-manager repos --disable= * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-15 02:02:18 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-15 02:02:18 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-15 02:02:18 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-15 02:02:18 (10973) [INFO] compromise: * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-15 02:02:18 (10973) [INFO] * 2026-03-15 02:02:18 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-15 02:02:18 (10990) [INFO] * 2026-03-15 02:02:18 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-15 02:02:18 (6792) [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 * 2026-03-15 02:02:20 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-15 02:02:20 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-15 02:02:20 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-15 02:02:20 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-15 02:02:20 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-15 02:02:27 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qq_8EZkyzO/ea_profile.json * 2026-03-15 02:04:31 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qq_8EZkyzO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-15 02:04:31 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-16 01:39:43 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-16 01:43:43 (12063) [INFO] Script is up to date. * 2026-03-16 01:47:46 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-16 01:47:46 (10960) [INFO] * 2026-03-16 01:49:10 (10990) [INFO] * 2026-03-16 01:49:10 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-16 01:49:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-16 01:49:11 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-16 01:49:11 (10960) [INFO] * 2026-03-16 01:56:12 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-16 01:56:12 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-16 01:56:12 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-16 01:56:12 (10960) [INFO] * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-16 01:56:47 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-16 01:56:47 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-16 01:56:47 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-16 01:56:47 (10960) [INFO] * 2026-03-16 01:56:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-16 01:56:48 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-16 01:57:19 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-16 01:57:19 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-16 01:57:19 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-16 01:57:19 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-16 01:57:19 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-16 01:57:19 (10973) [INFO] yum --disablerepo= ... * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-16 01:57:19 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-16 01:57:19 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] yum-config-manager --disable * 2026-03-16 01:57:19 (10973) [INFO] or * 2026-03-16 01:57:19 (10973) [INFO] subscription-manager repos --disable= * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-16 01:57:19 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-16 01:57:19 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-16 01:57:19 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-16 01:57:19 (10973) [INFO] compromise: * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-16 01:57:19 (10973) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-16 01:57:19 (10990) [INFO] * 2026-03-16 01:57:19 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-16 01:57:19 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-16 01:57:19 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-16 01:57:19 (10960) [INFO] * 2026-03-16 01:57:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-16 01:57:20 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-16 01:57:20 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-16 01:57:20 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-16 01:57:20 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-16 01:57:20 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-16 01:57:20 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-16 01:57:20 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-16 01:57:20 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-16 01:57:20 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-16 01:57:20 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-16 01:57:20 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-16 01:57:20 (10990) [INFO] * 2026-03-16 01:57:20 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-16 01:57:20 (10960) [INFO] * 2026-03-16 01:57:20 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-16 01:57:21 (10973) [INFO] Determining fastest mirrors * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-16 01:57:51 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-16 01:57:51 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-16 01:57:51 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-16 01:57:51 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-16 01:57:51 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-16 01:57:51 (10973) [INFO] yum --disablerepo= ... * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-16 01:57:51 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-16 01:57:51 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] yum-config-manager --disable * 2026-03-16 01:57:51 (10973) [INFO] or * 2026-03-16 01:57:51 (10973) [INFO] subscription-manager repos --disable= * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-16 01:57:51 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-16 01:57:51 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-16 01:57:51 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-16 01:57:51 (10973) [INFO] compromise: * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-16 01:57:51 (10973) [INFO] * 2026-03-16 01:57:51 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-16 01:57:51 (10990) [INFO] * 2026-03-16 01:57:52 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-16 01:57:52 (6792) [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 * 2026-03-16 01:57:53 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-16 01:57:53 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-16 01:57:53 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-16 01:57:53 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-16 01:57:53 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-16 01:57:59 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/76k4opCaHa/ea_profile.json * 2026-03-16 02:00:26 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/76k4opCaHa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-16 02:00:26 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-17 01:38:20 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-17 01:42:21 (12063) [INFO] Script is up to date. * 2026-03-17 01:46:23 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-17 01:46:23 (10960) [INFO] * 2026-03-17 01:47:38 (10990) [INFO] * 2026-03-17 01:47:38 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-17 01:47:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-17 01:47:39 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-17 01:47:39 (10960) [INFO] * 2026-03-17 01:54:41 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-17 01:54:41 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-17 01:54:41 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-17 01:54:41 (10960) [INFO] * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-17 01:55:17 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-17 01:55:17 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-17 01:55:17 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-17 01:55:17 (10960) [INFO] * 2026-03-17 01:55:17 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-17 01:55:17 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-17 01:55:49 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-17 01:55:49 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-17 01:55:49 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-17 01:55:49 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-17 01:55:49 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-17 01:55:49 (10973) [INFO] yum --disablerepo= ... * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-17 01:55:49 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-17 01:55:49 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] yum-config-manager --disable * 2026-03-17 01:55:49 (10973) [INFO] or * 2026-03-17 01:55:49 (10973) [INFO] subscription-manager repos --disable= * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-17 01:55:49 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-17 01:55:49 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-17 01:55:49 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-17 01:55:49 (10973) [INFO] compromise: * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-17 01:55:49 (10973) [INFO] * 2026-03-17 01:55:49 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-17 01:55:49 (10990) [INFO] * 2026-03-17 01:55:49 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-17 01:55:49 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-17 01:55:49 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-17 01:55:49 (10960) [INFO] * 2026-03-17 01:55:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-17 01:55:50 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-17 01:55:50 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-17 01:55:50 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-17 01:55:50 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-17 01:55:50 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-17 01:55:50 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-17 01:55:50 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-17 01:55:50 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-17 01:55:50 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-17 01:55:50 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-17 01:55:50 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-17 01:55:50 (10990) [INFO] * 2026-03-17 01:55:50 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-17 01:55:50 (10960) [INFO] * 2026-03-17 01:55:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-17 01:55:50 (10973) [INFO] Determining fastest mirrors * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-17 01:56:22 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-17 01:56:22 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-17 01:56:22 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-17 01:56:22 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-17 01:56:22 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-17 01:56:22 (10973) [INFO] yum --disablerepo= ... * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-17 01:56:22 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-17 01:56:22 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] yum-config-manager --disable * 2026-03-17 01:56:22 (10973) [INFO] or * 2026-03-17 01:56:22 (10973) [INFO] subscription-manager repos --disable= * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-17 01:56:22 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-17 01:56:22 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-17 01:56:22 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-17 01:56:22 (10973) [INFO] compromise: * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-17 01:56:22 (10973) [INFO] * 2026-03-17 01:56:22 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-17 01:56:22 (10990) [INFO] * 2026-03-17 01:56:22 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-17 01:56:22 (6792) [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 * 2026-03-17 01:56:24 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-17 01:56:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-17 01:56:24 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-17 01:56:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-17 01:56:24 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-17 01:56:30 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6_TT1v8t7n/ea_profile.json * 2026-03-17 01:59:29 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/6_TT1v8t7n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-17 01:59:29 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-18 01:38:38 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-18 01:42:38 (12063) [INFO] Script is up to date. * 2026-03-18 01:47:42 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-18 01:47:42 (10960) [INFO] * 2026-03-18 01:49:05 (10990) [INFO] * 2026-03-18 01:49:05 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-18 01:49:05 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-18 01:49:05 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-18 01:49:05 (10960) [INFO] * 2026-03-18 02:01:11 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-18 02:01:11 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-18 02:01:11 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-18 02:01:11 (10960) [INFO] * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-18 02:01:46 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-18 02:01:46 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-18 02:01:46 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-18 02:01:46 (10960) [INFO] * 2026-03-18 02:01:46 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-18 02:01:47 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-18 02:02:18 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-18 02:02:18 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-18 02:02:18 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-18 02:02:18 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-18 02:02:18 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-18 02:02:18 (10973) [INFO] yum --disablerepo= ... * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-18 02:02:18 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-18 02:02:18 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] yum-config-manager --disable * 2026-03-18 02:02:18 (10973) [INFO] or * 2026-03-18 02:02:18 (10973) [INFO] subscription-manager repos --disable= * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-18 02:02:18 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-18 02:02:18 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-18 02:02:18 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-18 02:02:18 (10973) [INFO] compromise: * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-18 02:02:18 (10973) [INFO] * 2026-03-18 02:02:18 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-18 02:02:18 (10990) [INFO] * 2026-03-18 02:02:18 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-18 02:02:18 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-18 02:02:18 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-18 02:02:18 (10960) [INFO] * 2026-03-18 02:02:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-18 02:02:19 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-18 02:02:19 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-18 02:02:19 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-18 02:02:19 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-18 02:02:19 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-18 02:02:19 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-18 02:02:19 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-18 02:02:19 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-18 02:02:19 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-18 02:02:19 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-18 02:02:19 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-18 02:02:19 (10990) [INFO] * 2026-03-18 02:02:19 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-18 02:02:19 (10960) [INFO] * 2026-03-18 02:02:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-18 02:02:20 (10973) [INFO] Determining fastest mirrors * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-18 02:02:50 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-18 02:02:50 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-18 02:02:50 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-18 02:02:50 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-18 02:02:50 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-18 02:02:50 (10973) [INFO] yum --disablerepo= ... * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-18 02:02:50 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-18 02:02:50 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] yum-config-manager --disable * 2026-03-18 02:02:50 (10973) [INFO] or * 2026-03-18 02:02:50 (10973) [INFO] subscription-manager repos --disable= * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-18 02:02:50 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-18 02:02:50 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-18 02:02:50 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-18 02:02:50 (10973) [INFO] compromise: * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-18 02:02:50 (10973) [INFO] * 2026-03-18 02:02:50 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-18 02:02:50 (10990) [INFO] * 2026-03-18 02:02:50 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-18 02:02:50 (6792) [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 * 2026-03-18 02:02:52 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-18 02:02:52 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-18 02:02:52 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-18 02:02:52 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-18 02:02:52 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-18 02:03:00 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bzpfwU5lwX/ea_profile.json * 2026-03-18 02:05:26 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bzpfwU5lwX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-18 02:05:26 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-19 01:39:11 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-19 01:44:11 (12063) [INFO] Script is up to date. * 2026-03-19 01:49:15 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-19 01:49:15 (10960) [INFO] * 2026-03-19 01:50:37 (10990) [INFO] * 2026-03-19 01:50:37 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-19 01:50:38 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-19 01:50:38 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-19 01:50:38 (10960) [INFO] * 2026-03-19 01:50:41 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-19 01:50:41 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-19 01:50:41 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-19 01:50:41 (10960) [INFO] * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-19 01:51:15 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-19 01:51:15 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-19 01:51:15 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-19 01:51:15 (10960) [INFO] * 2026-03-19 01:51:16 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-19 01:51:16 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-19 01:51:47 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-19 01:51:47 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-19 01:51:47 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-19 01:51:47 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-19 01:51:47 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-19 01:51:47 (10973) [INFO] yum --disablerepo= ... * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-19 01:51:47 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-19 01:51:47 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] yum-config-manager --disable * 2026-03-19 01:51:47 (10973) [INFO] or * 2026-03-19 01:51:47 (10973) [INFO] subscription-manager repos --disable= * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-19 01:51:47 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-19 01:51:47 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-19 01:51:47 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-19 01:51:47 (10973) [INFO] compromise: * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-19 01:51:47 (10973) [INFO] * 2026-03-19 01:51:47 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-19 01:51:47 (10990) [INFO] * 2026-03-19 01:51:47 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-19 01:51:47 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-19 01:51:47 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-19 01:51:47 (10960) [INFO] * 2026-03-19 01:51:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-19 01:51:48 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-19 01:51:48 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-19 01:51:48 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-19 01:51:48 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-19 01:51:48 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-19 01:51:48 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-19 01:51:48 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-19 01:51:48 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-19 01:51:48 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-19 01:51:48 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-19 01:51:48 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-19 01:51:48 (10990) [INFO] * 2026-03-19 01:51:48 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-19 01:51:48 (10960) [INFO] * 2026-03-19 01:51:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-19 01:51:49 (10973) [INFO] Determining fastest mirrors * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-19 01:52:20 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-19 01:52:20 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-19 01:52:20 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-19 01:52:20 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-19 01:52:20 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-19 01:52:20 (10973) [INFO] yum --disablerepo= ... * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-19 01:52:20 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-19 01:52:20 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] yum-config-manager --disable * 2026-03-19 01:52:20 (10973) [INFO] or * 2026-03-19 01:52:20 (10973) [INFO] subscription-manager repos --disable= * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-19 01:52:20 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-19 01:52:20 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-19 01:52:20 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-19 01:52:20 (10973) [INFO] compromise: * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-19 01:52:20 (10973) [INFO] * 2026-03-19 01:52:20 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-19 01:52:20 (10990) [INFO] * 2026-03-19 01:52:20 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-19 01:52:20 (6792) [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 * 2026-03-19 01:52:22 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-19 01:52:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-19 01:52:22 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-19 01:52:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-19 01:52:22 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-19 01:52:28 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2J9Gnoek97/ea_profile.json * 2026-03-19 01:54:55 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/2J9Gnoek97/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-19 01:54:55 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-20 01:41:21 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-20 01:46:21 (12063) [INFO] Script is up to date. * 2026-03-20 01:51:25 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-20 01:51:25 (10960) [INFO] * 2026-03-20 01:52:43 (10990) [INFO] * 2026-03-20 01:52:43 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-20 01:52:44 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-20 01:52:44 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-20 01:52:44 (10960) [INFO] * 2026-03-20 01:52:48 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-20 01:52:48 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-20 01:52:48 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-20 01:52:48 (10960) [INFO] * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-20 01:53:24 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-20 01:53:24 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-20 01:53:24 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-20 01:53:24 (10960) [INFO] * 2026-03-20 01:53:24 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-20 01:53:24 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-20 01:53:56 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-20 01:53:56 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-20 01:53:56 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-20 01:53:56 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-20 01:53:56 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-20 01:53:56 (10973) [INFO] yum --disablerepo= ... * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-20 01:53:56 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-20 01:53:56 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] yum-config-manager --disable * 2026-03-20 01:53:56 (10973) [INFO] or * 2026-03-20 01:53:56 (10973) [INFO] subscription-manager repos --disable= * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-20 01:53:56 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-20 01:53:56 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-20 01:53:56 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-20 01:53:56 (10973) [INFO] compromise: * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-20 01:53:56 (10973) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-20 01:53:56 (10990) [INFO] * 2026-03-20 01:53:56 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-20 01:53:56 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-20 01:53:56 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-20 01:53:56 (10960) [INFO] * 2026-03-20 01:53:56 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-20 01:53:57 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-20 01:53:57 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-20 01:53:57 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-20 01:53:57 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-20 01:53:57 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-20 01:53:57 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-20 01:53:57 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-20 01:53:57 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-20 01:53:57 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-20 01:53:57 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-20 01:53:57 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-20 01:53:57 (10990) [INFO] * 2026-03-20 01:53:57 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-20 01:53:57 (10960) [INFO] * 2026-03-20 01:53:57 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-20 01:53:57 (10973) [INFO] Determining fastest mirrors * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-20 01:54:28 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-20 01:54:28 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-20 01:54:28 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-20 01:54:28 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-20 01:54:28 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-20 01:54:28 (10973) [INFO] yum --disablerepo= ... * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-20 01:54:28 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-20 01:54:28 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] yum-config-manager --disable * 2026-03-20 01:54:28 (10973) [INFO] or * 2026-03-20 01:54:28 (10973) [INFO] subscription-manager repos --disable= * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-20 01:54:28 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-20 01:54:28 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-20 01:54:28 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-20 01:54:28 (10973) [INFO] compromise: * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-20 01:54:28 (10973) [INFO] * 2026-03-20 01:54:28 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-20 01:54:28 (10990) [INFO] * 2026-03-20 01:54:28 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-20 01:54:28 (6792) [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 * 2026-03-20 01:54:29 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-20 01:54:29 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-20 01:54:29 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-20 01:54:29 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-20 01:54:29 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-20 01:54:35 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jYt9f4Pohr/ea_profile.json * 2026-03-20 01:57:33 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/jYt9f4Pohr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-20 01:57:33 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-21 01:39:51 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-21 01:43:51 (12063) [INFO] Script is up to date. * 2026-03-21 01:47:55 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-21 01:47:55 (10960) [INFO] * 2026-03-21 01:48:46 (10990) [INFO] * 2026-03-21 01:48:46 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-21 01:48:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-21 01:48:47 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-21 01:48:47 (10960) [INFO] * 2026-03-21 01:55:49 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-21 01:55:49 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-21 01:55:49 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-21 01:55:49 (10960) [INFO] * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-21 01:56:24 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-21 01:56:24 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-21 01:56:24 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-21 01:56:24 (10960) [INFO] * 2026-03-21 01:56:24 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-21 01:56:25 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-21 01:56:56 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-21 01:56:56 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-21 01:56:56 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-21 01:56:56 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-21 01:56:56 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-21 01:56:56 (10973) [INFO] yum --disablerepo= ... * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-21 01:56:56 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-21 01:56:56 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] yum-config-manager --disable * 2026-03-21 01:56:56 (10973) [INFO] or * 2026-03-21 01:56:56 (10973) [INFO] subscription-manager repos --disable= * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-21 01:56:56 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-21 01:56:56 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-21 01:56:56 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-21 01:56:56 (10973) [INFO] compromise: * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-21 01:56:56 (10973) [INFO] * 2026-03-21 01:56:56 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-21 01:56:56 (10990) [INFO] * 2026-03-21 01:56:56 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-21 01:56:56 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-21 01:56:56 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-21 01:56:56 (10960) [INFO] * 2026-03-21 01:56:57 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-21 01:56:57 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-21 01:56:57 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-21 01:56:57 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-21 01:56:57 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-21 01:56:57 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-21 01:56:57 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-21 01:56:57 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-21 01:56:57 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-21 01:56:57 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-21 01:56:57 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-21 01:56:57 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-21 01:56:57 (10990) [INFO] * 2026-03-21 01:56:57 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-21 01:56:57 (10960) [INFO] * 2026-03-21 01:56:58 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-21 01:56:58 (10973) [INFO] Determining fastest mirrors * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-21 01:57:29 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-21 01:57:29 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-21 01:57:29 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-21 01:57:29 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-21 01:57:29 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-21 01:57:29 (10973) [INFO] yum --disablerepo= ... * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-21 01:57:29 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-21 01:57:29 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] yum-config-manager --disable * 2026-03-21 01:57:29 (10973) [INFO] or * 2026-03-21 01:57:29 (10973) [INFO] subscription-manager repos --disable= * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-21 01:57:29 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-21 01:57:29 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-21 01:57:29 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-21 01:57:29 (10973) [INFO] compromise: * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-21 01:57:29 (10973) [INFO] * 2026-03-21 01:57:29 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-21 01:57:29 (10990) [INFO] * 2026-03-21 01:57:29 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-21 01:57:29 (6792) [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 * 2026-03-21 01:57:31 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-21 01:57:31 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-21 01:57:31 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-21 01:57:31 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-21 01:57:31 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-21 01:57:37 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VJk6iT00Cu/ea_profile.json * 2026-03-21 02:00:05 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VJk6iT00Cu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-21 02:00:05 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-22 01:42:37 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-22 01:47:37 (12063) [INFO] Script is up to date. * 2026-03-22 01:52:40 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-22 01:52:40 (10960) [INFO] * 2026-03-22 01:53:29 (10990) [INFO] * 2026-03-22 01:53:29 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-22 01:53:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-22 01:53:30 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-22 01:53:30 (10960) [INFO] * 2026-03-22 01:53:35 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-22 01:53:35 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-22 01:53:35 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-22 01:53:35 (10960) [INFO] * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-22 01:54:11 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-22 01:54:11 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-22 01:54:11 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-22 01:54:11 (10960) [INFO] * 2026-03-22 01:54:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-22 01:54:12 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-22 01:54:42 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-22 01:54:42 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-22 01:54:42 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-22 01:54:42 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-22 01:54:42 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-22 01:54:42 (10973) [INFO] yum --disablerepo= ... * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-22 01:54:42 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-22 01:54:42 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] yum-config-manager --disable * 2026-03-22 01:54:42 (10973) [INFO] or * 2026-03-22 01:54:42 (10973) [INFO] subscription-manager repos --disable= * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-22 01:54:42 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-22 01:54:42 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-22 01:54:42 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-22 01:54:42 (10973) [INFO] compromise: * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-22 01:54:42 (10973) [INFO] * 2026-03-22 01:54:42 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-22 01:54:42 (10990) [INFO] * 2026-03-22 01:54:42 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-22 01:54:42 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-22 01:54:42 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-22 01:54:42 (10960) [INFO] * 2026-03-22 01:54:43 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-22 01:54:43 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-22 01:54:43 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-22 01:54:43 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-22 01:54:43 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-22 01:54:43 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-22 01:54:43 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-22 01:54:43 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-22 01:54:43 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-22 01:54:43 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-22 01:54:43 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-22 01:54:43 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-22 01:54:43 (10990) [INFO] * 2026-03-22 01:54:43 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-22 01:54:43 (10960) [INFO] * 2026-03-22 01:54:44 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-22 01:54:44 (10973) [INFO] Determining fastest mirrors * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-22 01:55:15 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-22 01:55:15 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-22 01:55:15 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-22 01:55:15 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-22 01:55:15 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-22 01:55:15 (10973) [INFO] yum --disablerepo= ... * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-22 01:55:15 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-22 01:55:15 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] yum-config-manager --disable * 2026-03-22 01:55:15 (10973) [INFO] or * 2026-03-22 01:55:15 (10973) [INFO] subscription-manager repos --disable= * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-22 01:55:15 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-22 01:55:15 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-22 01:55:15 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-22 01:55:15 (10973) [INFO] compromise: * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-22 01:55:15 (10973) [INFO] * 2026-03-22 01:55:15 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-22 01:55:15 (10990) [INFO] * 2026-03-22 01:55:15 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-22 01:55:15 (6792) [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 * 2026-03-22 01:55:17 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-22 01:55:17 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-22 01:55:17 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-22 01:55:17 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-22 01:55:17 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-22 01:55:23 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/PfEXX_6L48/ea_profile.json * 2026-03-22 01:57:49 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/PfEXX_6L48/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-22 01:57:49 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-23 01:38:44 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-23 01:43:44 (12063) [INFO] Script is up to date. * 2026-03-23 01:48:47 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-23 01:48:47 (10960) [INFO] * 2026-03-23 01:50:11 (10990) [INFO] * 2026-03-23 01:50:11 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-23 01:50:11 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-23 01:50:11 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-23 01:50:11 (10960) [INFO] * 2026-03-23 01:50:14 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-23 01:50:14 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-23 01:50:14 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-23 01:50:14 (10960) [INFO] * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-23 01:50:49 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-23 01:50:49 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-23 01:50:49 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-23 01:50:49 (10960) [INFO] * 2026-03-23 01:50:50 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-23 01:50:50 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-23 01:51:20 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-23 01:51:20 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-23 01:51:20 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-23 01:51:20 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-23 01:51:20 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-23 01:51:20 (10973) [INFO] yum --disablerepo= ... * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-23 01:51:20 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-23 01:51:20 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] yum-config-manager --disable * 2026-03-23 01:51:20 (10973) [INFO] or * 2026-03-23 01:51:20 (10973) [INFO] subscription-manager repos --disable= * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-23 01:51:20 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-23 01:51:20 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-23 01:51:20 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-23 01:51:20 (10973) [INFO] compromise: * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-23 01:51:20 (10973) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-23 01:51:20 (10990) [INFO] * 2026-03-23 01:51:20 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-23 01:51:20 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-23 01:51:20 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-23 01:51:20 (10960) [INFO] * 2026-03-23 01:51:20 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-23 01:51:21 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-23 01:51:21 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-23 01:51:21 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-23 01:51:21 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-23 01:51:21 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-23 01:51:21 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-23 01:51:21 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-23 01:51:21 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-23 01:51:21 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-23 01:51:21 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-23 01:51:21 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-23 01:51:21 (10990) [INFO] * 2026-03-23 01:51:21 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-23 01:51:21 (10960) [INFO] * 2026-03-23 01:51:21 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-23 01:51:21 (10973) [INFO] Determining fastest mirrors * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-23 01:51:52 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-23 01:51:52 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-23 01:51:52 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-23 01:51:52 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-23 01:51:52 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-23 01:51:52 (10973) [INFO] yum --disablerepo= ... * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-23 01:51:52 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-23 01:51:52 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] yum-config-manager --disable * 2026-03-23 01:51:52 (10973) [INFO] or * 2026-03-23 01:51:52 (10973) [INFO] subscription-manager repos --disable= * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-23 01:51:52 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-23 01:51:52 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-23 01:51:52 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-23 01:51:52 (10973) [INFO] compromise: * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-23 01:51:52 (10973) [INFO] * 2026-03-23 01:51:52 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-23 01:51:52 (10990) [INFO] * 2026-03-23 01:51:52 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-23 01:51:52 (6792) [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 * 2026-03-23 01:51:53 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-23 01:51:53 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-23 01:51:53 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-23 01:51:53 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-23 01:51:53 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-23 01:52:02 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HufP2PgCen/ea_profile.json * 2026-03-23 01:54:29 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HufP2PgCen/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-23 01:54:29 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-24 01:46:09 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-24 01:51:10 (12063) [INFO] Script is up to date. * 2026-03-24 01:56:13 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-24 01:56:13 (10960) [INFO] * 2026-03-24 01:57:29 (10990) [INFO] * 2026-03-24 01:57:29 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-24 01:57:29 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-24 01:57:29 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-24 01:57:29 (10960) [INFO] * 2026-03-24 02:02:03 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-24 02:02:03 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-24 02:02:03 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-24 02:02:03 (10960) [INFO] * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-24 02:02:39 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-24 02:02:39 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-24 02:02:39 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-24 02:02:39 (10960) [INFO] * 2026-03-24 02:02:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-24 02:02:40 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-24 02:03:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-24 02:03:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-24 02:03:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-24 02:03:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-24 02:03:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-24 02:03:11 (10973) [INFO] yum --disablerepo= ... * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-24 02:03:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-24 02:03:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] yum-config-manager --disable * 2026-03-24 02:03:11 (10973) [INFO] or * 2026-03-24 02:03:11 (10973) [INFO] subscription-manager repos --disable= * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-24 02:03:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-24 02:03:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-24 02:03:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-24 02:03:11 (10973) [INFO] compromise: * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-24 02:03:11 (10973) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-24 02:03:11 (10990) [INFO] * 2026-03-24 02:03:11 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-24 02:03:11 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-24 02:03:11 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-24 02:03:11 (10960) [INFO] * 2026-03-24 02:03:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-24 02:03:12 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-24 02:03:12 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-24 02:03:12 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-24 02:03:12 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-24 02:03:12 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-24 02:03:12 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-24 02:03:12 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-24 02:03:12 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-24 02:03:12 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-24 02:03:12 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-24 02:03:12 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-24 02:03:12 (10990) [INFO] * 2026-03-24 02:03:12 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-24 02:03:12 (10960) [INFO] * 2026-03-24 02:03:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-24 02:03:13 (10973) [INFO] Determining fastest mirrors * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-24 02:03:43 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-24 02:03:43 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-24 02:03:43 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-24 02:03:43 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-24 02:03:43 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-24 02:03:43 (10973) [INFO] yum --disablerepo= ... * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-24 02:03:43 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-24 02:03:43 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] yum-config-manager --disable * 2026-03-24 02:03:43 (10973) [INFO] or * 2026-03-24 02:03:43 (10973) [INFO] subscription-manager repos --disable= * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-24 02:03:43 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-24 02:03:43 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-24 02:03:43 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-24 02:03:43 (10973) [INFO] compromise: * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-24 02:03:43 (10973) [INFO] * 2026-03-24 02:03:43 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-24 02:03:43 (10990) [INFO] * 2026-03-24 02:03:43 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-24 02:03:43 (6792) [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 * 2026-03-24 02:03:45 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-24 02:03:45 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-24 02:03:45 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-24 02:03:45 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-24 02:03:45 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-24 02:03:52 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eFngJ6s8kf/ea_profile.json * 2026-03-24 02:06:49 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/eFngJ6s8kf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-24 02:06:49 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-25 01:38:17 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-25 01:43:17 (12063) [INFO] Script is up to date. * 2026-03-25 01:48:20 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-25 01:48:20 (10960) [INFO] * 2026-03-25 01:49:41 (10990) [INFO] * 2026-03-25 01:49:41 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-25 01:49:42 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-25 01:49:42 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-25 01:49:42 (10960) [INFO] * 2026-03-25 01:56:43 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-25 01:56:43 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-25 01:56:43 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-25 01:56:43 (10960) [INFO] * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-25 01:57:18 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-25 01:57:18 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-25 01:57:18 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-25 01:57:18 (10960) [INFO] * 2026-03-25 01:57:18 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-25 01:57:19 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-25 01:57:50 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-25 01:57:50 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-25 01:57:50 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-25 01:57:50 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-25 01:57:50 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-25 01:57:50 (10973) [INFO] yum --disablerepo= ... * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-25 01:57:50 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-25 01:57:50 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] yum-config-manager --disable * 2026-03-25 01:57:50 (10973) [INFO] or * 2026-03-25 01:57:50 (10973) [INFO] subscription-manager repos --disable= * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-25 01:57:50 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-25 01:57:50 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-25 01:57:50 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-25 01:57:50 (10973) [INFO] compromise: * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-25 01:57:50 (10973) [INFO] * 2026-03-25 01:57:50 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-25 01:57:50 (10990) [INFO] * 2026-03-25 01:57:50 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-25 01:57:50 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-25 01:57:50 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-25 01:57:50 (10960) [INFO] * 2026-03-25 01:57:51 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-25 01:57:51 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-25 01:57:51 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-25 01:57:51 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-25 01:57:51 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-25 01:57:51 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-25 01:57:51 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-25 01:57:51 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-25 01:57:51 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-25 01:57:51 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-25 01:57:51 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-25 01:57:51 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-25 01:57:51 (10990) [INFO] * 2026-03-25 01:57:51 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-25 01:57:51 (10960) [INFO] * 2026-03-25 01:57:52 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-25 01:57:52 (10973) [INFO] Determining fastest mirrors * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-25 01:58:23 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-25 01:58:23 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-25 01:58:23 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-25 01:58:23 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-25 01:58:23 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-25 01:58:23 (10973) [INFO] yum --disablerepo= ... * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-25 01:58:23 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-25 01:58:23 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] yum-config-manager --disable * 2026-03-25 01:58:23 (10973) [INFO] or * 2026-03-25 01:58:23 (10973) [INFO] subscription-manager repos --disable= * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-25 01:58:23 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-25 01:58:23 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-25 01:58:23 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-25 01:58:23 (10973) [INFO] compromise: * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-25 01:58:23 (10973) [INFO] * 2026-03-25 01:58:23 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-25 01:58:23 (10990) [INFO] * 2026-03-25 01:58:23 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-25 01:58:23 (6792) [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 * 2026-03-25 01:58:24 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-25 01:58:24 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-25 01:58:24 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-25 01:58:24 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-25 01:58:24 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-25 01:58:30 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XBYkdAUCL4/ea_profile.json * 2026-03-25 02:01:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/XBYkdAUCL4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-25 02:01:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-26 01:39:08 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-26 01:44:09 (12063) [INFO] Script is up to date. * 2026-03-26 01:49:12 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-26 01:49:12 (10960) [INFO] * 2026-03-26 01:50:32 (10990) [INFO] * 2026-03-26 01:50:32 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-26 01:50:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-26 01:50:32 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-26 01:50:32 (10960) [INFO] * 2026-03-26 01:52:01 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-26 01:52:01 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-26 01:52:01 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-26 01:52:01 (10960) [INFO] * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-26 01:52:37 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-26 01:52:37 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-26 01:52:37 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-26 01:52:37 (10960) [INFO] * 2026-03-26 01:52:37 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-26 01:52:38 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-26 01:53:08 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-26 01:53:08 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-26 01:53:08 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-26 01:53:08 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-26 01:53:08 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-26 01:53:08 (10973) [INFO] yum --disablerepo= ... * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-26 01:53:08 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-26 01:53:08 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] yum-config-manager --disable * 2026-03-26 01:53:08 (10973) [INFO] or * 2026-03-26 01:53:08 (10973) [INFO] subscription-manager repos --disable= * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-26 01:53:08 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-26 01:53:08 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-26 01:53:08 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-26 01:53:08 (10973) [INFO] compromise: * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-26 01:53:08 (10973) [INFO] * 2026-03-26 01:53:08 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-26 01:53:08 (10990) [INFO] * 2026-03-26 01:53:08 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-26 01:53:08 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-26 01:53:08 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-26 01:53:08 (10960) [INFO] * 2026-03-26 01:53:09 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-26 01:53:09 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-26 01:53:09 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-26 01:53:09 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-26 01:53:09 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-26 01:53:09 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-26 01:53:09 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-26 01:53:09 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-26 01:53:09 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-26 01:53:09 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-26 01:53:09 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-26 01:53:09 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-26 01:53:09 (10990) [INFO] * 2026-03-26 01:53:09 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-26 01:53:09 (10960) [INFO] * 2026-03-26 01:53:10 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-26 01:53:10 (10973) [INFO] Determining fastest mirrors * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-26 01:53:42 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-26 01:53:42 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-26 01:53:42 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-26 01:53:42 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-26 01:53:42 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-26 01:53:42 (10973) [INFO] yum --disablerepo= ... * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-26 01:53:42 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-26 01:53:42 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] yum-config-manager --disable * 2026-03-26 01:53:42 (10973) [INFO] or * 2026-03-26 01:53:42 (10973) [INFO] subscription-manager repos --disable= * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-26 01:53:42 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-26 01:53:42 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-26 01:53:42 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-26 01:53:42 (10973) [INFO] compromise: * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-26 01:53:42 (10973) [INFO] * 2026-03-26 01:53:42 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-26 01:53:42 (10990) [INFO] * 2026-03-26 01:53:42 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-26 01:53:42 (6792) [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 * 2026-03-26 01:53:43 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-26 01:53:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-26 01:53:44 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-26 01:53:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-26 01:53:44 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-26 01:53:50 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5V1ba32DCE/ea_profile.json * 2026-03-26 01:56:25 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5V1ba32DCE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-26 01:56:25 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-27 01:38:37 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-27 01:42:37 (12063) [INFO] Script is up to date. * 2026-03-27 01:46:40 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-27 01:46:40 (10960) [INFO] * 2026-03-27 01:47:59 (10990) [INFO] * 2026-03-27 01:47:59 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-27 01:47:59 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-27 01:47:59 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-27 01:47:59 (10960) [INFO] * 2026-03-27 01:56:24 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-27 01:56:24 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-27 01:56:24 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-27 01:56:24 (10960) [INFO] * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-27 01:56:58 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-27 01:56:58 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-27 01:56:58 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-27 01:56:58 (10960) [INFO] * 2026-03-27 01:56:58 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-27 01:56:59 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-27 01:57:30 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-27 01:57:30 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-27 01:57:30 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-27 01:57:30 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-27 01:57:30 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-27 01:57:30 (10973) [INFO] yum --disablerepo= ... * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-27 01:57:30 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-27 01:57:30 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] yum-config-manager --disable * 2026-03-27 01:57:30 (10973) [INFO] or * 2026-03-27 01:57:30 (10973) [INFO] subscription-manager repos --disable= * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-27 01:57:30 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-27 01:57:30 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-27 01:57:30 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-27 01:57:30 (10973) [INFO] compromise: * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-27 01:57:30 (10973) [INFO] * 2026-03-27 01:57:30 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-27 01:57:30 (10990) [INFO] * 2026-03-27 01:57:30 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-27 01:57:30 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-27 01:57:30 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-27 01:57:30 (10960) [INFO] * 2026-03-27 01:57:31 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-27 01:57:31 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-27 01:57:31 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-27 01:57:31 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-27 01:57:31 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-27 01:57:31 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-27 01:57:31 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-27 01:57:31 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-27 01:57:31 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-27 01:57:31 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-27 01:57:31 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-27 01:57:31 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-27 01:57:31 (10990) [INFO] * 2026-03-27 01:57:31 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-27 01:57:31 (10960) [INFO] * 2026-03-27 01:57:32 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-27 01:57:32 (10973) [INFO] Determining fastest mirrors * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-27 01:58:03 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-27 01:58:03 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-27 01:58:03 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-27 01:58:03 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-27 01:58:03 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-27 01:58:03 (10973) [INFO] yum --disablerepo= ... * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-27 01:58:03 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-27 01:58:03 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] yum-config-manager --disable * 2026-03-27 01:58:03 (10973) [INFO] or * 2026-03-27 01:58:03 (10973) [INFO] subscription-manager repos --disable= * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-27 01:58:03 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-27 01:58:03 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-27 01:58:03 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-27 01:58:03 (10973) [INFO] compromise: * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-27 01:58:03 (10973) [INFO] * 2026-03-27 01:58:03 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-27 01:58:03 (10990) [INFO] * 2026-03-27 01:58:03 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-27 01:58:03 (6792) [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 * 2026-03-27 01:58:05 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-27 01:58:05 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-27 01:58:05 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-27 01:58:05 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-27 01:58:05 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-27 01:58:11 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5WGIwGg6Mv/ea_profile.json * 2026-03-27 02:00:39 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/5WGIwGg6Mv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-27 02:00:39 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-28 01:40:06 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-28 01:44:06 (12063) [INFO] Script is up to date. * 2026-03-28 01:48:09 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-28 01:48:09 (10960) [INFO] * 2026-03-28 01:49:01 (10990) [INFO] * 2026-03-28 01:49:01 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-28 01:49:02 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-28 01:49:02 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-28 01:49:02 (10960) [INFO] * 2026-03-28 01:56:03 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-28 01:56:03 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-28 01:56:03 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-28 01:56:03 (10960) [INFO] * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-28 01:56:40 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-28 01:56:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-28 01:56:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-28 01:56:40 (10960) [INFO] * 2026-03-28 01:56:41 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-28 01:56:41 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-28 01:57:12 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-28 01:57:12 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-28 01:57:12 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-28 01:57:12 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-28 01:57:12 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-28 01:57:12 (10973) [INFO] yum --disablerepo= ... * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-28 01:57:12 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-28 01:57:12 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] yum-config-manager --disable * 2026-03-28 01:57:12 (10973) [INFO] or * 2026-03-28 01:57:12 (10973) [INFO] subscription-manager repos --disable= * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-28 01:57:12 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-28 01:57:12 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-28 01:57:12 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-28 01:57:12 (10973) [INFO] compromise: * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-28 01:57:12 (10973) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-28 01:57:12 (10990) [INFO] * 2026-03-28 01:57:12 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-28 01:57:12 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-28 01:57:12 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-28 01:57:12 (10960) [INFO] * 2026-03-28 01:57:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-28 01:57:13 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-28 01:57:13 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-28 01:57:13 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-28 01:57:13 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-28 01:57:13 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-28 01:57:13 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-28 01:57:13 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-28 01:57:13 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-28 01:57:13 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-28 01:57:13 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-28 01:57:13 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-28 01:57:13 (10990) [INFO] * 2026-03-28 01:57:13 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-28 01:57:13 (10960) [INFO] * 2026-03-28 01:57:13 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-28 01:57:14 (10973) [INFO] Determining fastest mirrors * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-28 01:57:45 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-28 01:57:45 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-28 01:57:45 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-28 01:57:45 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-28 01:57:45 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-28 01:57:45 (10973) [INFO] yum --disablerepo= ... * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-28 01:57:45 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-28 01:57:45 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] yum-config-manager --disable * 2026-03-28 01:57:45 (10973) [INFO] or * 2026-03-28 01:57:45 (10973) [INFO] subscription-manager repos --disable= * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-28 01:57:45 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-28 01:57:45 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-28 01:57:45 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-28 01:57:45 (10973) [INFO] compromise: * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-28 01:57:45 (10973) [INFO] * 2026-03-28 01:57:45 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-28 01:57:45 (10990) [INFO] * 2026-03-28 01:57:45 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-28 01:57:45 (6792) [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 * 2026-03-28 01:57:47 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-28 01:57:47 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-28 01:57:47 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-28 01:57:47 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-28 01:57:47 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-28 01:57:54 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HfkNp30APf/ea_profile.json * 2026-03-28 02:01:24 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/HfkNp30APf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-28 02:01:24 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-29 01:40:05 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-29 01:44:05 (12063) [INFO] Script is up to date. * 2026-03-29 01:48:08 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-29 01:48:08 (10960) [INFO] * 2026-03-29 01:49:03 (10990) [INFO] * 2026-03-29 01:49:03 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-29 01:49:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-29 01:49:03 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-29 01:49:03 (10960) [INFO] * 2026-03-29 01:59:57 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-29 01:59:57 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-29 01:59:57 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-29 01:59:57 (10960) [INFO] * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-29 02:00:34 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-29 02:00:34 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-29 02:00:34 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-29 02:00:34 (10960) [INFO] * 2026-03-29 02:00:34 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-29 02:00:34 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-29 02:01:05 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-29 02:01:05 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-29 02:01:05 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-29 02:01:05 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-29 02:01:05 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-29 02:01:05 (10973) [INFO] yum --disablerepo= ... * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-29 02:01:05 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-29 02:01:05 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] yum-config-manager --disable * 2026-03-29 02:01:05 (10973) [INFO] or * 2026-03-29 02:01:05 (10973) [INFO] subscription-manager repos --disable= * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-29 02:01:05 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-29 02:01:05 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-29 02:01:05 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-29 02:01:05 (10973) [INFO] compromise: * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-29 02:01:05 (10973) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-29 02:01:05 (10990) [INFO] * 2026-03-29 02:01:05 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-29 02:01:05 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-29 02:01:05 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-29 02:01:05 (10960) [INFO] * 2026-03-29 02:01:05 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-29 02:01:06 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-29 02:01:06 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-29 02:01:06 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-29 02:01:06 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-29 02:01:06 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-29 02:01:06 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-29 02:01:06 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-29 02:01:06 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-29 02:01:06 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-29 02:01:06 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-29 02:01:06 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-03-29 02:01:06 (10990) [INFO] * 2026-03-29 02:01:06 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-29 02:01:06 (10960) [INFO] * 2026-03-29 02:01:06 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-29 02:01:07 (10973) [INFO] Determining fastest mirrors * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-29 02:01:38 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-29 02:01:38 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-29 02:01:38 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-29 02:01:38 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-29 02:01:38 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-29 02:01:38 (10973) [INFO] yum --disablerepo= ... * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-29 02:01:38 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-29 02:01:38 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] yum-config-manager --disable * 2026-03-29 02:01:38 (10973) [INFO] or * 2026-03-29 02:01:38 (10973) [INFO] subscription-manager repos --disable= * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-29 02:01:38 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-29 02:01:38 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-29 02:01:38 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-29 02:01:38 (10973) [INFO] compromise: * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-29 02:01:38 (10973) [INFO] * 2026-03-29 02:01:38 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-29 02:01:38 (10990) [INFO] * 2026-03-29 02:01:38 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-29 02:01:38 (6792) [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 * 2026-03-29 02:01:40 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-29 02:01:40 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-29 02:01:40 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-29 02:01:40 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-29 02:01:40 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-29 02:01:46 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VwdsYMxCYK/ea_profile.json * 2026-03-29 02:04:43 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/VwdsYMxCYK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-29 02:04:43 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-30 01:39:13 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-30 01:43:13 (12063) [INFO] Script is up to date. * 2026-03-30 01:47:17 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-30 01:47:17 (10960) [INFO] * 2026-03-30 01:48:39 (10990) [INFO] * 2026-03-30 01:48:39 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-30 01:48:39 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-30 01:48:39 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-30 01:48:39 (10960) [INFO] * 2026-03-30 01:56:23 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-30 01:56:23 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-30 01:56:23 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-30 01:56:23 (10960) [INFO] * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-30 01:56:59 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-30 01:56:59 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-30 01:56:59 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-30 01:56:59 (10960) [INFO] * 2026-03-30 01:56:59 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-30 01:57:00 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-30 01:57:31 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-30 01:57:31 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-30 01:57:31 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-30 01:57:31 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-30 01:57:31 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-30 01:57:31 (10973) [INFO] yum --disablerepo= ... * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-30 01:57:31 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-30 01:57:31 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] yum-config-manager --disable * 2026-03-30 01:57:31 (10973) [INFO] or * 2026-03-30 01:57:31 (10973) [INFO] subscription-manager repos --disable= * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-30 01:57:31 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-30 01:57:31 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-30 01:57:31 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-30 01:57:31 (10973) [INFO] compromise: * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-30 01:57:31 (10973) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-30 01:57:31 (10990) [INFO] * 2026-03-30 01:57:31 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-30 01:57:31 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-30 01:57:31 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-30 01:57:31 (10960) [INFO] * 2026-03-30 01:57:31 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-30 01:57:31 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-30 01:57:31 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-30 01:57:31 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-30 01:57:31 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-30 01:57:31 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-30 01:57:31 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-30 01:57:31 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-30 01:57:31 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-30 01:57:31 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-30 01:57:32 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-30 01:57:32 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-30 01:57:32 (10990) [INFO] * 2026-03-30 01:57:32 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-30 01:57:32 (10960) [INFO] * 2026-03-30 01:57:32 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-30 01:57:32 (10973) [INFO] Determining fastest mirrors * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-30 01:58:03 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-30 01:58:03 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-30 01:58:03 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-30 01:58:03 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-30 01:58:03 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-30 01:58:03 (10973) [INFO] yum --disablerepo= ... * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-30 01:58:03 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-30 01:58:03 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] yum-config-manager --disable * 2026-03-30 01:58:03 (10973) [INFO] or * 2026-03-30 01:58:03 (10973) [INFO] subscription-manager repos --disable= * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-30 01:58:03 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-30 01:58:03 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-30 01:58:03 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-30 01:58:03 (10973) [INFO] compromise: * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-30 01:58:03 (10973) [INFO] * 2026-03-30 01:58:03 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-30 01:58:03 (10990) [INFO] * 2026-03-30 01:58:03 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-30 01:58:03 (6792) [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 * 2026-03-30 01:58:05 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-30 01:58:05 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-30 01:58:05 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-30 01:58:05 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-30 01:58:05 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-30 01:58:12 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GsTY_8m02A/ea_profile.json * 2026-03-30 02:00:39 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/GsTY_8m02A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-30 02:00:39 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-03-31 01:39:09 (12041) [INFO] Self-update of script version 80 requested. * 2026-03-31 01:43:09 (12063) [INFO] Script is up to date. * 2026-03-31 01:47:12 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-03-31 01:47:12 (10960) [INFO] * 2026-03-31 01:48:29 (10990) [INFO] * 2026-03-31 01:48:29 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-03-31 01:48:30 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-03-31 01:48:30 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-03-31 01:48:30 (10960) [INFO] * 2026-03-31 01:55:30 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-03-31 01:55:30 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-03-31 01:55:30 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-03-31 01:55:30 (10960) [INFO] * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-03-31 01:56:06 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-03-31 01:56:06 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-03-31 01:56:06 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-31 01:56:06 (10960) [INFO] * 2026-03-31 01:56:07 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-31 01:56:07 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-31 01:56:37 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-31 01:56:37 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-31 01:56:37 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-31 01:56:37 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-31 01:56:37 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-31 01:56:37 (10973) [INFO] yum --disablerepo= ... * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-31 01:56:37 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-31 01:56:37 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] yum-config-manager --disable * 2026-03-31 01:56:37 (10973) [INFO] or * 2026-03-31 01:56:37 (10973) [INFO] subscription-manager repos --disable= * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-31 01:56:37 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-31 01:56:37 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-31 01:56:37 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-31 01:56:37 (10973) [INFO] compromise: * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-31 01:56:37 (10973) [INFO] * 2026-03-31 01:56:37 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-31 01:56:37 (10990) [INFO] * 2026-03-31 01:56:37 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-31 01:56:37 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-03-31 01:56:37 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-03-31 01:56:37 (10960) [INFO] * 2026-03-31 01:56:38 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-31 01:56:38 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-03-31 01:56:38 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-03-31 01:56:38 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-03-31 01:56:38 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-03-31 01:56:38 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-03-31 01:56:38 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-03-31 01:56:38 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-03-31 01:56:38 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-03-31 01:56:38 (10973) [INFO] : wp-toolkit-thirdparties * 2026-03-31 01:56:38 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-03-31 01:56:38 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-03-31 01:56:38 (10990) [INFO] * 2026-03-31 01:56:38 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-03-31 01:56:38 (10960) [INFO] * 2026-03-31 01:56:39 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-03-31 01:56:39 (10973) [INFO] Determining fastest mirrors * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-03-31 01:57:10 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-03-31 01:57:10 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-03-31 01:57:10 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-03-31 01:57:10 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-03-31 01:57:10 (10973) [INFO] packages for the previous distribution release still work). * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-03-31 01:57:10 (10973) [INFO] yum --disablerepo= ... * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-03-31 01:57:10 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-03-31 01:57:10 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] yum-config-manager --disable * 2026-03-31 01:57:10 (10973) [INFO] or * 2026-03-31 01:57:10 (10973) [INFO] subscription-manager repos --disable= * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-03-31 01:57:10 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-03-31 01:57:10 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-03-31 01:57:10 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-03-31 01:57:10 (10973) [INFO] compromise: * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-03-31 01:57:10 (10973) [INFO] * 2026-03-31 01:57:10 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-03-31 01:57:10 (10990) [INFO] * 2026-03-31 01:57:10 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-03-31 01:57:10 (6792) [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 * 2026-03-31 01:57:12 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-03-31 01:57:12 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-03-31 01:57:12 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-03-31 01:57:12 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-03-31 01:57:12 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-03-31 01:57:18 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gZHOgWKCoU/ea_profile.json * 2026-03-31 01:59:45 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/gZHOgWKCoU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-03-31 01:59:45 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-01 01:45:44 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-01 01:49:45 (12063) [INFO] Script is up to date. * 2026-04-01 01:53:48 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-01 01:53:48 (10960) [INFO] * 2026-04-01 01:55:12 (10990) [INFO] * 2026-04-01 01:55:12 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-01 01:55:12 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-01 01:55:12 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-01 01:55:12 (10960) [INFO] * 2026-04-01 01:55:16 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-01 01:55:16 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-01 01:55:16 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-01 01:55:16 (10960) [INFO] * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-01 01:55:52 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-01 01:55:52 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-01 01:55:52 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-01 01:55:52 (10960) [INFO] * 2026-04-01 01:55:52 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-01 01:55:53 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-01 01:56:24 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-01 01:56:24 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-01 01:56:24 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-01 01:56:24 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-01 01:56:24 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-01 01:56:24 (10973) [INFO] yum --disablerepo= ... * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-01 01:56:24 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-01 01:56:24 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] yum-config-manager --disable * 2026-04-01 01:56:24 (10973) [INFO] or * 2026-04-01 01:56:24 (10973) [INFO] subscription-manager repos --disable= * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-01 01:56:24 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-01 01:56:24 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-01 01:56:24 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-01 01:56:24 (10973) [INFO] compromise: * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-01 01:56:24 (10973) [INFO] * 2026-04-01 01:56:24 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-01 01:56:24 (10990) [INFO] * 2026-04-01 01:56:24 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-01 01:56:24 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-01 01:56:24 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-01 01:56:24 (10960) [INFO] * 2026-04-01 01:56:25 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-01 01:56:25 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-01 01:56:25 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-01 01:56:25 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-01 01:56:25 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-01 01:56:25 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-01 01:56:25 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-01 01:56:25 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-01 01:56:25 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-01 01:56:25 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-01 01:56:25 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-01 01:56:25 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-01 01:56:25 (10990) [INFO] * 2026-04-01 01:56:25 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-01 01:56:25 (10960) [INFO] * 2026-04-01 01:56:26 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-01 01:56:26 (10973) [INFO] Determining fastest mirrors * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-01 01:56:57 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-01 01:56:57 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-01 01:56:57 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-01 01:56:57 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-01 01:56:57 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-01 01:56:57 (10973) [INFO] yum --disablerepo= ... * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-01 01:56:57 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-01 01:56:57 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] yum-config-manager --disable * 2026-04-01 01:56:57 (10973) [INFO] or * 2026-04-01 01:56:57 (10973) [INFO] subscription-manager repos --disable= * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-01 01:56:57 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-01 01:56:57 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-01 01:56:57 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-01 01:56:57 (10973) [INFO] compromise: * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-01 01:56:57 (10973) [INFO] * 2026-04-01 01:56:57 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-01 01:56:57 (10990) [INFO] * 2026-04-01 01:56:57 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-01 01:56:57 (6792) [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 * 2026-04-01 01:56:59 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-01 01:56:59 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-01 01:56:59 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-01 01:56:59 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-01 01:56:59 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-01 01:57:06 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tD5j9bH7x3/ea_profile.json * 2026-04-01 01:59:33 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/tD5j9bH7x3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-01 01:59:33 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-02 01:38:37 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-02 01:42:37 (12063) [INFO] Script is up to date. * 2026-04-02 01:46:41 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-02 01:46:41 (10960) [INFO] * 2026-04-02 01:47:57 (10990) [INFO] * 2026-04-02 01:47:57 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-02 01:47:57 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-02 01:47:57 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-02 01:47:57 (10960) [INFO] * 2026-04-02 01:48:01 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-02 01:48:01 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-02 01:48:01 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-02 01:48:01 (10960) [INFO] * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-02 01:48:36 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-02 01:48:36 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-02 01:48:36 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-02 01:48:36 (10960) [INFO] * 2026-04-02 01:48:36 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-02 01:48:36 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-02 01:49:08 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-02 01:49:08 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-02 01:49:08 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-02 01:49:08 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-02 01:49:08 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-02 01:49:08 (10973) [INFO] yum --disablerepo= ... * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-02 01:49:08 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-02 01:49:08 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] yum-config-manager --disable * 2026-04-02 01:49:08 (10973) [INFO] or * 2026-04-02 01:49:08 (10973) [INFO] subscription-manager repos --disable= * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-02 01:49:08 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-02 01:49:08 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-02 01:49:08 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-02 01:49:08 (10973) [INFO] compromise: * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-02 01:49:08 (10973) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-02 01:49:08 (10990) [INFO] * 2026-04-02 01:49:08 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-02 01:49:08 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-02 01:49:08 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-02 01:49:08 (10960) [INFO] * 2026-04-02 01:49:08 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-02 01:49:09 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-02 01:49:09 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-02 01:49:09 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-02 01:49:09 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-02 01:49:09 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-02 01:49:09 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-02 01:49:09 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-02 01:49:09 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-02 01:49:09 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-02 01:49:09 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-02 01:49:09 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-02 01:49:09 (10990) [INFO] * 2026-04-02 01:49:09 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-02 01:49:09 (10960) [INFO] * 2026-04-02 01:49:09 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-02 01:49:10 (10973) [INFO] Determining fastest mirrors * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-02 01:49:41 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-02 01:49:41 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-02 01:49:41 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-02 01:49:41 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-02 01:49:41 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-02 01:49:41 (10973) [INFO] yum --disablerepo= ... * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-02 01:49:41 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-02 01:49:41 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] yum-config-manager --disable * 2026-04-02 01:49:41 (10973) [INFO] or * 2026-04-02 01:49:41 (10973) [INFO] subscription-manager repos --disable= * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-02 01:49:41 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-02 01:49:41 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-02 01:49:41 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-02 01:49:41 (10973) [INFO] compromise: * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-02 01:49:41 (10973) [INFO] * 2026-04-02 01:49:41 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-02 01:49:41 (10990) [INFO] * 2026-04-02 01:49:41 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-02 01:49:41 (6792) [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 * 2026-04-02 01:49:43 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-02 01:49:43 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-02 01:49:43 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-02 01:49:43 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-02 01:49:43 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-02 01:49:50 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nNq6Q7zaCb/ea_profile.json * 2026-04-02 01:52:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/nNq6Q7zaCb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-02 01:52:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-03 01:39:11 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-03 01:43:12 (12063) [INFO] Script is up to date. * 2026-04-03 01:47:15 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-03 01:47:15 (10960) [INFO] * 2026-04-03 01:48:36 (10990) [INFO] * 2026-04-03 01:48:36 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-03 01:48:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-03 01:48:37 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-03 01:48:37 (10960) [INFO] * 2026-04-03 01:55:41 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-03 01:55:41 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-03 01:55:41 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-03 01:55:41 (10960) [INFO] * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-03 01:56:16 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-03 01:56:16 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-03 01:56:16 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-03 01:56:16 (10960) [INFO] * 2026-04-03 01:56:16 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-03 01:56:17 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-03 01:56:48 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-03 01:56:48 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-03 01:56:48 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-03 01:56:48 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-03 01:56:48 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-03 01:56:48 (10973) [INFO] yum --disablerepo= ... * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-03 01:56:48 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-03 01:56:48 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] yum-config-manager --disable * 2026-04-03 01:56:48 (10973) [INFO] or * 2026-04-03 01:56:48 (10973) [INFO] subscription-manager repos --disable= * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-03 01:56:48 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-03 01:56:48 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-03 01:56:48 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-03 01:56:48 (10973) [INFO] compromise: * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-03 01:56:48 (10973) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-03 01:56:48 (10990) [INFO] * 2026-04-03 01:56:48 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-03 01:56:48 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-03 01:56:48 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-03 01:56:48 (10960) [INFO] * 2026-04-03 01:56:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-03 01:56:49 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-03 01:56:49 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-03 01:56:49 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-03 01:56:49 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-03 01:56:49 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-03 01:56:49 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-03 01:56:49 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-03 01:56:49 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-03 01:56:49 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-03 01:56:49 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-03 01:56:49 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-03 01:56:49 (10990) [INFO] * 2026-04-03 01:56:49 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-03 01:56:49 (10960) [INFO] * 2026-04-03 01:56:49 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-03 01:56:49 (10973) [INFO] Determining fastest mirrors * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-03 01:57:20 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-03 01:57:20 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-03 01:57:20 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-03 01:57:20 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-03 01:57:20 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-03 01:57:20 (10973) [INFO] yum --disablerepo= ... * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-03 01:57:20 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-03 01:57:20 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] yum-config-manager --disable * 2026-04-03 01:57:20 (10973) [INFO] or * 2026-04-03 01:57:20 (10973) [INFO] subscription-manager repos --disable= * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-03 01:57:20 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-03 01:57:20 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-03 01:57:20 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-03 01:57:20 (10973) [INFO] compromise: * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-03 01:57:20 (10973) [INFO] * 2026-04-03 01:57:20 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-03 01:57:20 (10990) [INFO] * 2026-04-03 01:57:20 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-03 01:57:20 (6792) [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 * 2026-04-03 01:57:22 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-03 01:57:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-03 01:57:22 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-03 01:57:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-03 01:57:22 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-03 01:57:29 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ygiwOZGZzR/ea_profile.json * 2026-04-03 01:59:56 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/ygiwOZGZzR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-03 01:59:56 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-04 01:39:53 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-04 01:43:53 (12063) [INFO] Script is up to date. * 2026-04-04 01:47:56 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-04 01:47:56 (10960) [INFO] * 2026-04-04 01:48:50 (10990) [INFO] * 2026-04-04 01:48:50 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-04 01:48:50 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-04 01:48:50 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-04 01:48:50 (10960) [INFO] * 2026-04-04 01:55:50 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-04 01:55:50 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-04 01:55:50 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-04 01:55:50 (10960) [INFO] * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-04 01:56:25 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-04 01:56:25 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-04 01:56:25 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-04 01:56:25 (10960) [INFO] * 2026-04-04 01:56:25 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-04 01:56:26 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-04 01:56:57 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-04 01:56:57 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-04 01:56:57 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-04 01:56:57 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-04 01:56:57 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-04 01:56:57 (10973) [INFO] yum --disablerepo= ... * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-04 01:56:57 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-04 01:56:57 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] yum-config-manager --disable * 2026-04-04 01:56:57 (10973) [INFO] or * 2026-04-04 01:56:57 (10973) [INFO] subscription-manager repos --disable= * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-04 01:56:57 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-04 01:56:57 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-04 01:56:57 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-04 01:56:57 (10973) [INFO] compromise: * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-04 01:56:57 (10973) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-04 01:56:57 (10990) [INFO] * 2026-04-04 01:56:57 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-04 01:56:57 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-04 01:56:57 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-04 01:56:57 (10960) [INFO] * 2026-04-04 01:56:57 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-04 01:56:57 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-04 01:56:57 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-04 01:56:57 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-04 01:56:57 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-04 01:56:57 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-04 01:56:57 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-04 01:56:57 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-04 01:56:57 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-04 01:56:57 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-04 01:56:57 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-04 01:56:57 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-04 01:56:57 (10990) [INFO] * 2026-04-04 01:56:57 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-04 01:56:57 (10960) [INFO] * 2026-04-04 01:56:58 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-04 01:56:58 (10973) [INFO] Determining fastest mirrors * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-04 01:57:29 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-04 01:57:29 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-04 01:57:29 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-04 01:57:29 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-04 01:57:29 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-04 01:57:29 (10973) [INFO] yum --disablerepo= ... * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-04 01:57:29 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-04 01:57:29 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] yum-config-manager --disable * 2026-04-04 01:57:29 (10973) [INFO] or * 2026-04-04 01:57:29 (10973) [INFO] subscription-manager repos --disable= * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-04 01:57:29 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-04 01:57:29 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-04 01:57:29 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-04 01:57:29 (10973) [INFO] compromise: * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-04 01:57:29 (10973) [INFO] * 2026-04-04 01:57:29 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-04 01:57:29 (10990) [INFO] * 2026-04-04 01:57:29 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-04 01:57:29 (6792) [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 * 2026-04-04 01:57:31 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-04 01:57:31 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-04 01:57:31 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-04 01:57:31 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-04 01:57:31 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-04 01:57:38 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3cK5jbsWf4/ea_profile.json * 2026-04-04 02:00:04 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/3cK5jbsWf4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-04 02:00:04 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-05 01:39:55 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-05 01:43:56 (12063) [INFO] Script is up to date. * 2026-04-05 01:47:59 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-05 01:47:59 (10960) [INFO] * 2026-04-05 01:48:49 (10990) [INFO] * 2026-04-05 01:48:49 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-05 01:48:49 (264) [ERROR] *** Elevation Blocker detected: *** cPanel does not detect a valid license for itself on the system at this time. This could cause problems during the update. cPanel expects to find a license for the IP address 166.70.142.140. Verify whether that IP address is licensed using the following site: https://verify.cpanel.net/ * 2026-04-05 01:48:49 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-05 01:48:49 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-05 01:48:49 (10960) [INFO] * 2026-04-05 01:48:53 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-05 01:48:53 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-05 01:48:53 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-05 01:48:53 (10960) [INFO] * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-05 01:49:29 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-05 01:49:29 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-05 01:49:29 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-05 01:49:29 (10960) [INFO] * 2026-04-05 01:49:29 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-05 01:49:29 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-05 01:50:00 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-05 01:50:00 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-05 01:50:00 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-05 01:50:00 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-05 01:50:00 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-05 01:50:00 (10973) [INFO] yum --disablerepo= ... * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-05 01:50:00 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-05 01:50:00 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] yum-config-manager --disable * 2026-04-05 01:50:00 (10973) [INFO] or * 2026-04-05 01:50:00 (10973) [INFO] subscription-manager repos --disable= * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-05 01:50:00 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-05 01:50:00 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-05 01:50:00 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-05 01:50:00 (10973) [INFO] compromise: * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-05 01:50:00 (10973) [INFO] * 2026-04-05 01:50:00 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-05 01:50:00 (10990) [INFO] * 2026-04-05 01:50:00 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-05 01:50:00 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-05 01:50:00 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-05 01:50:00 (10960) [INFO] * 2026-04-05 01:50:01 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-05 01:50:01 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-05 01:50:01 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-05 01:50:01 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-05 01:50:01 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-05 01:50:01 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-05 01:50:01 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-05 01:50:01 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-05 01:50:01 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-05 01:50:01 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-05 01:50:01 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-05 01:50:01 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-05 01:50:01 (10990) [INFO] * 2026-04-05 01:50:01 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-05 01:50:01 (10960) [INFO] * 2026-04-05 01:50:02 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-05 01:50:03 (10973) [INFO] Determining fastest mirrors * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-05 01:50:33 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-05 01:50:33 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-05 01:50:33 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-05 01:50:33 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-05 01:50:33 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-05 01:50:33 (10973) [INFO] yum --disablerepo= ... * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-05 01:50:33 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-05 01:50:33 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] yum-config-manager --disable * 2026-04-05 01:50:33 (10973) [INFO] or * 2026-04-05 01:50:33 (10973) [INFO] subscription-manager repos --disable= * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-05 01:50:33 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-05 01:50:33 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-05 01:50:33 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-05 01:50:33 (10973) [INFO] compromise: * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-05 01:50:33 (10973) [INFO] * 2026-04-05 01:50:33 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-05 01:50:33 (10990) [INFO] * 2026-04-05 01:50:33 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-05 01:50:33 (6792) [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 * 2026-04-05 01:50:35 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-05 01:50:35 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-05 01:50:35 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-05 01:50:35 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-05 01:50:35 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-05 01:50:42 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mwp3keecHr/ea_profile.json * 2026-04-05 01:53:09 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/mwp3keecHr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-05 01:53:09 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-06 01:38:42 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-06 01:42:42 (12063) [INFO] Script is up to date. * 2026-04-06 01:46:45 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-06 01:46:45 (10960) [INFO] * 2026-04-06 01:48:03 (10990) [INFO] * 2026-04-06 01:48:03 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-06 01:48:03 (264) [ERROR] *** Elevation Blocker detected: *** cPanel does not detect a valid license for itself on the system at this time. This could cause problems during the update. cPanel expects to find a license for the IP address 166.70.142.140. Verify whether that IP address is licensed using the following site: https://verify.cpanel.net/ * 2026-04-06 01:48:03 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-06 01:48:03 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-06 01:48:03 (10960) [INFO] * 2026-04-06 01:58:14 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-06 01:58:14 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-06 01:58:14 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-06 01:58:14 (10960) [INFO] * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-06 01:58:48 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-06 01:58:48 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-06 01:58:48 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-06 01:58:48 (10960) [INFO] * 2026-04-06 01:58:49 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-06 01:58:49 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-06 01:59:20 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-06 01:59:20 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-06 01:59:20 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-06 01:59:20 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-06 01:59:20 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-06 01:59:20 (10973) [INFO] yum --disablerepo= ... * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-06 01:59:20 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-06 01:59:20 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] yum-config-manager --disable * 2026-04-06 01:59:20 (10973) [INFO] or * 2026-04-06 01:59:20 (10973) [INFO] subscription-manager repos --disable= * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-06 01:59:20 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-06 01:59:20 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-06 01:59:20 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-06 01:59:20 (10973) [INFO] compromise: * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-06 01:59:20 (10973) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-06 01:59:20 (10990) [INFO] * 2026-04-06 01:59:20 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-06 01:59:20 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-06 01:59:20 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-06 01:59:20 (10960) [INFO] * 2026-04-06 01:59:20 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-06 01:59:21 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-06 01:59:21 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-06 01:59:21 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-06 01:59:21 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-06 01:59:21 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-06 01:59:21 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-06 01:59:21 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-06 01:59:21 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-06 01:59:21 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-06 01:59:21 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-06 01:59:21 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-06 01:59:21 (10990) [INFO] * 2026-04-06 01:59:21 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-06 01:59:21 (10960) [INFO] * 2026-04-06 01:59:21 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-06 01:59:21 (10973) [INFO] Determining fastest mirrors * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-06 01:59:53 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-06 01:59:53 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-06 01:59:53 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-06 01:59:53 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-06 01:59:53 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-06 01:59:53 (10973) [INFO] yum --disablerepo= ... * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-06 01:59:53 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-06 01:59:53 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] yum-config-manager --disable * 2026-04-06 01:59:53 (10973) [INFO] or * 2026-04-06 01:59:53 (10973) [INFO] subscription-manager repos --disable= * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-06 01:59:53 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-06 01:59:53 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-06 01:59:53 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-06 01:59:53 (10973) [INFO] compromise: * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-06 01:59:53 (10973) [INFO] * 2026-04-06 01:59:53 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-06 01:59:53 (10990) [INFO] * 2026-04-06 01:59:53 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-06 01:59:53 (6792) [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 * 2026-04-06 01:59:54 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-06 01:59:54 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-06 01:59:54 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-06 01:59:54 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-06 01:59:54 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-06 02:00:03 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/82Steg7DCh/ea_profile.json * 2026-04-06 02:02:31 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/82Steg7DCh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-06 02:02:31 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-07 01:44:40 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-07 01:48:40 (12063) [INFO] Script is up to date. * 2026-04-07 01:52:43 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-07 01:52:43 (10960) [INFO] * 2026-04-07 01:54:04 (10990) [INFO] * 2026-04-07 01:54:04 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-07 01:54:04 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-07 01:54:04 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-07 01:54:04 (10960) [INFO] * 2026-04-07 02:01:05 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-07 02:01:05 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-07 02:01:05 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-07 02:01:05 (10960) [INFO] * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-07 02:01:42 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-07 02:01:42 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-07 02:01:42 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-07 02:01:42 (10960) [INFO] * 2026-04-07 02:01:42 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-07 02:01:42 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-07 02:02:13 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-07 02:02:13 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-07 02:02:13 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-07 02:02:13 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-07 02:02:13 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-07 02:02:13 (10973) [INFO] yum --disablerepo= ... * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-07 02:02:13 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-07 02:02:13 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] yum-config-manager --disable * 2026-04-07 02:02:13 (10973) [INFO] or * 2026-04-07 02:02:13 (10973) [INFO] subscription-manager repos --disable= * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-07 02:02:13 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-07 02:02:13 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-07 02:02:13 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-07 02:02:13 (10973) [INFO] compromise: * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-07 02:02:13 (10973) [INFO] * 2026-04-07 02:02:13 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-07 02:02:13 (10990) [INFO] * 2026-04-07 02:02:13 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-07 02:02:13 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-07 02:02:13 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-07 02:02:13 (10960) [INFO] * 2026-04-07 02:02:14 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-07 02:02:14 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-07 02:02:14 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-07 02:02:14 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-07 02:02:14 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-07 02:02:14 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-07 02:02:14 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-07 02:02:14 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-07 02:02:14 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-07 02:02:14 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-07 02:02:14 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-07 02:02:14 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-07 02:02:14 (10990) [INFO] * 2026-04-07 02:02:14 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-07 02:02:14 (10960) [INFO] * 2026-04-07 02:02:15 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-07 02:02:15 (10973) [INFO] Determining fastest mirrors * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-07 02:02:47 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-07 02:02:47 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-07 02:02:47 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-07 02:02:47 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-07 02:02:47 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-07 02:02:47 (10973) [INFO] yum --disablerepo= ... * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-07 02:02:47 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-07 02:02:47 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] yum-config-manager --disable * 2026-04-07 02:02:47 (10973) [INFO] or * 2026-04-07 02:02:47 (10973) [INFO] subscription-manager repos --disable= * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-07 02:02:47 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-07 02:02:47 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-07 02:02:47 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-07 02:02:47 (10973) [INFO] compromise: * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-07 02:02:47 (10973) [INFO] * 2026-04-07 02:02:47 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-07 02:02:47 (10990) [INFO] * 2026-04-07 02:02:47 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-07 02:02:47 (6792) [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 * 2026-04-07 02:02:48 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-07 02:02:48 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-07 02:02:48 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-07 02:02:48 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-07 02:02:48 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-07 02:02:55 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Jj45a0_VPU/ea_profile.json * 2026-04-07 02:05:22 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/Jj45a0_VPU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-07 02:05:22 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-08 01:38:38 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-08 01:42:39 (12063) [INFO] Script is up to date. * 2026-04-08 01:46:42 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-08 01:46:42 (10960) [INFO] * 2026-04-08 01:48:00 (10990) [INFO] * 2026-04-08 01:48:00 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-08 01:48:01 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-08 01:48:01 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-08 01:48:01 (10960) [INFO] * 2026-04-08 01:48:05 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-08 01:48:05 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-08 01:48:05 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-08 01:48:05 (10960) [INFO] * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-08 01:48:40 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-08 01:48:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-08 01:48:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-08 01:48:40 (10960) [INFO] * 2026-04-08 01:48:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-08 01:48:41 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-08 01:49:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-08 01:49:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-08 01:49:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-08 01:49:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-08 01:49:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-08 01:49:11 (10973) [INFO] yum --disablerepo= ... * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-08 01:49:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-08 01:49:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] yum-config-manager --disable * 2026-04-08 01:49:11 (10973) [INFO] or * 2026-04-08 01:49:11 (10973) [INFO] subscription-manager repos --disable= * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-08 01:49:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-08 01:49:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-08 01:49:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-08 01:49:11 (10973) [INFO] compromise: * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-08 01:49:11 (10973) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-08 01:49:11 (10990) [INFO] * 2026-04-08 01:49:11 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-08 01:49:11 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-08 01:49:11 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-08 01:49:11 (10960) [INFO] * 2026-04-08 01:49:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-08 01:49:12 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-08 01:49:12 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-08 01:49:12 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-08 01:49:12 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-08 01:49:12 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-08 01:49:12 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-08 01:49:12 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-08 01:49:12 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-08 01:49:12 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-08 01:49:12 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-08 01:49:12 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-08 01:49:12 (10990) [INFO] * 2026-04-08 01:49:12 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-08 01:49:12 (10960) [INFO] * 2026-04-08 01:49:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-08 01:49:12 (10973) [INFO] Determining fastest mirrors * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-08 01:49:44 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-08 01:49:44 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-08 01:49:44 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-08 01:49:44 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-08 01:49:44 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-08 01:49:44 (10973) [INFO] yum --disablerepo= ... * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-08 01:49:44 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-08 01:49:44 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] yum-config-manager --disable * 2026-04-08 01:49:44 (10973) [INFO] or * 2026-04-08 01:49:44 (10973) [INFO] subscription-manager repos --disable= * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-08 01:49:44 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-08 01:49:44 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-08 01:49:44 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-08 01:49:44 (10973) [INFO] compromise: * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-08 01:49:44 (10973) [INFO] * 2026-04-08 01:49:44 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-08 01:49:44 (10990) [INFO] * 2026-04-08 01:49:44 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-08 01:49:44 (6792) [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 * 2026-04-08 01:49:45 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-08 01:49:45 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-08 01:49:45 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-08 01:49:45 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-08 01:49:45 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-08 01:49:53 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qc2be8wen2/ea_profile.json * 2026-04-08 01:53:53 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/qc2be8wen2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-08 01:53:53 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-09 01:40:10 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-09 01:44:11 (12063) [INFO] Script is up to date. * 2026-04-09 01:48:13 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-09 01:48:13 (10960) [INFO] * 2026-04-09 01:49:34 (10990) [INFO] * 2026-04-09 01:49:34 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-09 01:49:34 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-09 01:49:34 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-09 01:49:34 (10960) [INFO] * 2026-04-09 01:49:38 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-09 01:49:38 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-09 01:49:38 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-09 01:49:38 (10960) [INFO] * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-09 01:50:14 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-09 01:50:14 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-09 01:50:14 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-09 01:50:14 (10960) [INFO] * 2026-04-09 01:50:15 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-09 01:50:15 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-09 01:50:46 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-09 01:50:46 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-09 01:50:46 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-09 01:50:46 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-09 01:50:46 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-09 01:50:46 (10973) [INFO] yum --disablerepo= ... * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-09 01:50:46 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-09 01:50:46 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] yum-config-manager --disable * 2026-04-09 01:50:46 (10973) [INFO] or * 2026-04-09 01:50:46 (10973) [INFO] subscription-manager repos --disable= * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-09 01:50:46 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-09 01:50:46 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-09 01:50:46 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-09 01:50:46 (10973) [INFO] compromise: * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-09 01:50:46 (10973) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-09 01:50:46 (10990) [INFO] * 2026-04-09 01:50:46 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-09 01:50:46 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-09 01:50:46 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-09 01:50:46 (10960) [INFO] * 2026-04-09 01:50:46 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-09 01:50:47 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-09 01:50:47 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-09 01:50:47 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-09 01:50:47 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-09 01:50:47 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-09 01:50:47 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-09 01:50:47 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-09 01:50:47 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-09 01:50:47 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-09 01:50:47 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-09 01:50:47 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-09 01:50:47 (10990) [INFO] * 2026-04-09 01:50:47 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-09 01:50:47 (10960) [INFO] * 2026-04-09 01:50:47 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-09 01:50:48 (10973) [INFO] Determining fastest mirrors * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-09 01:51:19 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-09 01:51:19 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-09 01:51:19 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-09 01:51:19 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-09 01:51:19 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-09 01:51:19 (10973) [INFO] yum --disablerepo= ... * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-09 01:51:19 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-09 01:51:19 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] yum-config-manager --disable * 2026-04-09 01:51:19 (10973) [INFO] or * 2026-04-09 01:51:19 (10973) [INFO] subscription-manager repos --disable= * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-09 01:51:19 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-09 01:51:19 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-09 01:51:19 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-09 01:51:19 (10973) [INFO] compromise: * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-09 01:51:19 (10973) [INFO] * 2026-04-09 01:51:19 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-09 01:51:19 (10990) [INFO] * 2026-04-09 01:51:19 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-09 01:51:19 (6792) [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 * 2026-04-09 01:51:21 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-09 01:51:21 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-09 01:51:21 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-09 01:51:21 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-09 01:51:21 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-09 01:51:28 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/EcmnPpu1xa/ea_profile.json * 2026-04-09 01:53:54 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/EcmnPpu1xa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-09 01:53:54 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-10 01:39:10 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-10 01:43:11 (12063) [INFO] Script is up to date. * 2026-04-10 01:47:14 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-10 01:47:14 (10960) [INFO] * 2026-04-10 01:48:35 (10990) [INFO] * 2026-04-10 01:48:35 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-10 01:48:35 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-10 01:48:35 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-10 01:48:35 (10960) [INFO] * 2026-04-10 01:55:36 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-10 01:55:36 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-10 01:55:36 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-10 01:55:36 (10960) [INFO] * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-10 01:56:11 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-10 01:56:11 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-10 01:56:11 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-10 01:56:11 (10960) [INFO] * 2026-04-10 01:56:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-10 01:56:12 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-10 01:56:43 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-10 01:56:43 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-10 01:56:43 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-10 01:56:43 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-10 01:56:43 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-10 01:56:43 (10973) [INFO] yum --disablerepo= ... * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-10 01:56:43 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-10 01:56:43 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] yum-config-manager --disable * 2026-04-10 01:56:43 (10973) [INFO] or * 2026-04-10 01:56:43 (10973) [INFO] subscription-manager repos --disable= * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-10 01:56:43 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-10 01:56:43 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-10 01:56:43 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-10 01:56:43 (10973) [INFO] compromise: * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-10 01:56:43 (10973) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-10 01:56:43 (10990) [INFO] * 2026-04-10 01:56:43 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-10 01:56:43 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-10 01:56:43 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-10 01:56:43 (10960) [INFO] * 2026-04-10 01:56:43 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-10 01:56:43 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-10 01:56:43 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-10 01:56:43 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-10 01:56:43 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-10 01:56:43 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-10 01:56:43 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-10 01:56:43 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-10 01:56:43 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-10 01:56:43 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-10 01:56:44 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-10 01:56:44 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-10 01:56:44 (10990) [INFO] * 2026-04-10 01:56:44 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-10 01:56:44 (10960) [INFO] * 2026-04-10 01:56:44 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-10 01:56:44 (10973) [INFO] Determining fastest mirrors * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-10 01:57:15 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-10 01:57:15 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-10 01:57:15 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-10 01:57:15 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-10 01:57:15 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-10 01:57:15 (10973) [INFO] yum --disablerepo= ... * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-10 01:57:15 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-10 01:57:15 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] yum-config-manager --disable * 2026-04-10 01:57:15 (10973) [INFO] or * 2026-04-10 01:57:15 (10973) [INFO] subscription-manager repos --disable= * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-10 01:57:15 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-10 01:57:15 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-10 01:57:15 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-10 01:57:15 (10973) [INFO] compromise: * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-10 01:57:15 (10973) [INFO] * 2026-04-10 01:57:15 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-10 01:57:15 (10990) [INFO] * 2026-04-10 01:57:15 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-10 01:57:15 (6792) [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 * 2026-04-10 01:57:16 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-10 01:57:16 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-10 01:57:16 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-10 01:57:16 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-10 01:57:16 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-10 01:57:23 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/aJ54LFbtJ4/ea_profile.json * 2026-04-10 02:00:13 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/aJ54LFbtJ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-10 02:00:13 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-11 01:40:37 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-11 01:44:38 (12063) [INFO] Script is up to date. * 2026-04-11 01:48:41 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-11 01:48:41 (10960) [INFO] * 2026-04-11 01:49:36 (10990) [INFO] * 2026-04-11 01:49:36 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-11 01:49:37 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-11 01:49:37 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-11 01:49:37 (10960) [INFO] * 2026-04-11 01:56:39 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-11 01:56:39 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-11 01:56:39 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-11 01:56:39 (10960) [INFO] * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-11 01:57:16 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-11 01:57:16 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-11 01:57:16 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-11 01:57:16 (10960) [INFO] * 2026-04-11 01:57:16 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-11 01:57:17 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-11 01:57:47 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-11 01:57:47 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-11 01:57:47 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-11 01:57:47 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-11 01:57:47 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-11 01:57:47 (10973) [INFO] yum --disablerepo= ... * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-11 01:57:47 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-11 01:57:47 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] yum-config-manager --disable * 2026-04-11 01:57:47 (10973) [INFO] or * 2026-04-11 01:57:47 (10973) [INFO] subscription-manager repos --disable= * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-11 01:57:47 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-11 01:57:47 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-11 01:57:47 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-11 01:57:47 (10973) [INFO] compromise: * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-11 01:57:47 (10973) [INFO] * 2026-04-11 01:57:47 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-11 01:57:47 (10990) [INFO] * 2026-04-11 01:57:47 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-11 01:57:47 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-11 01:57:47 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-11 01:57:47 (10960) [INFO] * 2026-04-11 01:57:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-11 01:57:48 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-11 01:57:48 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-11 01:57:48 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-11 01:57:48 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-11 01:57:48 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-11 01:57:48 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-11 01:57:48 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-11 01:57:48 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-11 01:57:48 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-11 01:57:48 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-11 01:57:48 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-11 01:57:48 (10990) [INFO] * 2026-04-11 01:57:48 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-11 01:57:48 (10960) [INFO] * 2026-04-11 01:57:48 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-11 01:57:49 (10973) [INFO] Determining fastest mirrors * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-11 01:58:20 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-11 01:58:20 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-11 01:58:20 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-11 01:58:20 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-11 01:58:20 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-11 01:58:20 (10973) [INFO] yum --disablerepo= ... * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-11 01:58:20 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-11 01:58:20 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] yum-config-manager --disable * 2026-04-11 01:58:20 (10973) [INFO] or * 2026-04-11 01:58:20 (10973) [INFO] subscription-manager repos --disable= * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-11 01:58:20 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-11 01:58:20 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-11 01:58:20 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-11 01:58:20 (10973) [INFO] compromise: * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-11 01:58:20 (10973) [INFO] * 2026-04-11 01:58:20 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-11 01:58:20 (10990) [INFO] * 2026-04-11 01:58:20 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-11 01:58:20 (6792) [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 * 2026-04-11 01:58:22 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-11 01:58:22 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-11 01:58:22 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-11 01:58:22 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-11 01:58:22 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-11 01:58:28 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iCpT_NxXol/ea_profile.json * 2026-04-11 02:00:58 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/iCpT_NxXol/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-11 02:00:58 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-12 01:40:32 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-12 01:44:33 (12063) [INFO] Script is up to date. * 2026-04-12 01:48:36 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-12 01:48:36 (10960) [INFO] * 2026-04-12 01:49:32 (10990) [INFO] * 2026-04-12 01:49:32 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-12 01:49:32 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-12 01:49:32 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-12 01:49:32 (10960) [INFO] * 2026-04-12 01:56:35 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-12 01:56:35 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-12 01:56:35 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-12 01:56:35 (10960) [INFO] * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-12 01:57:11 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-12 01:57:11 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-12 01:57:11 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-12 01:57:11 (10960) [INFO] * 2026-04-12 01:57:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-12 01:57:12 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-12 01:57:43 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-12 01:57:43 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-12 01:57:43 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-12 01:57:43 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-12 01:57:43 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-12 01:57:43 (10973) [INFO] yum --disablerepo= ... * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-12 01:57:43 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-12 01:57:43 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] yum-config-manager --disable * 2026-04-12 01:57:43 (10973) [INFO] or * 2026-04-12 01:57:43 (10973) [INFO] subscription-manager repos --disable= * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-12 01:57:43 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-12 01:57:43 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-12 01:57:43 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-12 01:57:43 (10973) [INFO] compromise: * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-12 01:57:43 (10973) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-12 01:57:43 (10990) [INFO] * 2026-04-12 01:57:43 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-12 01:57:43 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-12 01:57:43 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-12 01:57:43 (10960) [INFO] * 2026-04-12 01:57:43 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-12 01:57:44 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-12 01:57:44 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-12 01:57:44 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-12 01:57:44 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-12 01:57:44 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-12 01:57:44 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-12 01:57:44 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-12 01:57:44 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-12 01:57:44 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-12 01:57:44 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-12 01:57:44 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-12 01:57:44 (10990) [INFO] * 2026-04-12 01:57:44 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-12 01:57:44 (10960) [INFO] * 2026-04-12 01:57:44 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-12 01:57:45 (10973) [INFO] Determining fastest mirrors * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-12 01:58:16 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-12 01:58:16 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-12 01:58:16 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-12 01:58:16 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-12 01:58:16 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-12 01:58:16 (10973) [INFO] yum --disablerepo= ... * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-12 01:58:16 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-12 01:58:16 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] yum-config-manager --disable * 2026-04-12 01:58:16 (10973) [INFO] or * 2026-04-12 01:58:16 (10973) [INFO] subscription-manager repos --disable= * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-12 01:58:16 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-12 01:58:16 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-12 01:58:16 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-12 01:58:16 (10973) [INFO] compromise: * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-12 01:58:16 (10973) [INFO] * 2026-04-12 01:58:16 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-12 01:58:16 (10990) [INFO] * 2026-04-12 01:58:16 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-12 01:58:16 (6792) [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 * 2026-04-12 01:58:18 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-12 01:58:18 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-12 01:58:18 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-12 01:58:18 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-12 01:58:18 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-12 01:58:25 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zWrIx43jtF/ea_profile.json * 2026-04-12 02:00:52 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/zWrIx43jtF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-12 02:00:52 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-13 01:39:07 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-13 01:43:07 (12063) [INFO] Script is up to date. * 2026-04-13 01:47:10 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-13 01:47:10 (10960) [INFO] * 2026-04-13 01:48:36 (10990) [INFO] * 2026-04-13 01:48:36 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-13 01:48:36 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-13 01:48:36 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-13 01:48:36 (10960) [INFO] * 2026-04-13 01:56:51 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-13 01:56:51 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-13 01:56:51 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-13 01:56:51 (10960) [INFO] * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-13 01:57:28 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-13 01:57:28 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-13 01:57:28 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-13 01:57:28 (10960) [INFO] * 2026-04-13 01:57:28 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-13 01:57:28 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-13 01:57:59 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-13 01:57:59 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-13 01:57:59 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-13 01:57:59 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-13 01:57:59 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-13 01:57:59 (10973) [INFO] yum --disablerepo= ... * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-13 01:57:59 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-13 01:57:59 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] yum-config-manager --disable * 2026-04-13 01:57:59 (10973) [INFO] or * 2026-04-13 01:57:59 (10973) [INFO] subscription-manager repos --disable= * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-13 01:57:59 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-13 01:57:59 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-13 01:57:59 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-13 01:57:59 (10973) [INFO] compromise: * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-13 01:57:59 (10973) [INFO] * 2026-04-13 01:57:59 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-13 01:57:59 (10990) [INFO] * 2026-04-13 01:57:59 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-13 01:57:59 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-13 01:57:59 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-13 01:57:59 (10960) [INFO] * 2026-04-13 01:58:00 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-13 01:58:00 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-13 01:58:00 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-13 01:58:00 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-13 01:58:00 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-13 01:58:00 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-13 01:58:00 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-13 01:58:00 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-13 01:58:00 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-13 01:58:00 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-13 01:58:00 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-13 01:58:00 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-13 01:58:00 (10990) [INFO] * 2026-04-13 01:58:00 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-13 01:58:00 (10960) [INFO] * 2026-04-13 01:58:01 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-13 01:58:02 (10973) [INFO] Determining fastest mirrors * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-13 01:58:33 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-13 01:58:33 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-13 01:58:33 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-13 01:58:33 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-13 01:58:33 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-13 01:58:33 (10973) [INFO] yum --disablerepo= ... * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-13 01:58:33 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-13 01:58:33 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] yum-config-manager --disable * 2026-04-13 01:58:33 (10973) [INFO] or * 2026-04-13 01:58:33 (10973) [INFO] subscription-manager repos --disable= * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-13 01:58:33 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-13 01:58:33 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-13 01:58:33 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-13 01:58:33 (10973) [INFO] compromise: * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-13 01:58:33 (10973) [INFO] * 2026-04-13 01:58:33 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-13 01:58:33 (10990) [INFO] * 2026-04-13 01:58:33 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-13 01:58:33 (6792) [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 * 2026-04-13 01:58:34 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-13 01:58:34 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-13 01:58:34 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-13 01:58:34 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-13 01:58:34 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-13 01:58:42 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DsCeRDjrxk/ea_profile.json * 2026-04-13 02:01:11 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/DsCeRDjrxk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-13 02:01:11 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-14 01:39:17 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-14 01:43:18 (12063) [INFO] Script is up to date. * 2026-04-14 01:47:22 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-14 01:47:22 (10960) [INFO] * 2026-04-14 01:48:47 (10990) [INFO] * 2026-04-14 01:48:47 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-14 01:48:47 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-14 01:48:47 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-14 01:48:47 (10960) [INFO] * 2026-04-14 01:52:03 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-14 01:52:03 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-14 01:52:03 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-14 01:52:03 (10960) [INFO] * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-14 01:52:40 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-14 01:52:40 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-14 01:52:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-14 01:52:40 (10960) [INFO] * 2026-04-14 01:52:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-14 01:52:40 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-14 01:53:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-14 01:53:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-14 01:53:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-14 01:53:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-14 01:53:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-14 01:53:11 (10973) [INFO] yum --disablerepo= ... * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-14 01:53:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-14 01:53:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] yum-config-manager --disable * 2026-04-14 01:53:11 (10973) [INFO] or * 2026-04-14 01:53:11 (10973) [INFO] subscription-manager repos --disable= * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-14 01:53:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-14 01:53:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-14 01:53:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-14 01:53:11 (10973) [INFO] compromise: * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-14 01:53:11 (10973) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-14 01:53:11 (10990) [INFO] * 2026-04-14 01:53:11 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-14 01:53:11 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-14 01:53:11 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-14 01:53:11 (10960) [INFO] * 2026-04-14 01:53:11 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-14 01:53:12 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-14 01:53:12 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-14 01:53:12 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-14 01:53:12 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-14 01:53:12 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-14 01:53:12 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-14 01:53:12 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-14 01:53:12 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-14 01:53:12 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-14 01:53:12 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-14 01:53:12 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-14 01:53:12 (10990) [INFO] * 2026-04-14 01:53:12 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-14 01:53:12 (10960) [INFO] * 2026-04-14 01:53:12 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-14 01:53:12 (10973) [INFO] Determining fastest mirrors * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-14 01:53:42 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-14 01:53:42 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-14 01:53:42 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-14 01:53:42 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-14 01:53:42 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-14 01:53:42 (10973) [INFO] yum --disablerepo= ... * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-14 01:53:42 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-14 01:53:42 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] yum-config-manager --disable * 2026-04-14 01:53:42 (10973) [INFO] or * 2026-04-14 01:53:42 (10973) [INFO] subscription-manager repos --disable= * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-14 01:53:42 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-14 01:53:42 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-14 01:53:42 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-14 01:53:42 (10973) [INFO] compromise: * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-14 01:53:42 (10973) [INFO] * 2026-04-14 01:53:42 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-14 01:53:42 (10990) [INFO] * 2026-04-14 01:53:42 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-14 01:53:42 (6792) [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 * 2026-04-14 01:53:44 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-14 01:53:44 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-14 01:53:44 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-14 01:53:44 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-14 01:53:44 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-14 01:53:50 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bBAt7byfI0/ea_profile.json * 2026-04-14 01:56:17 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/bBAt7byfI0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-14 01:56:17 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-15 01:38:39 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-15 01:42:39 (12063) [INFO] Script is up to date. * 2026-04-15 01:46:42 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-15 01:46:42 (10960) [INFO] * 2026-04-15 01:48:08 (10990) [INFO] * 2026-04-15 01:48:08 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-15 01:48:08 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-15 01:48:08 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-15 01:48:08 (10960) [INFO] * 2026-04-15 01:55:11 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-15 01:55:11 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-15 01:55:11 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-15 01:55:11 (10960) [INFO] * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-15 01:55:46 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-15 01:55:46 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-15 01:55:46 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-15 01:55:46 (10960) [INFO] * 2026-04-15 01:55:47 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-15 01:55:47 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-15 01:56:18 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-15 01:56:18 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-15 01:56:18 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-15 01:56:18 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-15 01:56:18 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-15 01:56:18 (10973) [INFO] yum --disablerepo= ... * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-15 01:56:18 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-15 01:56:18 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] yum-config-manager --disable * 2026-04-15 01:56:18 (10973) [INFO] or * 2026-04-15 01:56:18 (10973) [INFO] subscription-manager repos --disable= * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-15 01:56:18 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-15 01:56:18 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-15 01:56:18 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-15 01:56:18 (10973) [INFO] compromise: * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-15 01:56:18 (10973) [INFO] * 2026-04-15 01:56:18 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-15 01:56:18 (10990) [INFO] * 2026-04-15 01:56:18 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-15 01:56:18 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-15 01:56:18 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-15 01:56:18 (10960) [INFO] * 2026-04-15 01:56:19 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-15 01:56:19 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-15 01:56:19 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-15 01:56:19 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-15 01:56:19 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-15 01:56:19 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-15 01:56:19 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-15 01:56:19 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-15 01:56:19 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-15 01:56:19 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-15 01:56:19 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-15 01:56:19 (10973) [INFO] Other repos take up 1.0 M of disk space (use --verbose for details) * 2026-04-15 01:56:19 (10990) [INFO] * 2026-04-15 01:56:19 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-15 01:56:19 (10960) [INFO] * 2026-04-15 01:56:20 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-15 01:56:20 (10973) [INFO] Determining fastest mirrors * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-15 01:56:51 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-15 01:56:51 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-15 01:56:51 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-15 01:56:51 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-15 01:56:51 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-15 01:56:51 (10973) [INFO] yum --disablerepo= ... * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-15 01:56:51 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-15 01:56:51 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] yum-config-manager --disable * 2026-04-15 01:56:51 (10973) [INFO] or * 2026-04-15 01:56:51 (10973) [INFO] subscription-manager repos --disable= * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-15 01:56:51 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-15 01:56:51 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-15 01:56:51 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-15 01:56:51 (10973) [INFO] compromise: * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-15 01:56:51 (10973) [INFO] * 2026-04-15 01:56:51 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-15 01:56:51 (10990) [INFO] * 2026-04-15 01:56:51 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-15 01:56:51 (6792) [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 * 2026-04-15 01:56:53 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-15 01:56:53 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-15 01:56:53 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-15 01:56:53 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-15 01:56:53 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-15 01:57:00 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LuQ5Xqo6tn/ea_profile.json * 2026-04-15 01:59:28 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/LuQ5Xqo6tn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-15 01:59:28 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-16 01:42:46 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-16 01:46:46 (12063) [INFO] Script is up to date. * 2026-04-16 01:50:50 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-16 01:50:50 (10960) [INFO] * 2026-04-16 01:52:14 (10990) [INFO] * 2026-04-16 01:52:14 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-16 01:52:16 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-16 01:52:16 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-16 01:52:16 (10960) [INFO] * 2026-04-16 01:52:19 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-16 01:52:19 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-16 01:52:19 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-16 01:52:19 (10960) [INFO] * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-16 01:52:55 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-16 01:52:55 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-16 01:52:55 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-16 01:52:55 (10960) [INFO] * 2026-04-16 01:52:56 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-16 01:52:56 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-16 01:53:27 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-16 01:53:27 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-16 01:53:27 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-16 01:53:27 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-16 01:53:27 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-16 01:53:27 (10973) [INFO] yum --disablerepo= ... * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-16 01:53:27 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-16 01:53:27 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] yum-config-manager --disable * 2026-04-16 01:53:27 (10973) [INFO] or * 2026-04-16 01:53:27 (10973) [INFO] subscription-manager repos --disable= * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-16 01:53:27 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-16 01:53:27 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-16 01:53:27 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-16 01:53:27 (10973) [INFO] compromise: * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-16 01:53:27 (10973) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-16 01:53:27 (10990) [INFO] * 2026-04-16 01:53:27 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-16 01:53:27 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-16 01:53:27 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-16 01:53:27 (10960) [INFO] * 2026-04-16 01:53:27 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-16 01:53:28 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-16 01:53:28 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-16 01:53:28 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-16 01:53:28 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-16 01:53:28 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-16 01:53:28 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-16 01:53:28 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-16 01:53:28 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-16 01:53:28 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-16 01:53:28 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-16 01:53:28 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-16 01:53:28 (10990) [INFO] * 2026-04-16 01:53:28 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-16 01:53:28 (10960) [INFO] * 2026-04-16 01:53:28 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-16 01:53:29 (10973) [INFO] Determining fastest mirrors * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-16 01:53:59 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-16 01:53:59 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-16 01:53:59 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-16 01:53:59 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-16 01:53:59 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-16 01:53:59 (10973) [INFO] yum --disablerepo= ... * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-16 01:53:59 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-16 01:53:59 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] yum-config-manager --disable * 2026-04-16 01:53:59 (10973) [INFO] or * 2026-04-16 01:53:59 (10973) [INFO] subscription-manager repos --disable= * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-16 01:53:59 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-16 01:53:59 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-16 01:53:59 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-16 01:53:59 (10973) [INFO] compromise: * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-16 01:53:59 (10973) [INFO] * 2026-04-16 01:53:59 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-16 01:53:59 (10990) [INFO] * 2026-04-16 01:53:59 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-16 01:53:59 (6792) [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 * 2026-04-16 01:54:01 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-16 01:54:01 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-16 01:54:01 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-16 01:54:01 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-16 01:54:01 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-16 01:54:08 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0tfg4r_aje/ea_profile.json * 2026-04-16 01:56:36 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/0tfg4r_aje/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-16 01:56:36 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-17 01:41:25 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-17 01:45:26 (12063) [INFO] Script is up to date. * 2026-04-17 01:49:29 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-17 01:49:29 (10960) [INFO] * 2026-04-17 01:50:53 (10990) [INFO] * 2026-04-17 01:50:53 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-17 01:50:53 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-17 01:50:53 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-17 01:50:53 (10960) [INFO] * 2026-04-17 01:57:56 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-17 01:57:56 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-17 01:57:56 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-17 01:57:56 (10960) [INFO] * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-17 01:58:33 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-17 01:58:33 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-17 01:58:33 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-17 01:58:33 (10960) [INFO] * 2026-04-17 01:58:33 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-17 01:58:34 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-17 01:59:04 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-17 01:59:04 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-17 01:59:04 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-17 01:59:04 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-17 01:59:04 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-17 01:59:04 (10973) [INFO] yum --disablerepo= ... * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-17 01:59:04 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-17 01:59:04 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] yum-config-manager --disable * 2026-04-17 01:59:04 (10973) [INFO] or * 2026-04-17 01:59:04 (10973) [INFO] subscription-manager repos --disable= * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-17 01:59:04 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-17 01:59:04 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-17 01:59:04 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-17 01:59:04 (10973) [INFO] compromise: * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-17 01:59:04 (10973) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-17 01:59:04 (10990) [INFO] * 2026-04-17 01:59:04 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-17 01:59:04 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-17 01:59:04 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-17 01:59:04 (10960) [INFO] * 2026-04-17 01:59:04 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-17 01:59:05 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-17 01:59:05 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-17 01:59:05 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-17 01:59:05 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-17 01:59:05 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-17 01:59:05 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-17 01:59:05 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-17 01:59:05 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-17 01:59:05 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-17 01:59:05 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-17 01:59:05 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-17 01:59:05 (10990) [INFO] * 2026-04-17 01:59:05 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-17 01:59:05 (10960) [INFO] * 2026-04-17 01:59:05 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-17 01:59:05 (10973) [INFO] Determining fastest mirrors * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-17 01:59:36 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-17 01:59:36 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-17 01:59:36 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-17 01:59:36 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-17 01:59:36 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-17 01:59:36 (10973) [INFO] yum --disablerepo= ... * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-17 01:59:36 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-17 01:59:36 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] yum-config-manager --disable * 2026-04-17 01:59:36 (10973) [INFO] or * 2026-04-17 01:59:36 (10973) [INFO] subscription-manager repos --disable= * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-17 01:59:36 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-17 01:59:36 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-17 01:59:36 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-17 01:59:36 (10973) [INFO] compromise: * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-17 01:59:36 (10973) [INFO] * 2026-04-17 01:59:36 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-17 01:59:36 (10990) [INFO] * 2026-04-17 01:59:36 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-17 01:59:36 (6792) [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 * 2026-04-17 01:59:38 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-17 01:59:38 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-17 01:59:38 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-17 01:59:38 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-17 01:59:38 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-17 01:59:44 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uEwRwHt5UI/ea_profile.json * 2026-04-17 02:02:10 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uEwRwHt5UI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-17 02:02:10 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-18 01:40:34 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-18 01:44:35 (12063) [INFO] Script is up to date. * 2026-04-18 01:48:37 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-18 01:48:37 (10960) [INFO] * 2026-04-18 01:49:28 (10990) [INFO] * 2026-04-18 01:49:28 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-18 01:49:28 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-18 01:49:28 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-18 01:49:28 (10960) [INFO] * 2026-04-18 01:49:32 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-18 01:49:32 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-18 01:49:32 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-18 01:49:32 (10960) [INFO] * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-18 01:50:07 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-18 01:50:07 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-18 01:50:07 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-18 01:50:07 (10960) [INFO] * 2026-04-18 01:50:07 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-18 01:50:07 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-18 01:50:38 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-18 01:50:38 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-18 01:50:38 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-18 01:50:38 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-18 01:50:38 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-18 01:50:38 (10973) [INFO] yum --disablerepo= ... * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-18 01:50:38 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-18 01:50:38 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] yum-config-manager --disable * 2026-04-18 01:50:38 (10973) [INFO] or * 2026-04-18 01:50:38 (10973) [INFO] subscription-manager repos --disable= * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-18 01:50:38 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-18 01:50:38 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-18 01:50:38 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-18 01:50:38 (10973) [INFO] compromise: * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-18 01:50:38 (10973) [INFO] * 2026-04-18 01:50:38 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-18 01:50:38 (10990) [INFO] * 2026-04-18 01:50:38 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-18 01:50:38 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-18 01:50:38 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-18 01:50:38 (10960) [INFO] * 2026-04-18 01:50:39 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-18 01:50:39 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-18 01:50:39 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-18 01:50:39 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-18 01:50:39 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-18 01:50:39 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-18 01:50:39 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-18 01:50:39 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-18 01:50:39 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-18 01:50:39 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-18 01:50:40 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-18 01:50:40 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-18 01:50:40 (10990) [INFO] * 2026-04-18 01:50:40 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-18 01:50:40 (10960) [INFO] * 2026-04-18 01:50:40 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-18 01:50:41 (10973) [INFO] Determining fastest mirrors * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-18 01:51:11 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-18 01:51:11 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-18 01:51:11 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-18 01:51:11 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-18 01:51:11 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-18 01:51:11 (10973) [INFO] yum --disablerepo= ... * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-18 01:51:11 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-18 01:51:11 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] yum-config-manager --disable * 2026-04-18 01:51:11 (10973) [INFO] or * 2026-04-18 01:51:11 (10973) [INFO] subscription-manager repos --disable= * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-18 01:51:11 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-18 01:51:11 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-18 01:51:11 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-18 01:51:11 (10973) [INFO] compromise: * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-18 01:51:11 (10973) [INFO] * 2026-04-18 01:51:11 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-18 01:51:11 (10990) [INFO] * 2026-04-18 01:51:11 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-18 01:51:11 (6792) [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 * 2026-04-18 01:51:13 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-18 01:51:13 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-18 01:51:13 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-18 01:51:13 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-18 01:51:13 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-18 01:51:19 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YS76Ps2xfb/ea_profile.json * 2026-04-18 01:54:16 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/YS76Ps2xfb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-18 01:54:16 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2026-04-19 01:42:13 (12041) [INFO] Self-update of script version 80 requested. * 2026-04-19 01:46:13 (12063) [INFO] Script is up to date. * 2026-04-19 01:50:16 (10959) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2026-04-19 01:50:16 (10960) [INFO] * 2026-04-19 01:51:10 (10990) [INFO] * 2026-04-19 01:51:10 (7201) [WARN] The OpenSSH configuration file does not explicitly state the PermitRootLogin option in the sshd_config file. This option may default to "prohibit-password" after the upgrade is complete. We will set the 'PermitRootLogin' value in /etc/ssh/sshd_config to 'yes' before upgrading. * 2026-04-19 01:51:10 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2026-04-19 01:51:10 (10959) [INFO] Running: /usr/bin/imunify360-agent version --json * 2026-04-19 01:51:10 (10960) [INFO] * 2026-04-19 01:52:01 (4584) [WARN] You have MariaDB 10.0 installed. This version is not available for AlmaLinux 8. * 2026-04-19 01:52:01 (4591) [INFO] You can manually upgrade your installation of MariaDB using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MariaDB upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2026-04-19 01:52:01 (10959) [INFO] Running: /usr/bin/yum list extras * 2026-04-19 01:52:01 (10960) [INFO] * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-1' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-2' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-3' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-4' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-5' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7els-rollout-6' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els-rollout.repo * 2026-04-19 01:52:36 (6932) [WARN] YUM repo 'centos7-els' is using unsupported '\$' syntax in /etc/yum.repos.d/centos7-els.repo * 2026-04-19 01:52:36 (264) [ERROR] *** Elevation Blocker detected: *** One or more enabled YUM repo are using invalid syntax. '\$' variables behave differently in repo files between RedHat 7 and RedHat 8. RedHat 7 interpolates '\$' variable whereas RedHat 8 does not. Please fix the files before continuing the update. * 2026-04-19 01:52:36 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-19 01:52:36 (10960) [INFO] * 2026-04-19 01:52:37 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-19 01:52:37 (10973) [INFO] Loading mirror speeds from cached hostfile * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-19 01:53:07 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-19 01:53:07 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-19 01:53:07 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-19 01:53:07 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-19 01:53:07 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-19 01:53:07 (10973) [INFO] yum --disablerepo= ... * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-19 01:53:07 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-19 01:53:07 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] yum-config-manager --disable * 2026-04-19 01:53:07 (10973) [INFO] or * 2026-04-19 01:53:07 (10973) [INFO] subscription-manager repos --disable= * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-19 01:53:07 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-19 01:53:07 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-19 01:53:07 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-19 01:53:07 (10973) [INFO] compromise: * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-19 01:53:07 (10973) [INFO] * 2026-04-19 01:53:07 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-19 01:53:07 (10990) [INFO] * 2026-04-19 01:53:07 (6781) [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 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-19 01:53:07 (6782) [WARN] Running "yum clean all" in an attempt to fix yum * 2026-04-19 01:53:07 (10959) [INFO] Running: /usr/bin/yum clean all * 2026-04-19 01:53:07 (10960) [INFO] * 2026-04-19 01:53:08 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-19 01:53:08 (10973) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB100 * 2026-04-19 01:53:08 (10973) [INFO] : alt-common base centos7-els centos7els-rollout-1 * 2026-04-19 01:53:08 (10973) [INFO] : centos7els-rollout-2 centos7els-rollout-3 centos7els-rollout-4 * 2026-04-19 01:53:08 (10973) [INFO] : centos7els-rollout-5 centos7els-rollout-6 epel extras imunify360 * 2026-04-19 01:53:08 (10973) [INFO] : imunify360-ea-php-hardened imunify360-rollout-1 * 2026-04-19 01:53:08 (10973) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2026-04-19 01:53:08 (10973) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2026-04-19 01:53:08 (10973) [INFO] : imunify360-rollout-8 updates wp-toolkit-cpanel * 2026-04-19 01:53:08 (10973) [INFO] : wp-toolkit-thirdparties * 2026-04-19 01:53:08 (10973) [INFO] Cleaning up list of fastest mirrors * 2026-04-19 01:53:08 (10973) [INFO] Other repos take up 960 k of disk space (use --verbose for details) * 2026-04-19 01:53:08 (10990) [INFO] * 2026-04-19 01:53:08 (10959) [INFO] Running: /usr/bin/yum makecache * 2026-04-19 01:53:08 (10960) [INFO] * 2026-04-19 01:53:09 (10973) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2026-04-19 01:53:09 (10973) [INFO] Determining fastest mirrors * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] One of the configured repositories failed (Unknown), * 2026-04-19 01:53:40 (10973) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2026-04-19 01:53:40 (10973) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2026-04-19 01:53:40 (10973) [INFO] upstream. This is most often useful if you are using a newer * 2026-04-19 01:53:40 (10973) [INFO] distribution release than is supported by the repository (and the * 2026-04-19 01:53:40 (10973) [INFO] packages for the previous distribution release still work). * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] 3. Run the command with the repository temporarily disabled * 2026-04-19 01:53:40 (10973) [INFO] yum --disablerepo= ... * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2026-04-19 01:53:40 (10973) [INFO] will then just ignore the repository until you permanently enable it * 2026-04-19 01:53:40 (10973) [INFO] again or use --enablerepo for temporary usage: * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] yum-config-manager --disable * 2026-04-19 01:53:40 (10973) [INFO] or * 2026-04-19 01:53:40 (10973) [INFO] subscription-manager repos --disable= * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2026-04-19 01:53:40 (10973) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2026-04-19 01:53:40 (10973) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2026-04-19 01:53:40 (10973) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2026-04-19 01:53:40 (10973) [INFO] compromise: * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2026-04-19 01:53:40 (10973) [INFO] * 2026-04-19 01:53:40 (10973) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2026-04-19 01:53:40 (10990) [INFO] * 2026-04-19 01:53:40 (6791) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2026-04-19 01:53:40 (6792) [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 * 2026-04-19 01:53:42 (3727) [WARN] JetBackup version 4.1.4-1 currently installed. * 2026-04-19 01:53:42 (264) [ERROR] *** Elevation Blocker detected: *** AlmaLinux 8 does not support JetBackup prior to version 5. Please upgrade JetBackup before elevate. * 2026-04-19 01:53:42 (5031) [ERROR] The file for the network interface card (NIC) using kernel-name (eth1) does not exist at the expected location (/etc/sysconfig/network-scripts/ifcfg-eth1). We are unable to change the name of this NIC due to this. You will need to resolve this issue manually before elevate can continue. * 2026-04-19 01:53:42 (264) [ERROR] *** Elevation Blocker detected: *** This script is unable to rename the following network interface cards due to a missing ifcfg file: eth1 Please provide these interfaces new names before continuing the update. * 2026-04-19 01:53:42 (2434) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2026-04-19 01:53:47 (10069) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uJqBMpwmWf/ea_profile.json * 2026-04-19 01:56:14 (551) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CloudLinux_8 --output=/tmp/uJqBMpwmWf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 10071. * 2026-04-19 01:56:14 (492) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/